create-claude-context 1.0.0 → 1.2.0

package/templates/base/indexes/routing/CATEGORY_INDEX.md

@@ -1,39 +1,39 @@
-# Routing Category Index
-
-## Purpose
-Entry point for task routing and classification
-
-## Task Types Available
-
-| Task Type | Description | When to Use |
-|-----------|-------------|-------------|
-| **Feature** | New feature implementation | When building new functionality |
-| **Bug Fix** | Issue resolution | When fixing bugs or issues |
-| **Refactor** | Code improvement | When refactoring existing code |
-| **Documentation** | Doc updates | When updating documentation |
-| **Technical Debt** | Legacy improvements | When addressing technical debt |
-| **Performance** | Optimization | When improving performance |
-
-## Quick Start
-
-1. Load this category index first (~5k tokens)
-2. Identify relevant task type
-3. Load routing matrix for detailed classification
-4. Follow routing instructions for implementation
-
-## Context Budget
-- Category Index: ~5k tokens (2.5% of context window)
-- Routing Matrix: ~10k tokens (5% of context window)
-- Implementation Guidance: ~30k tokens (15% of context window)
-
-## Getting Started
-
-```bash
-# Load category index first
-Read: .claude/indexes/routing/CATEGORY_INDEX.md
-
-# Then load relevant routing matrix
-Read: .claude/indexes/routing/[task_type].md
-
-# Finally follow routing instructions
-Follow guidance in routing matrix
+# Routing Category Index
+
+## Purpose
+Entry point for task routing and classification
+
+## Task Types Available
+
+| Task Type | Description | When to Use |
+|-----------|-------------|-------------|
+| **Feature** | New feature implementation | When building new functionality |
+| **Bug Fix** | Issue resolution | When fixing bugs or issues |
+| **Refactor** | Code improvement | When refactoring existing code |
+| **Documentation** | Doc updates | When updating documentation |
+| **Technical Debt** | Legacy improvements | When addressing technical debt |
+| **Performance** | Optimization | When improving performance |
+
+## Quick Start
+
+1. Load this category index first (~5k tokens)
+2. Identify relevant task type
+3. Load routing matrix for detailed classification
+4. Follow routing instructions for implementation
+
+## Context Budget
+- Category Index: ~5k tokens (2.5% of context window)
+- Routing Matrix: ~10k tokens (5% of context window)
+- Implementation Guidance: ~30k tokens (15% of context window)
+
+## Getting Started
+
+```bash
+# Load category index first
+Read: .claude/indexes/routing/CATEGORY_INDEX.md
+
+# Then load relevant routing matrix
+Read: .claude/indexes/routing/[task_type].md
+
+# Finally follow routing instructions
+Follow guidance in routing matrix

package/templates/base/indexes/search/CATEGORY_INDEX.md

@@ -1,39 +1,39 @@
-# Search Category Index
-
-## Purpose
-Entry point for search strategies and pattern recognition
-
-## Search Patterns Available
-
-| Pattern Type | Description | When to Use |
-|--------------|-------------|-------------|
-| **Configuration Values** | Environment variables, hardcoded settings | When searching for config values |
-| **Business Logic** | Core application logic files | When locating business rules |
-| **Database Schema** | Models, migrations, queries | When investigating data structures |
-| **External Integrations** | API calls, webhooks, Connectors | When examining third-party integrations |
-| **Error Handling** | Exception handling patterns | When debugging error scenarios |
-| **Performance Bottlenecks** | Heavy computations, slow queries | When optimizing performance |
-
-## Quick Start
-
-1. Load this category index first (~5k tokens)
-2. Identify relevant search pattern
-3. Load pattern details for specific implementation
-4. Use search strategies for investigation
-
-## Context Budget
-- Category Index: ~5k tokens (2.5% of context window)
-- Pattern Details: ~10k tokens (5% of context window)
-- Search Execution: ~30k tokens (15% of context window)
-
-## Getting Started
-
-```bash
-# Load category index first
-Read: .claude/indexes/search/CATEGORY_INDEX.md
-
-# Then load relevant pattern details
-Read: .claude/indexes/search/[pattern_type].md
-
-# Finally execute search strategy
-Follow pattern instructions for investigation
+# Search Category Index
+
+## Purpose
+Entry point for search strategies and pattern recognition
+
+## Search Patterns Available
+
+| Pattern Type | Description | When to Use |
+|--------------|-------------|-------------|
+| **Configuration Values** | Environment variables, hardcoded settings | When searching for config values |
+| **Business Logic** | Core application logic files | When locating business rules |
+| **Database Schema** | Models, migrations, queries | When investigating data structures |
+| **External Integrations** | API calls, webhooks, Connectors | When examining third-party integrations |
+| **Error Handling** | Exception handling patterns | When debugging error scenarios |
+| **Performance Bottlenecks** | Heavy computations, slow queries | When optimizing performance |
+
+## Quick Start
+
+1. Load this category index first (~5k tokens)
+2. Identify relevant search pattern
+3. Load pattern details for specific implementation
+4. Use search strategies for investigation
+
+## Context Budget
+- Category Index: ~5k tokens (2.5% of context window)
+- Pattern Details: ~10k tokens (5% of context window)
+- Search Execution: ~30k tokens (15% of context window)
+
+## Getting Started
+
+```bash
+# Load category index first
+Read: .claude/indexes/search/CATEGORY_INDEX.md
+
+# Then load relevant pattern details
+Read: .claude/indexes/search/[pattern_type].md
+
+# Finally execute search strategy
+Follow pattern instructions for investigation

