[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E1VKFDKY00C7KM9TPRST4W":3,"skill-same:01M6E1VKFDKY00C7KM9TPRST4W":72},{"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":18,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6E1VKFDKY00C7KM9TPRST4W","dev",null,"Implement a feature. Supports resuming interrupted work and team mode (--team flag). Reads spec\u002Ffeature\u002F[name]\u002Fspec.md and design.md, generates PLAN.md inside the feature directory, waits for user confirmation, then implements and verifies the feature.","ByeongminLee\u002Fnextjs-claude-code","ByeongminLee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71276006?v=4","01M6E1S467E7GC0NE144SWHC0V","Byeongmin Lee","01M6E1S4AV3W0B08Z2YBK26VG9",3,"MIT","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002F.claude\u002Fskills\u002Fdev\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29],"design","directory","spec","implement","team","plan","work","confirmation","user","feature","name","2026-11-10 10:12:30",false,"---\nname: dev\ndescription: Implement a feature. Supports resuming interrupted work and team mode (--team flag). Reads spec\u002Ffeature\u002F[name]\u002Fspec.md and design.md, generates PLAN.md inside the feature directory, waits for user confirmation, then implements and verifies the feature.\nargument-hint: \"[feature name] [--team]\"\ncontext: fork\n---\n\n## Prerequisite check\n\nBefore parsing arguments, verify `\u002Finit` has been run:\n\n- Check if `spec\u002FPROJECT.md` exists\n- If NOT exists → output: \"Project not initialized. Run `\u002Finit` first to analyze your codebase and set up the spec directory.\" → **STOP**\n\n## Argument Parsing\n\nParse `$ARGUMENTS` before anything else:\n\n1. If `$ARGUMENTS` contains `--team`:\n   - Remove `--team` from arguments → remaining text = feature name (trimmed)\n   - Set **MODE = team**\n2. Otherwise:\n   - Feature name = `$ARGUMENTS` as-is\n   - Set **MODE = solo**\n\n## Resume Protocol\n\nBefore starting, read `spec\u002FSTATE.md` and find the target feature's phase under `## Features`.\n\n### Feature name resolution:\n\n- If feature name (after parsing) is provided, use it.\n- If feature name is empty, look for features with non-idle phases in `spec\u002FSTATE.md`.\n  - If exactly one non-idle feature exists, use it.\n  - If multiple non-idle features exist, list them and ask the user which to continue.\n  - If all features are idle, ask the user which feature to work on.\n\n### Auto-generated spec check\n\nAfter resolving the feature name:\n\n- Read the first 10 lines of `spec\u002Ffeature\u002F[feature-name]\u002Fspec.md`\n- If the file contains `> DRAFT`:\n  - Output: \"Warning: The spec for \\\"[feature-name]\\\" was auto-generated by \u002Finit and is marked as DRAFT. Run `\u002Fspec [feature-name]` to review and finalize before developing. Proceed anyway? (yes\u002Fno)\"\n  - If \"no\" → **STOP**\n- If the file contains `> REFORGED`:\n  - Output: \"Warning: The spec for \\\"[feature-name]\\\" was auto-generated by \u002Freforge. Review with `\u002Fspec [feature-name]` if refinement needed. Proceed anyway? (yes\u002Fno)\"\n  - If \"no\" → **STOP**\n- If spec.md doesn't exist → skip (planner handles this)\n\n### Mode detection on resume:\n\nWhen resuming (phase is not `idle`), MODE is determined by the existing PLAN.md:\n\n- If `spec\u002Ffeature\u002F[name]\u002FPLAN.md` contains `## Team Composition` → MODE = team\n- Otherwise → MODE = solo\n\nThe `--team` flag is only needed for fresh starts. Resume auto-detects from PLAN.md.\n\n## Approval gate contract\n\nPlanning must not transition to execution without explicit user approval.\n\nAccepted approval replies:\n\n- `approve`\n- `approved`\n- `yes`\n- `proceed`\n\nRules:\n\n- If response is not an accepted approval reply, keep PLAN.md as `Status: pending`.\n- Do not spawn `lead-engineer` while status is pending.\n- If user requests changes, route back to planner and keep phase `planning`.\n\n### Model selection\n\nThe planner writes a `## Model Assignment` section in the feature's PLAN.md with the recommended model for each agent.\nWhen spawning agents, read PLAN.md and use the assigned model:\n\n- **planner**: always sonnet (no PLAN.md exists yet at this point)\n- **lead-engineer**: read `lead-engineer:` from PLAN.md `## Model Assignment`\n- **verifier**: always haiku (fixed — see `spec\u002Frules\u002F_model-routing.md`)\n\nIf `## Model Assignment` is missing for lead-engineer, default to sonnet.\n\n### Phase-based routing:\n\n- **`existing`** → Feature already has code but no formal spec.\n  Output:\n\n  ```\n  Feature \"[feature-name]\" was detected as existing code during \u002Finit.\n  Before modifying, create a formal spec:\n    \u002Fspec [feature-name] \"brief description\"\n  After running \u002Fspec, the phase updates to idle and you can run \u002Fdev normally.\n  ```\n\n  **STOP** — do not spawn any agent.\n\n- **`idle` (or no entry)** → Fresh start. Spawn `planner` (sonnet) with HANDOFF:\n  - TASK: `Create [team?] implementation plan for feature \"[feature-name]\"`\n  - If MODE = team: add `MODE: team` and include Team Composition in DONE-WHEN\n  - DONE-WHEN: PLAN.md approved, CONTEXT.md created, lead-engineer spawned\n  - MUST-NOT: Start implementation before user confirms, create plan without reading spec.md and design.md\n  - READS: `spec\u002Ffeature\u002F[feature-name]\u002Fspec.md`, `design.md`\n\n- **`planning`** → Planner was interrupted. Check `spec\u002Ffeature\u002F[name]\u002FPLAN.md`:\n  - If `Status: approved`: staleness check (compare spec.md mod time vs PLAN.md Created date). If stale, warn user. If proceeding, update phase to `executing` and spawn lead-engineer (same as `executing` below).\n  - If `Status: pending`: spawn `planner` (sonnet) — TASK: present pending plan for approval. MUST-NOT rewrite from scratch. READS: PLAN.md only.\n  - If PLAN.md missing: spawn `planner` same as `idle` above.\n\n- **`executing`** → Lead-engineer was interrupted. Read model from PLAN.md, spawn `lead-engineer` ({model}) with HANDOFF:\n  - TASK: `Resume implementing feature \"[feature-name]\" (skip completed tasks)`\n  - DONE-WHEN: all tasks `[x]`, tsc passes, verifier L1-3\n  - MUST-NOT: re-do `[x]` tasks, modify spec.md\u002Fdesign.md\n  - READS: `spec\u002Ffeature\u002F[feature-name]\u002FPLAN.md`, `CONTEXT.md`\n\n- **`verifying`** → Verifier was interrupted. Spawn `lead-engineer` ({model from PLAN.md}) — not verifier directly, because lead-engineer manages the auto-fix budget across sessions.\n  - TASK: `Resume verification for feature \"[feature-name]\" (re-run verifier)`\n  - DONE-WHEN: verifier L1-3 pass, L4 human-verify presented\n  - MUST-NOT: re-implement completed tasks, modify spec.md\u002Fdesign.md\n  - READS: `spec\u002Ffeature\u002F[feature-name]\u002FPLAN.md`, `CONTEXT.md`\n- **`looping`** → Feature is in a `\u002Floop` cycle. Do NOT start `\u002Fdev` flow.\n  Report to the user:\n  ```\n  Feature \"[feature-name]\" is currently in looping phase (managed by \u002Floop).\n  - To continue the loop: run `\u002Floop [feature-name]`\n  - To restart from scratch: manually set the phase to idle in spec\u002FSTATE.md, then run `\u002Fdev [feature-name]`\n  ```\n  Stop here — do not spawn any agent.\n\n---\n\nImplement the following feature:\n\n$ARGUMENTS\n","## Prerequisite check\n\nBefore parsing arguments, verify `\u002Finit` has been run:\n\n- Check if `spec\u002FPROJECT.md` exists\n- If NOT exists → output: \"Project not initialized. Run `\u002Finit` first to analyze your codebase and set up the spec directory.\" → **STOP**\n\n## Argument Parsing\n\nParse `$ARGUMENTS` before anything else:\n\n1. If `$ARGUMENTS` contains `--team`:\n   - Remove `--team` from arguments → remaining text = feature name (trimmed)\n   - Set **MODE = team**\n2. Otherwise:\n   - Feature name = `$ARGUMENTS` as-is\n   - Set **MODE = solo**\n\n## Resume Protocol\n\nBefore starting, read `spec\u002FSTATE.md` and find the target feature's phase under `## Features`.\n\n### Feature name resolution:\n\n- If feature name (after parsing) is provided, use it.\n- If feature name is empty, look for features with non-idle phases in `spec\u002FSTATE.md`.\n  - If exactly one non-idle feature exists, use it.\n  - If multiple non-idle features exist, list them and ask the user which to continue.\n  - If all features are idle, ask the user which feature to work on.\n\n### Auto-generated spec check\n\nAfter resolving the feature name:\n\n- Read the first 10 lines of `spec\u002Ffeature\u002F[feature-name]\u002Fspec.md`\n- If the file contains `> DRAFT`:\n  - Output: \"Warning: The spec for \\\"[feature-name]\\\" was auto-generated by \u002Finit and is marked as DRAFT. Run `\u002Fspec [feature-name]` to review and finalize before developing. Proceed anyway? (yes\u002Fno)\"\n  - If \"no\" → **STOP**\n- If the file contains `> REFORGED`:\n  - Output: \"Warning: The spec for \\\"[feature-name]\\\" was auto-generated by \u002Freforge. Review with `\u002Fspec [feature-name]` if refinement needed. Proceed anyway? (yes\u002Fno)\"\n  - If \"no\" → **STOP**\n- If spec.md doesn't exist → skip (planner handles this)\n\n### Mode detection on resume:\n\nWhen resuming (phase is not `idle`), MODE is determined by the existing PLAN.md:\n\n- If `spec\u002Ffeature\u002F[name]\u002FPLAN.md` contains `## Team Composition` → MODE = team\n- Otherwise → MODE = solo\n\nThe `--team` flag is only needed for fresh starts. Resume auto-detects from PLAN.md.\n\n## Approval gate contract\n\nPlanning must not transition to execution without explicit user approval.\n\nAccepted approval replies:\n\n- `approve`\n- `approved`\n- `yes`\n- `proceed`\n\nRules:\n\n- If response is not an accepted approval reply, keep PLAN.md as `Status: pending`.\n- Do not spawn `lead-engineer` while status is pending.\n- If user requests changes, route back to planner and keep phase `planning`.\n\n### Model selection\n\nThe planner writes a `## Model Assignment` section in the feature's PLAN.md with the recommended model for each agent.\nWhen spawning agents, read PLAN.md and use the assigned model:\n\n- **planner**: always sonnet (no PLAN.md exists yet at this point)\n- **lead-engineer**: read `lead-engineer:` from PLAN.md `## Model Assignment`\n- **verifier**: always haiku (fixed — see `spec\u002Frules\u002F_model-routing.md`)\n\nIf `## Model Assignment` is missing for lead-engineer, default to sonnet.\n\n### Phase-based routing:\n\n- **`existing`** → Feature already has code but no formal spec.\n  Output:\n\n  ```\n  Feature \"[feature-name]\" was detected as existing code during \u002Finit.\n  Before modifying, create a formal spec:\n    \u002Fspec [feature-name] \"brief description\"\n  After running \u002Fspec, the phase updates to idle and you can run \u002Fdev normally.\n  ```\n\n  **STOP** — do not spawn any agent.\n\n- **`idle` (or no entry)** → Fresh start. Spawn `planner` (sonnet) with HANDOFF:\n  - TASK: `Create [team?] implementation plan for feature \"[feature-name]\"`\n  - If MODE = team: add `MODE: team` and include Team Composition in DONE-WHEN\n  - DONE-WHEN: PLAN.md approved, CONTEXT.md created, lead-engineer spawned\n  - MUST-NOT: Start implementation before user confirms, create plan without reading spec.md and design.md\n  - READS: `spec\u002Ffeature\u002F[feature-name]\u002Fspec.md`, `design.md`\n\n- **`planning`** → Planner was interrupted. Check `spec\u002Ffeature\u002F[name]\u002FPLAN.md`:\n  - If `Status: approved`: staleness check (compare spec.md mod time vs PLAN.md Created date). If stale, warn user. If proceeding, update phase to `executing` and spawn lead-engineer (same as `executing` below).\n  - If `Status: pending`: spawn `planner` (sonnet) — TASK: present pending plan for approval. MUST-NOT rewrite from scratch. READS: PLAN.md only.\n  - If PLAN.md missing: spawn `planner` same as `idle` above.\n\n- **`executing`** → Lead-engineer was interrupted. Read model from PLAN.md, spawn `lead-engineer` ({model}) with HANDOFF:\n  - TASK: `Resume implementing feature \"[feature-name]\" (skip completed tasks)`\n  - DONE-WHEN: all tasks `[x]`, tsc passes, verifier L1-3\n  - MUST-NOT: re-do `[x]` tasks, modify spec.md\u002Fdesign.md\n  - READS: `spec\u002Ffeature\u002F[feature-name]\u002FPLAN.md`, `CONTEXT.md`\n\n- **`verifying`** → Verifier was interrupted. Spawn `lead-engineer` ({model from PLAN.md}) — not verifier directly, because lead-engineer manages the auto-fix budget across sessions.\n  - TASK: `Resume verification for feature \"[feature-name]\" (re-run verifier)`\n  - DONE-WHEN: verifier L1-3 pass, L4 human-verify presented\n  - MUST-NOT: re-implement completed tasks, modify spec.md\u002Fdesign.md\n  - READS: `spec\u002Ffeature\u002F[feature-name]\u002FPLAN.md`, `CONTEXT.md`\n- **`looping`** → Feature is in a `\u002Floop` cycle. Do NOT start `\u002Fdev` flow.\n  Report to the user:\n  ```\n  Feature \"[feature-name]\" is currently in looping phase (managed by \u002Floop).\n  - To continue the loop: run `\u002Floop [feature-name]`\n  - To restart from scratch: manually set the phase to idle in spec\u002FSTATE.md, then run `\u002Fdev [feature-name]`\n  ```\n  Stop here — do not spawn any agent.\n\n---\n\nImplement the following feature:\n\n$ARGUMENTS\n",{"name":5,"context":35,"description":7,"argument-hint":36},"fork","[feature name] [--team]","main","330a71e3d12264515ce3477e446d29fd34a88a9d","template\u002F.claude\u002Fskills\u002Fdev",1,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code","https:\u002F\u002Fbyeongminlee.github.io\u002Fnextjs-claude-code\u002F","https:\u002F\u002Fgithub.com\u002FByeongminLee","byeongmin.dev","2026-03-27 12:45:44",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add ByeongminLee\u002Fnextjs-claude-code --skill dev",{"tool":52,"command":53},"bunx","bunx skills add ByeongminLee\u002Fnextjs-claude-code --skill dev",{"tool":55,"command":56},"pnpm","pnpm dlx skills add ByeongminLee\u002Fnextjs-claude-code --skill dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002F.claude\u002Fskills\u002Fdev\u002FSKILL.md",true,[60,66],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fcreate_xmind.mjs","SCRIPT","脚本",15441,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__apeyroux--xmind\u002Fscripts\u002Fcreate_xmind.mjs",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"xmind-skill.zip","ASSET","资产文件",7754,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__apeyroux--xmind\u002Fxmind-skill.zip",[73,92,100,132,161,198],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":30},"01M6E263DRDCZ5AX01N6MDYC6Z","zustand","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fzustand\u002FSKILL.md",[],[75,80,81,82,83,84,85,86,87,88,89,90,91],"triggers","state management","zustand state","implementation","use","guide","management","src","actions","state","code","development",{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":30},"01M6E260QFP3ZMXY2Y6KTGZYXS","web-vitals","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fweb-vitals\u002FSKILL.md",[],[98,99],"web vitals","web",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":30},"01M6E25QEKXHH092S5RB0GKM0K","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\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-storage\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131],"vercel","vercel storage","storage","supabase","api","mongodb","SET","nextjs","database","auth","migrate","click","app","neon","prisma","postgres","expert","up","auto","configure",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":144,"publishedAt":30},"01M6E25EC9YM4QM0KBQ2W5R1SC","vercel-functions","Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-functions\u002FSKILL.md",[138,139],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[145,112,146,147,148,149,150,151,124,125,152,153,154,155,156,157,158,159,160,128],"functions","vercel functions","local","shared","project","time","apps","express","vercel ai sdk","router","loop","server","logs","streaming","delete","create",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":182,"publishedAt":30},"01M6E25873YRYP96MSQK7E2D9X","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fui-ux-pro-max\u002FSKILL.md",[167,170,173,176,179],{"categoryNo":168,"categoryName":169,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":171,"categoryName":172,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":174,"categoryName":175,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":177,"categoryName":178,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":180,"categoryName":181,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000033","数据分析师",[183,184,185,186,187,188,19,189,124,190,191,192,193,24,194,195,196,88,197,160],"ui ux pro max","ui","ux","max","css","MCP","react","card","chart","fix","projects","improve","Tailwind","Animation","search",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":30},"01M6E251G3FJSRB9019V20QK9X","turborepo","Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,\ndependsOn, caching, remote cache, the \"turbo\" CLI, --filter, --affected, CI optimization, environment\nvariables, internal packages, monorepo structure\u002Fbest practices, and boundaries.\n\nUse when user: configures tasks\u002Fworkflows\u002Fpipelines, creates packages, sets up\nmonorepo, shares code between apps, runs changed\u002Faffected packages, debugs cache,\nor has apps\u002Fpackages directories.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturborepo\u002FSKILL.md",[],[200,205,84,206,207,151,80,208,209,129,210,211,212,213,214,215,90,216,217,218],"cli","filter","environment variables","caching","structure","environment","monorepo","system","canary","Optimization","ci","packages","tasks","workflows"]