菜单
Use this skill when the user wants to convert one or more existing documents into a dedicated skill, including analyzing suitability, extracting capabilities, designing the skill structure, and drafting SKILL.md and references.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Incubate, validate, and refine a raw product idea into an evidence-backed, decision-ready requirement through one durable 12-phase workflow. Use when starting or resuming idea discovery, executing or revising a named incubation phase, answering a pending phase question, or deciding whether an idea should become a formal requirement.
Plan and drive safe old-to-new project or repository migrations with phase-based outputs, risk controls, and migration artifacts. Use when a user needs to: (1) audit an inherited or undocumented project before migration, (2) compare old and new repositories across tooling, architecture, routing, state, request, styling, CI/CD, or release flow, (3) produce migration deliverables such as audits, maps, diff matrices, plans, pilot scopes, adapter plans, risk lists, or verification checklists, (4) execute or update a specific migration phase such as intake, audit, map, diff, plan, pilot, execute, verify, or cleanup.
Clean Code 规范总览与路由，覆盖命名、函数、注释、格式、对象与数据结构、错误处理、边界、测试、类、系统、并发、简单设计、渐进式重构及各类代码坏味道。当用户进行代码审查、重构、写新代码或询问 Clean Code / 整洁代码 / 代码坏味道相关规范时使用，并按主题加载 references 中的对应规则文件。Use for code review, refactor, writing new code, or any clean code / code smell / readability question; routes to the matching rule file under references.
当用户要求将会话中的代码规范、工程约定、架构约束、命名规则、目录结构、测试要求、提交流程、协作规则或 AI 协作规则沉淀为长期可复用的项目规则，或在对话中持续出现这类稳定约束时，调用此 skill。用于识别规则、判断新增/更新/合并/冲突、过滤临时指令，并按职责同步到 .cursor/rules、AGENTS.md、CLAUDE.md。
Spec-driven development workflow skill for product requirement intake, engineering research, technical planning, task breakdown, implementation, testing, bugfix loop, and engineering review. Use when a user wants to run or continue a structured software delivery workflow with explicit specs, durable artifacts, and iterative implementation/testing loops.
Use this skill when the user wants to generate, update, or improve usage documentation for a project, file, component, SDK, module, or function based on source code.
| name | doc-skill-creator |
| description | Use this skill when the user wants to convert one or more existing documents into a dedicated skill, including analyzing suitability, extracting capabilities, designing the skill structure, and drafting SKILL.md and references. |
Convert existing documents into a dedicated skill design.
This skill is for turning static documentation such as component library docs, SDK docs, utility docs, FAQ, migration guides, standards docs, README files, and examples into practical skill artifacts.
Use this skill when the user wants to:
Do not use this skill when:
Unless the user requests otherwise, include:
See references/ for detailed guidance on analysis, skill typing, capability extraction, knowledge layering, references planning, output templates, examples, pitfalls, gaps, and migration.