package/templates/base/indexes/workflows/CATEGORY_INDEX.md

@@ -1,38 +1,38 @@
-# Workflows Category Index
-
-## Purpose
-Entry point for workflow-related navigation and task classification
-
-## Categories Available
-
-| Category | Description | When to Use |
-|----------|-------------|-------------|
-| **jobs** | Job-related workflows (hiring, onboarding, payroll) | When working with HR or recruitment processes |
-| **payment** | Payment processing workflows | When implementing payment features |
-| **email** | Email-related workflows | When building email functionality |
-| **reporting** | Reporting and analytics workflows | When creating dashboards or reports |
-| **authentication** | Auth-related workflows | When implementing login/registration features |
-
-## Quick Start
-
-1. Load this category index first (~5k tokens)
-2. Identify relevant category
-3. Load domain index for detailed navigation
-4. Access workflow detail files for implementation
-
-## Context Budget
-- Category Index: ~5k tokens (2.5% of context window)
-- Domain Index: ~15k tokens (7.5% of context window)
-- Workflow Detail: ~40k tokens (20% of context window)
-
-## Getting Started
-
-```bash
-# Load category index first
-Read: .claude/indexes/workflows/CATEGORY_INDEX.md
-
-# Then load relevant domain index
-Read: .claude/indexes/workflows/[category].md
-
-# Finally load workflow detail file
-Read: .claude/context/workflows/[workflow].md
+# Workflows Category Index
+
+## Purpose
+Entry point for workflow-related navigation and task classification
+
+## Categories Available
+
+| Category | Description | When to Use |
+|----------|-------------|-------------|
+| **jobs** | Job-related workflows (hiring, onboarding, payroll) | When working with HR or recruitment processes |
+| **payment** | Payment processing workflows | When implementing payment features |
+| **email** | Email-related workflows | When building email functionality |
+| **reporting** | Reporting and analytics workflows | When creating dashboards or reports |
+| **authentication** | Auth-related workflows | When implementing login/registration features |
+
+## Quick Start
+
+1. Load this category index first (~5k tokens)
+2. Identify relevant category
+3. Load domain index for detailed navigation
+4. Access workflow detail files for implementation
+
+## Context Budget
+- Category Index: ~5k tokens (2.5% of context window)
+- Domain Index: ~15k tokens (7.5% of context window)
+- Workflow Detail: ~40k tokens (20% of context window)
+
+## Getting Started
+
+```bash
+# Load category index first
+Read: .claude/indexes/workflows/CATEGORY_INDEX.md
+
+# Then load relevant domain index
+Read: .claude/indexes/workflows/[category].md
+
+# Finally load workflow detail file
+Read: .claude/context/workflows/[workflow].md

package/templates/base/knowledge/README.md

