Craft-Coder: Pair Programming with a Senior Dev
Master your craft through guided development, decision explanations, and TDD workflow.
Philosophy
vibe-coder: "Describe what you want" → [magic] → "Done!"
craft-coder: "Let's design together" → [dialogue] → "Here's why"
We explain WHAT we're doing and WHY.
Commands
| Command |
Description |
/craft {project} |
Guided project creation with explanations |
/craft {project} --learn |
Learning mode (detailed explanations) |
/craft {project} --fast |
Fast mode (minimal dialogue) |
/why |
Explain the last decision |
/why stack |
Why this technology stack? |
/why architecture |
Why this project structure? |
Quick Start
Start a new project
/craft notes-app
5-step guided process:
- Requirements gathering
- Architecture design (with rationale)
- Stack selection (with tradeoffs)
- Project initialization
- First feature implementation
Understand decisions
/why
Explains the most recent architectural decision.
/why stack
Shows why we chose this technology stack, what alternatives were considered, and trade-offs accepted.
Skills by Category
Backend
| Skill |
Description |
backend-core |
API design, authentication, security, databases |
backend-python |
FastAPI, Django, SQLAlchemy, async patterns |
backend-nodejs |
Express, NestJS, Prisma, TypeScript backend |
backend-rust |
Axum, Actix, SQLx, performance-critical services |
Frontend
| Skill |
Description |
frontend-react |
React 18+, hooks, state management, performance |
frontend-design |
Distinctive UI avoiding "AI slop" aesthetics |
theme-factory |
Color palettes, typography, design systems |
Quality & Testing
| Skill |
Description |
code-review |
PR review workflow, technical feedback |
testing-core |
Unit, integration, e2e testing strategies |
test-driven-development |
TDD cycle: red → green → refactor |
testing-anti-patterns |
Common testing mistakes to avoid |
Debugging
| Skill |
Description |
systematic-debugging |
Methodical bug investigation |
root-cause-tracing |
Find the actual source of issues |
defense-in-depth |
Prevent bugs from reaching production |
Documentation
| Skill |
Description |
decision-logger |
Log architectural decisions (ADR format) |
Modes
Learning Mode (--learn)
- Detailed explanations for every decision
- "Why?" sections included
- Links to learning resources
- Best for juniors and those learning new tech
Fast Mode (--fast)
- Skip explanations
- Use sensible defaults
- Minimal questions
- Best for experienced devs who want speed
Balanced Mode (default)
- Key decisions explained briefly
/why available for details- Good speed/understanding balance
- Best for most developers
Decision Records
All architectural decisions are logged to docs/DECISIONS.md in ADR format.
Example:
## ADR-001: Use Rust + Axum
**Context:** Need fast API with single binary deployment
**Decision:** Rust with Axum framework
**Why:** Meets <50ms requirement, compiles to single binary
**Alternatives:** Go (less type safety), Node (not single binary)
vs vibe-coder
| Aspect |
vibe-coder |
craft-coder |
| Decisions |
Automatic |
Explained |
| Errors |
Auto-fix |
Dialogue + options |
| Learning |
Hidden |
Built-in |
| Control |
Minimal |
Full |
| Speed |
Maximum |
Balanced |
| Audience |
Makers |
Developers |
Choose craft-coder when you want to:
- Understand architectural decisions
- Learn best practices
- Have control over technology choices
- Document decisions for your team
Choose vibe-coder when you want:
- Fastest path to MVP
- No technical decisions
- Just describe and ship
1---2name: craft-coder-help3description: Help and documentation for Craft-Coder plugin. Use when: user asks about available skills, commands, or how to use this plugin. Triggers: "help", "what can you do", "craft help", "как пользоваться".4---5
6# Craft-Coder: Pair Programming with a Senior Dev
7
8Master your craft through guided development, decision explanations, and TDD workflow.
9
10## Philosophy
11
12**vibe-coder:** "Describe what you want" → [magic] → "Done!"
13
14**craft-coder:** "Let's design together" → [dialogue] → "Here's why"
15
16We explain WHAT we're doing and WHY.
17
18## Commands
19
20| Command | Description |
21|---------|-------------|
22| `/craft {project}` | Guided project creation with explanations |
23| `/craft {project} --learn` | Learning mode (detailed explanations) |
24| `/craft {project} --fast` | Fast mode (minimal dialogue) |
25| `/why` | Explain the last decision |
26| `/why stack` | Why this technology stack? |
27| `/why architecture` | Why this project structure? |
28
29## Quick Start
30
31### Start a new project
32```
33/craft notes-app
34```
355-step guided process:
361. Requirements gathering
372. Architecture design (with rationale)
383. Stack selection (with tradeoffs)
394. Project initialization
405. First feature implementation
41
42### Understand decisions
43```
44/why
45```
46Explains the most recent architectural decision.
47
48```
49/why stack
50```
51Shows why we chose this technology stack, what alternatives were considered, and trade-offs accepted.
52
53## Skills by Category
54
55### Backend
56| Skill | Description |
57|-------|-------------|
58| `backend-core` | API design, authentication, security, databases |
59| `backend-python` | FastAPI, Django, SQLAlchemy, async patterns |
60| `backend-nodejs` | Express, NestJS, Prisma, TypeScript backend |
61| `backend-rust` | Axum, Actix, SQLx, performance-critical services |
62
63### Frontend
64| Skill | Description |
65|-------|-------------|
66| `frontend-react` | React 18+, hooks, state management, performance |
67| `frontend-design` | Distinctive UI avoiding "AI slop" aesthetics |
68| `theme-factory` | Color palettes, typography, design systems |
69
70### Quality & Testing
71| Skill | Description |
72|-------|-------------|
73| `code-review` | PR review workflow, technical feedback |
74| `testing-core` | Unit, integration, e2e testing strategies |
75| `test-driven-development` | TDD cycle: red → green → refactor |
76| `testing-anti-patterns` | Common testing mistakes to avoid |
77
78### Debugging
79| Skill | Description |
80|-------|-------------|
81| `systematic-debugging` | Methodical bug investigation |
82| `root-cause-tracing` | Find the actual source of issues |
83| `defense-in-depth` | Prevent bugs from reaching production |
84
85### Documentation
86| Skill | Description |
87|-------|-------------|
88| `decision-logger` | Log architectural decisions (ADR format) |
89
90## Modes
91
92### Learning Mode (`--learn`)
93- Detailed explanations for every decision
94- "Why?" sections included
95- Links to learning resources
96- Best for juniors and those learning new tech
97
98### Fast Mode (`--fast`)
99- Skip explanations
100- Use sensible defaults
101- Minimal questions
102- Best for experienced devs who want speed
103
104### Balanced Mode (default)
105- Key decisions explained briefly
106- `/why` available for details
107- Good speed/understanding balance
108- Best for most developers
109
110## Decision Records
111
112All architectural decisions are logged to `docs/DECISIONS.md` in ADR format.
113
114Example:
115```markdown
116## ADR-001: Use Rust + Axum
117
118**Context:** Need fast API with single binary deployment
119
120**Decision:** Rust with Axum framework
121
122**Why:** Meets <50ms requirement, compiles to single binary
123
124**Alternatives:** Go (less type safety), Node (not single binary)
125```
126
127## vs vibe-coder
128
129| Aspect | vibe-coder | craft-coder |
130|--------|------------|-------------|
131| Decisions | Automatic | Explained |
132| Errors | Auto-fix | Dialogue + options |
133| Learning | Hidden | Built-in |
134| Control | Minimal | Full |
135| Speed | Maximum | Balanced |
136| Audience | Makers | Developers |
137
138Choose **craft-coder** when you want to:
139- Understand architectural decisions
140- Learn best practices
141- Have control over technology choices
142- Document decisions for your team
143
144Choose **vibe-coder** when you want:
145- Fastest path to MVP
146- No technical decisions
147- Just describe and ship
majiayu000