Loading...
Loading...
Found 491 Skills
Facilitate structured idea exploration and product/design specification. Use when a user wants to talk through an idea, refine it via iterative questions, and converge on a clear design/spec (and later an implementation plan), especially after inspecting the current project state.
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.
Use when designing API endpoints, defining request/response schemas, generating OpenAPI specifications, choosing between REST/GraphQL/tRPC, or establishing API conventions for a project
Use when writing specifications for features, projects, or requirements — applies Jobs to Be Done (JTBD) methodology with acceptance criteria focus, no implementation details, and SLC release planning
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.
Global writing style specification for Chinese technical writing. Applicable to all Chinese content production (WeChat Official Accounts, blogs, X, knowledge bases, AIW). Cited by gracker-writer and content-quality-gate.
Ralph Wiggum-inspired automation loop for specification-driven development. Orchestrates task implementation, review, cleanup, and synchronization using a Python script. Use when: user runs /loop command, user asks to automate task implementation, user wants to iterate through spec tasks step-by-step, or user wants to run development workflow automation with context window management. One step per invocation. State machine: init → choose_task → implementation → review → fix → cleanup → sync → update_done. Supports --from-task and --to-task for task range filtering. State persisted in fix_plan.json.
Use this when you have specifications or requirements for multi-step tasks, before starting to write code
Interviews the user about a product idea or feature using structured questions, then generates a detailed spec document (SPEC.md). Use when the user wants to flesh out an idea, plan a feature, or create a buildable specification.
Generates test code from specifications, components, and API endpoints. Creates unit tests, integration tests, and E2E tests following project testing patterns and conventions.
Best Practices for Database and Table Name Specification Validation and Automatic Correction. Applicable to scenarios like "Does the database comply with specifications?", "table name specifications", "check table names", "optimize table names", "database naming", "check this file", "Is the table name compliant?"
Manage protocol/standard specifications that define what a system must do. Use to create, import, or update the contract that TASKs implement against.