Skill Claude CodeCodex
Use when starting a new feature or significant change with no spec yet. Covers single-repo and multi-repo features. Do NOT use for typos, single-line fixes, or post-hoc documentation of finished work.
Skill Claude CodeCodex
Use when executing TDD cycles with coverage gates and quality checks. Do NOT use for general testing advice or test writing without the full TDD cycle.
Skill Claude CodeCodex
Use when the user provides a GitHub Issue URL and wants it fixed in the current repo. Do NOT use for feature requests without a clear bug or for PRs (use /code-review).
Skill Claude CodeCodex
Use when generating cross-team API handoff prompts to communicate changes between frontend and backend teams. Do NOT use for general API documentation or OpenAPI spec generation.
Skill Claude CodeCodex
Use when designing new API endpoints, defining module boundaries, or establishing contracts between teams. Do NOT use for general code quality — use api-change-documentation for handoffs.
Skill Claude CodeCodex
Use when performance requirements exist, profiling reveals bottlenecks, or Core Web Vitals need improvement. Do NOT use without evidence — premature optimization adds complexity.
Skill Claude CodeCodex
Use when writing PRDs, defining acceptance criteria, or structuring product requirements with observable-behavior focus. Do NOT use for technical specs, architecture docs, or API documentation.
Skill Claude CodeCodex
Use when the user wants a second opinion from another AI (Codex, Gemini, Copilot, Claude) on code or architecture. Read-only consultation — does not write code.
Skill Claude CodeCodex
Use when writing code that handles user input, auth, sessions, or external data. Covers OWASP prevention patterns. Do NOT use for general code quality or performance — see dedicated skills.
Skill Claude CodeCodex
Use when ready to ship code to remote — handles direct push to main and PR-based feature branch flows. Do NOT use for partial workflows like just committing or just pushing.
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: