Skill Claude CodeCodex
Use when working on a Next.js App Router project that uses Prisma as the ORM — covers server component data fetching, singleton client setup, and type-safe query patterns.
Skill Claude CodeCodex
Use when performance is a real concern — measure first, isolate the bottleneck, and prove the improvement instead of guessing.
Skill Claude CodeCodex
Review a pull request from 6 perspectives (PM, Dev, QA, Security, DevOps, UX) for comprehensive, bias-free feedback.
Skill Claude CodeCodex
Use when a design question is still fuzzy — build a throwaway logic or UI prototype that answers one question fast, stays easy to run, and is meant to be deleted or absorbed.
Skill Claude CodeCodex
Use when adding or improving tests in a React project that uses Vitest — covers component testing with Testing Library, mocking hooks, and coverage configuration.
Skill Claude CodeCodex
Use when you have just received code review feedback (human or agent) and are about to act on it — verify each item against the codebase before implementing, and push back with technical reasoning instead of performative agreement.
Skill Claude CodeCodex
Use when code has grown complex, duplicated, or cluttered — clean up structure and remove dead code without changing observable behavior.
Skill Claude CodeCodex
Use when you want to check whether a code change follows the repository's documented conventions (Standards) and aligns with the originating issue or PRD (Spec) — compared against a pinned git reference.
Skill Claude CodeCodex
Use when you want to create a new SKILL.md file — describe a workflow and this skill generates a properly structured, frontmatter-complete SKILL.md that follows this repository's conventions.
Skill Claude CodeCodex
Use when implementing framework-specific or library-specific code — verify non-trivial APIs against official documentation before writing them, and record the source in task notes, docs, or the PR.
Skill Claude CodeCodex
Use before starting any non-trivial feature to write a technical spec first — prevents misaligned implementation and scope creep.
Skill Claude CodeCodex
Use when a bug is non-obvious or has resisted quick fixes — applies a 4-phase root cause analysis to find and permanently resolve the issue rather than patching symptoms.
Skill Claude CodeCodex
Use when starting a new feature or function to write failing tests first, then implement the minimal code to pass (Red→Green→Refactor).
Skill Claude Code
Use when you are lost in local code details — step one abstraction level up, map the owning modules and callers, and restate the system in project vocabulary.
Skill Claude CodeCodex
Use when you've shipped a feature, fix, or breaking change and need to update CHANGELOG.md — follows Keep a Changelog format and syncs version numbers across package manifests.
Skill Claude CodeCodex
Use when source code has changed and API docs are stale, or a new endpoint lacks documentation — generates accurate docs from implementation, not guesswork.
Skill Claude CodeCodex
Use when making significant, hard-to-reverse technical decisions to document context, rationale, and consequences as Architecture Decision Records (ADRs).
Skill Claude CodeCodex
Use when a user asks for a code tour, onboarding walkthrough, architecture tour, or PR tour — creates persona-targeted, step-by-step .tour files with real file and line anchors.
Skill Claude CodeCodex
Use when code has changed and documentation may be out of date — identifies stale docs, finds gaps between implementation and docs, and applies targeted updates.
Skill Claude CodeCodex
Use when a feature, module, or whole project needs missing documentation created from scratch - read the codebase, map the public surface with Diataxis (tutorial/how-to/reference/explanation), and generate the missing docs with cross-links.
Skill Claude CodeCodex
Use when you're ready to define a feature before building it — generates a structured PRD using Jobs-to-be-Done thinking, success metrics, and explicit scope boundaries.
Skill Claude CodeCodex
Use when you have a backlog of features and need to rank them for the next sprint — scores each feature using Impact × Confidence × Effort matrix with SQL tracking for transparent prioritization.
Skill Claude CodeCodex
Use when you're preparing to launch a product or feature publicly — builds a structured checklist covering positioning, distribution, messaging, and success metrics from private beta to GA.
Skill Claude CodeCodex
Use when you need to ensure every feature in the backlog connects to a measurable business outcome — applies Teresa Torres' OST framework to map outcomes → opportunities → solutions → experiments.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: