claude-code-templates 1.21.1 → 1.21.2

package/cli-tool/components/settings/statusline/time-statusline.json

@@ -1,7 +0,0 @@
-{
-  "description": "Status line with timestamp showing model, directory, and current time. Useful for tracking session duration and maintaining awareness of time during long coding sessions.",
-  "statusLine": {
-    "type": "command",
-    "command": "bash -c 'input=$(cat); MODEL=$(echo \"$input\" | jq -r \".model.display_name\"); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); TIME=$(date \"+%H:%M\"); echo \"[$MODEL] 📁 ${DIR##*/} | 🕐 $TIME\"'"
-  }
-}

package/cli-tool/components/settings/statusline/unity-project-dashboard-statusline.json

@@ -1,7 +0,0 @@
-{
-  "description": "Unity project dashboard displaying scene info, build target, asset pipeline status, and Unity version. Shows current scene name, active platform (iOS/Android/PC/WebGL), asset processing queue status, memory usage warnings, and available Unity package updates. Detects Unity projects and provides real-time development metrics.",
-  "statusLine": {
-    "type": "command",
-    "command": "python3 -c \"import json, sys, os, subprocess, glob; data=json.load(sys.stdin); model=data['model']['display_name']; current_dir=data['workspace']['current_dir']; os.chdir(current_dir); unity_project = os.path.exists('Assets') and os.path.exists('ProjectSettings'); scene_info = ''; build_target = ''; asset_status = ''; unity_version = ''; package_status = ''; if unity_project: scenes = glob.glob('Assets/**/*.unity', recursive=True); active_scene = os.path.basename(scenes[0]) if scenes else 'None'; scene_info = f'🎮 {active_scene.replace(\".unity\", \"\")}'; try: with open('ProjectSettings/ProjectVersion.txt', 'r') as f: unity_version = f.read().split(':')[1].strip()[:6]; except: unity_version = 'Unknown'; try: with open('ProjectSettings/EditorBuildSettings.asset', 'r') as f: content = f.read(); if 'iPhone' in content: build_target = '📱iOS'; elif 'Android' in content: build_target = '🤖And'; elif 'StandaloneWindows' in content: build_target = '🖥️PC'; elif 'WebGL' in content: build_target = '🌐Web'; else: build_target = '⚙️Multi'; except: build_target = '⚙️Build'; asset_count = len(glob.glob('Assets/**/*', recursive=True)) - len(glob.glob('Assets/**/*.meta', recursive=True)); if asset_count > 1000: asset_status = '⚠️Assets'; elif asset_count > 500: asset_status = '📦Assets'; else: asset_status = '✅Assets'; packages_dir = 'Packages'; if os.path.exists(f'{packages_dir}/manifest.json'): package_status = '📋Pkgs'; print(f'[{model}] {unity_version} | {scene_info} | {build_target} | {asset_status} | {package_status}'); else: dir_name = os.path.basename(current_dir); print(f'[{model}] 📁 {dir_name} | ❌ Not Unity Project')\""
-  }
-}

package/cli-tool/components/settings/statusline/vercel-deployment-monitor.json

@@ -1,7 +0,0 @@
-{
-  "description": "Real-time Vercel deployment monitor showing current build status, deployment URL, and time since last deployment. Displays build state with intuitive icons and tracks deployment history. Setup: Export environment variables 'export VERCEL_TOKEN=your_token' and 'export VERCEL_PROJECT_ID=your_project_id' (or manually replace $VERCEL_TOKEN and $VERCEL_PROJECT_ID in the command if you prefer not to use environment variables). Get your token from vercel.com/account/tokens and project ID from your Vercel dashboard.",
-  "statusLine": {
-    "type": "command",
-    "command": "bash -c 'input=$(cat); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); DEPLOY_DATA=$(curl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \"https://api.vercel.com/v6/deployments?projectId=$VERCEL_PROJECT_ID&limit=1\" 2>/dev/null); if [ -n \"$DEPLOY_DATA\" ] && [ \"$DEPLOY_DATA\" != \"null\" ]; then STATE=$(echo \"$DEPLOY_DATA\" | jq -r \".deployments[0].state // empty\"); URL=$(echo \"$DEPLOY_DATA\" | jq -r \".deployments[0].url // empty\" | cut -c1-20); CREATED=$(echo \"$DEPLOY_DATA\" | jq -r \".deployments[0].created // empty\"); if [ -n \"$CREATED\" ] && [ \"$CREATED\" != \"null\" ]; then AGO=$(( ($(date +%s) - $CREATED/1000) / 60 )); TIME_AGO=\"${AGO}m ago\"; else TIME_AGO=\"unknown\"; fi; case \"$STATE\" in READY) STATUS_ICON=\"✅\";; BUILDING) STATUS_ICON=\"🔄\";; QUEUED) STATUS_ICON=\"⏳\";; ERROR) STATUS_ICON=\"❌\";; *) STATUS_ICON=\"❓\";; esac; else STATE=\"unavailable\"; URL=\"\"; TIME_AGO=\"unknown\"; STATUS_ICON=\"❓\"; fi; echo \"▲ Vercel 🚀 $STATUS_ICON $STATE | 🌐 $URL | ⏰ $TIME_AGO | 📁 ${DIR##*/}\"'"
-  }
-}

