[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K19P9R6F6ETXVSARF7JMS2":3,"skill-same:01M6K19P9R6F6ETXVSARF7JMS2":81},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6K19P9R6F6ETXVSARF7JMS2","building-storefronts",null,"Load automatically when planning, researching, or implementing Medusa storefront features (calling custom API routes, SDK integration, React Query patterns, data fetching). REQUIRED for all storefront development in ALL modes (planning, implementation, exploration). Contains SDK usage patterns, frontend integration, and critical rules for calling Medusa APIs.","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\u002Fmedusa\u002Fskills\u002Fbuilding-storefronts\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"building storefronts","critical","custom","modes","data fetching","for","implementing","load","usage","medusa","frontend","query","calling","exploration","Rules","api","planning","development","react","sdk","2026-11-10 10:12:30",false,"---\nname: building-storefronts\ndescription: Load automatically when planning, researching, or implementing Medusa storefront features (calling custom API routes, SDK integration, React Query patterns, data fetching). REQUIRED for all storefront development in ALL modes (planning, implementation, exploration). Contains SDK usage patterns, frontend integration, and critical rules for calling Medusa APIs.\n---\n\n# Medusa Storefront Development\n\nFrontend integration guide for building storefronts with Medusa. Covers SDK usage, React Query patterns, and calling custom API routes.\n\n## When to Apply\n\n**Load this skill for ANY storefront development task, including:**\n- Calling custom Medusa API routes from the storefront\n- Integrating Medusa SDK in frontend applications\n- Using React Query for data fetching\n- Implementing mutations with optimistic updates\n- Error handling and cache invalidation\n\n**Also load building-with-medusa when:** Building the backend API routes that the storefront calls\n\n## CRITICAL: Load Reference Files When Needed\n\n**The quick reference below is NOT sufficient for implementation.** You MUST load the reference file before writing storefront integration code.\n\n**Load this reference when implementing storefront features:**\n\n- **Calling API routes?** → MUST load `references\u002Ffrontend-integration.md` first\n- **Using SDK?** → MUST load `references\u002Ffrontend-integration.md` first\n- **Implementing React Query?** → MUST load `references\u002Ffrontend-integration.md` first\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | SDK Usage | CRITICAL | `sdk-` |\n| 2 | React Query Patterns | HIGH | `query-` |\n| 3 | Data Display | HIGH (includes CRITICAL price rule) | `display-` |\n| 4 | Error Handling | MEDIUM | `error-` |\n\n## Quick Reference\n\n### 1. SDK Usage (CRITICAL)\n\n- `sdk-always-use` - **ALWAYS use the Medusa JS SDK for ALL API requests** - NEVER use regular fetch()\n- `sdk-existing-methods` - For built-in endpoints, use existing SDK methods (`sdk.store.product.list()`, `sdk.admin.order.retrieve()`)\n- `sdk-client-fetch` - For custom API routes, use `sdk.client.fetch()`\n- `sdk-required-headers` - SDK automatically adds required headers (publishable API key for store, auth for admin) - regular fetch() missing these headers causes errors\n- `sdk-no-json-stringify` - **NEVER use JSON.stringify() on body** - SDK handles serialization automatically\n- `sdk-plain-objects` - Pass plain JavaScript objects to body, not strings\n- `sdk-locate-first` - Always locate where SDK is instantiated in the project before using it\n\n### 2. React Query Patterns (HIGH)\n\n- `query-use-query` - Use `useQuery` for GET requests (data fetching)\n- `query-use-mutation` - Use `useMutation` for POST\u002FDELETE requests (mutations)\n- `query-invalidate` - Invalidate queries in `onSuccess` to refresh data after mutations\n- `query-keys-hierarchical` - Structure query keys hierarchically for effective cache management\n- `query-loading-states` - Always handle `isLoading`, `isPending`, `isError` states\n\n### 3. Data Display (HIGH)\n\n- `display-price-format` - **CRITICAL**: Prices from Medusa are stored as-is ($49.99 = 49.99, NOT in cents). Display them directly - NEVER divide by 100\n\n### 4. Error Handling (MEDIUM)\n\n- `error-on-error` - Implement `onError` callback in mutations to handle failures\n- `error-display` - Show error messages to users when mutations fail\n- `error-rollback` - Use optimistic updates with rollback on error for better UX\n\n## Critical SDK Pattern\n\n**ALWAYS pass plain objects to the SDK - NEVER use JSON.stringify():**\n\n```typescript\n\u002F\u002F ✅ CORRECT - Plain object\nawait sdk.client.fetch(\"\u002Fstore\u002Freviews\", {\n  method: \"POST\",\n  body: {\n    product_id: \"prod_123\",\n    rating: 5,\n  }\n})\n\n\u002F\u002F ❌ WRONG - JSON.stringify breaks the request\nawait sdk.client.fetch(\"\u002Fstore\u002Freviews\", {\n  method: \"POST\",\n  body: JSON.stringify({  \u002F\u002F ❌ DON'T DO THIS!\n    product_id: \"prod_123\",\n    rating: 5,\n  })\n})\n```\n\n**Why this matters:**\n- The SDK handles JSON serialization automatically\n- Using JSON.stringify() will double-serialize and break the request\n- The server won't be able to parse the body\n\n## Common Mistakes Checklist\n\nBefore implementing, verify you're NOT doing these:\n\n**SDK Usage:**\n- [ ] Using regular fetch() instead of the Medusa JS SDK (causes missing header errors)\n- [ ] Not using existing SDK methods for built-in endpoints (e.g., using sdk.client.fetch(\"\u002Fstore\u002Fproducts\") instead of sdk.store.product.list())\n- [ ] Using JSON.stringify() on the body parameter\n- [ ] Manually setting Content-Type headers (SDK adds them)\n- [ ] Hardcoding SDK import paths (locate in project first)\n- [ ] Not using sdk.client.fetch() for custom routes\n\n**React Query:**\n- [ ] Not invalidating queries after mutations\n- [ ] Using flat query keys instead of hierarchical\n- [ ] Not handling loading and error states\n- [ ] Forgetting to disable buttons during mutations (isPending)\n\n**Data Display:**\n- [ ] **CRITICAL**: Dividing prices by 100 when displaying (prices are stored as-is: $49.99 = 49.99, NOT in cents)\n\n**Error Handling:**\n- [ ] Not implementing onError callbacks\n- [ ] Not showing error messages to users\n- [ ] Not handling network failures gracefully\n\n## How to Use\n\n**For detailed patterns and examples, load reference file:**\n\n```\nreferences\u002Ffrontend-integration.md - SDK usage, React Query patterns, API integration\n```\n\nThe reference file contains:\n- Step-by-step SDK integration patterns\n- Complete React Query examples\n- Correct vs incorrect code examples\n- Query key best practices\n- Optimistic update patterns\n- Error handling strategies\n\n## When to Use MedusaDocs MCP Server\n\n**Use this skill for (PRIMARY SOURCE):**\n- How to call custom API routes from storefront\n- SDK usage patterns (sdk.client.fetch)\n- React Query integration patterns\n- Common mistakes and anti-patterns\n\n**Use MedusaDocs MCP server for (SECONDARY SOURCE):**\n- Built-in SDK methods (sdk.admin.*, sdk.store.*)\n- Official Medusa SDK API reference\n- Framework-specific configuration options\n\n**Why skills come first:**\n- Skills contain critical patterns like \"don't use JSON.stringify\" that MCP doesn't emphasize\n- Skills show correct vs incorrect patterns; MCP shows what's possible\n- Planning requires understanding patterns, not just API reference\n\n## Integration with Backend\n\n**⚠️ CRITICAL: ALWAYS use the Medusa JS SDK - NEVER use regular fetch()**\n\nWhen building features that span backend and frontend:\n\n1. **Backend (building-with-medusa skill):** Module → Workflow → API Route\n2. **Storefront (this skill):** SDK → React Query → UI Components\n3. **Connection:**\n   - Built-in endpoints: Use existing SDK methods (`sdk.store.product.list()`)\n   - Custom API routes: Use `sdk.client.fetch(\"\u002Fstore\u002Fmy-route\")`\n   - **NEVER use regular fetch()** - missing publishable API key causes errors\n\n**Why the SDK is required:**\n- Store routes need `x-publishable-api-key` header\n- Admin routes need `Authorization` and session headers\n- SDK handles all required headers automatically\n- Regular fetch() without headers → authentication\u002Fauthorization errors\n\nSee `building-with-medusa` for backend API route patterns.\n","# Medusa Storefront Development\n\nFrontend integration guide for building storefronts with Medusa. Covers SDK usage, React Query patterns, and calling custom API routes.\n\n## When to Apply\n\n**Load this skill for ANY storefront development task, including:**\n- Calling custom Medusa API routes from the storefront\n- Integrating Medusa SDK in frontend applications\n- Using React Query for data fetching\n- Implementing mutations with optimistic updates\n- Error handling and cache invalidation\n\n**Also load building-with-medusa when:** Building the backend API routes that the storefront calls\n\n## CRITICAL: Load Reference Files When Needed\n\n**The quick reference below is NOT sufficient for implementation.** You MUST load the reference file before writing storefront integration code.\n\n**Load this reference when implementing storefront features:**\n\n- **Calling API routes?** → MUST load `references\u002Ffrontend-integration.md` first\n- **Using SDK?** → MUST load `references\u002Ffrontend-integration.md` first\n- **Implementing React Query?** → MUST load `references\u002Ffrontend-integration.md` first\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | SDK Usage | CRITICAL | `sdk-` |\n| 2 | React Query Patterns | HIGH | `query-` |\n| 3 | Data Display | HIGH (includes CRITICAL price rule) | `display-` |\n| 4 | Error Handling | MEDIUM | `error-` |\n\n## Quick Reference\n\n### 1. SDK Usage (CRITICAL)\n\n- `sdk-always-use` - **ALWAYS use the Medusa JS SDK for ALL API requests** - NEVER use regular fetch()\n- `sdk-existing-methods` - For built-in endpoints, use existing SDK methods (`sdk.store.product.list()`, `sdk.admin.order.retrieve()`)\n- `sdk-client-fetch` - For custom API routes, use `sdk.client.fetch()`\n- `sdk-required-headers` - SDK automatically adds required headers (publishable API key for store, auth for admin) - regular fetch() missing these headers causes errors\n- `sdk-no-json-stringify` - **NEVER use JSON.stringify() on body** - SDK handles serialization automatically\n- `sdk-plain-objects` - Pass plain JavaScript objects to body, not strings\n- `sdk-locate-first` - Always locate where SDK is instantiated in the project before using it\n\n### 2. React Query Patterns (HIGH)\n\n- `query-use-query` - Use `useQuery` for GET requests (data fetching)\n- `query-use-mutation` - Use `useMutation` for POST\u002FDELETE requests (mutations)\n- `query-invalidate` - Invalidate queries in `onSuccess` to refresh data after mutations\n- `query-keys-hierarchical` - Structure query keys hierarchically for effective cache management\n- `query-loading-states` - Always handle `isLoading`, `isPending`, `isError` states\n\n### 3. Data Display (HIGH)\n\n- `display-price-format` - **CRITICAL**: Prices from Medusa are stored as-is ($49.99 = 49.99, NOT in cents). Display them directly - NEVER divide by 100\n\n### 4. Error Handling (MEDIUM)\n\n- `error-on-error` - Implement `onError` callback in mutations to handle failures\n- `error-display` - Show error messages to users when mutations fail\n- `error-rollback` - Use optimistic updates with rollback on error for better UX\n\n## Critical SDK Pattern\n\n**ALWAYS pass plain objects to the SDK - NEVER use JSON.stringify():**\n\n```typescript\n\u002F\u002F ✅ CORRECT - Plain object\nawait sdk.client.fetch(\"\u002Fstore\u002Freviews\", {\n  method: \"POST\",\n  body: {\n    product_id: \"prod_123\",\n    rating: 5,\n  }\n})\n\n\u002F\u002F ❌ WRONG - JSON.stringify breaks the request\nawait sdk.client.fetch(\"\u002Fstore\u002Freviews\", {\n  method: \"POST\",\n  body: JSON.stringify({  \u002F\u002F ❌ DON'T DO THIS!\n    product_id: \"prod_123\",\n    rating: 5,\n  })\n})\n```\n\n**Why this matters:**\n- The SDK handles JSON serialization automatically\n- Using JSON.stringify() will double-serialize and break the request\n- The server won't be able to parse the body\n\n## Common Mistakes Checklist\n\nBefore implementing, verify you're NOT doing these:\n\n**SDK Usage:**\n- [ ] Using regular fetch() instead of the Medusa JS SDK (causes missing header errors)\n- [ ] Not using existing SDK methods for built-in endpoints (e.g., using sdk.client.fetch(\"\u002Fstore\u002Fproducts\") instead of sdk.store.product.list())\n- [ ] Using JSON.stringify() on the body parameter\n- [ ] Manually setting Content-Type headers (SDK adds them)\n- [ ] Hardcoding SDK import paths (locate in project first)\n- [ ] Not using sdk.client.fetch() for custom routes\n\n**React Query:**\n- [ ] Not invalidating queries after mutations\n- [ ] Using flat query keys instead of hierarchical\n- [ ] Not handling loading and error states\n- [ ] Forgetting to disable buttons during mutations (isPending)\n\n**Data Display:**\n- [ ] **CRITICAL**: Dividing prices by 100 when displaying (prices are stored as-is: $49.99 = 49.99, NOT in cents)\n\n**Error Handling:**\n- [ ] Not implementing onError callbacks\n- [ ] Not showing error messages to users\n- [ ] Not handling network failures gracefully\n\n## How to Use\n\n**For detailed patterns and examples, load reference file:**\n\n```\nreferences\u002Ffrontend-integration.md - SDK usage, React Query patterns, API integration\n```\n\nThe reference file contains:\n- Step-by-step SDK integration patterns\n- Complete React Query examples\n- Correct vs incorrect code examples\n- Query key best practices\n- Optimistic update patterns\n- Error handling strategies\n\n## When to Use MedusaDocs MCP Server\n\n**Use this skill for (PRIMARY SOURCE):**\n- How to call custom API routes from storefront\n- SDK usage patterns (sdk.client.fetch)\n- React Query integration patterns\n- Common mistakes and anti-patterns\n\n**Use MedusaDocs MCP server for (SECONDARY SOURCE):**\n- Built-in SDK methods (sdk.admin.*, sdk.store.*)\n- Official Medusa SDK API reference\n- Framework-specific configuration options\n\n**Why skills come first:**\n- Skills contain critical patterns like \"don't use JSON.stringify\" that MCP doesn't emphasize\n- Skills show correct vs incorrect patterns; MCP shows what's possible\n- Planning requires understanding patterns, not just API reference\n\n## Integration with Backend\n\n**⚠️ CRITICAL: ALWAYS use the Medusa JS SDK - NEVER use regular fetch()**\n\nWhen building features that span backend and frontend:\n\n1. **Backend (building-with-medusa skill):** Module → Workflow → API Route\n2. **Storefront (this skill):** SDK → React Query → UI Components\n3. **Connection:**\n   - Built-in endpoints: Use existing SDK methods (`sdk.store.product.list()`)\n   - Custom API routes: Use `sdk.client.fetch(\"\u002Fstore\u002Fmy-route\")`\n   - **NEVER use regular fetch()** - missing publishable API key causes errors\n\n**Why the SDK is required:**\n- Store routes need `x-publishable-api-key` header\n- Admin routes need `Authorization` and session headers\n- SDK handles all required headers automatically\n- Regular fetch() without headers → authentication\u002Fauthorization errors\n\nSee `building-with-medusa` for backend API route patterns.\n",{"name":5,"description":7},"main","9a4409c8751439c3aeeea2bc3940ba05dc3cd3b5","plugins\u002Fmedusa\u002Fskills\u002Fbuilding-storefronts",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add NagyVikt\u002Fcodex-plugins --skill building-storefronts",{"tool":67,"command":68},"bunx","bunx skills add NagyVikt\u002Fcodex-plugins --skill building-storefronts",{"tool":70,"command":71},"pnpm","pnpm dlx skills add NagyVikt\u002Fcodex-plugins --skill building-storefronts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmedusa\u002Fskills\u002Fbuilding-storefronts\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Ffrontend-integration.md","REFERENCE","参考文档",6951,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmedusa\u002Fskills\u002Fbuilding-storefronts\u002Freferences\u002Ffrontend-integration.md",[82,120,153,177,203,225],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":100,"publishedAt":47},"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",[88,89,92,97],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000038","人力资源",[84,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"workflows","create","run","streaming","logs","start","why","loop","wait for","branch","auto","log","conversation","human","lib","condition","rendering","retries","sleep",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":136,"publishedAt":47},"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",[126,129,130,133],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":131,"categoryName":132,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":134,"categoryName":135,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000033","数据分析师",[122,137,104,138,42,139,110,140,141,142,143,144,145,146,147,148,149,150,151,152],"auth","routing middleware","projects","user story","full stack","jest","local","project","end","app","false","unit","error","middleware","loading","unit test",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":47},"01M6K1YPRYJS3BQEDP8HKBHPEJ","vercel-storage","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",[159],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,164,103,165,166,111,167,168,169,170,171,172,146,115,173,174,175,176],"storage","vercel storage","vercel","config","supabase","migrate","router","clerk","expert","prisma","connection pooling","neon","turso","upstash","URL","auth0",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":188,"publishedAt":47},"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",[183,184,185],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[189,190,163,37,191,192,193,194,195,196,197,52,198,199,144,200,146,201,149,202],"vercel services","services","docker compose","SET","configure","monorepo","go api","fastapi","up","aws lambda","go backend","get","apps","python backend",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":47},"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",[],[210,211,163,212,213,102,103,214,215,216,217,218,219,220,221,222,151,223,205,224],"sandbox","vercel sandbox","safe","ai agents","code","ai sdk","Code Generation","playground","generated","spawn","install","runner","io","child","student",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":232,"publishedAt":47},"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",[231],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[233,163,84,101,104,234,192,42,193,197,235,236,237,238,146,115,239,118,151,240],"vercel queues","beta","message","delivery","across","worker","processing","at"]