Loading...
Loading...
Found 538 Skills
Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.
Craft elegant technical specifications with ASCII artistry, flow diagrams, and the Grove voice. The swan glides with purpose—vision first, then form, then perfection. Use when creating specs, reviewing documents, or transforming technical plans into storybook entries.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Front-end routing specification, including routing file organization structure, dynamic routing generation, static auxiliary routing writing, RouteMeta meta information fields, and routing guard logic. Suitable for projects based on vue-vben-admin v5. This skill is used when you need to add new routes, configure routing permissions, write routing guards, or modify routing-related files.
Generates Tzatziki-based Cucumber BDD tests (.feature files) from a functional specification. Use this skill whenever a user wants to write Cucumber tests, add BDD scenarios, create feature files, generate tests, or test application behaviors with Gherkin — especially in Java/Spring projects using Tzatziki step definitions for HTTP, JPA, Kafka, MongoDB, OpenSearch, logging, or MCP. Also use when the user mentions writing integration tests, acceptance tests, or end-to-end tests in a project that already has Tzatziki/Cucumber dependencies, including TestNG-based setups.
Conduct an interactive discovery interview to produce a structured product specification. Triggers: write a spec, PRD, feature spec, requirements, product requirements, scope a project, brainstorm a feature, flesh out an idea, plan a new project. Uses AskUserQuestion for all user choices; WebSearch/WebFetch when the user wants research. Outputs: user stories, acceptance criteria, technical constraints, prioritized requirements in docs/specs/ per SPEC_TEMPLATE.md. Do NOT use for: implementation, code review, debugging, refactors, or when the user already has a complete spec they only want edited.
Use when designing API endpoints, defining request/response schemas, generating OpenAPI specifications, choosing between REST/GraphQL/tRPC, or establishing API conventions for a project
Manage the lifecycle of ExecPlans — self-contained, living specifications for multi-step work. Creates plans in the correct format, enforces living section updates, and handles the active → completed transition. Use for any work expected to take more than one session or touching more than 3 files. Triggers: "create a plan", "write a plan", "start plan", "continue plan", "resume plan", "finish plan", "complete plan", multi-step features, refactors, or tasks spanning sessions.
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation
Use when asked to identify and fix errors in an OpenAPI specification that are preventing it from running as mock or test
This skill is applicable when users explicitly request to 'write/generate NSFC budget specification', 'write budget explanation', 'generate budget.tex / budget.pdf', or 'write NSFC budget justification'. Based on the user's proposal text or supplementary materials, output a submittable budget specification LaTeX project and render `budget.pdf`. If the user does not specify a working directory, you must pause and ask them to specify it first. ⚠️ Not applicable: Users only want to understand budget principles; users only want budget table figures without writing the specification; or users are in the 2026 Youth A/B/C default lump-sum scenario where no budget specification is required.
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.