package/cli-tool/components/settings/statusline/vercel-error-alert-system.json

@@ -1,7 +0,0 @@
-{
-  "description": "Intelligent error monitoring system that tracks deployment failures and build issues. Automatically sends desktop notifications when errors are detected and maintains error count tracking. Features building status monitoring and provides immediate alerts for deployment problems, helping you catch issues quickly. Setup: Export environment variables 'export VERCEL_TOKEN=your_token' and 'export VERCEL_PROJECT_ID=your_project_id' (or manually replace $VERCEL_TOKEN and $VERCEL_PROJECT_ID in the command if you prefer not to use environment variables). Get your token from vercel.com/account/tokens and project ID from your Vercel dashboard. Desktop notifications work on macOS.",
-  "statusLine": {
-    "type": "command",
-    "command": "bash -c 'input=$(cat); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); SESSION=$(echo \"$input\" | jq -r \".session_id\" | cut -c1-8); ERROR_FILE=\"/tmp/vercel_errors_$SESSION\"; DEPLOYS=$(curl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \"https://api.vercel.com/v6/deployments?projectId=$VERCEL_PROJECT_ID&limit=5\" 2>/dev/null); if [ -n \"$DEPLOYS\" ] && [ \"$DEPLOYS\" != \"null\" ]; then ERRORS=$(echo \"$DEPLOYS\" | jq -r \".deployments[].state\" | grep -c \"ERROR\" 2>/dev/null || echo \"0\"); BUILDING=$(echo \"$DEPLOYS\" | jq -r \".deployments[].state\" | grep -c \"BUILDING\" 2>/dev/null || echo \"0\"); if [ \"$ERRORS\" -gt 0 ]; then echo \"$ERRORS\" > \"$ERROR_FILE\"; ALERT=\"🚨 $ERRORS errors!\"; osascript -e \"display notification \\\"$ERRORS deployment errors found\\\" with title \\\"Vercel Alert\\\"\" 2>/dev/null; elif [ \"$BUILDING\" -gt 0 ]; then ALERT=\"🔄 Building...\"; else ALERT=\"✅ All good\"; fi; else ALERT=\"❓ API error\"; ERRORS=\"?\"; BUILDING=\"?\"; fi; echo \"▲ Vercel 🚀 $ALERT | Building: $BUILDING | 📁 ${DIR##*/}\"'"
-  }
-}

package/cli-tool/components/settings/statusline/vercel-multi-env-status.json

@@ -1,7 +0,0 @@
-{
-  "description": "Monitors both production and preview environments simultaneously with color-coded status indicators. Perfect for teams managing multiple deployment targets. Shows real-time status of your latest production and preview deployments with green/yellow/red indicators for quick visual assessment. Setup: Export environment variables 'export VERCEL_TOKEN=your_token' and 'export VERCEL_PROJECT_ID=your_project_id' (or manually replace $VERCEL_TOKEN and $VERCEL_PROJECT_ID in the command if you prefer not to use environment variables). Get your token from vercel.com/account/tokens and project ID from your Vercel dashboard.",
-  "statusLine": {
-    "type": "command",
-    "command": "bash -c 'input=$(cat); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); DEPLOYS=$(curl -s -H \"Authorization: Bearer $VERCEL_TOKEN\" \"https://api.vercel.com/v6/deployments?projectId=$VERCEL_PROJECT_ID&limit=10\" 2>/dev/null); if [ -n \"$DEPLOYS\" ] && [ \"$DEPLOYS\" != \"null\" ]; then PROD=$(echo \"$DEPLOYS\" | jq -r \".deployments[] | select(.target == \\\"production\\\") | .state\" | head -1); PREVIEW=$(echo \"$DEPLOYS\" | jq -r \".deployments[] | select(.target == \\\"preview\\\") | .state\" | head -1); case \"$PROD\" in READY) PROD_ICON=\"🟢\";; BUILDING) PROD_ICON=\"🟡\";; ERROR) PROD_ICON=\"🔴\";; *) PROD_ICON=\"⚪\";; esac; case \"$PREVIEW\" in READY) PREV_ICON=\"🟢\";; BUILDING) PREV_ICON=\"🟡\";; ERROR) PREV_ICON=\"🔴\";; *) PREV_ICON=\"⚪\";; esac; else PROD_ICON=\"❓\"; PREV_ICON=\"❓\"; fi; echo \"▲ Vercel 🚀 Prod:$PROD_ICON Prev:$PREV_ICON | 📁 ${DIR##*/}\"'"
-  }
-}

