jev-superpowers

In the author's own words, from each skill's SKILL.md.

• brainstorming

  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.

  skills/brainstorming/SKILL.md on GitHub (opens in a new tab)

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

  skills/dispatching-parallel-agents/SKILL.md on GitHub (opens in a new tab)

• executing-plans

  Use when you have a written implementation plan to execute in a separate session with review checkpoints

  skills/executing-plans/SKILL.md on GitHub (opens in a new tab)

• finishing-a-development-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

  skills/finishing-a-development-branch/SKILL.md on GitHub (opens in a new tab)

• jev-brainstorming

  Use before any creative architecture, feature design, or stack selection - explores requirements, generates 2-3 approaches, and uses TypeSafe Jev (jev-axi pick) to converge on the optimal technical decision

  skills/jev-brainstorming/SKILL.md on GitHub (opens in a new tab)

• jev-executing-plans

  Use when executing a written implementation plan - guides step-by-step TDD execution while enforcing jev-guard for command safety and git-jev for pre-commit diff screening

  skills/jev-executing-plans/SKILL.md on GitHub (opens in a new tab)

• jev-systematic-debugging

  Use when encountering any bug, test failure, or build error - enforces root-cause investigation using jev-axi triage for build errors and Jev Score for hypothesis ranking

  skills/jev-systematic-debugging/SKILL.md on GitHub (opens in a new tab)

• jev-using-superpowers

  Use when starting any non-trivial engineering conversation - establishes Jev-verified skill invocation, enforcing TypeSafe System One decisions, crate vetting, and completion gates

  skills/jev-using-superpowers/SKILL.md on GitHub (opens in a new tab)

• jev-verification

  Use before claiming work is complete, fixed, or passing - enforces fresh test evidence, supercov quality anti-pattern auditing, and limpet stop-policy checks before finishing a turn

  skills/jev-verification/SKILL.md on GitHub (opens in a new tab)

• jev-writing-plans

  Use when you have a spec or requirements for a multi-step task, before touching code - crafts bite-sized TDD plans and uses jev-scout to verify real crates/libraries, eliminating hallucinated packages

  skills/jev-writing-plans/SKILL.md on GitHub (opens in a new tab)

• receiving-code-review

  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

  skills/receiving-code-review/SKILL.md on GitHub (opens in a new tab)

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

  skills/requesting-code-review/SKILL.md on GitHub (opens in a new tab)

• subagent-driven-development

  Use when executing implementation plans with independent tasks in the current session

  skills/subagent-driven-development/SKILL.md on GitHub (opens in a new tab)

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

  skills/systematic-debugging/SKILL.md on GitHub (opens in a new tab)

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

  skills/test-driven-development/SKILL.md on GitHub (opens in a new tab)

• using-git-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

  skills/using-git-worktrees/SKILL.md on GitHub (opens in a new tab)

• using-superpowers

  Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

  skills/using-superpowers/SKILL.md on GitHub (opens in a new tab)

• verification-before-completion

  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

  skills/verification-before-completion/SKILL.md on GitHub (opens in a new tab)

• writing-plans

  Use when you have a spec or requirements for a multi-step task, before touching code

  skills/writing-plans/SKILL.md on GitHub (opens in a new tab)

• writing-skills

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

  skills/writing-skills/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• skillsby NVIDIA Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA,… 3.6k stars · 30 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• ui-ux-pro-max-skillby nextlevelbuilder An AI skill that provides design intelligence for building professional UI/UX across multiple platforms. 136k stars · 7 skills
• graphifyby Graphify-Labs Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Curs… 127k stars · 1 skill
• agent-skillsby addyosmani Production-grade engineering skills for AI coding agents. 107k stars · 25 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills