claude-code-workflow 6.1.3 → 6.2.1

package/.claude/workflows/cli-templates/prompts/tech/tech-module-format.txt

@@ -1,359 +0,0 @@
-Template for generating tech stack module documentation files
-
-## Purpose
-Guide agent to create modular tech stack documentation from Exa research results.
-
-## File Location
-`.claude/skills/{tech_stack_name}/*.md`
-
-## Module Structure
-
-Each module should include:
-- **Frontmatter**: YAML with module name and tech stack
-- **Main Sections**: Clear headings with hierarchical organization
-- **Code Examples**: Real examples from Exa research
-- **Best Practices**: Do's and don'ts sections
-- **References**: Attribution to Exa sources
-
----
-
-## Module 1: principles.md (~3K tokens)
-
-**Purpose**: Core concepts, philosophies, and fundamental principles
-
-**Frontmatter**:
-```yaml
----
-module: principles
-tech_stack: {tech_stack_name}
-description: Core concepts and philosophies
-tokens: ~3000
----
-```
-
-**Structure**:
-```markdown
-# {Tech} Principles
-
-## Core Concepts
-- Fundamental principle 1
-- Fundamental principle 2
-- Key philosophy
-
-## Design Philosophy
-- Approach to problem-solving
-- Architectural principles
-- Core values
-
-## Key Features
-- Feature 1: Description
-- Feature 2: Description
-
-## When to Use
-- Use case scenarios
-- Best fit situations
-
-## References
-- Source 1 from Exa
-- Source 2 from Exa
-```
-
----
-
-## Module 2: patterns.md (~5K tokens)
-
-**Purpose**: Implementation patterns with code examples
-
-**Frontmatter**:
-```yaml
----
-module: patterns
-tech_stack: {tech_stack_name}
-description: Implementation patterns with examples
-tokens: ~5000
----
-```
-
-**Structure**:
-```markdown
-# {Tech} Patterns
-
-## Common Patterns
-
-### Pattern 1: {Name}
-**Use Case**: When to use this pattern
-**Implementation**:
-\`\`\`{language}
-// Code example from Exa
-\`\`\`
-**Benefits**: Why use this pattern
-
-### Pattern 2: {Name}
-[Same structure]
-
-## Architectural Patterns
-- Pattern descriptions
-- Code examples
-
-## Component Patterns
-- Reusable component structures
-- Integration examples
-
-## References
-- Exa sources with pattern examples
-```
-
----
-
-## Module 3: practices.md (~4K tokens)
-
-**Purpose**: Best practices, anti-patterns, pitfalls
-
-**Frontmatter**:
-```yaml
----
-module: practices
-tech_stack: {tech_stack_name}
-description: Best practices and anti-patterns
-tokens: ~4000
----
-```
-
-**Structure**:
-```markdown
-# {Tech} Best Practices
-
-## Do's
-✅ **Practice 1**: Description
-   - Rationale
-   - Example scenario
-
-✅ **Practice 2**: Description
-
-## Don'ts
-❌ **Anti-pattern 1**: What to avoid
-   - Why it's problematic
-   - Better alternative
-
-❌ **Anti-pattern 2**: What to avoid
-
-## Common Pitfalls
-1. **Pitfall 1**: Description and solution
-2. **Pitfall 2**: Description and solution
-
-## Performance Considerations
-- Optimization techniques
-- Common bottlenecks
-
-## Security Best Practices
-- Security considerations
-- Common vulnerabilities
-
-## References
-- Exa sources for best practices
-```
-
----
-
-## Module 4: testing.md (~3K tokens)
-
-**Purpose**: Testing strategies, frameworks, and examples
-
-**Frontmatter**:
-```yaml
----
-module: testing
-tech_stack: {tech_stack_name}
-description: Testing strategies and frameworks
-tokens: ~3000
----
-```
-
-**Structure**:
-```markdown
-# {Tech} Testing
-
-## Testing Strategies
-- Unit testing approach
-- Integration testing approach
-- E2E testing approach
-
-## Testing Frameworks
-### Framework 1
-- Setup
-- Basic usage
-- Example:
-\`\`\`{language}
-// Test example from Exa
-\`\`\`
-
-## Test Patterns
-- Common test patterns
-- Mock strategies
-- Assertion best practices
-
-## Coverage Recommendations
-- What to test
-- Coverage targets
-
-## References
-- Exa sources for testing examples
-```
-
----
-
-## Module 5: config.md (~3K tokens)
-
-**Purpose**: Setup, configuration, and tooling
-
-**Frontmatter**:
-```yaml
----
-module: config
-tech_stack: {tech_stack_name}
-description: Setup, configuration, and tooling
-tokens: ~3000
----
-```
-
-**Structure**:
-```markdown
-# {Tech} Configuration
-
-## Installation
-\`\`\`bash
-# Installation commands
-\`\`\`
-
-## Basic Configuration
-\`\`\`{config-format}
-// Configuration example from Exa
-\`\`\`
-
-## Common Configurations
-### Development
-- Dev config setup
-- Hot reload configuration
-
-### Production
-- Production optimizations
-- Build configurations
-
-## Tooling
-- Recommended tools
-- IDE/Editor setup
-- Linters and formatters
-
-## Environment Setup
-- Environment variables
-- Config file structure
-
-## References
-- Exa sources for configuration
-```
-
----
-
-## Module 6: frameworks.md (~4K tokens) [CONDITIONAL]
-
-**Purpose**: Framework integration patterns (only for composite tech stacks)
-
-**Condition**: Only generate if `is_composite = true`
-
-**Frontmatter**:
-```yaml
----
-module: frameworks
-tech_stack: {tech_stack_name}
-description: Framework integration patterns
-tokens: ~4000
-conditional: composite_only
----
-```
-
-**Structure**:
-```markdown
-# {Main Tech} + {Framework} Integration
-
-## Integration Overview
-- How {main_tech} works with {framework}
-- Architecture considerations
-
-## Setup
-\`\`\`bash
-# Integration setup commands
-\`\`\`
-
-## Integration Patterns
-
-### Pattern 1: {Name}
-\`\`\`{language}
-// Integration example from Exa
-\`\`\`
-
-## Best Practices
-- Integration best practices
-- Common pitfalls
-
-## Examples
-- Real-world integration examples
-- Code samples from Exa
-
-## References
-- Exa sources for integration patterns
-```
-
----
-
-## Metadata File: metadata.json
-
-**Purpose**: Store generation metadata and research summary
-
-**Structure**:
-```json
-{
-  "tech_stack_name": "typescript-react-nextjs",
-  "components": ["typescript", "react", "nextjs"],
-  "is_composite": true,
-  "generated_at": "2025-11-04T22:00:00Z",
-  "source": "exa-research",
-  "research_summary": {
-    "total_queries": 6,
-    "total_sources": 25,
-    "query_list": [
-      "typescript core principles best practices 2025",
-      "react common patterns architecture examples",
-      "nextjs configuration setup tooling 2025",
-      "testing strategies",
-      "react nextjs integration",
-      "typescript react integration"
-    ]
-  }
-}
-```
-
----
-
-## Generation Guidelines
-
-### Content Synthesis from Exa
-- Extract relevant code examples from Exa results
-- Synthesize information from multiple sources
-- Maintain technical accuracy
-- Cite sources in References section
-
-### Formatting Rules
-- Use clear markdown headers
-- Include code fences with language specification
-- Use emoji for Do's (✅) and Don'ts (❌)
-- Keep token estimates accurate
-
-### Error Handling
-- If Exa query fails, note in References section
-- If insufficient data, mark section as "Limited research available"
-- Handle missing components gracefully
-
-### Token Distribution
-- Total budget: ~22K tokens for 6 modules
-- Adjust module size based on content availability
-- Prioritize quality over hitting exact token counts

