Two things in one repo:
- Spec-driven development – a complete workflow where specs are the source of truth, code implements specs, and a suite of skills keeps everything in sync. From idea to spec to plan to implementation to review.
- General-purpose skills – tools that make Claude Code smarter regardless of your workflow: session retrospectives, structured interviews, multi-agent debugging, PR automation, and more.
Steal what's useful. Most people point Claude at this repo and cherry-pick what fits their workflow.
📘 Rolling out Claude Code at your organization? See the adoption recipes – opinionated patterns for project organization, design-to-execution workflow, AI security, and data proxies. Each recipe pairs an approachable description for non-technical readers with a technical reference for Claude.
The fastest path: install as a plugin and run the setup wizard.
/plugin install claude-skills@anutron/claude-skills
/claude-skills:setup
That gets you everything – skills, rules, hooks, status line – with interactive setup and auto-updates.
Three other paths exist: per-project sandbox (no global install), clone-and-promote (full control), and steal-the-pieces (cherry-pick). See the quick start guide for all four.
Six docs cover how the pieces fit together.
How the skills compose into a single development cycle. The skill cascade (brainstorm, execute-plan, ralph-review, spec-audit, bugbash, fixit), what each step produces, how it hands off to the next, and the WHY of specs as the source of truth.
The OpenSpec-based workflow: idea → spec → plan → test → implement → review. The full skill set, setup instructions, and how it degrades gracefully when not all pieces are present.
Read about spec-driven development →
The complete index of skills, grouped by purpose – development, discipline and orchestration, git/PR, and general utilities.
Version-controlled CLAUDE.md snippets with a compilation system. Each rule is a small focused snippet that compiles into the final CLAUDE.md – portable, reviewable, and template-variable-aware.
The set-topic skill plus the hook that ensures Claude actually uses it. Displays in the status line for easy session identification.
Three hooks that track which skills get invoked and which get loaded as dependencies. Pair with /skill-audit for periodic pruning recommendations.
Read about skill usage tracking →
A set of opinionated patterns for orgs scaling Claude Code adoption – covers personal workshops, the design-to-execution pipeline, AI security, and data proxies. Each recipe has an approachable orientation up top and a technical reference at the bottom for Claude.
See docs/claude-code-recipes/.
| File | Description |
|---|---|
| docs/permissions-guide.md | Recommended permission rules – reduce nagging, protect sensitive files, block destructive commands |
| docs/stack-spectrum.md | Tech stack tiers from lightweight to deployable – picking the right size for the job |
| docs/handling-api-keys.md | Best practice for API keys – keep them in a vault (1Password or macOS Keychain), never on disk or in git. Covers the op-secret.md 1Password loader (bin/op-secret.sh) |
| bin/statusline.sh | Custom Claude Code status line – git status, session topic, terminal title |
| Plugin | Source | What it does |
|---|---|---|
| pr-review-toolkit | claude-plugins-official |
Comprehensive PR review using specialized agents |
| commit-commands | claude-plugins-official |
Git workflow shortcuts – commit, push, PR creation |
| github | claude-plugins-official |
GitHub MCP integration – issues, PRs, code search |