claude-cli-advanced-starter-pack 1.0.3 → 1.0.5

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.
@@ -0,0 +1,320 @@
1
+ ---
2
+ description: Agent-powered project implementation - audit, enhance, detect stack, configure
3
+ model: sonnet
4
+ allowed-tools:
5
+ - Read
6
+ - Grep
7
+ - Glob
8
+ - Task
9
+ - Write
10
+ - Edit
11
+ - Bash
12
+ - AskUserQuestion
13
+ ---
14
+
15
+ # /project-impl - Project Implementation
16
+
17
+ Agent-powered project configuration, tech stack detection, and CLAUDE.md management.
18
+
19
+ ## Quick Menu
20
+
21
+ | Key | Action | Description |
22
+ |-----|--------|-------------|
23
+ | **1** | Audit CLAUDE.md | Analyze configuration against best practices |
24
+ | **2** | Enhance CLAUDE.md | Generate/improve documentation from codebase |
25
+ | **3** | Detect Tech Stack | Scan codebase and identify technologies |
26
+ | **4** | Project Settings | Configure deployment, tunnels, GitHub |
27
+ | **B** | Back to /menu | Return to main menu |
28
+
29
+ ## Instructions for Claude
30
+
31
+ When invoked, display the menu above and use AskUserQuestion to get the user's selection.
32
+
33
+ ---
34
+
35
+ ### Option 1: Audit CLAUDE.md
36
+
37
+ Deploy an audit agent to analyze the project's CLAUDE.md configuration:
38
+
39
+ 1. **Read CLAUDE.md and .claude/ folder** to understand current setup
40
+ 2. **Check length** - warn if >60 lines, error if >300 lines (Anthropic best practice)
41
+ 3. **Find anti-patterns:**
42
+ - Vague instructions ("be careful", "try to")
43
+ - Long code blocks (>20 lines)
44
+ - Missing runnable commands
45
+ - No emphasis keywords (IMPORTANT, MUST, NEVER)
46
+ 4. **Find good patterns:**
47
+ - Emphasis keywords (IMPORTANT, MUST, CRITICAL)
48
+ - Runnable bash commands
49
+ - @imports for context
50
+ - Clear, specific instructions
51
+ 5. **Score and report findings:**
52
+ - Green: Excellent (score 80-100)
53
+ - Yellow: Good with improvements (score 60-79)
54
+ - Red: Needs work (score <60)
55
+ 6. **Offer to run enhancement** if issues found
56
+
57
+ **Report Format:**
58
+ ```
59
+ 📊 CLAUDE.md Audit Report
60
+ ═══════════════════════════
61
+
62
+ ✓ PASSED
63
+ - Line count: XX (recommended <60)
64
+ - Has runnable commands
65
+ - Uses emphasis keywords
66
+
67
+ ⚠ WARNINGS
68
+ - [List of warnings]
69
+
70
+ ✗ ERRORS
71
+ - [List of errors]
72
+
73
+ 📋 RECOMMENDATIONS
74
+ - [Actionable suggestions]
75
+
76
+ Score: XX/100
77
+ ```
78
+
79
+ ---
80
+
81
+ ### Option 2: Enhance CLAUDE.md
82
+
83
+ 1. **Deploy Explore agent** to detect tech stack:
84
+ - Scan package.json for frameworks and dependencies
85
+ - Check config files (vite.config.*, webpack.config.*, etc.)
86
+ - Identify state managers, test frameworks, build tools
87
+ - Detect deployment configurations
88
+
89
+ 2. **Ask user via AskUserQuestion:**
90
+ - "Generate from scratch" - Create new CLAUDE.md based on detected stack
91
+ - "Add missing sections" - Enhance existing CLAUDE.md
92
+
93
+ 3. **Generate content based on detected stack:**
94
+ - Project overview
95
+ - Tech stack summary
96
+ - Key commands (build, test, dev, deploy)
97
+ - Important paths and files
98
+ - Architecture notes
99
+ - Common gotchas
100
+
101
+ 4. **Show preview** of generated content
102
+
103
+ 5. **Write to CLAUDE.md:**
104
+ - If file exists, create backup at `.claude/backups/CLAUDE.md.{timestamp}.bak`
105
+ - Write new content
106
+
107
+ **Generated CLAUDE.md Structure:**
108
+ ```markdown
109
+ # Project Name
110
+
111
+ Brief description of the project.
112
+
113
+ ## Tech Stack
114
+ - Frontend: [framework]
115
+ - Backend: [framework]
116
+ - Database: [type]
117
+ - Testing: [framework]
118
+
119
+ ## Commands
120
+ \`\`\`bash
121
+ npm run dev # Start development server
122
+ npm run build # Build for production
123
+ npm test # Run tests
124
+ \`\`\`
125
+
126
+ ## Key Paths
127
+ | Path | Description |
128
+ |------|-------------|
129
+ | src/ | Source code |
130
+ | ... | ... |
131
+
132
+ ## Architecture Notes
133
+ [Key architectural decisions and patterns]
134
+
135
+ ## Gotchas
136
+ - [Common issues and solutions]
137
+ ```
138
+
139
+ ---
140
+
141
+ ### Option 3: Detect Tech Stack
142
+
143
+ Deploy an Explore agent to scan the codebase:
144
+
145
+ 1. **Scan package.json** for:
146
+ - Framework: react, vue, angular, svelte, next, nuxt
147
+ - State: redux, zustand, mobx, pinia, jotai
148
+ - Styling: tailwind, styled-components, emotion, sass
149
+ - Testing: jest, vitest, playwright, cypress
150
+ - Build: vite, webpack, esbuild, parcel
151
+
152
+ 2. **Check config files:**
153
+ - `vite.config.*`, `webpack.config.*`, `rollup.config.*`
154
+ - `tsconfig.json`, `jsconfig.json`
155
+ - `tailwind.config.*`, `postcss.config.*`
156
+ - `.eslintrc.*`, `prettier.config.*`
157
+ - `playwright.config.*`, `jest.config.*`
158
+
159
+ 3. **Identify backend (if present):**
160
+ - `requirements.txt`, `pyproject.toml` → Python
161
+ - `go.mod` → Go
162
+ - `Cargo.toml` → Rust
163
+ - `package.json` scripts with `node`, `ts-node` → Node.js
164
+
165
+ 4. **Detect deployment configs:**
166
+ - `railway.json`, `railway.toml` → Railway
167
+ - `vercel.json` → Vercel
168
+ - `wrangler.toml` → Cloudflare
169
+ - `Dockerfile`, `docker-compose.yml` → Docker
170
+ - `.github/workflows/` → GitHub Actions
171
+
172
+ 5. **Report in structured format:**
173
+ ```
174
+ 🔍 Tech Stack Detection
175
+ ═══════════════════════════
176
+
177
+ Frontend:
178
+ Framework: React 19
179
+ State: Zustand
180
+ Styling: Tailwind CSS v4
181
+ Build: Vite
182
+
183
+ Backend:
184
+ Runtime: Node.js
185
+ Framework: Express
186
+
187
+ Testing:
188
+ Unit: Vitest
189
+ E2E: Playwright
190
+
191
+ Deployment:
192
+ Frontend: Cloudflare Pages
193
+ Backend: Railway
194
+ CI/CD: GitHub Actions
195
+ ```
196
+
197
+ 6. **Offer to save** to `.claude/config/tech-stack.json`
198
+
199
+ ---
200
+
201
+ ### Option 4: Project Settings
202
+
203
+ Use AskUserQuestion for interactive configuration:
204
+
205
+ **GitHub Project Board:**
206
+ ```
207
+ Questions:
208
+ 1. Do you have a GitHub Project Board? (Yes/No)
209
+ 2. Repository owner (e.g., 'username' or 'org-name')
210
+ 3. Repository name
211
+ 4. Project number (from URL: /projects/NUMBER)
212
+ ```
213
+
214
+ **Deployment Platforms:**
215
+ ```
216
+ Questions:
217
+ 1. Frontend deployment platform?
218
+ - Cloudflare Pages
219
+ - Vercel
220
+ - Netlify
221
+ - GitHub Pages
222
+ - None
223
+ 2. Backend deployment platform?
224
+ - Railway
225
+ - Heroku
226
+ - Render
227
+ - AWS
228
+ - None
229
+ 3. Project identifiers (IDs, names) for each platform
230
+ ```
231
+
232
+ **Tunnel Services:**
233
+ ```
234
+ Questions:
235
+ 1. Tunnel service for mobile testing?
236
+ - ngrok
237
+ - localtunnel
238
+ - cloudflare-tunnel
239
+ - serveo
240
+ - None
241
+ 2. Subdomain preference (optional)
242
+ ```
243
+
244
+ **Token Management:**
245
+ ```
246
+ Questions:
247
+ 1. Enable token budget tracking? (Yes/No)
248
+ 2. Daily budget limit (default: 200000)
249
+ 3. Compact threshold (default: 75%)
250
+ ```
251
+
252
+ **Happy Mode:**
253
+ ```
254
+ Questions:
255
+ 1. Enable Happy Mode integration? (Yes/No)
256
+ 2. Checkpoint interval (default: 10 tasks)
257
+ 3. Verbosity level (condensed/normal/verbose)
258
+ ```
259
+
260
+ **Write selections to `.claude/config/tech-stack.json`:**
261
+ ```json
262
+ {
263
+ "versionControl": {
264
+ "provider": "github",
265
+ "projectBoard": {
266
+ "type": "github-projects-v2",
267
+ "owner": "username",
268
+ "repo": "repo-name",
269
+ "projectNumber": 1
270
+ }
271
+ },
272
+ "deployment": {
273
+ "frontend": {
274
+ "platform": "cloudflare",
275
+ "projectName": "my-project"
276
+ },
277
+ "backend": {
278
+ "platform": "railway",
279
+ "projectId": "xxx",
280
+ "serviceId": "yyy"
281
+ }
282
+ },
283
+ "devEnvironment": {
284
+ "tunnel": {
285
+ "service": "ngrok",
286
+ "subdomain": "my-app"
287
+ }
288
+ },
289
+ "tokenManagement": {
290
+ "enabled": true,
291
+ "dailyBudget": 200000,
292
+ "thresholds": { "compact": 0.75 }
293
+ },
294
+ "happyMode": {
295
+ "enabled": true,
296
+ "checkpointInterval": 10
297
+ }
298
+ }
299
+ ```
300
+
301
+ ---
302
+
303
+ ## Navigation
304
+
305
+ After completing any option, ask the user:
306
+ - "Would you like to perform another action? (1-4, B to go back, Q to quit)"
307
+
308
+ ## Terminal Alternative
309
+
310
+ These operations can also be run from the terminal:
311
+
312
+ ```bash
313
+ npx ccasp wizard # Interactive setup wizard
314
+ npx ccasp detect-stack # Detect tech stack
315
+ npx ccasp claude-audit # Audit CLAUDE.md
316
+ ```
317
+
318
+ ---
319
+
320
+ *Part of Claude CLI Advanced Starter Pack*
@@ -0,0 +1,322 @@
1
+ ---
2
+ description: Check for CCASP updates and add new features to your project
3
+ model: sonnet
4
+ allowed-tools:
5
+ - Read
6
+ - Write
7
+ - Edit
8
+ - Bash
9
+ - Glob
10
+ - Grep
11
+ - Task
12
+ - AskUserQuestion
13
+ ---
14
+
15
+ # /update-check - CCASP Update Manager
16
+
17
+ Check for Claude CLI Advanced Starter Pack updates and manage new features.
18
+
19
+ ## Quick Menu
20
+
21
+ | Key | Action | Description |
22
+ |-----|--------|-------------|
23
+ | **1** | Check for Updates | Check npm registry for new versions |
24
+ | **2** | Add New Features | Install features from recent updates |
25
+ | **3** | Prior Releases | Review and enable features from older versions |
26
+ | **4** | View Changelog | See what changed in each release |
27
+ | **P** | Planning Mode | Audit new features before adding them |
28
+ | **B** | Back to /menu | Return to main menu |
29
+
30
+ ---
31
+
32
+ ## Instructions for Claude
33
+
34
+ When invoked, perform a version check and display the menu.
35
+
36
+ ### Step 1: Check Current State
37
+
38
+ Read the current state files:
39
+ ```bash
40
+ # Check installed version
41
+ cat node_modules/claude-cli-advanced-starter-pack/package.json 2>/dev/null | grep version
42
+ # Or check global install
43
+ npm list -g claude-cli-advanced-starter-pack 2>/dev/null | grep claude-cli-advanced-starter-pack
44
+ ```
45
+
46
+ Read `.claude/config/ccasp-state.json` if it exists:
47
+ ```json
48
+ {
49
+ "lastCheckTimestamp": 1706644800000,
50
+ "lastCheckResult": { "latestVersion": "1.0.5" },
51
+ "lastSeenVersion": "1.0.4",
52
+ "dismissedVersions": [],
53
+ "installedFeatures": ["menu", "e2e-test", "create-agent"],
54
+ "skippedFeatures": ["roadmap-sync"]
55
+ }
56
+ ```
57
+
58
+ ### Step 2: Check for Updates
59
+
60
+ Run npm to check latest version:
61
+ ```bash
62
+ npm view claude-cli-advanced-starter-pack version
63
+ ```
64
+
65
+ Compare with installed version. If update available, display:
66
+
67
+ ```
68
+ ╔════════════════════════════════════════════════════════════════╗
69
+ ║ 🆕 UPDATE AVAILABLE ║
70
+ ║ v1.0.4 → v1.0.5 ║
71
+ ╠════════════════════════════════════════════════════════════════╣
72
+ ║ What's New in v1.0.5: ║
73
+ ║ • Agent-powered project implementation ║
74
+ ║ • Version tracking with update notifications ║
75
+ ║ • Prior releases menu for feature management ║
76
+ ║ ║
77
+ ║ New Features: ║
78
+ ║ • /project-impl - Agent-powered setup & configuration ║
79
+ ║ • /update-check - Check updates and add features ║
80
+ ╠════════════════════════════════════════════════════════════════╣
81
+ ║ To Update: ║
82
+ ║ npm update -g claude-cli-advanced-starter-pack ║
83
+ ╚════════════════════════════════════════════════════════════════╝
84
+ ```
85
+
86
+ ### Step 3: Display Menu and Get Selection
87
+
88
+ Use AskUserQuestion:
89
+ ```
90
+ What would you like to do?
91
+
92
+ 1. Check for Updates - Check npm for new versions
93
+ 2. Add New Features - Install features from recent updates
94
+ 3. Prior Releases - Review features from older versions
95
+ 4. View Changelog - See release history
96
+ P. Planning Mode - Audit features before adding
97
+ B. Back to /menu
98
+ ```
99
+
100
+ ---
101
+
102
+ ## Option 1: Check for Updates
103
+
104
+ 1. Run: `npm view claude-cli-advanced-starter-pack version`
105
+ 2. Compare with current version
106
+ 3. If update available:
107
+ - Show version comparison
108
+ - List highlights from releases.json
109
+ - Show update command
110
+ - Offer to add new features after update
111
+ 4. If up to date:
112
+ - Show "You're on the latest version!"
113
+ - Offer to review available features not yet installed
114
+
115
+ ---
116
+
117
+ ## Option 2: Add New Features
118
+
119
+ 1. Read `.claude/config/ccasp-state.json` for installed/skipped features
120
+ 2. Read `.claude/commands/` to see what commands exist
121
+ 3. Compare against available features in releases.json
122
+ 4. Show features available to add:
123
+
124
+ ```
125
+ ╔════════════════════════════════════════════════════════════════╗
126
+ ║ Available Features to Add ║
127
+ ╠════════════════════════════════════════════════════════════════╣
128
+ ║ Commands: ║
129
+ ║ [ ] /project-impl - Agent-powered project implementation ║
130
+ ║ [ ] /roadmap-sync - Sync roadmaps with GitHub ║
131
+ ║ [ ] /claude-settings - Configure permissions and modes ║
132
+ ║ ║
133
+ ║ Optional Features: ║
134
+ ║ [ ] Token Management - Monitor API token usage ║
135
+ ║ [ ] Happy Mode - Mobile app integration ║
136
+ ║ [ ] Tunnel Services - ngrok/localtunnel for mobile testing ║
137
+ ╚════════════════════════════════════════════════════════════════╝
138
+ ```
139
+
140
+ 5. Use AskUserQuestion to let user select features
141
+ 6. For each selected feature:
142
+ - Read the template from templates/commands/
143
+ - Write to .claude/commands/
144
+ - Update ccasp-state.json
145
+ 7. Show summary of what was added
146
+
147
+ ---
148
+
149
+ ## Option 3: Prior Releases
150
+
151
+ 1. Load releases.json data
152
+ 2. Show release history:
153
+
154
+ ```
155
+ ╔════════════════════════════════════════════════════════════════╗
156
+ ║ CCASP Release History ║
157
+ ╠════════════════════════════════════════════════════════════════╣
158
+ ║ v1.0.5 (2025-01-30) - Agent-powered implementation ║
159
+ ║ v1.0.4 (2025-01-29) - Settings schema update ║
160
+ ║ v1.0.3 (2025-01-28) - Backup and uninstall wizard ║
161
+ ║ v1.0.2 (2025-01-27) - Template fallback and fixes ║
162
+ ║ v1.0.1 (2025-01-26) - Documentation improvements ║
163
+ ║ v1.0.0 (2025-01-25) - Initial release ║
164
+ ╚════════════════════════════════════════════════════════════════╝
165
+
166
+ Select a version to see details and available features: [1-6]
167
+ ```
168
+
169
+ 3. Show details for selected version:
170
+ - Summary
171
+ - Highlights
172
+ - New features with descriptions
173
+ - Option to add any features from that release
174
+
175
+ ---
176
+
177
+ ## Option 4: View Changelog
178
+
179
+ Display formatted changelog from releases.json:
180
+
181
+ ```markdown
182
+ # CCASP Changelog
183
+
184
+ ## v1.0.5 (2025-01-30)
185
+ **Agent-powered project implementation**
186
+
187
+ ### Highlights
188
+ - New /project-impl command for agent-powered setup
189
+ - Version tracking with update notifications
190
+ - Prior releases menu for feature management
191
+
192
+ ### New Commands
193
+ - `/project-impl` - Agent-powered project implementation
194
+ - `/update-check` - Check updates and add features
195
+
196
+ ---
197
+
198
+ ## v1.0.4 (2025-01-29)
199
+ **Settings schema update**
200
+ ...
201
+ ```
202
+
203
+ ---
204
+
205
+ ## Option P: Planning Mode
206
+
207
+ For users who want to audit new features before adding them:
208
+
209
+ 1. Show available features with detailed descriptions
210
+ 2. Enter plan mode to:
211
+ - Explore the template files
212
+ - Review what changes will be made
213
+ - Check for conflicts with existing commands
214
+ - Understand feature dependencies
215
+ 3. Create an implementation plan
216
+ 4. Ask user to approve before making changes
217
+ 5. Exit plan mode and implement approved changes
218
+
219
+ **Planning Mode Flow:**
220
+ ```
221
+ 1. Explore: Read template files for selected features
222
+ 2. Analyze: Check for conflicts or dependencies
223
+ 3. Plan: Create step-by-step implementation plan
224
+ 4. Review: Present plan to user
225
+ 5. Approve: User confirms or modifies
226
+ 6. Implement: Execute approved changes
227
+ ```
228
+
229
+ ---
230
+
231
+ ## Feature Installation Process
232
+
233
+ When adding a feature:
234
+
235
+ ### For Commands:
236
+ 1. Check if template exists: `templates/commands/{name}.template.md`
237
+ 2. Check if command already exists: `.claude/commands/{name}.md`
238
+ 3. If exists, ask: Skip, Overwrite, or Backup & Overwrite
239
+ 4. Copy template to `.claude/commands/{name}.md`
240
+ 5. Update INDEX.md
241
+ 6. Update ccasp-state.json
242
+
243
+ ### For Hooks:
244
+ 1. Check template in `templates/hooks/`
245
+ 2. Copy to `.claude/hooks/`
246
+ 3. Update settings.json hooks configuration
247
+
248
+ ### For Optional Features:
249
+ 1. Update `.claude/config/tech-stack.json`
250
+ 2. Deploy associated commands/hooks
251
+ 3. Show post-configuration instructions if needed
252
+
253
+ ---
254
+
255
+ ## State Management
256
+
257
+ Update `.claude/config/ccasp-state.json` after each operation:
258
+
259
+ ```json
260
+ {
261
+ "lastCheckTimestamp": 1706644800000,
262
+ "lastCheckResult": {
263
+ "latestVersion": "1.0.5"
264
+ },
265
+ "lastSeenVersion": "1.0.5",
266
+ "dismissedVersions": [],
267
+ "installedFeatures": [
268
+ "menu",
269
+ "e2e-test",
270
+ "create-agent",
271
+ "project-impl"
272
+ ],
273
+ "skippedFeatures": [
274
+ "roadmap-sync"
275
+ ],
276
+ "installHistory": [
277
+ {
278
+ "feature": "project-impl",
279
+ "version": "1.0.5",
280
+ "installedAt": "2025-01-30T12:00:00Z"
281
+ }
282
+ ]
283
+ }
284
+ ```
285
+
286
+ ---
287
+
288
+ ## Terminal Alternative
289
+
290
+ These operations can also be run from the terminal:
291
+
292
+ ```bash
293
+ # Check for updates
294
+ npm outdated -g claude-cli-advanced-starter-pack
295
+
296
+ # Update package
297
+ npm update -g claude-cli-advanced-starter-pack
298
+
299
+ # Run wizard to add features
300
+ ccasp wizard
301
+ ```
302
+
303
+ ---
304
+
305
+ ## After Installation Reminder
306
+
307
+ After adding new features, remind user:
308
+
309
+ ```
310
+ ⚠️ RESTART REQUIRED
311
+
312
+ New commands have been added to .claude/commands/.
313
+ To use them, restart your Claude Code session:
314
+
315
+ 1. Exit (Ctrl+C or /exit)
316
+ 2. Restart: claude or claude .
317
+ 3. New commands will be available
318
+ ```
319
+
320
+ ---
321
+
322
+ *Part of Claude CLI Advanced Starter Pack*