package/.claude/workflows/cli-templates/prompts/tech/tech-skill-index.txt

@@ -1,185 +0,0 @@
-Template for generating tech stack SKILL.md index file
-
-## Purpose
-Create main SKILL package index with module references and loading recommendations.
-
-## File Location
-`.claude/skills/{tech_stack_name}/SKILL.md`
-
-## Template Structure
-
-```markdown
----
-name: {TECH_STACK_NAME}
-description: {MAIN_TECH} development guidelines from industry standards (Exa research)
-version: 1.0.0
-generated: {ISO_TIMESTAMP}
-source: exa-research
----
-# {TechStackTitle} SKILL Package
-
-## Overview
-
-{Brief 1-2 sentence description of the tech stack and purpose of this SKILL package}
-
-**Primary Technology**: {MAIN_TECH}
-{IF_COMPOSITE}**Frameworks**: {COMPONENT_LIST}{/IF_COMPOSITE}
-
-## Modular Documentation
-
-### Core Understanding (~8K tokens)
-- [Principles](./principles.md) - Core concepts and philosophies
-- [Patterns](./patterns.md) - Implementation patterns with examples
-
-### Practical Guidance (~7K tokens)
-- [Best Practices](./practices.md) - Do's, don'ts, anti-patterns
-- [Testing](./testing.md) - Testing strategies and frameworks
-
-### Configuration & Integration (~7K tokens)
-- [Configuration](./config.md) - Setup, tooling, configuration
-{IF_COMPOSITE}- [Frameworks](./frameworks.md) - Integration patterns{/IF_COMPOSITE}
-
-## Loading Recommendations
-
-### Quick Reference (~7K tokens)
-Load for quick consultation on core concepts:
-- principles.md
-- practices.md
-
-**Use When**: Need quick reminder of best practices or core principles
-
-### Implementation Focus (~8K tokens)
-Load for active development work:
-- patterns.md
-- config.md
-
-**Use When**: Writing code, setting up projects, implementing features
-
-### Complete Package (~22K tokens)
-Load all modules for comprehensive understanding:
-- All 5-6 modules
-
-**Use When**: Learning tech stack, architecture reviews, comprehensive reference
-
-## Usage
-
-**Load this SKILL when**:
-- Starting new {TECH_STACK} projects
-- Reviewing {TECH_STACK} code
-- Learning {TECH_STACK} best practices
-- Implementing {TECH_STACK} patterns
-- Troubleshooting {TECH_STACK} issues
-
-**Auto-triggers on**:
-- Keywords: {TECH_KEYWORDS}
-- File types: {FILE_EXTENSIONS}
-
-## Research Metadata
-
-- **Generated**: {ISO_TIMESTAMP}
-- **Source**: Exa Research (web search + code context)
-- **Queries Executed**: {QUERY_COUNT}
-- **Sources Consulted**: {SOURCE_COUNT}
-- **Research Quality**: {QUALITY_INDICATOR}
-
-## Tech Stack Components
-
-**Primary**: {MAIN_TECH} - {MAIN_TECH_DESCRIPTION}
-
-{IF_COMPOSITE}
-**Additional Frameworks**:
-{FOR_EACH_COMPONENT}
-- **{COMPONENT_NAME}**: {COMPONENT_DESCRIPTION}
-{/FOR_EACH_COMPONENT}
-{/IF_COMPOSITE}
-
-## Version History
-
-- **v1.0.0** ({DATE}): Initial SKILL package generated from Exa research
-
----
-
-## Developer Notes
-
-This SKILL package was auto-generated using:
-- `/memory:tech-research` command
-- Exa AI research APIs (mcp__exa__get_code_context_exa, mcp__exa__web_search_exa)
-- Token limit: ~5K per module, ~22K total
-
-To regenerate:
-```bash
-/memory:tech-research "{tech_stack_name}" --regenerate
-```
-```
-
----
-
-## Variable Substitution Guide
-
-### Required Variables
-- `{TECH_STACK_NAME}`: Lowercase hyphenated name (e.g., "typescript-react-nextjs")
-- `{TechStackTitle}`: Title case display name (e.g., "TypeScript React Next.js")
-- `{MAIN_TECH}`: Primary technology (e.g., "TypeScript")
-- `{ISO_TIMESTAMP}`: ISO 8601 timestamp (e.g., "2025-11-04T22:00:00Z")
-- `{QUERY_COUNT}`: Number of Exa queries executed (e.g., 6)
-- `{SOURCE_COUNT}`: Total sources consulted (e.g., 25)
-
-### Conditional Variables
-- `{IF_COMPOSITE}...{/IF_COMPOSITE}`: Only include if tech stack has multiple components
-- `{COMPONENT_LIST}`: Comma-separated list of framework names
-- `{FOR_EACH_COMPONENT}...{/FOR_EACH_COMPONENT}`: Loop through components
-
-### Optional Variables
-- `{MAIN_TECH_DESCRIPTION}`: One-line description of primary tech
-- `{COMPONENT_DESCRIPTION}`: One-line description per component
-- `{TECH_KEYWORDS}`: Comma-separated trigger keywords
-- `{FILE_EXTENSIONS}`: File extensions (e.g., ".ts, .tsx, .jsx")
-- `{QUALITY_INDICATOR}`: Research quality metric (e.g., "High", "Medium")
-
----
-
-## Generation Instructions
-
-### Step 1: Read metadata.json
-Extract values for variables from metadata.json generated during module creation.
-
-### Step 2: Determine composite status
-- Single tech: Omit {IF_COMPOSITE} sections
-- Composite: Include frameworks section and integration module reference
-
-### Step 3: Calculate token estimates
-- Verify module files exist
-- Adjust token estimates based on actual file sizes
-- Update loading recommendation estimates
-
-### Step 4: Generate descriptions
-- **Overview**: Brief description of tech stack purpose
-- **Main tech description**: One-liner for primary technology
-- **Component descriptions**: One-liner per additional framework
-
-### Step 5: Build keyword lists
-- Extract common keywords from tech stack name
-- Add file extensions relevant to tech stack
-- Include framework-specific triggers
-
-### Step 6: Format timestamps
-- Use ISO 8601 format for all timestamps
-- Include timezone (UTC recommended)
-
-### Step 7: Write SKILL.md
-- Apply template with all substitutions
-- Validate markdown formatting
-- Verify all relative paths work
-
----
-
-## Validation Checklist
-
-- [ ] All module files exist and are referenced
-- [ ] Token estimates are reasonably accurate
-- [ ] Conditional sections handled correctly (composite vs single)
-- [ ] Timestamps in ISO 8601 format
-- [ ] All relative paths use ./ prefix
-- [ ] Metadata section matches metadata.json
-- [ ] Loading recommendations align with actual module sizes
-- [ ] Usage section includes relevant trigger keywords

