claude-init 1.0.10 → 1.0.12
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/.claude/settings.local.json +2 -1
- package/.devcontainer/Dockerfile +2 -0
- package/.devcontainer/devcontainer.json +1 -1
- package/README.md +32 -10
- package/package.json +1 -1
- package/.claude/commands/gogogo.md +0 -3
- package/.claude/commands/impl-planning.md +0 -2
- package/.claude/commands/plan.md +0 -30
package/.devcontainer/Dockerfile
CHANGED
|
@@ -87,6 +87,8 @@ RUN sh -c "$(wget -O- https://github.com/deluan/zsh-in-docker/releases/download/
|
|
|
87
87
|
RUN npm install -g @anthropic-ai/claude-code@${CLAUDE_CODE_VERSION}
|
|
88
88
|
# Install Codex
|
|
89
89
|
RUN npm install -g @openai/codex@${CODEX_VERSION}
|
|
90
|
+
# Install spec-kit
|
|
91
|
+
RUN uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
|
|
90
92
|
|
|
91
93
|
|
|
92
94
|
# Copy and set up firewall script
|
package/README.md
CHANGED
|
@@ -9,15 +9,31 @@ A CLI tool to initialize Claude development environment with standardized config
|
|
|
9
9
|
- **Progress Feedback**: Clear visual indicators of what's being created, updated, or skipped
|
|
10
10
|
- **Cross-platform**: Works on Windows, macOS, and Linux
|
|
11
11
|
|
|
12
|
+
## Requirements
|
|
13
|
+
|
|
14
|
+
- Node.js `>=16.0.0`
|
|
15
|
+
- Permission to write files in the target project directory
|
|
16
|
+
|
|
17
|
+
## Installation
|
|
18
|
+
|
|
19
|
+
- One-off run (recommended):
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
npx claude-init
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
- Or install globally:
|
|
26
|
+
|
|
27
|
+
```bash
|
|
28
|
+
npm install -g claude-init
|
|
29
|
+
claude-init
|
|
30
|
+
```
|
|
31
|
+
|
|
12
32
|
## Usage
|
|
13
33
|
|
|
14
34
|
### Quick Start
|
|
15
35
|
|
|
16
|
-
|
|
17
|
-
npx claude-init
|
|
18
|
-
```
|
|
19
|
-
|
|
20
|
-
This will set up your current directory with:
|
|
36
|
+
Running `npx claude-init` sets up your current directory with:
|
|
21
37
|
|
|
22
38
|
- `CLAUDE.md` - Project instructions and scratchpad for Claude
|
|
23
39
|
- `.devcontainer/` - Development container configuration
|
|
@@ -28,9 +44,10 @@ This will set up your current directory with:
|
|
|
28
44
|
### What It Does
|
|
29
45
|
|
|
30
46
|
#### 📄 CLAUDE.md
|
|
31
|
-
- **If missing**: Creates new file with template content
|
|
32
|
-
- **If exists**:
|
|
33
|
-
- **If
|
|
47
|
+
- **If missing**: Creates new file with the template content.
|
|
48
|
+
- **If exists and has `# CLAUDE.md` heading**: Inserts the template content directly under that heading.
|
|
49
|
+
- **If exists and no `# CLAUDE.md` heading**: Adds a `# CLAUDE.md` heading at the top, then the template content, keeping your original content below.
|
|
50
|
+
- **If it already contains the template content**: Skips to preserve your content.
|
|
34
51
|
|
|
35
52
|
#### 📁 .devcontainer
|
|
36
53
|
- **If missing**: Creates complete directory with Docker configuration
|
|
@@ -77,10 +94,15 @@ your-project/
|
|
|
77
94
|
└── .claude/
|
|
78
95
|
├── settings.json # Claude settings
|
|
79
96
|
├── commands/ # Custom commands
|
|
97
|
+
│ ├── commit.md
|
|
98
|
+
│ ├── continue-tasks.md
|
|
80
99
|
│ ├── debug.md
|
|
81
100
|
│ ├── gogogo.md
|
|
101
|
+
│ ├── impl-planning.md
|
|
82
102
|
│ ├── plan.md
|
|
83
|
-
│
|
|
103
|
+
│ ├── prompt-enhancement.md
|
|
104
|
+
│ ├── review-plan.md
|
|
105
|
+
│ └── security-review.md
|
|
84
106
|
└── agents/ # Specialized agents
|
|
85
107
|
└── library-usage-researcher.md
|
|
86
108
|
```
|
|
@@ -101,4 +123,4 @@ npm run dev
|
|
|
101
123
|
|
|
102
124
|
## License
|
|
103
125
|
|
|
104
|
-
MIT
|
|
126
|
+
MIT
|
package/package.json
CHANGED
package/.claude/commands/plan.md
DELETED
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
ultrathink.
|
|
2
|
-
|
|
3
|
-
You are an experienced project manager. For every question posed by the user, you do not rush to write code. Instead, you focus on thoughtful, structured reasoning to provide high-quality answers, explore multiple possible solutions, and identify the best one. Before starting, ensure you fully understand the following project requirements and process descriptions.
|
|
4
|
-
|
|
5
|
-
You possess the following capabilities:
|
|
6
|
-
|
|
7
|
-
1. Requirements Clarification
|
|
8
|
-
|
|
9
|
-
- Clearly restate the user's question or problem in your own words.
|
|
10
|
-
- Establish high-level communication to clarify the user's needs.
|
|
11
|
-
- Offer analogous case studies to inspire the user's thinking.
|
|
12
|
-
- Explain the primary challenges and constraints.
|
|
13
|
-
- During your reasoning process, ask questions to fill in any missing information or details you need.
|
|
14
|
-
|
|
15
|
-
2. Solution Exploration
|
|
16
|
-
|
|
17
|
-
- Explore multiple feasible implementation methods based on existing technologies.
|
|
18
|
-
- List the pros, cons, applicable scenarios, and costs of each solution.
|
|
19
|
-
- Prioritize leveraging existing technical solutions in the ecosystem to avoid reinventing the wheel.
|
|
20
|
-
- Provide an optimal recommendation based on the requirements, explaining the rationale and potential improvements.
|
|
21
|
-
- Ensure the recommended solution is scalable and maintainable, offering corresponding optimization suggestions.
|
|
22
|
-
|
|
23
|
-
Additionally, maintain the following principles throughout your work process:
|
|
24
|
-
|
|
25
|
-
1. Optimal Choices: When selecting technologies or implementation methods, prioritize mature, stable, and efficient solutions.
|
|
26
|
-
2. Environment Considerations: Thoughtfully address potential environment issues, such as dependency version conflicts or system compatibility, and proactively provide solutions.
|
|
27
|
-
|
|
28
|
-
Now, no need to code, read through and understand the codebase and give me a detailed plan on:
|
|
29
|
-
|
|
30
|
-
$ARGUMENTS
|