mirror of
https://github.com/duthaho/claudekit.git
synced 2026-06-12 21:24:56 +03:00
refactor: documentation for workflows: update Planning & Building, Reviewing & Shipping, and Testing & Debugging sections to enhance clarity and structure.
This commit is contained in:
duthaho
@@ -1,66 +1,77 @@
|
||||
---
|
||||
title: Introduction
|
||||
description: Learn what Claude Kit is and how it accelerates your development workflow.
|
||||
description: A verification-first engineering toolkit for Claude Code. Built for senior ICs and tech leads.
|
||||
---
|
||||
|
||||
# Introduction to Claude Kit
|
||||
|
||||
Claude Kit is an open-source Claude Code plugin that transforms Claude Code into a production-ready AI development team. It provides auto-triggered skills, specialized agents, and an interactive setup wizard that accelerates your development workflow.
|
||||
Claude Kit is a Claude Code plugin that adds a **verification-first engineering workflow** — every claim has evidence, every step has a checkpoint, every skill has a Rationalizations table that names the excuses an engineer makes to skip discipline. Built for senior ICs and tech leads who already know how to ship and want a workflow that keeps the bar high without ceremony.
|
||||
|
||||
## What is Claude Kit?
|
||||
|
||||
Claude Kit is a Claude Code plugin you install via a marketplace:
|
||||
A Claude Code plugin you install via the marketplace:
|
||||
|
||||
- **35 Skills** — Organized around a 6-phase development workflow. 13 user-invocable spine skills (typed as `/claudekit:<name>`) plus 22 supporting skills that auto-trigger by context
|
||||
- **24 Agents** — Specialized subagents for focused tasks (code review, security audit, database design, plan review, etc.)
|
||||
- **7 Modes** — Behavioral configurations installed via `/claudekit:init`
|
||||
- **Setup Wizard** — `/claudekit:init` scaffolds rules, modes, hooks, and MCP servers into your project
|
||||
- **15 Skills** — A 5-phase spine (Investigate → Design → Implement → Verify → Ship) plus 1 setup skill. All user-invocable as `/claudekit:<name>`. Each skill has 8 required sections including a Rationalizations table and Evidence Requirements.
|
||||
- **8 Agents** — Specialist subagents, one dispatcher each. No agent-bloat.
|
||||
- **5 Output Styles** — Native Claude Code output styles shipped with the plugin (Brainstorm, Deep Research, Implementation, Review, Token Efficient). Switch via `/config`.
|
||||
- **Setup Wizard** — `/claudekit:init` scaffolds rules, modes, hooks, and MCP servers into your project.
|
||||
|
||||
Skills activate automatically based on keywords in your conversation. No commands to memorize — just describe what you want to do.
|
||||
Skills activate automatically based on keywords in your conversation, or invoke directly by name.
|
||||
|
||||
## Why Claude Kit?
|
||||
|
||||
### The Problem with Raw Claude Code
|
||||
### The problem with raw Claude Code workflows
|
||||
|
||||
| Problem | Symptom |
|
||||
|---------|---------|
|
||||
| **Context Spirals** | Token budgets run out, Claude loses track of what it was doing |
|
||||
| **Inconsistent Output** | Quality varies wildly between sessions |
|
||||
| **No Structure** | Every session starts from scratch |
|
||||
| **Missing Expertise** | Claude doesn't know your team's patterns and standards |
|
||||
| **Self-reported "done"** | "Tests pass — trust me" claims that don't hold up |
|
||||
| **Symptom patches** | Bugs fixed at the line where the error appeared, not at the cause |
|
||||
| **Silent skip-it discipline** | Steps elided when the engineer thinks they "see the problem" |
|
||||
| **Vague plans** | "Implement the X" tasks that hide three sub-decisions nobody made |
|
||||
|
||||
### How Claude Kit Helps
|
||||
### What Claude Kit adds
|
||||
|
||||
1. **Auto-Triggered Skills** — Say "fix this bug" and systematic-debugging activates. Say "plan this" and brainstorming kicks in.
|
||||
2. **Specialized Agents** — Dispatch focused subagents for code review, testing, security audits, and more.
|
||||
3. **Consistent Quality** — Built-in TDD enforcement, verification before completion, and code review workflows.
|
||||
4. **Full Customization** — Add your own skills, agents, and modes.
|
||||
1. **Rationalizations tables** — Every skill names the excuses someone makes to skip a step ("I see the problem, let me just patch it") with rebuttals. The skill refuses to be skipped silently.
|
||||
2. **Evidence Requirements** — Every checkpoint produces an artifact you could paste into a code review. "It seems right" is failure.
|
||||
3. **Pre-completion gates** — `verification-gate` runs before any "done" claim. Tests run. Negative path checked. Non-IDE environment exercised. Original ask cross-checked.
|
||||
4. **Plan-review pipeline** — Two parallel reviewers (architecture + experience) score 5 sub-dimensions each, consolidate into one fix gate. Catches structural issues before code.
|
||||
5. **No founder voice** — No "ambitious vision," no "10x outcomes," no "delight." Engineering analogies, real file paths, real commands.
|
||||
|
||||
## How Skills Work
|
||||
## How skills work
|
||||
|
||||
Skills are the core of Claude Kit. They trigger automatically based on keywords:
|
||||
Skills trigger automatically based on keywords, or you can invoke them directly:
|
||||
|
||||
```
|
||||
You: "I need to add user authentication to our app"
|
||||
↓ triggers: brainstorming, writing-plans
|
||||
You: "Why is this endpoint returning 500s?"
|
||||
→ triggers: investigate-root-cause
|
||||
|
||||
You: "There's a TypeError in the UserService"
|
||||
↓ triggers: systematic-debugging, root-cause-tracing
|
||||
You: "How does the auth flow work?"
|
||||
→ triggers: map-codebase
|
||||
|
||||
You: "Let's write tests for the API endpoints"
|
||||
↓ triggers: testing, test-driven-development
|
||||
You: "Plan the migration to PostgreSQL"
|
||||
→ triggers: shape-spec, then write-plan, then plan-review
|
||||
|
||||
You: "Is this PR ready to merge?"
|
||||
→ triggers: verification-gate, then code-review-loop
|
||||
```
|
||||
|
||||
No slash commands needed — Claude reads your intent and activates the right skills.
|
||||
Or invoke directly: `/claudekit:investigate-root-cause`, `/claudekit:plan-review`, `/claudekit:verification-gate`.
|
||||
|
||||
## Who is Claude Kit For?
|
||||
## Who is Claude Kit for?
|
||||
|
||||
- **Solo developers** who want to ship faster
|
||||
- **Small teams (1-3 developers)** working on multi-stack projects
|
||||
- **Anyone using Claude Code** who wants more structure and consistency
|
||||
- **Senior ICs** who want a workflow that respects how they already think — not founder-flavored coaching, not "magical AI" framing.
|
||||
- **Tech leads** running plan reviews, code reviews, and engineering rigor across teams. Plan-review is the headline workflow.
|
||||
- **Anyone using Claude Code** who's tired of self-reported "done" claims and wants a discipline that produces evidence.
|
||||
|
||||
## Next Steps
|
||||
## What Claude Kit isn't for
|
||||
|
||||
1. [Install Claude Kit](/getting-started/installation/) — Install the plugin
|
||||
2. [Configuration](/getting-started/configuration/) — Run `/claudekit:init` to customize
|
||||
3. [Skills Reference](/reference/skills/) — Browse all 35 skills
|
||||
- Pure exploratory work where the goal is learning, not shipping.
|
||||
- One-line typo fixes that don't need a workflow.
|
||||
- Strategy / scope / "is this worth building" questions — that's a different lane.
|
||||
|
||||
## Next steps
|
||||
|
||||
1. [Install Claude Kit](/getting-started/installation/) — Install the plugin from the marketplace.
|
||||
2. [Configuration](/getting-started/configuration/) — Run `/claudekit:init` to scaffold rules, modes, hooks, and MCP servers.
|
||||
3. [Skills Reference](/reference/skills/) — Browse the 16 skills.
|
||||
4. [Agents Reference](/reference/agents/) — Browse the 8 specialist agents.
|
||||
|
||||
Reference in New Issue
Block a user