package/cli-tool/components/settings/statusline/virtual-code-garden-statusline.json

@@ -1,7 +0,0 @@
-{
-  "description": "Watch your code garden grow with each session. Plants evolve from seeds to trees based on your activity, with dynamic weather effects. Displays: Plant stages (🌱 seed 0-9, 🌿 sprout 10-19, 🍃 sapling 20-29, 🌳 tree 30-39, 🌺 flower 40+), Weather (🌧️ rainy every 7 growth points, ☀️ sunny every 5 points, ⛅ cloudy default), Garden Level (stage number), Growth counter (total session interactions).",
-  "statusLine": {
-    "type": "command",
-    "command": "bash -c 'input=$(cat); MODEL=$(echo \"$input\" | jq -r \".model.display_name\"); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); SESSION=$(echo \"$input\" | jq -r \".session_id\" | cut -c1-8); CACHE=\"/tmp/garden_$SESSION\"; if [ ! -f \"$CACHE\" ]; then echo \"0\" > \"$CACHE\"; fi; GROWTH=$(cat \"$CACHE\"); GROWTH=$((GROWTH + 1)); echo \"$GROWTH\" > \"$CACHE\"; STAGE=$((GROWTH / 10)); case $STAGE in 0) PLANT=\"🌱\";; 1) PLANT=\"🌿\";; 2) PLANT=\"🍃\";; 3) PLANT=\"🌳\";; *) PLANT=\"🌺\";; esac; WEATHER=$([ $((GROWTH % 7)) -eq 0 ] && echo \"🌧️\" || [ $((GROWTH % 5)) -eq 0 ] && echo \"☀️\" || echo \"⛅\"); echo \"[$MODEL] $PLANT $WEATHER Garden Lv.$STAGE | 📁 ${DIR##*/} | Growth: $GROWTH\"'"
-  }
-}

package/cli-tool/components/settings/statusline/zero-config-deployment-monitor.json

@@ -1,7 +0,0 @@
-{
-  "description": "Auto-detecting Vercel deployment monitor with zero configuration required. Automatically discovers your Vercel auth token from CLI config (macOS: ~/Library/Application Support/com.vercel.cli/auth.json, Linux: ~/.config/vercel/auth.json, Windows: %APPDATA%/vercel/auth.json) and project ID from .vercel/project.json. Shows real-time deployment status, build state icons, deployment URL preview, and time elapsed since last deployment. Falls back gracefully to environment variables VERCEL_TOKEN and VERCEL_PROJECT_ID if auto-detection fails. Works across all platforms without any manual setup.",
-  "statusLine": {
-    "type": "command",
-    "command": "bash -c 'input=$(cat); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); if [[ \"$OSTYPE\" == \"darwin\"* ]]; then AUTH_FILE=\"$HOME/Library/Application Support/com.vercel.cli/auth.json\"; elif [[ \"$OSTYPE\" == \"linux-gnu\"* ]]; then AUTH_FILE=\"$HOME/.config/vercel/auth.json\"; elif [[ \"$OSTYPE\" == \"msys\" || \"$OSTYPE\" == \"cygwin\" ]]; then AUTH_FILE=\"$APPDATA/vercel/auth.json\"; else AUTH_FILE=\"$HOME/.config/vercel/auth.json\"; fi; PROJECT_FILE=\".vercel/project.json\"; if [ -f \"$AUTH_FILE\" ]; then TOKEN=$(jq -r \".token // empty\" \"$AUTH_FILE\" 2>/dev/null); else TOKEN=\"$VERCEL_TOKEN\"; fi; if [ -f \"$PROJECT_FILE\" ]; then PROJECT=$(jq -r \".projectId // empty\" \"$PROJECT_FILE\" 2>/dev/null); else PROJECT=\"$VERCEL_PROJECT_ID\"; fi; if [ -n \"$TOKEN\" ] && [ -n \"$PROJECT\" ] && [ \"$TOKEN\" != \"null\" ] && [ \"$PROJECT\" != \"null\" ]; then DEPLOY_DATA=$(curl -s -H \"Authorization: Bearer $TOKEN\" \"https://api.vercel.com/v6/deployments?projectId=$PROJECT&limit=1\" 2>/dev/null); if [ -n \"$DEPLOY_DATA\" ] && [ \"$DEPLOY_DATA\" != \"null\" ]; then STATE=$(echo \"$DEPLOY_DATA\" | jq -r \".deployments[0].state // empty\"); URL=$(echo \"$DEPLOY_DATA\" | jq -r \".deployments[0].url // empty\" | cut -c1-20); CREATED=$(echo \"$DEPLOY_DATA\" | jq -r \".deployments[0].created // empty\"); if [ -n \"$CREATED\" ] && [ \"$CREATED\" != \"null\" ]; then AGO=$(( ($(date +%s) - $CREATED/1000) / 60 )); TIME_AGO=\"${AGO}m ago\"; else TIME_AGO=\"unknown\"; fi; case \"$STATE\" in READY) STATUS_ICON=\"✅\";; BUILDING) STATUS_ICON=\"🔄\";; QUEUED) STATUS_ICON=\"⏳\";; ERROR) STATUS_ICON=\"❌\";; *) STATUS_ICON=\"❓\";; esac; else STATE=\"API error\"; URL=\"\"; TIME_AGO=\"\"; STATUS_ICON=\"❌\"; fi; else STATE=\"config missing\"; URL=\"\"; TIME_AGO=\"\"; STATUS_ICON=\"⚠️\"; fi; echo \"▲ Vercel 🚀 $STATUS_ICON $STATE | 🌐 $URL | ⏰ $TIME_AGO | 📁 ${DIR##*/}\"'"
-  }
-}