@@ -1,98 +1,98 @@
-# Shared Knowledge Base
-
-Central repository for team knowledge, decisions, patterns, and session handoffs.
-
-## Directory Structure
-
-```
-knowledge/
-├── shared/           # Team-shared knowledge
-│   ├── decisions/    # Architecture Decision Records (ADRs)
-│   └── patterns/     # Reusable code patterns
-├── sessions/         # Session handoff documents
-└── README.md         # This file
-```
-
-## Shared Knowledge
-
-### Architecture Decision Records (ADRs)
-
-Located in `shared/decisions/`, ADRs document significant architectural decisions.
-
-**Creating an ADR:**
-1. Copy `shared/decisions/TEMPLATE.md`
-2. Name it `NNNN-descriptive-title.md` (e.g., `0001-use-postgresql.md`)
-3. Fill in all sections
-4. Submit for team review
-
-**ADR Statuses:**
-- `proposed` - Under discussion
-- `accepted` - Approved and in effect
-- `deprecated` - Superseded by another ADR
-- `rejected` - Not approved
-
-### Reusable Patterns
-
-Located in `shared/patterns/`, patterns document proven solutions to common problems.
-
-**Pattern Categories:**
-- `api/` - API design patterns
-- `data/` - Data handling patterns
-- `ui/` - User interface patterns
-- `testing/` - Testing patterns
-- `security/` - Security patterns
-
-## Session Handoffs
-
-Located in `sessions/`, handoff documents enable continuity between Claude Code sessions.
-
-**Handoff Document Contents:**
-- Session summary
-- Work completed
-- Work in progress
-- Blockers and issues
-- Next steps
-- Relevant context
-
-**Creating a Handoff:**
-```
-/collab handoff
-```
-
-**Naming Convention:**
-`YYYY-MM-DD-HH-MM-member-id.md`
-
-## Usage
-
-### Adding Knowledge
-
-1. Create document in appropriate directory
-2. Follow the template structure
-3. Run `/collab sync` to notify team
-
-### Finding Knowledge
-
-1. Check category directories for relevant content
-2. Use grep/search for specific terms
-3. Review recent session handoffs for context
-
-### Updating Knowledge
-
-1. Edit the document
-2. Update the `last_updated` metadata
-3. Add to revision history if significant
-
-## Retention Policy
-
-| Content Type | Retention |
-|--------------|-----------|
-| ADRs | Permanent (archive deprecated) |
-| Patterns | Permanent (version updates) |
-| Session Handoffs | 90 days (archive important ones) |
-
-## Best Practices
-
-1. **Keep it Current** - Update knowledge when code changes
-2. **Be Specific** - Include concrete examples
-3. **Link to Code** - Reference file:line where applicable
-4. **Review Regularly** - Prune outdated content monthly
+# Shared Knowledge Base
+
+Central repository for team knowledge, decisions, patterns, and session handoffs.
+
+## Directory Structure
+
+```
+knowledge/
+├── shared/           # Team-shared knowledge
+│   ├── decisions/    # Architecture Decision Records (ADRs)
+│   └── patterns/     # Reusable code patterns
+├── sessions/         # Session handoff documents
+└── README.md         # This file
+```
+
+## Shared Knowledge
+
+### Architecture Decision Records (ADRs)
+
+Located in `shared/decisions/`, ADRs document significant architectural decisions.
+
+**Creating an ADR:**
+1. Copy `shared/decisions/TEMPLATE.md`
+2. Name it `NNNN-descriptive-title.md` (e.g., `0001-use-postgresql.md`)
+3. Fill in all sections
+4. Submit for team review
+
+**ADR Statuses:**
+- `proposed` - Under discussion
+- `accepted` - Approved and in effect
+- `deprecated` - Superseded by another ADR
+- `rejected` - Not approved
+
+### Reusable Patterns
+
+Located in `shared/patterns/`, patterns document proven solutions to common problems.
+
+**Pattern Categories:**
+- `api/` - API design patterns
+- `data/` - Data handling patterns
+- `ui/` - User interface patterns
+- `testing/` - Testing patterns
+- `security/` - Security patterns
+
+## Session Handoffs
+
+Located in `sessions/`, handoff documents enable continuity between Claude Code sessions.
+
+**Handoff Document Contents:**
+- Session summary
+- Work completed
+- Work in progress
+- Blockers and issues
+- Next steps
+- Relevant context
+
+**Creating a Handoff:**
+```
+/collab handoff
+```
+
+**Naming Convention:**
+`YYYY-MM-DD-HH-MM-member-id.md`
+
+## Usage
+
+### Adding Knowledge
+
+1. Create document in appropriate directory
+2. Follow the template structure
+3. Run `/collab sync` to notify team
+
+### Finding Knowledge
+
+1. Check category directories for relevant content
+2. Use grep/search for specific terms
+3. Review recent session handoffs for context
+
+### Updating Knowledge
+
+1. Edit the document
+2. Update the `last_updated` metadata
+3. Add to revision history if significant
+
+## Retention Policy
+
+| Content Type | Retention |
+|--------------|-----------|
+| ADRs | Permanent (archive deprecated) |
+| Patterns | Permanent (version updates) |
+| Session Handoffs | 90 days (archive important ones) |
+
+## Best Practices
+
+1. **Keep it Current** - Update knowledge when code changes
+2. **Be Specific** - Include concrete examples
+3. **Link to Code** - Reference file:line where applicable
+4. **Review Regularly** - Prune outdated content monthly

