clauderc 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +221 -0
- package/bin/cli.js +802 -0
- package/package.json +44 -0
- package/src/detector.js +387 -0
- package/src/project.js +435 -0
- package/src/stacks.js +299 -0
- package/templates/agents/project-setup-wizard.md +230 -0
- package/templates/commands/lint.md +33 -0
- package/templates/commands/pr.md +46 -0
- package/templates/commands/setup.md +51 -0
- package/templates/commands/test.md +33 -0
- package/templates/commands/verify.md +69 -0
- package/templates/manifest.json +93 -0
- package/templates/project-setup/AGENTS_TEMPLATE.md +100 -0
- package/templates/project-setup/CLAUDE_MD_TEMPLATE.md +49 -0
- package/templates/project-setup/COMMANDS_TEMPLATE.md +92 -0
- package/templates/project-setup/SKILLS_TEMPLATE.md +113 -0
- package/templates/project-setup/TEAM_DOCS_TEMPLATE.md +102 -0
- package/templates/skills/claude-code-templates/SKILL.md +260 -0
- package/templates/skills/project-analysis/SKILL.md +184 -0
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
# Full verification before commit/PR
|
|
2
|
+
|
|
3
|
+
Run all checks: lint, typecheck, test, build.
|
|
4
|
+
|
|
5
|
+
## When to use
|
|
6
|
+
- Before committing changes
|
|
7
|
+
- Before creating a PR
|
|
8
|
+
- After major refactoring
|
|
9
|
+
|
|
10
|
+
## Implementation
|
|
11
|
+
```bash
|
|
12
|
+
echo "🔍 Running verification..."
|
|
13
|
+
|
|
14
|
+
# Node.js
|
|
15
|
+
if [ -f "package.json" ]; then
|
|
16
|
+
echo "→ Lint"
|
|
17
|
+
npm run lint 2>/dev/null || true
|
|
18
|
+
|
|
19
|
+
echo "→ Typecheck"
|
|
20
|
+
npm run typecheck 2>/dev/null || npx tsc --noEmit 2>/dev/null || true
|
|
21
|
+
|
|
22
|
+
echo "→ Test"
|
|
23
|
+
npm test
|
|
24
|
+
|
|
25
|
+
echo "→ Build"
|
|
26
|
+
npm run build 2>/dev/null || true
|
|
27
|
+
fi
|
|
28
|
+
|
|
29
|
+
# Python
|
|
30
|
+
if [ -f "pyproject.toml" ]; then
|
|
31
|
+
echo "→ Lint"
|
|
32
|
+
ruff check .
|
|
33
|
+
|
|
34
|
+
echo "→ Type check"
|
|
35
|
+
mypy . 2>/dev/null || true
|
|
36
|
+
|
|
37
|
+
echo "→ Test"
|
|
38
|
+
pytest
|
|
39
|
+
fi
|
|
40
|
+
|
|
41
|
+
# Go
|
|
42
|
+
if [ -f "go.mod" ]; then
|
|
43
|
+
echo "→ Lint"
|
|
44
|
+
golangci-lint run
|
|
45
|
+
|
|
46
|
+
echo "→ Test"
|
|
47
|
+
go test ./...
|
|
48
|
+
|
|
49
|
+
echo "→ Build"
|
|
50
|
+
go build ./...
|
|
51
|
+
fi
|
|
52
|
+
|
|
53
|
+
# Rust
|
|
54
|
+
if [ -f "Cargo.toml" ]; then
|
|
55
|
+
echo "→ Format check"
|
|
56
|
+
cargo fmt --check
|
|
57
|
+
|
|
58
|
+
echo "→ Clippy"
|
|
59
|
+
cargo clippy
|
|
60
|
+
|
|
61
|
+
echo "→ Test"
|
|
62
|
+
cargo test
|
|
63
|
+
|
|
64
|
+
echo "→ Build"
|
|
65
|
+
cargo build
|
|
66
|
+
fi
|
|
67
|
+
|
|
68
|
+
echo "✅ Verification complete"
|
|
69
|
+
```
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "1.0.0",
|
|
3
|
+
"generatedAt": "2025-01-24T00:00:00.000Z",
|
|
4
|
+
"files": {
|
|
5
|
+
"agents/project-setup-wizard.md": {
|
|
6
|
+
"version": "1.0.0",
|
|
7
|
+
"added": "1.0.0",
|
|
8
|
+
"description": "Setup wizard agent for configuring Claude Code in any project"
|
|
9
|
+
},
|
|
10
|
+
"skills/project-analysis/SKILL.md": {
|
|
11
|
+
"version": "1.0.0",
|
|
12
|
+
"added": "1.0.0",
|
|
13
|
+
"description": "Systematic project analysis skill"
|
|
14
|
+
},
|
|
15
|
+
"skills/claude-code-templates/SKILL.md": {
|
|
16
|
+
"version": "1.0.0",
|
|
17
|
+
"added": "1.0.0",
|
|
18
|
+
"description": "Quick reference for Claude Code templates"
|
|
19
|
+
},
|
|
20
|
+
"commands/test.md": {
|
|
21
|
+
"version": "1.0.0",
|
|
22
|
+
"added": "1.0.0",
|
|
23
|
+
"description": "Run project tests"
|
|
24
|
+
},
|
|
25
|
+
"commands/lint.md": {
|
|
26
|
+
"version": "1.0.0",
|
|
27
|
+
"added": "1.0.0",
|
|
28
|
+
"description": "Run linter and formatter"
|
|
29
|
+
},
|
|
30
|
+
"commands/verify.md": {
|
|
31
|
+
"version": "1.0.0",
|
|
32
|
+
"added": "1.0.0",
|
|
33
|
+
"description": "Full verification before commit/PR"
|
|
34
|
+
},
|
|
35
|
+
"commands/pr.md": {
|
|
36
|
+
"version": "1.0.0",
|
|
37
|
+
"added": "1.0.0",
|
|
38
|
+
"description": "Create a Pull Request"
|
|
39
|
+
},
|
|
40
|
+
"commands/setup.md": {
|
|
41
|
+
"version": "1.0.0",
|
|
42
|
+
"added": "1.0.0",
|
|
43
|
+
"description": "Project setup and dependency installation"
|
|
44
|
+
},
|
|
45
|
+
"templates/project-setup/CLAUDE_MD_TEMPLATE.md": {
|
|
46
|
+
"version": "1.0.0",
|
|
47
|
+
"added": "1.0.0",
|
|
48
|
+
"description": "Template for CLAUDE.md files"
|
|
49
|
+
},
|
|
50
|
+
"templates/project-setup/COMMANDS_TEMPLATE.md": {
|
|
51
|
+
"version": "1.0.0",
|
|
52
|
+
"added": "1.0.0",
|
|
53
|
+
"description": "Template for slash commands"
|
|
54
|
+
},
|
|
55
|
+
"templates/project-setup/SKILLS_TEMPLATE.md": {
|
|
56
|
+
"version": "1.0.0",
|
|
57
|
+
"added": "1.0.0",
|
|
58
|
+
"description": "Template for skills"
|
|
59
|
+
},
|
|
60
|
+
"templates/project-setup/AGENTS_TEMPLATE.md": {
|
|
61
|
+
"version": "1.0.0",
|
|
62
|
+
"added": "1.0.0",
|
|
63
|
+
"description": "Template for subagents"
|
|
64
|
+
},
|
|
65
|
+
"templates/project-setup/TEAM_DOCS_TEMPLATE.md": {
|
|
66
|
+
"version": "1.0.0",
|
|
67
|
+
"added": "1.0.0",
|
|
68
|
+
"description": "Template for team documentation"
|
|
69
|
+
}
|
|
70
|
+
},
|
|
71
|
+
"changelog": [
|
|
72
|
+
{
|
|
73
|
+
"version": "1.0.0",
|
|
74
|
+
"date": "2025-01-24",
|
|
75
|
+
"changes": {
|
|
76
|
+
"added": [
|
|
77
|
+
"agents/project-setup-wizard.md - Setup wizard agent",
|
|
78
|
+
"skills/project-analysis/SKILL.md - Project analysis skill",
|
|
79
|
+
"skills/claude-code-templates/SKILL.md - Templates reference skill",
|
|
80
|
+
"commands/test.md - Test command",
|
|
81
|
+
"commands/lint.md - Lint command",
|
|
82
|
+
"commands/verify.md - Verify command",
|
|
83
|
+
"commands/pr.md - PR command",
|
|
84
|
+
"commands/setup.md - Setup command",
|
|
85
|
+
"templates/project-setup/* - All project setup templates"
|
|
86
|
+
],
|
|
87
|
+
"changed": [],
|
|
88
|
+
"removed": [],
|
|
89
|
+
"deprecated": []
|
|
90
|
+
}
|
|
91
|
+
}
|
|
92
|
+
]
|
|
93
|
+
}
|
|
@@ -0,0 +1,100 @@
|
|
|
1
|
+
# Subagent Templates
|
|
2
|
+
|
|
3
|
+
## security-reviewer.md
|
|
4
|
+
|
|
5
|
+
```markdown
|
|
6
|
+
---
|
|
7
|
+
name: security-reviewer
|
|
8
|
+
description: Review code for security vulnerabilities
|
|
9
|
+
model: inherit
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
You are a SECURITY REVIEWER.
|
|
13
|
+
|
|
14
|
+
## Checklist
|
|
15
|
+
- [ ] No SQL/NoSQL injection vectors
|
|
16
|
+
- [ ] Input validation on user inputs
|
|
17
|
+
- [ ] Auth checks on protected routes
|
|
18
|
+
- [ ] No secrets in code
|
|
19
|
+
- [ ] Dependencies have no critical CVEs
|
|
20
|
+
- [ ] Error messages don't leak info
|
|
21
|
+
- [ ] HTTPS enforced
|
|
22
|
+
- [ ] CORS properly configured
|
|
23
|
+
|
|
24
|
+
## Output Format
|
|
25
|
+
|
|
26
|
+
### Critical Issues
|
|
27
|
+
- [file:line] Description
|
|
28
|
+
|
|
29
|
+
### Warnings
|
|
30
|
+
- [file:line] Description
|
|
31
|
+
|
|
32
|
+
### Good Practices Found
|
|
33
|
+
- Description
|
|
34
|
+
|
|
35
|
+
### Recommendations
|
|
36
|
+
- Suggestion
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## test-writer.md
|
|
42
|
+
|
|
43
|
+
```markdown
|
|
44
|
+
---
|
|
45
|
+
name: test-writer
|
|
46
|
+
description: Write comprehensive tests for code
|
|
47
|
+
model: inherit
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
You are a TEST WRITER specialist.
|
|
51
|
+
|
|
52
|
+
## Approach
|
|
53
|
+
1. Analyze code to understand behavior
|
|
54
|
+
2. Identify edge cases
|
|
55
|
+
3. Write tests following project conventions
|
|
56
|
+
4. Ensure good coverage
|
|
57
|
+
|
|
58
|
+
## Test Categories
|
|
59
|
+
- **Happy path**: Normal expected usage
|
|
60
|
+
- **Edge cases**: Boundaries, empty inputs, nulls
|
|
61
|
+
- **Error cases**: Invalid inputs, failures
|
|
62
|
+
- **Integration**: Component interactions
|
|
63
|
+
|
|
64
|
+
## Output
|
|
65
|
+
- Tests in project's test framework
|
|
66
|
+
- Clear test names describing behavior
|
|
67
|
+
- Proper setup/teardown
|
|
68
|
+
- Mocks where appropriate
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
|
|
73
|
+
## code-quality.md
|
|
74
|
+
|
|
75
|
+
```markdown
|
|
76
|
+
---
|
|
77
|
+
name: code-quality
|
|
78
|
+
description: Review code for quality and maintainability
|
|
79
|
+
model: inherit
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
You are a CODE QUALITY reviewer.
|
|
83
|
+
|
|
84
|
+
## Review Areas
|
|
85
|
+
1. **Readability**: Clear names, comments where needed
|
|
86
|
+
2. **Maintainability**: DRY, single responsibility
|
|
87
|
+
3. **Performance**: Obvious inefficiencies
|
|
88
|
+
4. **Patterns**: Following project conventions
|
|
89
|
+
|
|
90
|
+
## Output Format
|
|
91
|
+
|
|
92
|
+
### Issues Found
|
|
93
|
+
- [severity] [file:line] Description
|
|
94
|
+
|
|
95
|
+
### Suggestions
|
|
96
|
+
- Improvement opportunity
|
|
97
|
+
|
|
98
|
+
### Positive Notes
|
|
99
|
+
- Good patterns observed
|
|
100
|
+
```
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# CLAUDE.md Template
|
|
2
|
+
|
|
3
|
+
Use this template as base for generating project-specific CLAUDE.md files.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
```markdown
|
|
8
|
+
# {{PROJECT_NAME}}
|
|
9
|
+
|
|
10
|
+
## Stack
|
|
11
|
+
{{STACK_SUMMARY}}
|
|
12
|
+
|
|
13
|
+
## Commands
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
# Dev
|
|
17
|
+
{{DEV_COMMANDS}}
|
|
18
|
+
|
|
19
|
+
# Test
|
|
20
|
+
{{TEST_COMMANDS}}
|
|
21
|
+
|
|
22
|
+
# Build
|
|
23
|
+
{{BUILD_COMMANDS}}
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
## Code Style
|
|
27
|
+
{{CODE_STYLE_RULES}}
|
|
28
|
+
|
|
29
|
+
## Workflow
|
|
30
|
+
- Plan Mode for: refactors > 3 files, new features, architecture changes
|
|
31
|
+
- Always run `{{VERIFY_COMMAND}}` before commit
|
|
32
|
+
- Parallel work OK for: independent modules, test files, docs
|
|
33
|
+
|
|
34
|
+
## Architecture
|
|
35
|
+
{{ARCHITECTURE_NOTES}}
|
|
36
|
+
|
|
37
|
+
## Docs
|
|
38
|
+
{{DOC_REFERENCES}}
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
## Guidelines
|
|
44
|
+
|
|
45
|
+
1. **Keep it under 100 lines** - Be concise, link to detailed docs
|
|
46
|
+
2. **Commands must be copy-pasteable** - Test them before adding
|
|
47
|
+
3. **Focus on what's different** - Don't repeat language defaults
|
|
48
|
+
4. **Use @imports for details** - `@docs/architecture.md` instead of inline
|
|
49
|
+
5. **Update the date** - Add `Last updated: YYYY-MM-DD` at bottom
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# Slash Commands Templates
|
|
2
|
+
|
|
3
|
+
## /test.md
|
|
4
|
+
|
|
5
|
+
```markdown
|
|
6
|
+
Run project test suite.
|
|
7
|
+
|
|
8
|
+
## Steps
|
|
9
|
+
1. Execute test command for this project
|
|
10
|
+
2. Report results with coverage if available
|
|
11
|
+
3. Highlight failures with context
|
|
12
|
+
|
|
13
|
+
## Implementation
|
|
14
|
+
\`\`\`bash
|
|
15
|
+
{{TEST_COMMAND}}
|
|
16
|
+
\`\`\`
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## /lint.md
|
|
22
|
+
|
|
23
|
+
```markdown
|
|
24
|
+
Check and fix code quality issues.
|
|
25
|
+
|
|
26
|
+
## Steps
|
|
27
|
+
1. Run linter with auto-fix
|
|
28
|
+
2. Run formatter
|
|
29
|
+
3. Report remaining issues
|
|
30
|
+
|
|
31
|
+
## Implementation
|
|
32
|
+
\`\`\`bash
|
|
33
|
+
{{LINT_COMMAND}}
|
|
34
|
+
\`\`\`
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
---
|
|
38
|
+
|
|
39
|
+
## /verify.md
|
|
40
|
+
|
|
41
|
+
```markdown
|
|
42
|
+
Full project validation before commit/PR.
|
|
43
|
+
|
|
44
|
+
## Steps
|
|
45
|
+
1. Run linter
|
|
46
|
+
2. Run tests
|
|
47
|
+
3. Run build
|
|
48
|
+
4. Report any failures
|
|
49
|
+
|
|
50
|
+
## Implementation
|
|
51
|
+
\`\`\`bash
|
|
52
|
+
{{LINT_COMMAND}} && {{TEST_COMMAND}} && {{BUILD_COMMAND}}
|
|
53
|
+
\`\`\`
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
---
|
|
57
|
+
|
|
58
|
+
## /pr.md
|
|
59
|
+
|
|
60
|
+
```markdown
|
|
61
|
+
Create a pull request with auto-generated description.
|
|
62
|
+
|
|
63
|
+
## Steps
|
|
64
|
+
1. Check git status
|
|
65
|
+
2. Analyze commits since branch point
|
|
66
|
+
3. Generate PR description
|
|
67
|
+
4. Create PR using gh CLI
|
|
68
|
+
|
|
69
|
+
## Prerequisites
|
|
70
|
+
- GitHub CLI installed and authenticated
|
|
71
|
+
- Clean working directory (all changes committed)
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
---
|
|
75
|
+
|
|
76
|
+
## /setup.md
|
|
77
|
+
|
|
78
|
+
```markdown
|
|
79
|
+
Setup development environment.
|
|
80
|
+
|
|
81
|
+
## Steps
|
|
82
|
+
1. Install dependencies
|
|
83
|
+
2. Setup environment variables (from .env.example if exists)
|
|
84
|
+
3. Run database migrations if applicable
|
|
85
|
+
4. Verify setup with quick test
|
|
86
|
+
|
|
87
|
+
## Implementation
|
|
88
|
+
\`\`\`bash
|
|
89
|
+
{{INSTALL_COMMAND}}
|
|
90
|
+
{{SETUP_COMMANDS}}
|
|
91
|
+
\`\`\`
|
|
92
|
+
```
|
|
@@ -0,0 +1,113 @@
|
|
|
1
|
+
# Skills Templates
|
|
2
|
+
|
|
3
|
+
## debug-workflow/SKILL.md
|
|
4
|
+
|
|
5
|
+
```markdown
|
|
6
|
+
# Debug Workflow
|
|
7
|
+
|
|
8
|
+
Systematic approach to debugging issues.
|
|
9
|
+
|
|
10
|
+
## When to Use
|
|
11
|
+
- Bug reports
|
|
12
|
+
- Failing tests without obvious cause
|
|
13
|
+
- Performance issues
|
|
14
|
+
- Production errors
|
|
15
|
+
|
|
16
|
+
## Workflow
|
|
17
|
+
|
|
18
|
+
### 1. Reproduce
|
|
19
|
+
- [ ] Create minimal reproduction
|
|
20
|
+
- [ ] Document steps to reproduce
|
|
21
|
+
- [ ] Identify expected vs actual behavior
|
|
22
|
+
|
|
23
|
+
### 2. Isolate
|
|
24
|
+
- [ ] Add debug logging
|
|
25
|
+
- [ ] Check recent changes in related files
|
|
26
|
+
- [ ] Bisect if needed: `git bisect`
|
|
27
|
+
|
|
28
|
+
### 3. Fix
|
|
29
|
+
- [ ] Implement minimal fix
|
|
30
|
+
- [ ] Add regression test
|
|
31
|
+
- [ ] Verify locally
|
|
32
|
+
|
|
33
|
+
### 4. Validate
|
|
34
|
+
- [ ] Run full test suite
|
|
35
|
+
- [ ] Check for side effects
|
|
36
|
+
- [ ] Update docs if needed
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## verification-workflow/SKILL.md
|
|
42
|
+
|
|
43
|
+
```markdown
|
|
44
|
+
# Verification-First Development
|
|
45
|
+
|
|
46
|
+
Write Test -> Write Code -> Verify
|
|
47
|
+
|
|
48
|
+
## Workflow
|
|
49
|
+
|
|
50
|
+
### 1. Write Test First
|
|
51
|
+
Create failing test that defines expected behavior.
|
|
52
|
+
|
|
53
|
+
### 2. Implement
|
|
54
|
+
Write minimal code to make test pass.
|
|
55
|
+
|
|
56
|
+
### 3. Verify
|
|
57
|
+
\`\`\`bash
|
|
58
|
+
/test # Should pass
|
|
59
|
+
/lint # Should pass
|
|
60
|
+
/verify # Full validation
|
|
61
|
+
\`\`\`
|
|
62
|
+
|
|
63
|
+
### 4. Refactor (if needed)
|
|
64
|
+
Improve code while keeping tests green.
|
|
65
|
+
|
|
66
|
+
## Checklist Before Commit
|
|
67
|
+
- [ ] All tests pass
|
|
68
|
+
- [ ] Linter passes
|
|
69
|
+
- [ ] Build succeeds
|
|
70
|
+
- [ ] Feature works (manual test)
|
|
71
|
+
- [ ] Docs updated
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
---
|
|
75
|
+
|
|
76
|
+
## parallel-work/SKILL.md
|
|
77
|
+
|
|
78
|
+
```markdown
|
|
79
|
+
# Parallel Work with Multiple Claudes
|
|
80
|
+
|
|
81
|
+
## When to Parallelize
|
|
82
|
+
- Independent test files
|
|
83
|
+
- Separate features/modules
|
|
84
|
+
- Documentation updates
|
|
85
|
+
- Code review of different areas
|
|
86
|
+
|
|
87
|
+
## When NOT to Parallelize
|
|
88
|
+
- Interdependent changes
|
|
89
|
+
- Database migrations
|
|
90
|
+
- Breaking API changes
|
|
91
|
+
- Cross-cutting refactors
|
|
92
|
+
|
|
93
|
+
## How To
|
|
94
|
+
|
|
95
|
+
### Using Worktrees (Recommended)
|
|
96
|
+
\`\`\`bash
|
|
97
|
+
claude --worktree feature-auth
|
|
98
|
+
claude --worktree feature-dashboard
|
|
99
|
+
claude --worktree docs-update
|
|
100
|
+
\`\`\`
|
|
101
|
+
|
|
102
|
+
### Patterns
|
|
103
|
+
|
|
104
|
+
**Test Suite Split**
|
|
105
|
+
- Claude 1: Unit tests (src/utils)
|
|
106
|
+
- Claude 2: Unit tests (src/components)
|
|
107
|
+
- Claude 3: Integration tests
|
|
108
|
+
|
|
109
|
+
**Feature Development**
|
|
110
|
+
- Claude 1: Backend API
|
|
111
|
+
- Claude 2: Frontend UI
|
|
112
|
+
- Claude 3: Tests + Docs
|
|
113
|
+
```
|
|
@@ -0,0 +1,102 @@
|
|
|
1
|
+
# Team Documentation Templates
|
|
2
|
+
|
|
3
|
+
## CLAUDE_CODE_GUIDE.md
|
|
4
|
+
|
|
5
|
+
```markdown
|
|
6
|
+
# Claude Code Guide - {{PROJECT_NAME}}
|
|
7
|
+
|
|
8
|
+
## Quick Start
|
|
9
|
+
|
|
10
|
+
1. Install: `npm i -g @anthropic-ai/claude-code` (or appropriate method)
|
|
11
|
+
2. Run: `cd {{PROJECT_PATH}} && claude`
|
|
12
|
+
3. Try: `/test`, `/lint`, `/verify`
|
|
13
|
+
|
|
14
|
+
## Commands
|
|
15
|
+
|
|
16
|
+
| Command | Purpose |
|
|
17
|
+
|---------|---------|
|
|
18
|
+
| `/test` | Run test suite |
|
|
19
|
+
| `/lint` | Check code quality |
|
|
20
|
+
| `/verify` | Full validation (build + test + lint) |
|
|
21
|
+
| `/pr` | Create pull request |
|
|
22
|
+
|
|
23
|
+
## Workflows
|
|
24
|
+
|
|
25
|
+
### New Feature
|
|
26
|
+
1. Enter Plan Mode (Shift+Tab 2x)
|
|
27
|
+
2. Describe feature requirements
|
|
28
|
+
3. Approve plan
|
|
29
|
+
4. Implement with verification-first approach
|
|
30
|
+
|
|
31
|
+
### Bug Fix
|
|
32
|
+
1. Use: "Investigate bug: [description]"
|
|
33
|
+
2. Claude will reproduce, isolate, fix
|
|
34
|
+
3. Run `/verify` before committing
|
|
35
|
+
|
|
36
|
+
### Parallel Work
|
|
37
|
+
```bash
|
|
38
|
+
claude --worktree feature-a
|
|
39
|
+
claude --worktree feature-b
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
## Tips
|
|
43
|
+
- Use Plan Mode for changes > 3 files
|
|
44
|
+
- Reference existing code: "similar to src/utils/auth.ts"
|
|
45
|
+
- Always run `/verify` before committing
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
## CONTRIBUTING_WITH_CLAUDE.md
|
|
51
|
+
|
|
52
|
+
```markdown
|
|
53
|
+
# Contributing with Claude Code
|
|
54
|
+
|
|
55
|
+
## Setup
|
|
56
|
+
1. Clone repo
|
|
57
|
+
2. Run `/setup` in Claude
|
|
58
|
+
3. Verify with `/verify`
|
|
59
|
+
|
|
60
|
+
## Workflow
|
|
61
|
+
1. Create branch: `git checkout -b feature/description`
|
|
62
|
+
2. Use Plan Mode for non-trivial changes
|
|
63
|
+
3. Implement with tests
|
|
64
|
+
4. Run `/verify`
|
|
65
|
+
5. Create PR with `/pr`
|
|
66
|
+
|
|
67
|
+
## Standards
|
|
68
|
+
- All code must have tests
|
|
69
|
+
- Must pass linter
|
|
70
|
+
- Update docs for new features
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## TROUBLESHOOTING.md
|
|
76
|
+
|
|
77
|
+
```markdown
|
|
78
|
+
# Troubleshooting
|
|
79
|
+
|
|
80
|
+
## "Tests failing"
|
|
81
|
+
```bash
|
|
82
|
+
/test # See failures
|
|
83
|
+
# Share errors with Claude
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
## "Build broken"
|
|
87
|
+
```bash
|
|
88
|
+
/verify # See build errors
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
## "Need fresh context"
|
|
92
|
+
```bash
|
|
93
|
+
/clear
|
|
94
|
+
# Start with focused prompt
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
## Decision Tree
|
|
98
|
+
- Bug? → "Use debug workflow"
|
|
99
|
+
- New feature? → Plan Mode + verification-first
|
|
100
|
+
- Refactor? → Plan Mode
|
|
101
|
+
- Quick fix (< 10 lines)? → Direct execution
|
|
102
|
+
```
|