83,201 skills sorted by stars.
Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirement...
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying...
Interactive idea refinement using Socratic method to develop fully-formed designs
Socratic questioning protocol + user communication.
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavio...
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-f...
Collaborative ideation-to-spec refinement via one-question-at-a-time dialogue. Use before implementing new features, cha...
Use this skill before any creative or constructive work (features, components, architecture, behavior changes, or functi...
当用户明确要求"使用 brainstorming"或"使用 awesome-code"时使用。⚠️ 不适用:用户只是想优化/改进某个功能(应直接修改)、只是询问技能问题(应直接回答)、没有明确使用 brainstorming/awesome...
Rapid ideation skill adapted from obra/superpowers to kick off cortex sessions. Use when defining scope, aligning on goa...
Use when starting new features, major changes, or unclear requirements. Establishes shared understanding before implemen...
Transform rough ideas into solid designs through structured questioning
Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated desig...
Use this before any feature work. Full lifecycle: brainstorm, design, implement with parallel Teams, two-stage review, a...
Use when rough ideas need design before code or multiple approaches
Start a work item: triage risk, run structured brainstorming to clarify requirements, compare solution options, and prod...
Collaborative design exploration that refines ideas into validated specs through iterative questioning. Use before any c...
Clarify vague requirements through exploratory questioning and option generation before committing to research or implem...
This skill should be used before implementing features, building components, or making changes. It guides exploring user...