Skill Claude CodeCodex
Turn a rough coding or repo idea into a spec, executable plan, and long-running Codex /goal contract. Use when the user wants to create a coding spec, spec out a repo feature, tighten a coding spec, turn an implementation idea into a /goal-ready plan, prepare for autonomous coding, forge a goal, start a /goal…
Skill Claude CodeCodex
Distill any book into an executable Claude Code skill pack. Evaluates skillability, generates structured skills with modules/templates/examples, and supports multi-book synthesis. Use when you want to turn a book's methods into repeatable, actionable skills.
michaelpersonal/superpowers-cursor-rules
Cursor rule
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when creating visual design mockups in Pencil, before implementing interfaces - creates comprehensive design specs and systematic Pencil implementations with visual verification.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use at the end of any project to generate a "How I Built This" retrospective guide - creates both project documentation and a shareable version for teaching others.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when executing implementation plans with independent tasks in the current session.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when implementing any feature or bugfix, before writing implementation code.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Use when you have a spec or requirements for a multi-step task, before touching code.
michaelpersonal/superpowers-cursor-rules
Cursor rule
Superpowers - A complete software development workflow with TDD, systematic debugging, and structured planning.
michaelpersonal/compound-engineering
Cursor rule
Based on Every.to's Compound Engineering.