package/templates/base/knowledge/sessions/README.md

@@ -1,88 +1,88 @@
-# Session Handoffs
-
-This directory contains session handoff documents that enable continuity between Claude Code sessions.
-
-## Purpose
-
-Session handoffs capture:
-- Work completed during a session
-- Work in progress with current state
-- Blockers and issues encountered
-- Context needed for continuation
-- Recommended next steps
-
-## Creating a Handoff
-
-Use the `/collab handoff` command at the end of a session:
-
-```
-/collab handoff
-```
-
-This generates a handoff document from the current session state.
-
-## Manual Handoff
-
-If the command isn't available, copy `TEMPLATE.md` and fill in:
-
-1. Session metadata
-2. Completed work summary
-3. In-progress work state
-4. Any blockers or issues
-5. Context for next session
-6. Recommended next steps
-
-## Naming Convention
-
-Handoff files are named:
-```
-YYYY-MM-DD-HH-MM-member-id.md
-```
-
-Example: `2024-01-15-14-30-dev-1.md`
-
-## Finding Relevant Handoffs
-
-### Most Recent
-
-Sort by filename (most recent first):
-```bash
-ls -r sessions/*.md
-```
-
-### By Team Member
-
-```bash
-ls sessions/*-member-id.md
-```
-
-### By Date Range
-
-```bash
-ls sessions/2024-01-*.md
-```
-
-## Retention
-
-| Age | Action |
-|-----|--------|
-| < 7 days | Keep (active reference) |
-| 7-30 days | Review for archival |
-| 30-90 days | Archive important, delete routine |
-| > 90 days | Delete unless historically significant |
-
-## Archiving
-
-Important handoffs (major feature completions, incident resolutions) should be:
-
-1. Moved to `sessions/archive/`
-2. Renamed with descriptive suffix: `YYYY-MM-DD-feature-name.md`
-3. Referenced in relevant ADRs if applicable
-
-## Best Practices
-
-1. **Create handoffs proactively** - Don't wait until context is lost
-2. **Be specific** - Include file paths, line numbers, commit hashes
-3. **Note blockers clearly** - Help the next person avoid wasted effort
-4. **Include context** - Share discoveries that aren't in the code
-5. **Suggest next steps** - Prioritize what should happen next
+# Session Handoffs
+
+This directory contains session handoff documents that enable continuity between Claude Code sessions.
+
+## Purpose
+
+Session handoffs capture:
+- Work completed during a session
+- Work in progress with current state
+- Blockers and issues encountered
+- Context needed for continuation
+- Recommended next steps
+
+## Creating a Handoff
+
+Use the `/collab handoff` command at the end of a session:
+
+```
+/collab handoff
+```
+
+This generates a handoff document from the current session state.
+
+## Manual Handoff
+
+If the command isn't available, copy `TEMPLATE.md` and fill in:
+
+1. Session metadata
+2. Completed work summary
+3. In-progress work state
+4. Any blockers or issues
+5. Context for next session
+6. Recommended next steps
+
+## Naming Convention
+
+Handoff files are named:
+```
+YYYY-MM-DD-HH-MM-member-id.md
+```
+
+Example: `2024-01-15-14-30-dev-1.md`
+
+## Finding Relevant Handoffs
+
+### Most Recent
+
+Sort by filename (most recent first):
+```bash
+ls -r sessions/*.md
+```
+
+### By Team Member
+
+```bash
+ls sessions/*-member-id.md
+```
+
+### By Date Range
+
+```bash
+ls sessions/2024-01-*.md
+```
+
+## Retention
+
+| Age | Action |
+|-----|--------|
+| < 7 days | Keep (active reference) |
+| 7-30 days | Review for archival |
+| 30-90 days | Archive important, delete routine |
+| > 90 days | Delete unless historically significant |
+
+## Archiving
+
+Important handoffs (major feature completions, incident resolutions) should be:
+
+1. Moved to `sessions/archive/`
+2. Renamed with descriptive suffix: `YYYY-MM-DD-feature-name.md`
+3. Referenced in relevant ADRs if applicable
+
+## Best Practices
+
+1. **Create handoffs proactively** - Don't wait until context is lost
+2. **Be specific** - Include file paths, line numbers, commit hashes
+3. **Note blockers clearly** - Help the next person avoid wasted effort
+4. **Include context** - Share discoveries that aren't in the code
+5. **Suggest next steps** - Prioritize what should happen next