@champpaba/claude-agent-kit 2.0.1 → 2.1.1

package/.claude/contexts/patterns/change-workflow.md

@@ -18,34 +18,7 @@ This pattern describes how the multi-agent system integrates with OpenSpec to de
 
 ## 📋 Workflow Commands
 
-### 1. `/psetup` - Project Setup (One-Time)
-
-**When to use:** First time setting up the project
-
-**What it does:**
-1. Detects tech stack from package files
-2. Queries Context7 for best practices
-3. Creates `domain/` structure (3-level indexing)
-4. Generates framework-specific best practices files
-
-**Output:**
-```
-.claude/contexts/domain/
-├── index.md                              # Level 1 - Project Registry
-└── {project}/
-    ├── README.md                         # Level 2 - Project Overview
-    ├── tech-stack.md                     # Tech details
-    └── best-practices/
-        ├── index.md                      # Level 3 - Best Practices Registry
-        ├── react-18.md
-        ├── nextjs-15.md
-        ├── prisma-6.md
-        └── vitest-2.md
-```
-
----
-
-### 2. `/csetup {change-id}` - Change Setup
+### 1. `/csetup {change-id}` - Change Setup (Includes Project Setup)
 
 **When to use:** After creating OpenSpec change, before development
 
@@ -78,7 +51,7 @@ openspec/changes/CHANGE-XXX/.claude/
 
 ---
 
-### 3. `/cdev {change-id}` - Start/Continue Development
+### 2. `/cdev {change-id}` - Start/Continue Development
 
 **When to use:** After `/csetup`, to execute agent workflow
 
@@ -159,7 +132,7 @@ Ready to archive!
 
 ---
 
-### 4. `/cview {change-id}` - View Progress
+### 3. `/cview {change-id}` - View Progress
 
 **When to use:** Check detailed phase-by-phase progress
 
@@ -228,7 +201,7 @@ Ready to archive!
 
 ---
 
-### 5. `/cstatus {change-id}` - Quick Status
+### 4. `/cstatus {change-id}` - Quick Status
 
 **When to use:** Quick glance at progress
 
@@ -485,27 +458,22 @@ else template = 'full-stack' // Safe default
 
 ## 🎯 Best Practices
 
-### 1. Always Run `/psetup` First
-- One-time project setup
-- Generates framework-specific best practices
-- Required for agent discovery
-
-### 2. Use `/csetup` After Creating OpenSpec Change
+### 1. Run `/csetup` First
+- Auto-detects tech stack and generates best practices
 - Analyzes tasks and generates workflow
-- Creates per-change context
-- Enables progress tracking
+- Required for agent discovery
 
-### 3. Use `/cdev` for Execution
+### 2. Use `/cdev` for Execution
 - Orchestrates agent workflow
 - Updates progress automatically
 - Handles user actions
 
-### 4. Check Progress with `/cview` or `/cstatus`
+### 3. Check Progress with `/cview` or `/cstatus`
 - `/cview` for detailed breakdown
 - `/cstatus` for quick glance
 - Real-time updates from `flags.json`
 
-### 5. Agents Update `flags.json` After Each Phase
+### 4. Agents Update `flags.json` After Each Phase
 - Marks phase as completed
 - Records actual time spent
 - Lists files created
@@ -519,7 +487,7 @@ else template = 'full-stack' // Safe default
 **Solution:** Run `/csetup {change-id}` first
 
 **Problem:** Agent doesn't load project context
-**Solution:** Run `/psetup` to create domain/ structure
+**Solution:** Run `/csetup` to create domain/ structure (auto-detects tech stack)
 
 **Problem:** Progress tracking not working
 **Solution:** Check if `flags.json` exists and is valid JSON

package/.claude/lib/README.md

@@ -46,7 +46,7 @@ Unified pattern for loading design system files. 3-tier strategy: STYLE_TOKENS.j
 ## 📁 Detailed Guides (v1.4.0 - NEW!)
 
 **`detailed-guides/best-practices-system.md`** - How best practices work
-Complete guide to auto-generated best practices via Context7 MCP. Covers `/agentsetup`, 3-level indexing, and agent discovery flow.
+Complete guide to auto-generated best practices via Context7 MCP. Covers `/csetup`, 3-level indexing, and agent discovery flow.
 
 **`detailed-guides/context-optimization.md`** - Token optimization strategy
 Details the 70% token reduction in design system loading. Explains 3-tier loading, before/after comparisons, and benefits.

