zuppaclaude 1.3.9 → 1.3.10
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/assets/CLAUDE.md +123 -0
- package/package.json +1 -1
package/assets/CLAUDE.md
ADDED
|
@@ -0,0 +1,123 @@
|
|
|
1
|
+
# Claude Code - Enhanced System Instructions
|
|
2
|
+
|
|
3
|
+
## General Behavior
|
|
4
|
+
- Be proactive: After analysis ask "Should I implement?" or "Let's start?"
|
|
5
|
+
- Provide summary report when done (commit hash, changes, line count)
|
|
6
|
+
- Don't ask open-ended questions, suggest the best option
|
|
7
|
+
|
|
8
|
+
## SuperClaude Framework (Active)
|
|
9
|
+
SuperClaude slash commands are loaded. Use them proactively:
|
|
10
|
+
|
|
11
|
+
### Planning & Design
|
|
12
|
+
- `/sc:brainstorm` - Idea development and brainstorming
|
|
13
|
+
- `/sc:design` - Architectural design
|
|
14
|
+
- `/sc:estimate` - Time/resource estimation
|
|
15
|
+
- `/sc:spec-panel` - Specification panel
|
|
16
|
+
|
|
17
|
+
### Development
|
|
18
|
+
- `/sc:implement` - Code implementation
|
|
19
|
+
- `/sc:build` - Build and compile
|
|
20
|
+
- `/sc:improve` - Code improvement
|
|
21
|
+
- `/sc:explain` - Code explanation
|
|
22
|
+
|
|
23
|
+
### Testing & Quality
|
|
24
|
+
- `/sc:test` - Test creation
|
|
25
|
+
- `/sc:analyze` - Code analysis
|
|
26
|
+
- `/sc:troubleshoot` - Debugging
|
|
27
|
+
- `/sc:reflect` - Retrospective
|
|
28
|
+
|
|
29
|
+
### Documentation & Help
|
|
30
|
+
- `/sc:document` - Documentation creation
|
|
31
|
+
- `/sc:help` - Command help
|
|
32
|
+
|
|
33
|
+
### Research
|
|
34
|
+
- `/sc:research` - Deep web research
|
|
35
|
+
- `/sc:business-panel` - Business analysis
|
|
36
|
+
|
|
37
|
+
### Project Management
|
|
38
|
+
- `/sc:task` - Task management
|
|
39
|
+
- `/sc:workflow` - Workflow management
|
|
40
|
+
- `/sc:pm` - Project management
|
|
41
|
+
|
|
42
|
+
### Other
|
|
43
|
+
- `/sc:agent` - Agent management
|
|
44
|
+
- `/sc:spawn` - Sub-agent creation
|
|
45
|
+
- `/sc:index-repo` - Repository indexing
|
|
46
|
+
- `/sc:git` - Git operations
|
|
47
|
+
|
|
48
|
+
## Spec Kit (Active)
|
|
49
|
+
Spec-driven development with `specify` CLI:
|
|
50
|
+
|
|
51
|
+
```bash
|
|
52
|
+
specify init # Initialize project
|
|
53
|
+
specify constitution # Project rules
|
|
54
|
+
specify spec # Functional requirements
|
|
55
|
+
specify plan # Technical implementation plan
|
|
56
|
+
specify tasks # Task breakdown
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
For large features, recommend this workflow:
|
|
60
|
+
1. `specify constitution` - Base rules
|
|
61
|
+
2. `specify spec` - What to do
|
|
62
|
+
3. `specify plan` - How to do it
|
|
63
|
+
4. `specify tasks` - Step-by-step tasks
|
|
64
|
+
5. Implementation
|
|
65
|
+
|
|
66
|
+
## Task Completion (Critical)
|
|
67
|
+
- ALWAYS provide summary report when done
|
|
68
|
+
- Don't finish with just "Tasks: 6/6" - that's NOT a summary
|
|
69
|
+
- Show commit hash, change list, line count
|
|
70
|
+
|
|
71
|
+
## Response Format
|
|
72
|
+
- Short and concise answers
|
|
73
|
+
- Use Markdown formatting
|
|
74
|
+
- Specify language for code blocks
|
|
75
|
+
- Status: OK = success, ERR = error, WARN = warning
|
|
76
|
+
|
|
77
|
+
## Git Commit Message Guidelines
|
|
78
|
+
|
|
79
|
+
Follow Conventional Commits specification.
|
|
80
|
+
|
|
81
|
+
### Format
|
|
82
|
+
```
|
|
83
|
+
<type>: <description>
|
|
84
|
+
|
|
85
|
+
[optional body]
|
|
86
|
+
|
|
87
|
+
[optional footer]
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### Types
|
|
91
|
+
- **feat**: A new feature
|
|
92
|
+
- **fix**: A bug fix
|
|
93
|
+
- **docs**: Documentation only changes
|
|
94
|
+
- **style**: Changes that do not affect the meaning of the code
|
|
95
|
+
- **refactor**: A code change that neither fixes a bug nor adds a feature
|
|
96
|
+
- **perf**: A code change that improves performance
|
|
97
|
+
- **test**: Adding missing tests or correcting existing tests
|
|
98
|
+
- **chore**: Changes to the build process or auxiliary tools
|
|
99
|
+
|
|
100
|
+
### Rules
|
|
101
|
+
1. Use simple present tense: "adds" not "add" or "added"
|
|
102
|
+
2. Use lowercase: "feat: adds feature" not "Feat: Adds Feature"
|
|
103
|
+
3. Limit first line to 72 characters or less
|
|
104
|
+
4. Use bullet points in body with hyphens (-)
|
|
105
|
+
5. Be specific and descriptive
|
|
106
|
+
|
|
107
|
+
### Examples
|
|
108
|
+
|
|
109
|
+
#### Good
|
|
110
|
+
```
|
|
111
|
+
feat: adds user authentication system
|
|
112
|
+
|
|
113
|
+
- adds login and registration endpoints
|
|
114
|
+
- adds JWT token generation
|
|
115
|
+
- adds password hashing with bcrypt
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
```
|
|
119
|
+
fix: resolves login validation issue
|
|
120
|
+
|
|
121
|
+
- fixes email format validation
|
|
122
|
+
- adds proper error messages
|
|
123
|
+
```
|