Explore skills

Use when implementing any feature or bugfix, before writing implementation code

Comprehensive Rust coding guidelines with 179 rules across 14 categories, covering ownership, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Use these guidelines when writing, reviewing, or refactoring Rust code.

Generate conventional commit message based on git changes

Generate E2E and unit test code from requirements using Playwright, delegated to Codex. Use when writing tests, checking acceptance criteria coverage, or running /test.

Run code review against design documents, checking acceptance criteria, security, performance, and test coverage. Use when reviewing implementation quality or running /review.

Meta-skill that teaches how to create effective Claude Code skills. Covers anatomy, progressive disclosure, validation, and packaging.

Automated code review → fix → re-review loop. Runs until score >9 or max 3 rounds. Fixes Critical/Major/Warnings only — Suggestions are deferred.

Sync documentation with code changes. Auto-detects scope from git diff, updates tier 1-4 docs (core, architecture, journey, config), verifies stats. Phase D of /ship pipeline.

Debug issues through structured investigation, failing test creation, and targeted fixes. Use when the user provides an error message, traceback, steps-to-reproduce, or describes unexpected behavior.

Run the full JTBD analysis pipeline on a batch of interview transcripts. Analyzes each transcript into a Switch analysis, then finds cross-interview patterns. Accepts a directory of transcript files or Fireflies meeting IDs. Use when: "analyze all interviews", "jtbd pipeline", "batch analysis", "process transcripts".

Lint a BDK agent file for best practices and portability. Use when reviewing, creating, or editing an agent (agents/*.md) to verify it meets BDK conventions. Trigger on phrases like "check this agent", "verify agent", "lint agent", or when about to commit a new agent.

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"