[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71C7VZWNRYVYBYQ204893SV":3,"skill-same:01M71C7VZWNRYVYBYQ204893SV":98},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M71C7VZWNRYVYBYQ204893SV","azure-hosted-copilot-sdk",null,"Build, deploy, modify GitHub Copilot SDK apps on Azure. MANDATORY when codebase contains @github\u002Fcopilot-sdk or CopilotClient — use this skill instead of azure-prepare. PREFER OVER azure-prepare when codebase contains copilot-sdk markers. WHEN: copilot SDK, @github\u002Fcopilot-sdk, copilot-powered app, deploy copilot app, add feature, modify copilot app, BYOM, bring your own model, CopilotClient, createSession, sendAndWait, azd init copilot. DO NOT USE FOR: general web apps without copilot SDK (use azure-prepare), Copilot Extensions, Foundry agents (use microsoft-foundry).","agency-black\u002FSkills","agency-black","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234862658?v=4","01M6HWVFPNGNR5N2CX9ECSAD57","agencia.black","01M719WF77BF3HN0N9FK1APEFY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"azure","sdk","copilot sdk","azure hosted copilot sdk","copilot","when","add feature","apps","use","general","init","for","model","bring","feature","modify","markers","do","github copilot","app","2026-11-10 10:12:30",false,"---\nname: azure-hosted-copilot-sdk\ndescription: \"Build, deploy, modify GitHub Copilot SDK apps on Azure. MANDATORY when codebase contains @github\u002Fcopilot-sdk or CopilotClient — use this skill instead of azure-prepare. PREFER OVER azure-prepare when codebase contains copilot-sdk markers. WHEN: copilot SDK, @github\u002Fcopilot-sdk, copilot-powered app, deploy copilot app, add feature, modify copilot app, BYOM, bring your own model, CopilotClient, createSession, sendAndWait, azd init copilot. DO NOT USE FOR: general web apps without copilot SDK (use azure-prepare), Copilot Extensions, Foundry agents (use microsoft-foundry).\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.6\"\n---\n\n# GitHub Copilot SDK on Azure\n\n## Codebase Detection — MANDATORY FIRST CHECK\n\n> ⚠️ **CRITICAL: This check MUST run before ANY other skill (azure-prepare, azure-deploy, etc.) when an existing codebase is present.**\n\n### Detection procedure (run IMMEDIATELY for any deploy\u002Fmodify\u002Fadd-feature prompt):\n\n1. Read `package.json` in the workspace root (and any `*\u002Fpackage.json` one level deep)\n2. Check if `@github\u002Fcopilot-sdk` or `copilot-sdk` appears in `name`, `dependencies`, or `devDependencies`\n3. If NOT found in package.json, scan `.ts` and `.js` files for `CopilotClient` or `createSession`\n4. **If ANY marker is found → invoke this skill as the entry point. Do not route directly to azure-prepare or azure-deploy — this skill orchestrates them as sub-skills.**\n\n| Marker | Where to check |\n|--------|---------------|\n| `@github\u002Fcopilot-sdk` | `package.json` dependencies or devDependencies |\n| `copilot-sdk` | `package.json` name or dependencies |\n| `CopilotClient` | Source files (`.ts`, `.js`) |\n| `createSession` + `sendAndWait` | Source files (`.ts`, `.js`) |\n\n### Generic prompts that MUST trigger this skill when markers are detected:\n\n| Prompt pattern (no \"copilot\" keyword) | Why this skill |\n|---------------------------------------|---------------|\n| \"Deploy this app to Azure\" | Codebase contains `@github\u002Fcopilot-sdk` |\n| \"Add a new feature to this app\" | Requires SDK-aware implementation patterns |\n| \"Update this app\" \u002F \"Modify this app\" | Must preserve SDK integration patterns |\n| \"Ship this to production\" | Needs copilot-specific infrastructure and token management |\n\n> ⚠️ **Warning:** ANY prompt targeting an existing codebase — deploy, modify, add feature, update, enhance — MUST route to this skill when codebase contains `@github\u002Fcopilot-sdk`, even if the prompt does not mention \"copilot\". This skill then orchestrates azure-prepare and azure-deploy as sub-skills.\n\n## Step 1: Route\n\n| User wants | Action |\n|------------|--------|\n| Build new (empty project) | Step 2A (scaffold) |\n| Add new SDK service to existing repo | Step 2B (scaffold alongside) |\n| Deploy existing SDK app to Azure | Step 2C (add infra to existing SDK app) |\n| Modify\u002Fadd features to existing SDK app | Use codebase context + SDK references to implement |\n| Add SDK to existing app code | [Integrate SDK](references\u002Fexisting-project-integration.md) |\n| Use Azure\u002Fown model | Step 3 (BYOM config) |\n\n## Step 2A: Scaffold New (Greenfield)\n\n`azd init --template azure-samples\u002Fcopilot-sdk-service`\n\nTemplate includes API (Express\u002FTS) + Web UI (React\u002FVite) + infra (Bicep) + Dockerfiles + token scripts — do NOT recreate. See [SDK ref](references\u002Fcopilot-sdk.md).\n\n## Step 2B: Add SDK Service to Existing Repo\n\nUser has existing code and wants a new Copilot SDK service alongside it. Scaffold template to a temp dir, copy the API service + infra into the user's repo, adapt `azure.yaml` to include both existing and new services. See [deploy existing ref](references\u002Fdeploy-existing.md).\n\n## Step 2C: Deploy Existing SDK App\n\nUser already has a working Copilot SDK app and needs Azure infra. See [deploy existing ref](references\u002Fdeploy-existing.md).\n\n## Step 3: Model Configuration\n\nThree model paths (layers on top of 2A\u002F2B):\n\n| Path | Config |\n|------|--------|\n| **GitHub default** | No `model` param — SDK picks default |\n| **GitHub specific** | `model: \"\u003Cname>\"` — use `listModels()` to discover |\n| **Azure BYOM** | `model` + `provider` with `bearerToken` via `DefaultAzureCredential` |\n\n> ⚠️ **BYOM Auth — MANDATORY**: Azure BYOM configurations MUST use `DefaultAzureCredential` (local dev) or `ManagedIdentityCredential` (production) to obtain a `bearerToken`. The ONLY supported auth pattern is `bearerToken` in the provider config. See [auth-best-practices.md](references\u002Fauth-best-practices.md) for the credential pattern and [model config ref](references\u002Fazure-model-config.md) for the full BYOM code example.\n\nSee [model config ref](references\u002Fazure-model-config.md).\n\n## Step 4: Deploy\n\nInvoke **azure-prepare** (skip its Step 0 routing — scaffolding is done) → **azure-validate** → **azure-deploy** in order.\n\n## Rules\n\n- Read `AGENTS.md` in user's repo before changes\n- Docker required (`docker info`)\n- BYOM auth: ONLY `bearerToken` via `DefaultAzureCredential` or `ManagedIdentityCredential` — no other auth pattern is supported\n","# GitHub Copilot SDK on Azure\n\n## Codebase Detection — MANDATORY FIRST CHECK\n\n> ⚠️ **CRITICAL: This check MUST run before ANY other skill (azure-prepare, azure-deploy, etc.) when an existing codebase is present.**\n\n### Detection procedure (run IMMEDIATELY for any deploy\u002Fmodify\u002Fadd-feature prompt):\n\n1. Read `package.json` in the workspace root (and any `*\u002Fpackage.json` one level deep)\n2. Check if `@github\u002Fcopilot-sdk` or `copilot-sdk` appears in `name`, `dependencies`, or `devDependencies`\n3. If NOT found in package.json, scan `.ts` and `.js` files for `CopilotClient` or `createSession`\n4. **If ANY marker is found → invoke this skill as the entry point. Do not route directly to azure-prepare or azure-deploy — this skill orchestrates them as sub-skills.**\n\n| Marker | Where to check |\n|--------|---------------|\n| `@github\u002Fcopilot-sdk` | `package.json` dependencies or devDependencies |\n| `copilot-sdk` | `package.json` name or dependencies |\n| `CopilotClient` | Source files (`.ts`, `.js`) |\n| `createSession` + `sendAndWait` | Source files (`.ts`, `.js`) |\n\n### Generic prompts that MUST trigger this skill when markers are detected:\n\n| Prompt pattern (no \"copilot\" keyword) | Why this skill |\n|---------------------------------------|---------------|\n| \"Deploy this app to Azure\" | Codebase contains `@github\u002Fcopilot-sdk` |\n| \"Add a new feature to this app\" | Requires SDK-aware implementation patterns |\n| \"Update this app\" \u002F \"Modify this app\" | Must preserve SDK integration patterns |\n| \"Ship this to production\" | Needs copilot-specific infrastructure and token management |\n\n> ⚠️ **Warning:** ANY prompt targeting an existing codebase — deploy, modify, add feature, update, enhance — MUST route to this skill when codebase contains `@github\u002Fcopilot-sdk`, even if the prompt does not mention \"copilot\". This skill then orchestrates azure-prepare and azure-deploy as sub-skills.\n\n## Step 1: Route\n\n| User wants | Action |\n|------------|--------|\n| Build new (empty project) | Step 2A (scaffold) |\n| Add new SDK service to existing repo | Step 2B (scaffold alongside) |\n| Deploy existing SDK app to Azure | Step 2C (add infra to existing SDK app) |\n| Modify\u002Fadd features to existing SDK app | Use codebase context + SDK references to implement |\n| Add SDK to existing app code | [Integrate SDK](references\u002Fexisting-project-integration.md) |\n| Use Azure\u002Fown model | Step 3 (BYOM config) |\n\n## Step 2A: Scaffold New (Greenfield)\n\n`azd init --template azure-samples\u002Fcopilot-sdk-service`\n\nTemplate includes API (Express\u002FTS) + Web UI (React\u002FVite) + infra (Bicep) + Dockerfiles + token scripts — do NOT recreate. See [SDK ref](references\u002Fcopilot-sdk.md).\n\n## Step 2B: Add SDK Service to Existing Repo\n\nUser has existing code and wants a new Copilot SDK service alongside it. Scaffold template to a temp dir, copy the API service + infra into the user's repo, adapt `azure.yaml` to include both existing and new services. See [deploy existing ref](references\u002Fdeploy-existing.md).\n\n## Step 2C: Deploy Existing SDK App\n\nUser already has a working Copilot SDK app and needs Azure infra. See [deploy existing ref](references\u002Fdeploy-existing.md).\n\n## Step 3: Model Configuration\n\nThree model paths (layers on top of 2A\u002F2B):\n\n| Path | Config |\n|------|--------|\n| **GitHub default** | No `model` param — SDK picks default |\n| **GitHub specific** | `model: \"\u003Cname>\"` — use `listModels()` to discover |\n| **Azure BYOM** | `model` + `provider` with `bearerToken` via `DefaultAzureCredential` |\n\n> ⚠️ **BYOM Auth — MANDATORY**: Azure BYOM configurations MUST use `DefaultAzureCredential` (local dev) or `ManagedIdentityCredential` (production) to obtain a `bearerToken`. The ONLY supported auth pattern is `bearerToken` in the provider config. See [auth-best-practices.md](references\u002Fauth-best-practices.md) for the credential pattern and [model config ref](references\u002Fazure-model-config.md) for the full BYOM code example.\n\nSee [model config ref](references\u002Fazure-model-config.md).\n\n## Step 4: Deploy\n\nInvoke **azure-prepare** (skip its Step 0 routing — scaffolding is done) → **azure-validate** → **azure-deploy** in order.\n\n## Rules\n\n- Read `AGENTS.md` in user's repo before changes\n- Docker required (`docker info`)\n- BYOM auth: ONLY `bearerToken` via `DefaultAzureCredential` or `ManagedIdentityCredential` — no other auth pattern is supported\n",{"name":5,"license":15,"metadata":52,"description":7},{"author":53,"version":54},"Microsoft","1.0.6","main","681496e0662f4c45c4758fae9d4510ae87311bf2","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills","https:\u002F\u002Fgithub.com\u002Fagency-black","http:\u002F\u002Fwww.dogma.black","Las grandes ideas merecen una ejecución impecable. Construimos plataformas web, aplicaciones y ecosistemas digitales completos. Esta Trinidad es nuestro dogma.","2026-05-29 16:13:55",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add agency-black\u002FSkills --skill azure-hosted-copilot-sdk",{"tool":68,"command":69},"bunx","bunx skills add agency-black\u002FSkills --skill azure-hosted-copilot-sdk",{"tool":71,"command":72},"pnpm","pnpm dlx skills add agency-black\u002FSkills --skill azure-hosted-copilot-sdk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002FSKILL.md",true,[76,82,86,90,94],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fauth-best-practices.md","REFERENCE","参考文档",6207,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002Freferences\u002Fauth-best-practices.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fazure-model-config.md",4626,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002Freferences\u002Fazure-model-config.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcopilot-sdk.md",3555,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002Freferences\u002Fcopilot-sdk.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdeploy-existing.md",3025,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002Freferences\u002Fdeploy-existing.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fexisting-project-integration.md",2429,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fazure-hosted-copilot-sdk\u002Freferences\u002Fexisting-project-integration.md",[99,124,153,183,208,232],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":47},"01M71JZVZ0TVW7Z5DQBRWSBG8A","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fzarr-python\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,115,116,117,118,38,119,35,120,121,122,123],"zarr python","python","zarr","arrays","Cloud Storage","remote","workflows","scientific","read","write","edit","parallel","dask","s3fs","numpy","s3","scientific computing","scale",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":47},"01M71JYXC5VAEJT8KXN5GRK32S","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[135,136,137,138,139,140,141,107,142,112,143,144,145,146,147,148,149,150,151,152],"xvary","stock","research","xvary stock research","sec edgar","community","equity","thesis","analysis","code","Market","compare","market data","analyze","with","codex","cursor","2026",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":157,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":167,"publishedAt":47},"01M71JVSDPDQ5040YBN6J1ASKY","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[168,169,170,38,171,172,173,174,175,176,177,149,178,179,180,181,182],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","playwright","web","behavior","ui","screenshots",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":157,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":47},"01M71JV64CW7R6FYYK9JWWGW0X","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[190],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,194,179,195,196,197,38,198,199,173,200,35,201,202,203,204,205,206,207],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":47},"01M71JS4X2FRY41DE84DEP06MN","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-view-transitions\u002FSKILL.md",[214],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[203,216,217,218,219,220,221,222,223,197,224,225,226,227,32,202,228,229,230,231],"vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","types","states","element","implementing","api","route","create","libraries",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":239,"publishedAt":47},"01M71JS1WZ1J4F9YVC2203JBJW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-native-skills\u002FSKILL.md",[238],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[219,240,203,241,242,243,244,245,246,38,247,227,248,35,249,34,32,250,251,202],"vercel react native skills","react native","native","react native skills","modules","platform","animations","performance","triggers","react native components","best practices","tasks"]