package/.claude/workflows/cli-templates/prompts/test/test-concept-analysis.txt

@@ -1,179 +0,0 @@
-PURPOSE: Analyze test coverage gaps and design comprehensive test generation strategy
-TASK:
-• Read test-context-package.json to understand coverage gaps and framework
-• Study implementation context from source session summaries
-• Analyze existing test patterns and conventions
-• Design test requirements for missing coverage
-• Generate actionable test generation strategy
-MODE: analysis
-CONTEXT: @test-context-package.json @../../../{source-session-id}/.summaries/*.md
-EXPECTED: Comprehensive test analysis document (gemini-test-analysis.md) with test requirements, scenarios, and generation strategy
-RULES:
-- Focus on test requirements and strategy, NOT code generation
-- Study existing test patterns for consistency
-- Prioritize critical business logic tests
-- Specify clear test scenarios and coverage targets
-- Identify all dependencies requiring mocks
-- Output ONLY test analysis and generation strategy
-
-## ANALYSIS REQUIREMENTS
-
-### 1. Implementation Understanding
-- Load all implementation summaries from source session
-- Understand implemented features, APIs, and business logic
-- Extract key functions, classes, and modules
-- Identify integration points and dependencies
-
-### 2. Existing Test Pattern Analysis
-- Study existing test files for patterns and conventions
-- Identify test structure (describe/it, test suites, fixtures)
-- Analyze assertion patterns and mocking strategies
-- Extract test setup/teardown patterns
-
-### 3. Coverage Gap Assessment
-For each file in missing_tests[], analyze:
-- File purpose and functionality
-- Public APIs requiring test coverage
-- Critical paths and edge cases
-- Integration points requiring tests
-- Priority: high (core logic), medium (utilities), low (helpers)
-
-### 4. Test Requirements Specification
-For each missing test file, specify:
-- Test scope: What needs to be tested
-- Test scenarios: Happy path, error cases, edge cases, integration
-- Test data: Required fixtures, mocks, test data
-- Dependencies: External services, databases, APIs to mock
-- Coverage targets: Functions/methods requiring tests
-
-### 5. Test Generation Strategy
-- Determine test generation approach for each file
-- Identify reusable test patterns from existing tests
-- Plan test data and fixture requirements
-- Define mocking strategy for dependencies
-- Specify expected test file structure
-
-## EXPECTED OUTPUT FORMAT
-
-Write comprehensive analysis to gemini-test-analysis.md:
-
-# Test Generation Analysis
-
-## 1. Implementation Context Summary
-- **Source Session**: {source_session_id}
-- **Implemented Features**: {feature_summary}
-- **Changed Files**: {list_of_implementation_files}
-- **Tech Stack**: {technologies_used}
-
-## 2. Test Coverage Assessment
-- **Existing Tests**: {count} files
-- **Missing Tests**: {count} files
-- **Coverage Percentage**: {percentage}%
-- **Priority Breakdown**:
-  - High Priority: {count} files (core business logic)
-  - Medium Priority: {count} files (utilities, helpers)
-  - Low Priority: {count} files (configuration, constants)
-
-## 3. Existing Test Pattern Analysis
-- **Test Framework**: {framework_name_and_version}
-- **File Naming Convention**: {pattern}
-- **Test Structure**: {describe_it_or_other}
-- **Assertion Style**: {expect_assert_should}
-- **Mocking Strategy**: {mocking_framework_and_patterns}
-- **Setup/Teardown**: {beforeEach_afterEach_patterns}
-- **Test Data**: {fixtures_factories_builders}
-
-## 4. Test Requirements by File
-
-### File: {implementation_file_path}
-**Test File**: {suggested_test_file_path}
-**Priority**: {high|medium|low}
-
-#### Scope
-- {description_of_what_needs_testing}
-
-#### Test Scenarios
-1. **Happy Path Tests**
-   - {scenario_1}
-   - {scenario_2}
-
-2. **Error Handling Tests**
-   - {error_scenario_1}
-   - {error_scenario_2}
-
-3. **Edge Case Tests**
-   - {edge_case_1}
-   - {edge_case_2}
-
-4. **Integration Tests** (if applicable)
-   - {integration_scenario_1}
-   - {integration_scenario_2}
-
-#### Test Data & Fixtures
-- {required_test_data}
-- {required_mocks}
-- {required_fixtures}
-
-#### Dependencies to Mock
-- {external_service_1}
-- {external_service_2}
-
-#### Coverage Targets
-- Function: {function_name} - {test_requirements}
-- Function: {function_name} - {test_requirements}
-
----
-[Repeat for each missing test file]
----
-
-## 5. Test Generation Strategy
-
-### Overall Approach
-- {strategy_description}
-
-### Test Generation Order
-1. {file_1} - {rationale}
-2. {file_2} - {rationale}
-3. {file_3} - {rationale}
-
-### Reusable Patterns
-- {pattern_1_from_existing_tests}
-- {pattern_2_from_existing_tests}
-
-### Test Data Strategy
-- {approach_to_test_data_and_fixtures}
-
-### Mocking Strategy
-- {approach_to_mocking_dependencies}
-
-### Quality Criteria
-- Code coverage target: {percentage}%
-- Test scenarios per function: {count}
-- Integration test coverage: {approach}
-
-## 6. Implementation Targets
-
-**Purpose**: Identify new test files to create
-
-**Format**: New test files only (no existing files to modify)
-
-**Test Files to Create**:
-1. **Target**: `tests/auth/TokenValidator.test.ts`
-   - **Type**: Create new test file
-   - **Purpose**: Test TokenValidator class
-   - **Scenarios**: 15 test cases covering validation logic, error handling, edge cases
-   - **Dependencies**: Mock JWT library, test fixtures for tokens
-
-2. **Target**: `tests/middleware/errorHandler.test.ts`
-   - **Type**: Create new test file
-   - **Purpose**: Test error handling middleware
-   - **Scenarios**: 8 test cases for different error types and response formats
-   - **Dependencies**: Mock Express req/res/next, error fixtures
-
-[List all test files to create]
-
-## 7. Success Metrics
-- **Test Coverage Goal**: {target_percentage}%
-- **Test Quality**: All scenarios covered (happy, error, edge, integration)
-- **Convention Compliance**: Follow existing test patterns
-- **Maintainability**: Clear test descriptions, reusable fixtures