Skill Claude Code
Structured 4-phase debugging process. Use when a bug is unclear, a fix has failed twice, or you're stuck on a problem instead of guessing randomly.
Personal Claude Code configuration (commands, agents, skills, plugins)
Skill Claude Code
Structured 4-phase debugging process. Use when a bug is unclear, a fix has failed twice, or you're stuck on a problem instead of guessing randomly.
Skill Claude Code
Define the technical stack and architecture for a project. Interactive session with the Architect agent.
Skill Claude Code
Enforce TDD (Red-Green-Refactor) for features, bug fixes, and refactoring. Use when writing new functionality, fixing bugs, or when the user explicitly asks for TDD.
Skill Claude Code
Intelligently update project documentation (CLAUDE.md, memory-bank/) based on recent changes. Use after implementing features, establishing new patterns, or when documentation needs to reflect current state.
Skill Claude Code
Update progress tracking files (progress.md and implementation plan). Use after completing tasks, implementing features, or when the user wants to record progress.
Skill Claude Code
Quick validation check returning pass/fail. Use AUTOMATICALLY before any git commit, before pushing code, when user asks "is it ready?", "can we commit?", "does it build?", "c'est prêt?", "on peut commit?", "ça build?", or wants a quick health check. Runs silently in background.
Skill Claude Code
Complete workflow to validate build, update documentation, update progress, and push changes. Use when finalizing work, before ending a session, or when the user says "finalize", "wrap up", or "ship it".
Skill Claude Code
Run lint, build, and E2E tests in sequence. Use when the user wants to validate their code, run tests, or check if everything works before committing.
Skill Claude Code
Create a new skill for the Claude Code config. Use when the user wants to add a new skill, command, or workflow to their configuration.
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: