Developer plugin for Claude Code — slash commands, agents, and workflow tools
Skill Claude CodeCodex
Generate Architecture Decision Records that capture the reasoning behind technical decisions. Use when the user asks to "create an ADR", "document a decision", "record why we chose X", or discusses architectural trade-offs worth preserving.
Skill Claude CodeCodex
Audit whether another agent actually did what was asked, not just whether the code is good. Use to watch, audit, compare, or fix another agent's work: a Claude Code or Codex session, a transcript, a PR, a branch, a CI run, or a workflow run.
Skill Claude CodeCodex
Audit a workspace for recurring friction, pick the highest-leverage one, and build the automation that removes it. Use when the user asks "what should I automate", "what's wasting my time", "find the friction in my workflow", wants a self-improvement pass over their own tooling, or runs this on a recurring loop.
Skill Claude CodeCodex
Ultra-compressed response mode. Cuts token usage 75% while keeping full technical accuracy. Use when the user says "caveman", "caveman mode", "be brief", "less tokens", "compress output", or invokes /caveman.
Skill Claude CodeCodex
Review what agents accomplished, surface loose ends across sessions.
Skill Claude CodeCodex
Systematic debugging that applies the scientific method to failures. Use when the user says "debug this", "why is this failing", "help me find the bug", or is stuck on a problem and thrashing without progress.
Skill Claude CodeCodex
Intentional design thinking for interfaces, components, and systems. Use when the user asks to "build a UI", "design a page", "create a component", "make this look good", "design an API", "design a system", or any task where aesthetic or structural design decisions matter.
Skill Claude CodeCodex
Create Excalidraw diagrams programmatically. Use when the user wants architecture diagrams, flowcharts, or any visual diagram with a hand-drawn aesthetic, where editable output and drag-and-drop editing add value over Mermaid's text-only approach.
Skill Claude CodeCodex
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against their project's language and documented decisions, or asks to "grill me with docs" or…
Skill Claude CodeCodex
Evaluate and improve how information is organized for findability. Use when the user asks to "organize this", "restructure docs", "improve navigation", "where should this go", "review file structure", or when documentation grows beyond a single page.
Skill Claude CodeCodex
Find deepening opportunities in a codebase. Use when the user asks to "improve architecture", "find refactoring opportunities", "consolidate modules", "make code more testable", or wants the codebase made more AI-navigable.
Skill Claude CodeCodex
Create diagrams and visualizations using Mermaid.js v11 syntax. Use when generating flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, user journeys, timelines, or any of 24+ diagram types. Supports CLI rendering to SVG/PNG/PDF, theming, and configuration.
Skill Claude CodeCodex
Evaluate and improve names in code using naming as a design diagnostic. Use when the user asks to "name this", "rename", "review naming", "what should I call", struggles to name something, or when a code review surfaces vague or misleading names.
Skill Claude CodeCodex
Profiling methodology and optimization strategy for performance work. Use when the user asks to "make this faster", "optimize", "profile", "reduce latency", "fix slow", "improve throughput", or when investigating performance regressions.
Skill Claude CodeCodex
Apply Strunk's writing rules to prose: documentation, commits, error messages, UI text. Clearer, stronger, more professional. Also sharpens and tightens overlong drafts by subtraction.
Skill Claude CodeCodex
Systematic technical investigation: evidence gathering, option comparison, and actionable recommendations. Use when the user asks to "research X", "investigate Y", "compare X vs Y", "how does X work", or needs analysis of libraries, APIs, frameworks, or architectural approaches.
Skill Claude CodeCodex
Reflect on recent work—capture learnings and surface what to think about next.
Skill Claude CodeCodex
Framework for code review that captures context future maintainers need: concerns raised, alternatives rejected, risks accepted. Use for PRs, local changes, or architecture review when the decision matters more than the diff. Produces structured feedback with must-address issues, suggestions, and observations "for the…
Skill Claude CodeCodex
Post-op check for artifacts, damage, and stale references after agent work.
Skill Claude CodeCodex
Design test strategy using Beck's Test Desiderata — which properties matter, which tradeoffs to make. Use when the user asks "how should I test this", "what tests do I need", "review my test strategy", "is this well-tested", or when planning tests for a new feature or refactor.
Skill Claude CodeCodex
Survey the project and choose what to play next.
Skill Claude CodeCodex
Judgment linter for vibe-coded output: reads the energy of the code, not just correctness. Use when the user says "vibe check", "does this hold up", "sanity check this AI code", or after a fast generation session before committing.
Skill Claude CodeCodex
Turn a PR, branch, commit, or git diff into a structured visual recap so a reviewer scans the shape of the change before reading raw lines. Use when asked to "recap this PR/branch", "show me what changed", or to summarize a large multi-file diff at a higher altitude than line-by-line review.
Skill Claude CodeCodex
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable. Reach for it when authoring, pruning, or debugging a skill.