Skill Explorer
Interactive index of every audit, workflow, meta, and wiki skill — filter by category, search by name or description.
The kit ships 23 skills (20 base + 3 wiki module). The sidebar groups them by category, but if you want to filter and search, this page is for you.
Each skill is invoked with /skill-name in a Claude Code session. Click any card to read the full guide.
- Audit
/accessibility-auditAccessibility Audit
Audits UI code for WCAG 2.1 AA compliance including semantics, keyboard navigation, color contrast, and ARIA usage
- Audit
/architecture-reviewArchitecture Review
Reviews codebase architecture for SOLID violations, dependency health, module boundaries, and structural issues
- Audit
/code-quality-auditCode Quality Audit
Audits codebase for code smells, error handling gaps, and maintainability issues with actionable fix recommendations
- Audit
/dead-code-auditDead Code Audit
Detects unused code including unreferenced functions, dead imports, orphan files, and unreachable branches
- Audit
/deepening-reviewDeepening Review
Surface shallow modules as deepening candidates, then grill the chosen one interactively — depth/seam paradigm. Use for testability and AI-navigability when modules feel pass-through or fragmented.
- Audit
/dependency-auditDependency Audit
Audits project dependencies for security vulnerabilities, outdated versions, license risks, and bloat
- Audit
/design-reviewDesign Review
Reviews UI implementation for design consistency, visual quality, AI slop detection, and responsive behavior
- Audit
/documentation-auditDocumentation Audit
Audits code documentation quality including inline comments, API docs, README completeness, and doc-code sync
- Audit
/interface-designInterface Design
Design It Twice — spawn 3-4 parallel sub-agents producing radically different interfaces for a module, then compare on depth, locality, and seam placement. Use before committing to a new interface.
- Audit
/performance-auditPerformance Audit
Identifies performance bottlenecks including rendering, startup, memory, and I/O issues across any tech stack
- Audit
/project-health-reportProject Health Report
Generates a comprehensive project health report covering code quality, architecture, testing, dependencies, and documentation
- Audit
/refactoring-guideRefactoring Guide
Provides Fowler-based refactoring recommendations with specific techniques, risk assessment, and step-by-step execution plans
- Audit
/testing-auditTesting Audit
Audits test suite for coverage gaps, test quality, flaky tests, and testing strategy alignment
- Workflow
/debugDebug
Systematic root-cause debugging with evidence-before-fix enforcement and regression test generation
- Workflow
/office-hoursOffice Hours
Pre-coding product validation using forcing functions — clarify what to build and why before writing any code
- Workflow
/retroRetro
Weekly retrospective with session analytics, LOC metrics, pattern detection, and persistent history
- Workflow
/shape-specShape Spec
Creates a timestamped feature spec folder with structured plan, decisions, and references for multi-session features
- Workflow
/shipShip
Full deployment pipeline — tests, coverage audit, CHANGELOG generation, bisectable commits, and PR creation
- Meta
/skill-extractorSkill Extractor
Extracts non-obvious knowledge discovered during sessions into reusable SKILL.md files
- Meta
/skill-generatorSkill Generator
Generates project-specific coding skills by analyzing tech stack, architecture, and constraints
- Wiki Module
/wiki-briefingWiki Briefing
Morning briefing from the knowledge wiki — recent activity, new sources, open actions, and key updates
requires --wiki flag
- Wiki Module
/wiki-ingestWiki Ingest
Ingest a new source into the knowledge wiki — read, summarize, cross-reference, and update index
requires --wiki flag
- Wiki Module
/wiki-lintWiki Lint
Health-check the knowledge wiki — find contradictions, orphans, missing pages, and stale content
requires --wiki flag
How skills load
You don't manually load skills — Claude Code loads them automatically when the frontmatter description semantically matches the task. So the description on each card is also what determines whether Claude picks the skill up.
Bad description → skill never matches.
Good description → skill activates exactly when relevant.
See the Skills guide for how to write your own.
Categories at a glance
| Category | What it is | Examples |
|---|---|---|
| Audit | Read-only analysis with structured findings | code-quality-audit, architecture-review, dependency-audit |
| Workflow | Process / lifecycle skills you invoke during work | debug, ship, office-hours, retro |
| Meta | Skills that produce other skills | skill-extractor, skill-generator |
| Wiki Module | Optional knowledge wiki ops (requires --wiki install flag) | wiki-ingest, wiki-lint, wiki-briefing |