claude-cli-advanced-starter-pack 1.0.0

package/templates/commands/github-task-start.template.md

@@ -0,0 +1,99 @@
+---
+description: Start or complete a task from GitHub Project Board
+model: sonnet
+---
+
+# /github-task-start - Start GitHub Task
+
+Start working on a task from your GitHub Project Board or mark it complete.
+
+{{#if versionControl.projectBoard.number}}
+
+## Usage
+
+```
+/github-task-start <issue-number>           # Start working on issue
+/github-task-start <issue-number> --complete # Complete the issue
+```
+
+## Workflow
+
+### Starting a Task
+
+1. **Fetch Issue Details**
+   ```bash
+   gh issue view <number> --repo {{versionControl.owner}}/{{versionControl.repo}} --json title,body,labels,assignees
+   ```
+
+2. **Create Branch** (optional)
+   ```bash
+   git checkout -b feature/<issue-number>-<slug>
+   ```
+
+3. **Update Project Board Status**
+   ```bash
+   # Move to "In Progress" status
+   gh project item-edit --id <item-id> --project-id {{versionControl.projectBoard.id}} --field-id <status-field-id> --single-select-option-id <in-progress-id>
+   ```
+
+4. **Create Task List**
+   - Analyze issue requirements
+   - Create TodoWrite tasks based on acceptance criteria
+   - Begin implementation
+
+### Completing a Task
+
+1. **Verify All Tests Pass**
+   ```bash
+   {{#if testing.e2e.testCommand}}
+   {{testing.e2e.testCommand}}
+   {{else}}
+   npm test
+   {{/if}}
+   ```
+
+2. **Create Commit**
+   ```bash
+   git add .
+   git commit -m "feat: <description>
+
+   Closes #<issue-number>"
+   ```
+
+3. **Create PR**
+   ```bash
+   gh pr create --title "<title>" --body "Closes #<issue-number>" --repo {{versionControl.owner}}/{{versionControl.repo}}
+   ```
+
+4. **Update Project Board Status**
+   - Move to "Done" status
+   - Add completion comment
+
+## Instructions for Claude
+
+When invoked with an issue number:
+
+1. Parse arguments for issue number and --complete flag
+2. Fetch issue details from GitHub
+3. If starting:
+   - Display issue summary
+   - Ask about branch creation
+   - Update project board status
+   - Generate task list from requirements
+4. If completing:
+   - Verify tests pass
+   - Create PR if not exists
+   - Update project board status
+   - Add completion comment
+
+{{else}}
+
+## Configuration Required
+
+GitHub Project Board is not configured. Run `/menu` → Project Settings → GitHub Project Board.
+
+{{/if}}
+
+---
+
+*Generated from tech-stack.json template*

package/templates/commands/github-update.template.md

@@ -0,0 +1,69 @@
+---
+description: View and sync GitHub Project Board status
+model: haiku
+---
+
+# /github-update - GitHub Project Board Sync
+
+View current status of your GitHub Project Board and sync progress.
+
+{{#if versionControl.projectBoard.number}}
+
+## Project Board Configuration
+
+| Setting | Value |
+|---------|-------|
+| Owner | {{versionControl.owner}} |
+| Repository | {{versionControl.repo}} |
+| Project # | {{versionControl.projectBoard.number}} |
+| URL | {{versionControl.projectBoard.url}} |
+
+## Commands
+
+### View Board Status
+
+```bash
+# View all items on the project board
+gh project item-list {{versionControl.projectBoard.number}} --owner {{versionControl.owner}} --format json | jq '.items'
+
+# View issues only
+gh issue list --repo {{versionControl.owner}}/{{versionControl.repo}} --state open --json number,title,state,labels
+
+# View PRs
+gh pr list --repo {{versionControl.owner}}/{{versionControl.repo}} --state open --json number,title,state,headRefName
+```
+
+### Sync Tasks
+
+1. **Pull from GitHub** - Fetch latest status from Project Board
+2. **Push to GitHub** - Update Project Board with local progress
+3. **Reconcile** - Two-way sync with conflict resolution
+
+## Instructions for Claude
+
+When this command is invoked:
+
+1. Check gh CLI authentication: `gh auth status`
+2. Fetch current board status using the commands above
+3. Display a formatted summary:
+   - Total items
+   - Items by status (Todo, In Progress, Done)
+   - Recent activity
+4. Ask if user wants to sync or view details
+
+{{else}}
+
+## Configuration Required
+
+GitHub Project Board is not configured. Please run `/menu` → Project Settings → GitHub Project Board to configure.
+
+Required settings:
+- GitHub owner (username or organization)
+- Repository name
+- Project board number (from URL)
+
+{{/if}}
+
+---
+
+*Generated from tech-stack.json template*

package/templates/commands/happy-start.template.md

@@ -0,0 +1,117 @@
+---
+description: Start a Happy Mode session for mobile app integration
+model: sonnet
+---
+
+# /happy-start - Start Happy Mode Session
+
+Initialize Happy Engineering integration for mobile app control and checkpoint management.
+
+{{#if happyMode.enabled}}
+
+## Configuration
+
+| Setting | Value |
+|---------|-------|
+| Dashboard URL | {{happyMode.dashboardUrl}} |
+| Checkpoint Interval | {{happyMode.checkpointInterval}} minutes |
+| Verbosity | {{happyMode.verbosity}} |
+| Notify on Task Complete | {{happyMode.notifications.onTaskComplete}} |
+| Notify on Error | {{happyMode.notifications.onError}} |
+
+## Session Modes
+
+### 1. Full Verbosity
+Complete responses with all details. Best for desktop use.
+
+### 2. Condensed (Recommended for Mobile)
+Summarized responses optimized for mobile viewing:
+- Bullet points instead of paragraphs
+- Collapsed code blocks
+- Status indicators (✓, ⚠, ✗)
+
+### 3. Minimal
+Essential information only:
+- Task status
+- Error messages
+- Required user input
+
+## Commands During Happy Session
+
+| Command | Description |
+|---------|-------------|
+| `happy:checkpoint` | Save current progress checkpoint |
+| `happy:status` | Show session status and metrics |
+| `happy:pause` | Pause and save state |
+| `happy:resume` | Resume from last checkpoint |
+| `happy:end` | End Happy session gracefully |
+
+## Checkpoint Structure
+
+Checkpoints are saved to: `.claude/self-hosted-happy/checkpoints/`
+
+```json
+{
+  "timestamp": "2025-01-30T12:00:00Z",
+  "sessionId": "uuid",
+  "progress": {
+    "tasksCompleted": 3,
+    "tasksRemaining": 2,
+    "currentTask": "Implement feature X"
+  },
+  "context": {
+    "summary": "Working on...",
+    "recentFiles": ["src/...", "..."],
+    "pendingActions": []
+  }
+}
+```
+
+## Instructions for Claude
+
+When this command is invoked:
+
+1. **Initialize Session**
+   - Generate session ID
+   - Create initial checkpoint
+   - Set response format to `{{happyMode.verbosity}}`
+
+2. **Configure Notifications**
+   {{#if happyMode.notifications.onTaskComplete}}
+   - Enable task completion notifications
+   {{/if}}
+   {{#if happyMode.notifications.onError}}
+   - Enable error notifications
+   {{/if}}
+
+3. **Start Checkpoint Timer**
+   - Schedule checkpoints every {{happyMode.checkpointInterval}} minutes
+   - Auto-save on significant progress
+
+4. **Respond with Session Info**
+   ```
+   Happy Mode Started
+   ─────────────────
+   Session: <id>
+   Verbosity: {{happyMode.verbosity}}
+   Checkpoints: Every {{happyMode.checkpointInterval}} min
+
+   Ready for tasks. Mobile app can now control this session.
+   ```
+
+{{else}}
+
+## Happy Mode Disabled
+
+Happy Engineering integration is not enabled for this project.
+
+To enable:
+1. Run `/menu` → Project Settings → Happy Mode
+2. Configure dashboard URL and checkpoint interval
+3. Install Happy Coder mobile app
+
+{{/if}}
+
+---
+
+*Generated from tech-stack.json template*

package/templates/commands/phase-track.template.md

@@ -0,0 +1,142 @@
+---
+description: Track progress of phased development plans
+model: haiku
+---
+
+# /phase-track - Phased Development Progress Tracker
+
+View and update progress on phased development plans.
+
+{{#if phasedDevelopment.enabled}}
+
+## Configuration
+
+| Setting | Value |
+|---------|-------|
+| Default Scale | {{phasedDevelopment.defaultScale}} |
+| Success Target | {{phasedDevelopment.successTarget}} ({{phasedDevelopment.successTarget * 100}}%) |
+| Progress File | {{phasedDevelopment.progressFile}} |
+
+## Available Projects
+
+Scan `.claude/docs/` for active phased development projects:
+
+```bash
+# Find all PROGRESS.json files
+find .claude/docs -name "PROGRESS.json" -type f 2>/dev/null
+
+# Or on Windows
+dir /s /b .claude\docs\PROGRESS.json
+```
+
+## Progress File Structure
+
+```json
+{
+  "projectName": "Feature X",
+  "scale": "M",
+  "targetSuccess": 0.95,
+  "phases": [
+    {
+      "id": 1,
+      "name": "Setup & Foundation",
+      "status": "completed",
+      "tasks": [
+        { "id": "1.1", "description": "Create database schema", "completed": true },
+        { "id": "1.2", "description": "Set up API endpoints", "completed": true }
+      ],
+      "completedAt": "2025-01-30T10:00:00Z"
+    },
+    {
+      "id": 2,
+      "name": "Core Implementation",
+      "status": "in_progress",
+      "tasks": [
+        { "id": "2.1", "description": "Implement business logic", "completed": true },
+        { "id": "2.2", "description": "Add validation", "completed": false }
+      ]
+    }
+  ],
+  "metrics": {
+    "totalTasks": 10,
+    "completedTasks": 5,
+    "currentPhase": 2,
+    "estimatedCompletion": "2025-01-31"
+  }
+}
+```
+
+## Commands
+
+### View Progress
+
+```
+/phase-track <project-slug>
+```
+
+Displays:
+- Overall progress percentage
+- Current phase status
+- Remaining tasks
+- Estimated completion
+
+### Update Task Status
+
+```
+/phase-track <project-slug> --complete <task-id>
+```
+
+Marks a task as completed and updates metrics.
+
+### Generate Report
+
+```
+/phase-track <project-slug> --report
+```
+
+Generates a markdown progress report.
+
+## Progress Visualization
+
+```
+Project: Feature X (M scale, 95% target)
+════════════════════════════════════════
+
+Phase 1: Setup & Foundation     ████████████████████ 100% ✓
+Phase 2: Core Implementation    ████████████░░░░░░░░  60%
+Phase 3: Testing & Validation   ░░░░░░░░░░░░░░░░░░░░   0%
+Phase 4: Documentation          ░░░░░░░░░░░░░░░░░░░░   0%
+
+Overall: ████████░░░░░░░░░░░░  40% (4/10 tasks)
+
+Current Task: 2.2 - Add validation
+```
+
+## Instructions for Claude
+
+When this command is invoked:
+
+1. If no project specified, list all available projects with PROGRESS.json
+2. If project specified:
+   - Load PROGRESS.json
+   - Display progress visualization
+   - Show current phase and task details
+3. If --complete flag, update task status and recalculate metrics
+4. If --report flag, generate markdown report
+
+{{else}}
+
+## Phased Development Disabled
+
+Phased development system is not enabled for this project.
+
+To enable:
+1. Run `/menu` → Project Settings (if available)
+2. Or set `phasedDevelopment.enabled: true` in tech-stack.json
+3. Use `/create-phase-dev` to create a new phased plan
+
+{{/if}}
+
+---
+
+*Generated from tech-stack.json template*

package/templates/commands/tunnel-start.template.md

@@ -0,0 +1,127 @@
+---
+description: Start tunnel service for exposing local development server
+model: haiku
+---
+
+# /tunnel-start - Start Development Tunnel
+
+Expose your local development server to the internet for mobile testing or webhooks.
+
+{{#if (neq devEnvironment.tunnel.service "none")}}
+
+## Configuration
+
+| Setting | Value |
+|---------|-------|
+| Service | {{devEnvironment.tunnel.service}} |
+| Subdomain | {{devEnvironment.tunnel.subdomain}} |
+| Start Command | `{{devEnvironment.tunnel.startCommand}}` |
+{{#if devEnvironment.tunnel.adminPort}}
+| Admin Port | {{devEnvironment.tunnel.adminPort}} |
+{{/if}}
+
+## Start Tunnel
+
+{{#if (eq devEnvironment.tunnel.service "ngrok")}}
+### ngrok
+
+```bash
+# Start tunnel
+{{devEnvironment.tunnel.startCommand}}
+
+# Check status (in another terminal)
+curl http://localhost:{{devEnvironment.tunnel.adminPort}}/api/tunnels
+```
+
+After starting, get the public URL from:
+- Terminal output
+- ngrok dashboard at http://localhost:{{devEnvironment.tunnel.adminPort}}
+{{/if}}
+
+{{#if (eq devEnvironment.tunnel.service "localtunnel")}}
+### localtunnel
+
+```bash
+# Install if needed
+npm install -g localtunnel
+
+# Start tunnel
+{{devEnvironment.tunnel.startCommand}}
+```
+
+The public URL will be displayed in terminal output.
+{{/if}}
+
+{{#if (eq devEnvironment.tunnel.service "cloudflare-tunnel")}}
+### Cloudflare Tunnel
+
+```bash
+# Start tunnel (requires cloudflared installed and authenticated)
+{{devEnvironment.tunnel.startCommand}}
+```
+
+URL will be displayed in terminal. For persistent URL, configure a named tunnel in Cloudflare dashboard.
+{{/if}}
+
+{{#if (eq devEnvironment.tunnel.service "serveo")}}
+### Serveo
+
+```bash
+# Start tunnel (no installation required)
+{{devEnvironment.tunnel.startCommand}}
+```
+
+The assigned URL will be displayed. Note: Serveo may be unavailable at times.
+{{/if}}
+
+## Usage Notes
+
+1. **Mobile Testing**: Use tunnel URL in mobile browser for testing
+2. **Webhooks**: Configure webhook services to use tunnel URL
+3. **Demos**: Share tunnel URL for quick demos
+
+## Update tech-stack.json
+
+After starting tunnel, update the URL:
+
+```json
+{
+  "devEnvironment": {
+    "tunnel": {
+      "url": "<your-tunnel-url>"
+    }
+  }
+}
+```
+
+## Instructions for Claude
+
+When this command is invoked:
+
+1. Check if tunnel service is installed
+2. Display the start command
+3. Offer to run the command
+4. If run, capture and display the public URL
+5. Update tech-stack.json with tunnel URL
+
+{{else}}
+
+## Tunnel Service Not Configured
+
+No tunnel service is configured for this project.
+
+To configure:
+1. Run `/menu` → Project Settings → Tunnel Services
+2. Select a tunnel service:
+   - **ngrok** - Popular, reliable, requires account for reserved subdomains
+   - **localtunnel** - Free, no signup required
+   - **cloudflare-tunnel** - Enterprise-grade, requires Cloudflare account
+   - **serveo** - Free SSH-based, may be unreliable
+
+3. Optionally set a reserved subdomain
+
+{{/if}}
+
+---
+
+*Generated from tech-stack.json template*

package/templates/commands/tunnel-stop.template.md

@@ -0,0 +1,106 @@
+---
+description: Stop the running tunnel service
+model: haiku
+---
+
+# /tunnel-stop - Stop Development Tunnel
+
+Stop the currently running tunnel service and clean up.
+
+{{#if (neq devEnvironment.tunnel.service "none")}}
+
+## Stop Commands
+
+{{#if (eq devEnvironment.tunnel.service "ngrok")}}
+### ngrok
+
+```bash
+# Find ngrok process
+{{#if (eq process.platform "win32")}}
+tasklist | findstr ngrok
+{{else}}
+pgrep -f ngrok
+{{/if}}
+
+# Kill ngrok
+{{#if (eq process.platform "win32")}}
+taskkill /IM ngrok.exe /F
+{{else}}
+pkill ngrok
+{{/if}}
+
+# Or use ngrok API
+curl -X DELETE http://localhost:{{devEnvironment.tunnel.adminPort}}/api/tunnels/<tunnel-name>
+```
+{{/if}}
+
+{{#if (eq devEnvironment.tunnel.service "localtunnel")}}
+### localtunnel
+
+```bash
+# Find and kill localtunnel process
+{{#if (eq process.platform "win32")}}
+taskkill /IM node.exe /F  # Warning: kills all Node processes
+{{else}}
+pkill -f localtunnel
+{{/if}}
+```
+
+Or simply press Ctrl+C in the terminal running localtunnel.
+{{/if}}
+
+{{#if (eq devEnvironment.tunnel.service "cloudflare-tunnel")}}
+### Cloudflare Tunnel
+
+```bash
+# Find and kill cloudflared
+{{#if (eq process.platform "win32")}}
+taskkill /IM cloudflared.exe /F
+{{else}}
+pkill cloudflared
+{{/if}}
+```
+
+Or press Ctrl+C in the terminal running cloudflared.
+{{/if}}
+
+{{#if (eq devEnvironment.tunnel.service "serveo")}}
+### Serveo
+
+Simply close the SSH connection or press Ctrl+C.
+{{/if}}
+
+## Clean Up
+
+After stopping, clear the tunnel URL from configuration:
+
+```json
+{
+  "devEnvironment": {
+    "tunnel": {
+      "url": null
+    }
+  }
+}
+```
+
+## Instructions for Claude
+
+When this command is invoked:
+
+1. Identify running tunnel processes
+2. Offer to kill the process
+3. Clear tunnel URL from tech-stack.json
+4. Confirm tunnel is stopped
+
+{{else}}
+
+## No Tunnel Configured
+
+No tunnel service is configured. Run `/menu` → Project Settings → Tunnel Services to set up.
+
+{{/if}}
+
+---
+
+*Generated from tech-stack.json template*