package/cli-tool/components/settings/telemetry/custom-telemetry.json

@@ -1,7 +0,0 @@
-{
-  "description": "Custom telemetry configuration with different endpoint.",
-  "env": {
-    "CLAUDE_CODE_ENABLE_TELEMETRY": "0",
-    "OTEL_METRICS_EXPORTER": "custom"
-  }
-}

package/cli-tool/components/settings/telemetry/disable-telemetry.json

@@ -1,6 +0,0 @@
-{
-  "description": "Disable Claude Code telemetry for privacy.",
-  "env": {
-    "DISABLE_TELEMETRY": "1"
-  }
-}

package/cli-tool/components/settings/telemetry/enable-telemetry.json

@@ -1,6 +0,0 @@
-{
-  "description": "Enable Claude Code telemetry for usage analytics and improvements.",
-  "env": {
-    "CLAUDE_CODE_ENABLE_TELEMETRY": "1"
-  }
-}

package/cli-tool/docs_to_claude/ANALYTICS_STATE_DETECTION.md

@@ -1,183 +0,0 @@
-# Analytics State Detection System
-
-## Overview
-This document describes how the Claude Code Analytics Dashboard determines and displays conversation states in real-time.
-
-## State Detection Flow
-
-### 1. Backend State Calculation (`/api/conversation-state`)
-
-The conversation state endpoint processes **ALL** conversations and calculates their current state:
-
-#### API Endpoint: `/api/conversation-state`
-- **Method**: GET
-- **Response Format**: `{ activeStates: {conversationId: state}, timestamp: number }`
-- **Update Frequency**: Called by frontend every 5-30 seconds
-
-#### State Calculation Logic
-
-For each conversation, the system:
-
-1. **Checks for Running Process**:
-   - If `conversation.runningProcess` exists, uses `StateCalculator.quickStateCalculation()`
-   - Returns states like: "Claude Code working...", "Awaiting user input...", "User typing..."
-
-2. **Falls back to Basic Heuristics** (for conversations without active processes):
-   ```javascript
-   const timeDiff = (now - new Date(conversation.lastModified)) / (1000 * 60); // minutes
-   
-   if (timeDiff < 5) {
-     state = 'Recently active';
-   } else if (timeDiff < 60) {
-     state = 'Idle';
-   } else if (timeDiff < 1440) { // 24 hours
-     state = 'Inactive';
-   } else {
-     state = 'Old';
-   }
-   ```
-
-### 2. StateCalculator Logic (`src/analytics/core/StateCalculator.js`)
-
-The StateCalculator determines detailed conversation states based on:
-
-#### Primary Factors:
-- **Running Process**: Whether there's an active Claude Code process
-- **Last Message Role**: 'user' vs 'assistant'
-- **Message Timing**: Time since last message
-- **File Activity**: File modification time
-- **Process Activity**: Active commands in the process
-
-#### State Categories:
-
-**Active Process States**:
-- `"Claude Code working..."` - User just sent message or recent file activity
-- `"Awaiting user input..."` - Claude responded and waiting for user
-- `"User typing..."` - User hasn't responded for a while
-- `"Awaiting response..."` - User sent message but Claude hasn't responded
-
-**Inactive Process States**:
-- `"Recently active"` - Modified within 5 minutes
-- `"Idle"` - Modified within 1 hour
-- `"Inactive"` - Modified within 24 hours
-- `"Old"` - Modified more than 24 hours ago
-
-### 3. Frontend State Display (`AgentsPage.js`)
-
-#### State Mapping
-The frontend maps backend states to display labels and CSS classes:
-
-```javascript
-// Label mapping
-const stateLabels = {
-  'Claude Code working...': 'Working',
-  'Awaiting user input...': 'Awaiting input',
-  'User typing...': 'Typing',
-  'Awaiting response...': 'Awaiting response',
-  'Recently active': 'Recent',
-  'Idle': 'Idle',
-  'Inactive': 'Inactive',
-  'Old': 'Old',
-  'unknown': 'Unknown'
-};
-
-// CSS class mapping
-const stateClasses = {
-  'Claude Code working...': 'status-active',
-  'Awaiting user input...': 'status-waiting',
-  'User typing...': 'status-typing',
-  'Awaiting response...': 'status-pending',
-  'Recently active': 'status-recent',
-  'Idle': 'status-idle',
-  'Inactive': 'status-inactive',
-  'Old': 'status-old',
-  'unknown': 'status-unknown'
-};
-```
-
-#### Visual Indicators
-States are displayed in the conversation sidebar as:
-- **Status Dot**: Colored circle indicator
-- **Status Badge**: Text label with background color
-- **CSS Classes**: For consistent styling across components
-
-## Real-time Updates
-
-### WebSocket Integration
-- State changes are pushed via WebSocket when available
-- Falls back to polling every 5-30 seconds when WebSocket unavailable
-
-### Update Triggers
-- File system changes (FileWatcher)
-- Process detection updates
-- Periodic refresh intervals
-
-## Troubleshooting
-
-### Common Issues
-
-1. **States showing as "unknown"**:
-   - Check if `/api/conversation-state` is returning data
-   - Verify conversation IDs match between API and frontend
-   - Ensure StateCalculator is processing all conversations
-
-2. **States not updating in real-time**:
-   - Check WebSocket connection in browser dev tools
-   - Verify FileWatcher is detecting changes
-   - Check for polling fallback activation
-
-3. **Incorrect state calculations**:
-   - Review StateCalculator logic for edge cases
-   - Check conversation file modification times
-   - Verify process detection is working
-
-### Debug Commands
-
-```bash
-# Test state endpoint
-curl -s http://localhost:3333/api/conversation-state | jq .
-
-# Check conversations count
-curl -s "http://localhost:3333/api/conversations?page=0&limit=1" | jq '.pagination.totalCount'
-
-# Monitor server logs for state calculation
-# Look for: "🔍 Processing X conversations for state calculation"
-```
-
-## Configuration
-
-### State Update Intervals
-- **With WebSocket**: 30 seconds cache duration
-- **Without WebSocket**: 5 seconds cache duration
-- **File Watch**: Immediate updates when files change
-
-### Performance Considerations
-- StateCalculator uses caching to avoid repeated calculations
-- Quick state calculation for active processes only
-- Batch processing of all conversations in single API call
-
-## Future Improvements
-
-1. **Enhanced Process Detection**: Better correlation between conversations and running processes
-2. **Message-Level Analysis**: Analyze message content for more accurate state detection
-3. **User Activity Tracking**: Detect actual user typing vs idle time
-4. **Custom State Rules**: Allow configuration of state calculation logic
-5. **State History**: Track state changes over time for analytics
-
-## Integration Points
-
-### Files Involved
-- `/src/analytics.js` - Main server and API endpoints
-- `/src/analytics/core/StateCalculator.js` - Core state logic
-- `/src/analytics-web/components/AgentsPage.js` - Frontend display
-- `/src/analytics-web/services/DataService.js` - API communication
-- `/src/analytics-web/index.html` - CSS styling
-
-### Key Functions
-- `StateCalculator.determineConversationState()` - Main state detection
-- `StateCalculator.quickStateCalculation()` - Fast state for active processes
-- `AgentsPage.getStateClass()` - CSS class mapping
-- `AgentsPage.getStateLabel()` - Display label mapping
-- `DataService.getConversationStates()` - API communication
-
-This system provides real-time visibility into Claude Code conversation states, helping users understand what's happening across all their active sessions.