Loading...
Loading...
Found 29 Skills
Create a well-thought-out plan covering problem statement, goals, technical approach, and verification criteria. Use while planning / before implementing any non-trivial feature.
This skill is used when users express the intention to develop products, applications, tools or any software projects. Collect requirements through in-depth conversations, use straightforward follow-up questions to help users clarify their ideas, and finally generate a Product Spec document (.md file) that can be directly used in Google AI Studio Builder.
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
(NS) Normative visual appearance guides for UI surfaces (card/form/shell/overlay): block order, states, palette, Action|What-changes tables. MUST use for descrição normativa, guia visual, aparência, visual QA checklist, "how this looks", docs named *-visual.md / *-painel-visual.md / *-appearance.md (and kin), or shell vs content / card vs form / carcaça vs formulário. Prefer prototype/ as source of truth when present; after behavioral UX guides, offer ns-living-spec appearance mode. Do NOT use for business rules, ERDs, layout/grid math, API/auth, e2e, or prototype create/evolve (ns-proto-creator).
Generate a custom checklist for the current feature based on user requirements.
Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
Conversational discovery — adapts from quick scoping (3-5 questions) to deep interviews (multi-round). Talk until we're clear, then build. Produces inline decisions; optionally saves spec.md or scope contract. Not for multi-perspective debate (use agent-room). Not for decomposing work (use task-breakdown).
Ideation: Use for /ideation or when organizing messy brain dumps into structured specs. NOT for existing tickets (use /spec instead).
Use this skill when the user needs to turn an idea into a buildable spec, write a project scope, create feature requirements, or define an MVP. Covers quick feature specs (10-15 min) for immediate AI builds and full project scopes (1-2 hours) for planning and contractor estimates.
Archive a completed spec-driven change. Warns on incomplete tasks, moves change to archive/ with a date prefix.
Reverse-engineer a SPEC document from an existing project. Analyzes code, config, tests, and structure to produce a comprehensive specification. Triggers on: code-to-spec, reverse spec, generate spec, 逆向规格, 生成规格文档, 生成设计文档, 生成设计方案, extract spec, document this project, what does this project do.
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/spec.doc", or when asked to document a codebase directory.