ccstart 2.0.1 → 2.1.0

package/template/.claude/commands/update-claude-md.md

@@ -1,23 +0,0 @@
----
-description: "Automatically update CLAUDE.md with project-specific information"
-allowedTools: ["Read", "Write", "Edit", "Grep", "LS", "Bash"]
----
-
-I'll analyze your project and automatically update the CLAUDE.md file with project-specific information.
-
-First, let me examine your project structure to understand:
-1. Project type and technology stack
-2. Available scripts and commands
-3. Directory structure
-4. Dependencies and frameworks
-5. Testing and build configurations
-
-Then I'll update the following sections in CLAUDE.md:
-- Project Overview
-- Key Objectives (based on README if available)
-- Common Commands
-- Additional Notes
-
-I'll preserve any existing custom content you've added while updating the auto-generated sections.
-
-Let me start by analyzing your project...

package/template/.claude/hooks/README.md

@@ -1,65 +0,0 @@
-# Claude Code Hooks
-
-This directory contains hooks that automatically enhance Claude's behavior based on your interactions.
-
-## Available Hooks
-
-### workflow-detector.sh
-Automatically detects when you're describing a task that matches one of our workflow patterns and suggests the appropriate workflow command.
-
-**Detects:**
-- Feature development requests
-- Bug reports and fixes
-- API development tasks
-- QA and testing requests
-- Refactoring needs
-- UI component development
-
-### How It Works
-When you type a message to Claude, the hook analyzes it for patterns and adds helpful context suggesting the appropriate workflow command.
-
-## Setup
-
-1. **Enable hooks in Claude Code settings**:
-   Create or update `.claude/settings.json`:
-   ```json
-   {
-     "hooks": {
-       "UserPromptSubmit": [
-         {
-           "hooks": [
-             {
-               "type": "command",
-               "command": ".claude/hooks/workflow-detector.sh"
-             }
-           ]
-         }
-       ]
-     }
-   }
-   ```
-
-2. **Make hooks executable**:
-   ```bash
-   chmod +x .claude/hooks/*.sh
-   ```
-
-## Examples
-
-### Input: "I need to add user authentication to my app"
-**Hook adds**: "Detected feature request. Consider using /workflow-feature command for systematic implementation."
-
-### Input: "Fix the bug where users get logged out after 5 minutes"
-**Hook adds**: "Detected bug report. Consider using /workflow-bug command for systematic debugging."
-
-### Input: "Create REST API for managing blog posts"
-**Hook adds**: "Detected API development task. Consider using /workflow-api command."
-
-## Creating Custom Hooks
-
-You can create your own hooks by:
-1. Adding a new script to this directory
-2. Updating `.claude/settings.json` to reference it
-3. Using exit codes and JSON output to control behavior
-
-See Claude Code documentation for more details on hook development.

package/template/.claude/hooks/workflow-detector.sh

@@ -1,61 +0,0 @@
-#!/bin/bash
-# workflow-detector.sh - Detects workflow patterns in user prompts
-# and suggests appropriate workflow commands
-
-input=$(cat)
-
-# Store original input for passthrough
-original_input="$input"
-
-# Initialize suggestions array
-suggestions=""
-
-# Detect feature requests
-if echo "$input" | grep -iE "(implement|add|create|build|develop).*(feature|functionality|component|system)" > /dev/null; then
-  suggestions="${suggestions}🚀 Detected feature development task. Consider using: /workflow-feature [your feature description]\n"
-fi
-
-# Detect bug reports
-if echo "$input" | grep -iE "(fix|bug|error|issue|broken|not working|problem|crash)" > /dev/null; then
-  suggestions="${suggestions}🐛 Detected bug fix task. Consider using: /workflow-bug [issue description]\n"
-fi
-
-# Detect API development
-if echo "$input" | grep -iE "(api|endpoint|rest|graphql|route).*(create|implement|build|design)" > /dev/null; then
-  suggestions="${suggestions}🔌 Detected API development task. Consider using: /workflow-api [API description]\n"
-fi
-
-# Detect QA/testing requests
-if echo "$input" | grep -iE "(test|qa|quality|review|audit|check).*(feature|code|implementation|system)" > /dev/null; then
-  suggestions="${suggestions}🧪 Detected QA task. Consider using: /workflow-qa [what to test]\n"
-fi
-
-# Detect refactoring needs
-if echo "$input" | grep -iE "(refactor|improve|optimize|clean up|restructure).*(code|implementation|architecture)" > /dev/null; then
-  suggestions="${suggestions}🔧 Detected refactoring task. Consider using: /workflow-refactor [what to refactor]\n"
-fi
-
-# Detect UI component development
-if echo "$input" | grep -iE "(ui|interface|component|frontend|design).*(create|implement|build|develop)" > /dev/null; then
-  suggestions="${suggestions}🎨 Detected UI development task. Consider using: /workflow-ui [component description]\n"
-fi
-
-# Detect blockchain/web3 development
-if echo "$input" | grep -iE "(blockchain|smart contract|web3|defi|nft|crypto)" > /dev/null; then
-  suggestions="${suggestions}⛓️ Detected blockchain task. Consider using: /workflow-blockchain [blockchain feature]\n"
-fi
-
-# If we detected any patterns, add suggestions as additional context
-if [ -n "$suggestions" ]; then
-  # Create JSON response with additional context
-  context="💡 Workflow Suggestions:\\n${suggestions}\\nThese commands will automatically orchestrate the appropriate agents for your task."
-  
-  # Escape for JSON
-  context=$(echo -n "$context" | sed 's/"/\\"/g')
-  
-  # Output JSON with additional context
-  echo "{\"additionalContext\": \"$context\"}"
-else
-  # No patterns detected, pass through without modification
-  echo "$original_input"
-fi

package/template/.claude/settings.json.example

@@ -1,18 +0,0 @@
-{
-  "hooks": {
-    "UserPromptSubmit": [
-      {
-        "description": "Detect workflow patterns and suggest appropriate commands",
-        "hooks": [
-          {
-            "type": "command",
-            "command": ".claude/hooks/workflow-detector.sh"
-          }
-        ]
-      }
-    ]
-  },
-  "tools": {
-    "enabled": true
-  }
-}

package/template/claude/plans/README.md

@@ -1,53 +0,0 @@
-# Plans
-
-This directory contains project plans and architectural documents.
-
-## Purpose
-Store detailed implementation plans, architectural decisions, and strategic roadmaps created by the planner agent or during project planning sessions.
-
-## Plan Structure
-Each plan should be a markdown file with:
-- Clear objectives and goals
-- Detailed implementation steps
-- Technical architecture decisions
-- Risk analysis and mitigation strategies
-- Success metrics
-
-## Example Plan Format
-```markdown
-# PLAN-XXX: [Plan Title]
-
-## Executive Summary
-[High-level overview]
-
-## Objectives
-- [ ] Objective 1
-- [ ] Objective 2
-
-## Architecture
-[Technical approach and design]
-
-## Implementation Phases
-### Phase 1: Foundation
-- Task 1
-- Task 2
-
-### Phase 2: Core Features
-- Task 3
-- Task 4
-
-## Risks & Mitigations
-| Risk | Impact | Mitigation |
-|------|--------|------------|
-| Risk 1 | High | Strategy 1 |
-
-## Success Metrics
-- Metric 1
-- Metric 2
-```
-
-## Plan Naming Convention
-Use format: `PLAN-XXX-brief-description.md`
-
-## Current Plans
-[List active plans here]