package/.claude/lib/agent-router.md

@@ -156,7 +156,7 @@ const WORK_PATTERNS = {
 
   'orchestration': {
     keywords: [
-      '/cdev', '/csetup', '/cview', '/cstatus', '/psetup',
+      '/cdev', '/csetup', '/cview', '/cstatus', '/pstatus',
       'continue workflow', 'next phase', 'progress'
     ],
     agent: 'main-claude',

package/.claude/lib/context-loading-protocol.md

@@ -18,7 +18,7 @@ This protocol defines how agents discover and load context before starting work.
 
 **Who uses this:**
 - All 6 agents (integration, uxui-frontend, test-debug, frontend, backend, database)
-- Commands that need tech stack info (/agentsetup, /csetup, /cdev)
+- Commands that need tech stack info (/csetup, /cdev)
 
 ---
 
@@ -92,7 +92,7 @@ From tech-stack.md, extract:
 
 ```
 ⚠️ tech-stack.md not found!
-💡 User should run: /agentsetup
+💡 User should run: /csetup
 
 FALLBACK (use ONLY if absolutely necessary):
 - Detect from package.json (JavaScript)
@@ -383,7 +383,7 @@ Troubleshooting:
 ⚠️ Warning: tech-stack.md shows pnpm, but pnpm-lock.yaml not found
 
 Suggestion:
-- Run: /agentsetup (regenerate tech-stack.md)
+- Run: /csetup (regenerate tech-stack.md)
 - Or manually update tech-stack.md
 ```
 
@@ -392,7 +392,7 @@ Suggestion:
 ## 🔄 When to Re-load Context
 
 **Re-load Level 0-2 when:**
-- ✅ User runs `/agentsetup` (tech stack changed)
+- ✅ User runs `/csetup` (tech stack changed)
 - ✅ Framework version upgraded
 - ✅ New dependencies added
 

package/.claude/lib/detailed-guides/agent-system.md

@@ -110,7 +110,7 @@ WHY routing matters: Specialist agents have domain-specific validation (design t
 
 WHY: STYLE_GUIDE.md has project-specific tokens. design/*.md has universal principles.
 
-**Fallback:** If discovery fails, suggest `/agentsetup` or `/designsetup`
+**Fallback:** If discovery fails, suggest `/csetup` or `/designsetup`
 
 ---
 

package/.claude/lib/detailed-guides/best-practices-system.md

@@ -8,7 +8,7 @@
 
 ## 📚 How It Works
 
-1. **Run `/agentsetup`** to detect tech stack and generate best practices
+1. **Run `/csetup`** to detect tech stack and generate best practices
 2. **Context7 queries** latest framework docs (React, Next.js, Prisma, etc.)
 3. **Best practices files** created in `domain/{project}/best-practices/`
 4. **Agents auto-discover** project via 3-level indexing
@@ -119,11 +119,10 @@ design-system/
 # 1. Generate style guide FIRST (optional but recommended)
 /designsetup
 
-# 2. Setup project (discovers style guide)
-/psetup
+# 2. Setup change and project (discovers style guide, auto-detects tech stack)
+/csetup feature-login
 
 # 3. Start development (agents use STYLE_GUIDE.md)
-/csetup feature-login
 /cdev feature-login
 ```
 
@@ -143,8 +142,7 @@ design-system/
 
 ## 🔗 See Also
 
-- `../../commands/agentsetup.md` - /agentsetup command (generates best practices)
+- `../../commands/csetup.md` - /csetup command (setup change + auto-detect tech stack + generate best practices)
 - `../../commands/designsetup.md` - /designsetup command (generates style guide)
-- `../../commands/psetup.md` - /psetup command (one-time project setup)
 - `../../contexts/patterns/agent-discovery.md` - Shared agent discovery flow
 - `context-loading-protocol.md` - How agents load framework-specific context

package/.claude/lib/detailed-guides/design-system.md

@@ -66,11 +66,10 @@ design-system/
 # 1. Generate style guide FIRST (optional but recommended)
 /designsetup
 
-# 2. Setup project (discovers style guide)
-/psetup
+# 2. Setup change and project (discovers style guide, auto-detects tech stack)
+/csetup feature-login
 
 # 3. Start development (agents use STYLE_GUIDE.md)
-/csetup feature-login
 /cdev feature-login
 ```
 

package/.claude/templates/PROJECT_STATUS.template.yml

@@ -0,0 +1,105 @@
+# PROJECT_STATUS.yml
+# Cross-session context for Claude - update after significant milestones
+# Optional: Remove this file if your project doesn't need cross-session tracking
+#
+# WHY this file exists:
+# - New Claude sessions lose context about infrastructure state, blockers, and priorities
+# - Reading multiple files (README, archived proposals, tasks.md) wastes tokens
+# - This single file provides quick context snapshot for AI sessions
+
+last_updated: "YYYY-MM-DD"
+
+# Optional settings
+_config:
+  stale_warning_days: 7  # Suggest /pstatus review if older than this
+
+# -------------------------------------------------------------------
+# CURRENT FOCUS
+# What phase is the project in? What's actively being worked on?
+# -------------------------------------------------------------------
+current_focus:
+  description: "Brief description of current project phase"
+  active_change: null  # change-id if OpenSpec change in progress, null if between changes
+
+# -------------------------------------------------------------------
+# COMPLETED CHANGES
+# Recently shipped work - helps Claude understand what's already done
+# -------------------------------------------------------------------
+completed_changes: []
+  # Example:
+  # - id: auth-system
+  #   date: "2025-11-30"
+  #   summary: "Login/logout, JWT tokens, protected routes"
+  # - id: infrastructure-cicd
+  #   date: "2025-11-28"
+  #   summary: "Docker, CI/CD pipeline, Cloudflare Tunnel"
+
+# -------------------------------------------------------------------
+# INFRASTRUCTURE STATUS
+# Current state of services - helps Claude understand what's running
+# -------------------------------------------------------------------
+infrastructure: {}
+  # Example structure (customize for your project):
+  #
+  # database:
+  #   status: healthy  # healthy | degraded | down | not_setup
+  #   notes: "PostgreSQL, 4 tables deployed"
+  #
+  # api:
+  #   status: healthy
+  #   notes: "6 endpoints, running on port 3000"
+  #
+  # cloudflare_tunnel:
+  #   status: running
+  #   waiting_for: domain  # null if fully operational
+  #   notes: "Tunnel active, pending domain configuration"
+  #
+  # Status values: healthy, degraded, down, not_setup, waiting
+
+# -------------------------------------------------------------------
+# BLOCKERS
+# External dependencies blocking progress
+# Claude will avoid suggesting work that's blocked
+# -------------------------------------------------------------------
+blockers: []
+  # Example:
+  # - id: domain-config
+  #   description: "Need domain for Cloudflare public routes"
+  #   blocks: [production-launch, ssl-setup]
+  #
+  # - id: stripe-api-key
+  #   description: "Waiting for Stripe test API key from finance team"
+  #   blocks: [payment-integration]
+
+# -------------------------------------------------------------------
+# NEXT PRIORITIES
+# What should be worked on next (with reasoning)
+# Helps Claude suggest appropriate next steps
+# -------------------------------------------------------------------
+next_priorities: []
+  # Example:
+  # - id: payment-integration
+  #   reason: "Revenue blocker - needed before launch"
+  #
+  # - id: user-profile
+  #   reason: "Dependency for RIASEC save feature"
+
+# -------------------------------------------------------------------
+# NOTES
+# Free-form context that doesn't fit above
+# -------------------------------------------------------------------
+notes: |
+  Add any additional context here.
+  Examples:
+  - Dev server running on localhost:3000
+  - Test with: curl http://localhost:3000/health
+  - Staging environment: https://staging.example.com
+
+# -------------------------------------------------------------------
+# REFERENCES (optional)
+# Quick links to important project files
+# -------------------------------------------------------------------
+references:
+  # roadmap: "docs/proposal_list.md"
+  # architecture: "openspec/specs/architecture.md"
+  # style_guide: "design-system/STYLE_GUIDE.md"

package/.claude/templates/design-context-template.md

@@ -1,6 +1,6 @@
 # Design Context: {PROJECT_NAME}
 
-> **Auto-generated by `/psetup` or `/designsetup`**
+> **Auto-generated by `/csetup` or `/designsetup`**
 > **Last updated:** {UPDATED_AT}
 
 ---
@@ -195,7 +195,7 @@ Tokens: ~500
 
 ## 🔄 When to Update This File
 
-Run `/psetup` or `/designsetup` again when:
+Run `/csetup` or `/designsetup` again when:
 - ✅ Design tokens change (new colors, spacing)
 - ✅ Component library changes (shadcn → Chakra UI)
 - ✅ STYLE_GUIDE.md updated