[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K1MH68SPHTW8S84XXMMZVG":3,"skill-same:01M6K1MH68SPHTW8S84XXMMZVG":133},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":110,"commitSha":111,"skillDirectory":112,"forksCount":113,"repositoryHtmlUrl":114,"repositoryHomepageUrl":6,"ownerHtmlUrl":115,"ownerBlogUrl":116,"ownerDescription":117,"updatedAt":118,"install":119,"resources":132},"01M6K1MH68SPHTW8S84XXMMZVG","bootstrap",null,"Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db\u002Fdev commands happen in the correct safe order.","NagyVikt\u002Fcodex-plugins","NagyVikt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F137165288?v=4","01M6K0SJ3R2DAZRJKJJS10VN87","Viktor Nagy","01M6K0SJ9HXN0GBD91QDQ9WNVV",2,"MIT","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fbootstrap\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"dev commands","Variables","URL","upstash","resources","db","neon","prisma","project","local","safe","clerk","bcp","getting started","migrate","run","generate","repos","config","2026-11-10 10:12:30",false,"---\nname: bootstrap\ndescription: Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db\u002Fdev commands happen in the correct safe order.\nmetadata:\n  priority: 8\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fgetting-started-with-vercel\"\n    - \"https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fgetting-started\u002Finstallation\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml\"\n  pathPatterns:\n    - '.env.example'\n    - '.env.sample'\n    - '.env.template'\n    - 'README*'\n    - 'docs\u002F**\u002Fsetup*'\n    - 'package.json'\n    - 'drizzle.config.*'\n    - 'prisma\u002Fschema.prisma'\n    - 'auth.*'\n    - 'src\u002F**\u002Fauth.*'\n  bashPatterns:\n    - '\\\\bcp\\\\s+\\\\.env\\\\.(?:example|sample|template)\\\\s+\\\\.env\\\\.local\\\\b'\n    - '\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+db:(?:push|seed|migrate|generate)\\\\b'\n    - '\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+dev\\\\b'\n    - '\\\\bvercel\\\\s+link\\\\b'\n    - '\\\\bvercel\\\\s+integration\\\\s+(?:add|install)\\\\b'\n    - '\\\\bvercel\\\\s+env\\\\s+pull\\\\b'\n  importPatterns:\n    - '@neondatabase\u002Fserverless'\n    - 'drizzle-orm'\n    - '@upstash\u002Fredis'\n    - '@vercel\u002Fblob'\n    - '@vercel\u002Fedge-config'\n    - 'next-auth'\n    - '@auth\u002Fcore'\n    - 'better-auth'\nchainTo:\n  -\n    pattern: '@vercel\u002F(postgres|kv)|\\b(KV_REST_API_URL|POSTGRES_URL)\\b'\n    targetSkill: vercel-storage\n    message: '@vercel\u002Fpostgres and @vercel\u002Fkv are sunset — loading Vercel Storage guidance for Neon and Upstash migration.'\n  -\n    pattern: 'from\\s+[''\"\"](next-auth|@auth\u002Fcore|@clerk\u002Fnextjs|better-auth)[''\"\"]'\n    targetSkill: auth\n    message: 'Auth library detected during bootstrap — loading Auth guidance for Clerk Marketplace setup and middleware patterns.'\n  -\n    pattern: 'OPENAI_API_KEY|ANTHROPIC_API_KEY|AI_GATEWAY'\n    targetSkill: env-vars\n    message: 'AI provider env vars detected — loading Environment Variables guidance for OIDC-based auth via vercel env pull.'\n    skipIfFileContains: 'VERCEL_OIDC|vercel env pull'\nretrieval:\n  aliases:\n    - project setup\n    - repo init\n    - getting started\n    - scaffold\n  intents:\n    - set up project\n    - initialize repo\n    - link vercel project\n    - pull env vars\n  entities:\n    - vercel link\n    - env pull\n    - database setup\n    - first run\n\n---\n\n# Project Bootstrap Orchestrator\n\nExecute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete.\n\n## Rules\n\n- Do not run `db:push`, `db:migrate`, `db:seed`, or `dev` until Vercel linking is complete and env keys are verified.\n- Prefer Vercel-managed provisioning (`vercel integration ...`) for shared resources.\n- Use provider CLIs only as fallback when Vercel integration flow is unavailable.\n- Never echo secret values in terminal output, logs, or summaries.\n\n## Preflight\n\n1. Confirm Vercel CLI is installed and authenticated.\n\n```bash\nvercel --version\nvercel whoami\n```\n\n2. Confirm repo linkage by checking `.vercel\u002Fproject.json`.\n3. If not linked, inspect available teams\u002Fprojects before asking the user to choose:\n\n```bash\nvercel teams ls\nvercel projects ls --scope \u003Cteam>\nvercel link --yes --scope \u003Cteam> --project \u003Cproject>\n```\n\n4. Find the env template in priority order: `.env.example`, `.env.sample`, `.env.template`.\n5. Create local env file if missing:\n\n```bash\ncp .env.example .env.local\n```\n\n## Resource Setup: Postgres\n\n### Preferred path (Vercel-managed Neon)\n\n1. Read integration setup guidance:\n\n```bash\nvercel integration guide neon\n```\n\n2. Add Neon integration to the Vercel scope:\n\n```bash\nvercel integration add neon --scope \u003Cteam>\n```\n\n3. Verify expected environment variable names exist in Vercel and pull locally:\n\n```bash\nvercel env ls\nvercel env pull .env.local --yes\n```\n\n### Fallback path 1 (Dashboard)\n\n1. Provision Neon through the Vercel dashboard integration UI.\n2. Re-run `vercel env pull .env.local --yes`.\n\n### Fallback path 2 (Neon CLI)\n\nUse Neon CLI only when Vercel-managed provisioning is unavailable. After creating resources, add required env vars in Vercel and pull again.\n\n## AUTH_SECRET Generation\n\nGenerate a high-entropy secret without printing it, then store it in Vercel and refresh local env:\n\n```bash\nAUTH_SECRET=\"$(node -e \"console.log(require('node:crypto').randomBytes(32).toString('base64url'))\")\"\nprintf \"%s\" \"$AUTH_SECRET\" | vercel env add AUTH_SECRET development preview production\nunset AUTH_SECRET\nvercel env pull .env.local --yes\n```\n\n## Env Verification\n\nCompare required keys from template file against `.env.local` keys (names only, never values):\n\n```bash\ntemplate_file=\"\"\nfor candidate in .env.example .env.sample .env.template; do\n  if [ -f \"$candidate\" ]; then\n    template_file=\"$candidate\"\n    break\n  fi\ndone\n\ncomm -23 \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' \"$template_file\" | cut -d '=' -f 1 | sort -u) \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' .env.local | cut -d '=' -f 1 | sort -u)\n```\n\nProceed only when missing key list is empty.\n\n## App Setup\n\nAfter linkage + env verification:\n\n```bash\nnpm run db:push\nnpm run db:seed\nnpm run dev\n```\n\nUse the repository package manager (`npm`, `pnpm`, `bun`, or `yarn`) and run only scripts that exist in `package.json`.\n\n## UI Baseline for Next.js + shadcn Projects\n\nAfter linkage and env verification, establish the UI foundation before feature work:\n1. Add a baseline primitive set: `npx shadcn@latest add button card input label textarea select switch tabs dialog alert-dialog sheet dropdown-menu badge separator skeleton table`\n2. Apply the Geist font fix in `layout.tsx` and `globals.css`.\n3. Confirm the app shell uses `bg-background text-foreground`.\n4. Default to dark mode for product, admin, and AI apps unless the repo is clearly marketing-first.\n\n## Bootstrap Verification\n\nConfirm each checkpoint:\n\n- `vercel whoami` succeeds.\n- `.vercel\u002Fproject.json` exists and matches chosen project.\n- Postgres integration path completed (Vercel integration, dashboard, or provider CLI fallback).\n- `vercel env pull .env.local --yes` succeeds.\n- Required env key diff is empty.\n- Database command status is recorded (`db:push`, `db:seed`, `db:migrate`, `db:generate` as applicable).\n- `dev` command starts without immediate config\u002Fauth\u002Fenv failure.\n\nIf verification fails, stop and report exact failing step plus remediation.\n\n## Summary Format\n\nReturn a final bootstrap summary in this format:\n\n```md\n## Bootstrap Result\n- **Linked Project**: \u003Cteam>\u002F\u003Cproject>\n- **Resource Path**: vercel-integration-neon | dashboard-neon | neon-cli\n- **Env Keys**: \u003Ccount> required, \u003Ccount> present, \u003Ccount> missing\n- **Secrets**: AUTH_SECRET set in Vercel (value never shown)\n- **Migration Status**: not-run | success | failed (\u003Cstep>)\n- **Dev Result**: not-run | started | failed\n```\n\n## Bootstrap Next Steps\n\n- If env keys are still missing, add the missing keys in Vercel and re-run `vercel env pull .env.local --yes`.\n- If DB commands fail, fix connectivity\u002Fschema issues and re-run only the failed db step.\n- If `dev` fails, resolve runtime errors, then restart with your package manager's `run dev`.\n\n## next-forge Projects\n\nIf the project was scaffolded with `npx next-forge init` (detected by `pnpm-workspace.yaml` + `packages\u002Fauth` + `packages\u002Fdatabase` + `@repo\u002F*` imports):\n\n1. Env files are per-app (`apps\u002Fapp\u002F.env.local`, `apps\u002Fweb\u002F.env.local`, `apps\u002Fapi\u002F.env.local`) plus `packages\u002Fdatabase\u002F.env`.\n2. Run `pnpm migrate` (not `db:push`) — it runs `prisma format` + `prisma generate` + `prisma db push`.\n3. Minimum env vars: `DATABASE_URL`, `CLERK_SECRET_KEY`, `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY`, `NEXT_PUBLIC_APP_URL`, `NEXT_PUBLIC_WEB_URL`, `NEXT_PUBLIC_API_URL`.\n4. Optional services (Stripe, Resend, PostHog, etc.) can be skipped initially — but remove their `@repo\u002F*` imports from app `env.ts` files to avoid validation errors.\n5. Deploy as 3 separate Vercel projects with root directories `apps\u002Fapp`, `apps\u002Fapi`, `apps\u002Fweb`.\n\n=> skill: next-forge — Full next-forge monorepo guide\n","# Project Bootstrap Orchestrator\n\nExecute bootstrap in strict order. Do not run migrations or development server until project linking and environment verification are complete.\n\n## Rules\n\n- Do not run `db:push`, `db:migrate`, `db:seed`, or `dev` until Vercel linking is complete and env keys are verified.\n- Prefer Vercel-managed provisioning (`vercel integration ...`) for shared resources.\n- Use provider CLIs only as fallback when Vercel integration flow is unavailable.\n- Never echo secret values in terminal output, logs, or summaries.\n\n## Preflight\n\n1. Confirm Vercel CLI is installed and authenticated.\n\n```bash\nvercel --version\nvercel whoami\n```\n\n2. Confirm repo linkage by checking `.vercel\u002Fproject.json`.\n3. If not linked, inspect available teams\u002Fprojects before asking the user to choose:\n\n```bash\nvercel teams ls\nvercel projects ls --scope \u003Cteam>\nvercel link --yes --scope \u003Cteam> --project \u003Cproject>\n```\n\n4. Find the env template in priority order: `.env.example`, `.env.sample`, `.env.template`.\n5. Create local env file if missing:\n\n```bash\ncp .env.example .env.local\n```\n\n## Resource Setup: Postgres\n\n### Preferred path (Vercel-managed Neon)\n\n1. Read integration setup guidance:\n\n```bash\nvercel integration guide neon\n```\n\n2. Add Neon integration to the Vercel scope:\n\n```bash\nvercel integration add neon --scope \u003Cteam>\n```\n\n3. Verify expected environment variable names exist in Vercel and pull locally:\n\n```bash\nvercel env ls\nvercel env pull .env.local --yes\n```\n\n### Fallback path 1 (Dashboard)\n\n1. Provision Neon through the Vercel dashboard integration UI.\n2. Re-run `vercel env pull .env.local --yes`.\n\n### Fallback path 2 (Neon CLI)\n\nUse Neon CLI only when Vercel-managed provisioning is unavailable. After creating resources, add required env vars in Vercel and pull again.\n\n## AUTH_SECRET Generation\n\nGenerate a high-entropy secret without printing it, then store it in Vercel and refresh local env:\n\n```bash\nAUTH_SECRET=\"$(node -e \"console.log(require('node:crypto').randomBytes(32).toString('base64url'))\")\"\nprintf \"%s\" \"$AUTH_SECRET\" | vercel env add AUTH_SECRET development preview production\nunset AUTH_SECRET\nvercel env pull .env.local --yes\n```\n\n## Env Verification\n\nCompare required keys from template file against `.env.local` keys (names only, never values):\n\n```bash\ntemplate_file=\"\"\nfor candidate in .env.example .env.sample .env.template; do\n  if [ -f \"$candidate\" ]; then\n    template_file=\"$candidate\"\n    break\n  fi\ndone\n\ncomm -23 \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' \"$template_file\" | cut -d '=' -f 1 | sort -u) \\\n  \u003C(grep -E '^[A-Za-z_][A-Za-z0-9_]*=' .env.local | cut -d '=' -f 1 | sort -u)\n```\n\nProceed only when missing key list is empty.\n\n## App Setup\n\nAfter linkage + env verification:\n\n```bash\nnpm run db:push\nnpm run db:seed\nnpm run dev\n```\n\nUse the repository package manager (`npm`, `pnpm`, `bun`, or `yarn`) and run only scripts that exist in `package.json`.\n\n## UI Baseline for Next.js + shadcn Projects\n\nAfter linkage and env verification, establish the UI foundation before feature work:\n1. Add a baseline primitive set: `npx shadcn@latest add button card input label textarea select switch tabs dialog alert-dialog sheet dropdown-menu badge separator skeleton table`\n2. Apply the Geist font fix in `layout.tsx` and `globals.css`.\n3. Confirm the app shell uses `bg-background text-foreground`.\n4. Default to dark mode for product, admin, and AI apps unless the repo is clearly marketing-first.\n\n## Bootstrap Verification\n\nConfirm each checkpoint:\n\n- `vercel whoami` succeeds.\n- `.vercel\u002Fproject.json` exists and matches chosen project.\n- Postgres integration path completed (Vercel integration, dashboard, or provider CLI fallback).\n- `vercel env pull .env.local --yes` succeeds.\n- Required env key diff is empty.\n- Database command status is recorded (`db:push`, `db:seed`, `db:migrate`, `db:generate` as applicable).\n- `dev` command starts without immediate config\u002Fauth\u002Fenv failure.\n\nIf verification fails, stop and report exact failing step plus remediation.\n\n## Summary Format\n\nReturn a final bootstrap summary in this format:\n\n```md\n## Bootstrap Result\n- **Linked Project**: \u003Cteam>\u002F\u003Cproject>\n- **Resource Path**: vercel-integration-neon | dashboard-neon | neon-cli\n- **Env Keys**: \u003Ccount> required, \u003Ccount> present, \u003Ccount> missing\n- **Secrets**: AUTH_SECRET set in Vercel (value never shown)\n- **Migration Status**: not-run | success | failed (\u003Cstep>)\n- **Dev Result**: not-run | started | failed\n```\n\n## Bootstrap Next Steps\n\n- If env keys are still missing, add the missing keys in Vercel and re-run `vercel env pull .env.local --yes`.\n- If DB commands fail, fix connectivity\u002Fschema issues and re-run only the failed db step.\n- If `dev` fails, resolve runtime errors, then restart with your package manager's `run dev`.\n\n## next-forge Projects\n\nIf the project was scaffolded with `npx next-forge init` (detected by `pnpm-workspace.yaml` + `packages\u002Fauth` + `packages\u002Fdatabase` + `@repo\u002F*` imports):\n\n1. Env files are per-app (`apps\u002Fapp\u002F.env.local`, `apps\u002Fweb\u002F.env.local`, `apps\u002Fapi\u002F.env.local`) plus `packages\u002Fdatabase\u002F.env`.\n2. Run `pnpm migrate` (not `db:push`) — it runs `prisma format` + `prisma generate` + `prisma db push`.\n3. Minimum env vars: `DATABASE_URL`, `CLERK_SECRET_KEY`, `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY`, `NEXT_PUBLIC_APP_URL`, `NEXT_PUBLIC_WEB_URL`, `NEXT_PUBLIC_API_URL`.\n4. Optional services (Stripe, Resend, PostHog, etc.) can be skipped initially — but remove their `@repo\u002F*` imports from app `env.ts` files to avoid validation errors.\n5. Deploy as 3 separate Vercel projects with root directories `apps\u002Fapp`, `apps\u002Fapi`, `apps\u002Fweb`.\n\n=> skill: next-forge — Full next-forge monorepo guide\n",{"name":5,"chainTo":48,"metadata":62,"retrieval":95,"description":7},[49,53,57],{"message":50,"pattern":51,"targetSkill":52},"@vercel\u002Fpostgres and @vercel\u002Fkv are sunset — loading Vercel Storage guidance for Neon and Upstash migration.","@vercel\u002F(postgres|kv)|\\b(KV_REST_API_URL|POSTGRES_URL)\\b","vercel-storage",{"message":54,"pattern":55,"targetSkill":56},"Auth library detected during bootstrap — loading Auth guidance for Clerk Marketplace setup and middleware patterns.","from\\s+['\"\"](next-auth|@auth\u002Fcore|@clerk\u002Fnextjs|better-auth)['\"\"]","auth",{"message":58,"pattern":59,"targetSkill":60,"skipIfFileContains":61},"AI provider env vars detected — loading Environment Variables guidance for OIDC-based auth via vercel env pull.","OPENAI_API_KEY|ANTHROPIC_API_KEY|AI_GATEWAY","env-vars","VERCEL_OIDC|vercel env pull",{"docs":63,"sitemap":66,"priority":67,"bashPatterns":68,"pathPatterns":75,"importPatterns":86},[64,65],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fgetting-started-with-vercel","https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fgetting-started\u002Finstallation","https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml",8,[69,70,71,72,73,74],"\\\\bcp\\\\s+\\\\.env\\\\.(?:example|sample|template)\\\\s+\\\\.env\\\\.local\\\\b","\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+db:(?:push|seed|migrate|generate)\\\\b","\\\\b(?:npm|pnpm|bun|yarn)\\\\s+run\\\\s+dev\\\\b","\\\\bvercel\\\\s+link\\\\b","\\\\bvercel\\\\s+integration\\\\s+(?:add|install)\\\\b","\\\\bvercel\\\\s+env\\\\s+pull\\\\b",[76,77,78,79,80,81,82,83,84,85],".env.example",".env.sample",".env.template","README*","docs\u002F**\u002Fsetup*","package.json","drizzle.config.*","prisma\u002Fschema.prisma","auth.*","src\u002F**\u002Fauth.*",[87,88,89,90,91,92,93,94],"@neondatabase\u002Fserverless","drizzle-orm","@upstash\u002Fredis","@vercel\u002Fblob","@vercel\u002Fedge-config","next-auth","@auth\u002Fcore","better-auth",{"aliases":96,"intents":100,"entities":105},[97,98,37,99],"project setup","repo init","scaffold",[101,102,103,104],"set up project","initialize repo","link vercel project","pull env vars",[106,107,108,109],"vercel link","env pull","database setup","first run","main","9a4409c8751439c3aeeea2bc3940ba05dc3cd3b5","plugins\u002Fvercel\u002Fskills\u002Fbootstrap",0,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FNagyVikt","https:\u002F\u002Fwebu.hu\u002F","Codex is a tool they said...\r\n\r\nCreator of GitGuardex, CueCards. Tech stack: Next.js · TypeScript · Rust · Linux. ","2026-03-30 02:19:53",{"source":8,"skillName":5,"commands":120,"prompt":130,"zipAvailable":131},[121,124,127],{"tool":122,"command":123},"npx","npx skills add NagyVikt\u002Fcodex-plugins --skill bootstrap",{"tool":125,"command":126},"bunx","bunx skills add NagyVikt\u002Fcodex-plugins --skill bootstrap",{"tool":128,"command":129},"pnpm","pnpm dlx skills add NagyVikt\u002Fcodex-plugins --skill bootstrap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fbootstrap\u002FSKILL.md",true,[],[134,171,202,218,247,268],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":152,"publishedAt":43},"01M6K1ZEN8P9R2S6NPNJNJ8JVH","workflow","Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[140,141,144,149],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":150,"categoryName":151,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000038","人力资源",[136,153,154,39,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170],"workflows","create","streaming","logs","start","why","loop","wait for","branch","auto","log","conversation","human","lib","condition","rendering","retries","sleep",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":187,"publishedAt":43},"01M6K1Z71NWFSPHK2VJJ73MVSY","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[177,180,181,184],{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":182,"categoryName":183,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":185,"categoryName":186,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000033","数据分析师",[173,56,155,188,189,190,161,191,192,193,33,32,194,195,196,197,198,199,200,201],"routing middleware","api","projects","user story","full stack","jest","end","app","false","unit","error","middleware","loading","unit test",{"skillNo":203,"name":52,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":43},"01M6K1YPRYJS3BQEDP8HKBHPEJ","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[207],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[209,210,211,42,39,212,38,162,213,35,214,31,215,30,195,166,216,27,26,217],"storage","vercel storage","vercel","supabase","router","expert","connection pooling","turso","auth0",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":231,"publishedAt":43},"01M6K1YFEP0GPPGMQ3D0FPTS27","vercel-services","Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[224,227,228],{"categoryNo":225,"categoryName":226,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[232,233,211,234,235,236,237,238,239,240,241,110,242,243,32,244,195,245,198,246],"vercel services","services","frontend","docker compose","SET","configure","monorepo","go api","fastapi","up","aws lambda","go backend","get","apps","python backend",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":251,"categories":252,"keywords":253,"publishedAt":43},"01M6K1Y8S3CRD43DPKX0PK1MTT","vercel-sandbox","Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[254,255,211,34,256,154,39,257,258,259,260,261,262,263,264,265,200,266,249,267],"sandbox","vercel sandbox","ai agents","code","ai sdk","Code Generation","playground","generated","spawn","install","runner","io","child","student",{"skillNo":269,"name":270,"nameZh":6,"description":271,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":272,"categories":273,"keywords":275,"publishedAt":43},"01M6K1Y1J8S7AN97H75SHBGF7J","vercel-queues","Vercel Queues guidance (public beta) — durable event streaming with topics, consumer groups, retries, and delayed delivery. $0.60\u002F1M ops. Powers Workflow DevKit. Use when building async processing, fan-out patterns, or event-driven architectures.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-queues\u002FSKILL.md",[274],{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},[276,211,136,153,155,277,236,189,237,241,278,279,280,281,195,166,282,169,200,283],"vercel queues","beta","message","delivery","across","worker","processing","at"]