Loading...
Loading...
Found 196 Skills
Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.
Interactive creative thought partner that discovers hidden brilliance in ideas through pattern spotting, paradox hunting, and naming unnamed concepts. Use when the user wants to brainstorm, explore ideas deeply, develop newsletter content, find unique perspectives, or have a creative thinking session. Triggers on "brainstorm with me", "help me think through...", "explore this idea", "thought partner", "find the insight in...", or "creative session".
Discuss and brainstorm a spec-driven change from a rough idea, then propose a change name and, after explicit confirmation, generate the same five proposal artifacts as spec-driven-propose.
Use BEFORE coding any non-trivial change. Explores user intent, demand, tradeoffs, and approach. Produces a design doc in docs/design-docs/, not code. Required for LARGE tasks, optional for MEDIUM, skip for SMALL.
Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change
Generate project ideas via creative constraints.
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
Expert experiences council with 6 advisors (Pine, Parker, Meyer, Sutherland, Godin, Gray) for events, experiences, space activation, and idea generation.
Brainstorm and validate names for plugins, skills, agents, and commands. Use when naming a new plugin, choosing atom names, validating naming conventions, or when user mentions "name plugin", "name skill", "naming convention", "brainstorm names", "what should I call", "plugin name", "good name for".
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Turn rough ideas into structured, validated idea documents through collaborative dialogue. Explores context, asks clarifying questions one at a time, proposes alternative approaches with feasibility evaluation, and produces documents ready for requirements definition. Use when: "ideation", "brainstorm", "new idea", "explore an idea", "I want to build", "what if we", "let's think about", "propose approaches", "evaluate this idea", "idea document", "アイデア出し", "案出し", "ブレスト", "アイデアを整理", "検討したい".
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.