Loading...
Loading...
Found 749 Skills
Use BEFORE brainstorming — when the user wants to capture WHAT a feature should do as Gherkin scenarios. Trigger when the user says "I need to build X", "let's spec this out", "what should this feature do?", or wants to formally capture a new edge case or bug as a BDD scenario.
LOAD THIS SKILL when: gathering requirements for new features, user mentions 'requirements', 'requirements-start', 'requirements-end', 'requirements-status', 'requirements-current', 'requirements-list', 'requirements-remind'. Covers structured Q&A workflow with 5-phase requirements gathering, codebase analysis, and spec generation.
Use when storing project artifacts in basic memory storage.
Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.
ThinkPHP 后端开发规范。当开发 ThinkPHP 项目、实现 REST API、模型数据访问、JWT 认证时使用此 skill。
Use when the user is starting a new project or feature, or mentions "concept", "roadmap", "feature", "spec", "plan", "idea", or "what to build". Walks them through three plain-English phases — Concept (what & why) → Roadmap (the path) → Features (the work) — producing one-page markdown artifacts under `specdriven/` that anchor every later turn. Skip when the task is already small and well-scoped (a rename, a one-line bug fix).
Use this skill when users need to create or configure Salesforce Custom Applications. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Always use this skill for custom application work.
Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".
This skill should be used when the user asks to "design a CLI", "help me design command-line flags", "what flags should my tool have", "create a CLI spec", "refactor my CLI interface", "design a CLI my agent can call", or wants to design command-line UX (args/flags/subcommands/help/output/errors/config) before implementation or audit an existing CLI surface for consistency and composability.
Research, discuss, and write specs. Use this when creating or refining specs.
Améliorer un Prompt avec le Contexte du Projet, Techniques Avancées et Skills Spécialisés
Ensures frontend and backend agree on API request/response shapes using Apidog MCP as the single source of truth. Replaces manual contracts.md files. Use when implementing or reviewing API endpoints and their consumers. Automatically loaded by team-lead, backend-dev, web-dev, mobile-dev, and reviewer.