dreaming
Envision possibilities beyond current constraints. Use when planning evolution, imagining new capabilities, or exploring what could be.
validate
Check decisions against beliefs, wisdom, and intentions. Use before significant actions to ensure coherence with accumulated knowledge.
checkpoint
Capture a moment of clarity before moving forward. Use before /clear, risky changes, breakthroughs, or session boundaries.
compound
Distill observations into universal wisdom. Use to promote project patterns to soul wisdom when they reach critical mass.
recover
Break out of stuckness through inversion, simplification, and fresh angles. Use when repeating approaches without progress.
improve
Soul self-improvement loop. Use after introspection reveals targets, or to act on evolution insights.
neural
Feedback-driven learning. The soul learns from experience - what helped gets strengthened, what misled gets weakened.
antahkarana
Multi-perspective reasoning through Upanishadic Antahkarana voices. Use for complex problems requiring diverse viewpoints and synthesis. Spawns multiple Claude agents that reason from different perspectives and synthesize wisdom.
ddd-guide
Document-Driven Development workflow for existing codebases. Provides systematic planning, documentation-first design, and implementation verification.
brainstorm
Use when starting from rough ideas - refines concepts into executable specifications through collaborative questioning, alternative exploration, and incremental validation, use this skill when called from a command
using-superpowers-sdd
Establishes SDD methodology - workflow routing, process discipline, spec-first principle, and skill discovery. Use when starting any SDD conversation to determine which workflow skill to invoke.
sequential-thinking
Use for atypically complex problems requiring explicit step-by-step reasoning. Skill autonomously decides if sequential-thinking MCP overhead is justified based on problem complexity.
aiwf:spec-driven-development
Use when starting new features, building applications from scratch, or needing structured development workflow - provides standalone specification-first methodology without external dependencies, generates specs, plans, tasks directly, with superpowers integration for execution
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
brainstorming
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
problem-solving
Systematic problem-solving techniques for stuck-ness. Techniques: simplification cascade (complexity spirals), collision-zone thinking (innovation blocks), meta-pattern recognition (recurring issues), inversion exercise (assumption constraints), scale game (uncertainty). Actions: simplify, analyze, recognize patterns, invert assumptions, scale thinking. Keywords: problem solving, complexity spiral, innovation block, stuck, simplification, meta-pattern, assumption inversion, scale uncertainty, breakthrough thinking, root cause, systematic analysis, Microsoft Amplifier, debugging approach, creative solution. Use when: complexity spiraling, hitting innovation blocks, seeing recurring patterns, constrained by assumptions, uncertain about scale, generally stuck on problems.
sequential-thinking
Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems.
metaphor-to-protocol-translation
Translate metaphorical descriptions into executable protocols.
Page 2 of 16 · 272 results