@codemieai/code 0.0.33 → 0.0.34

package/dist/agents/plugins/claude/plugin/claude-templates/templates/guides/testing/testing-patterns.md.template

@@ -1,143 +1,315 @@
+---
 # Testing Patterns
 
-## Quick Summary
+<!--
+GENERATION INSTRUCTIONS:
+1. Identify test framework from dependencies/config
+2. Scan test directory structure and naming patterns
+3. Extract fixture/factory patterns from setup files
+4. Find mocking patterns in existing tests
+5. Locate test database configuration
+6. Extract commands from package.json/Makefile/scripts
+7. Output: 150-300 lines max
+-->
+
+**Project**: [Extract from config]
+**Framework**: [Detect: Jest | Pytest | Mocha | Vitest | RSpec | etc.]
+**Coverage Tool**: [Detect: coverage.py | nyc | c8 | etc.]
+**Test Location**: `[Detect tests/ or __tests__/ or spec/]`
+
+---
+
+## Test Organization
+
+<!-- Scan actual test directory structure -->
+
+```
+[test_root]/
+├── [unit/]                 [Detected structure]
+│   └── [pattern]/
+├── [integration/]          [If exists]
+│   └── [pattern]/
+├── [e2e/]                  [If exists]
+├── [fixtures/factories/]   [Test data location]
+└── [setup files]           [conftest.py, setup.ts, etc.]
+```
+
+### Naming Conventions
 
-Testing patterns for [PROJECT_NAME] using [TEST_FRAMEWORK]: unit tests, integration tests, fixtures, and mocking.
+| Element | Pattern | Example |
+|---------|---------|---------|
+| Test files | `[detected pattern]` | `[actual example]` |
+| Test functions | `[detected pattern]` | `[actual example]` |
+| Fixture files | `[detected pattern]` | `[actual example]` |
 
-**Category**: Testing
-**Complexity**: Medium
-**Prerequisites**: [TEST_FRAMEWORK], testing fundamentals
+---
+
+## Running Tests
+
+<!-- Extract exact commands from scripts -->
+
+| Action | Command |
+|--------|---------|
+| All tests | `[exact command]` |
+| Unit only | `[command or N/A]` |
+| Integration only | `[command or N/A]` |
+| Single file | `[command pattern]` |
+| Single test | `[command pattern]` |
+| Watch mode | `[command or N/A]` |
+| With coverage | `[command]` |
+| Verbose/debug | `[command with flags]` |
 
 ---
 
-## 🚨 SIZE LIMIT WARNING
+## Unit Test Pattern
 
-**This generated guide MUST be 200-400 lines maximum.**
+<!-- Extract canonical unit test example -->
 
-**When filling this template**:
-- ✅ Code examples: 5-15 lines (NEVER > 20)
-- ✅ ONE example per pattern
-- ✅ Use file:line references, not full code
-- ✅ Use tables for multiple patterns
-- ❌ NO multiple examples for same pattern
-- ❌ NO verbose explanations
-- ❌ NO copying entire functions
+```[lang]
+// Source: [file:lines]
+[Extract representative unit test showing framework syntax]
+```
+
+### Structure
 
-**Validate line count after generation**: `wc -l [this-file]`
-**If > 400 lines**: Condense immediately before continuing!
+```[lang]
+// Standard test structure in this codebase:
+[describe/test block] {
+    // Arrange - setup test data
+    // Act - call function under test
+    // Assert - verify result
+}
+```
 
 ---
 
-## Test Structure
+## Fixtures / Test Data
+
+<!-- Find fixture or factory patterns -->
 
+### Setup Pattern
+
+```[lang]
+// Source: [file:lines]
+[Extract fixture/factory definition]
 ```
-tests/
-├── unit/                   Mirror source structure
-│   └── [module]/
-│       └── test_[file].[ext]
-├── integration/
-│   └── test_[feature].[ext]
-└── fixtures/
-    └── [fixture_files]
+
+### Using Fixtures
+
+```[lang]
+// Source: [file:lines]
+[Extract fixture usage in test]
 ```
 
-**Naming**: `test_[scenario]_[expected_outcome]`
+### Common Fixtures
+
+| Fixture | Purpose | Location |
+|---------|---------|----------|
+| `[fixture name]` | [What it provides] | `[file:line]` |
+| `[fixture name]` | [What it provides] | `[file:line]` |
+| `[fixture name]` | [What it provides] | `[file:line]` |
 
 ---
 
-## Unit Test Pattern
+## Mocking
+
+<!-- Extract mocking patterns used -->
+
+### Mock Syntax
+
+```[lang]
+// Source: [file:lines]
+[Extract mocking example - service, module, or function mock]
+```
+
+### What to Mock
+
+| Layer | Mock In Unit Tests | Mock In Integration |
+|-------|-------------------|---------------------|
+| External APIs | ✅ Always | ✅ Usually |
+| Database | ✅ Usually | ❌ Use test DB |
+| Other services | ✅ Yes | Depends |
+| File system | ✅ Yes | Depends |
+| Time/Date | ✅ When needed | When needed |
+
+### Mock Patterns in This Codebase
+
+| What | How | Source |
+|------|-----|--------|
+| `[Service/Module]` | `[mock syntax]` | `[file:line]` |
+| `[External API]` | `[mock syntax]` | `[file:line]` |
+| `[Database/Repository]` | `[mock syntax]` | `[file:line]` |
+
+---
+
+## Database Testing
+
+<!-- Find test database configuration -->
 
-```[language]
-# Source: [test_file:lines]
-[unit_test_example]
+### Setup
+
+**Test DB**: `[separate DB / transactions / in-memory / mocked]`
+
+```[lang]
+// Source: [file:lines]
+[Extract test DB setup/connection]
+```
+
+### Isolation Pattern
+
+```[lang]
+// Source: [file:lines]
+[Extract transaction rollback or cleanup pattern]
 ```
 
-**Structure**: Arrange → Act → Assert
+### Seeding Test Data
+
+```[lang]
+// Source: [file:lines]
+[Extract test data seeding pattern]
+```
 
 ---
 
-## Fixtures
+## API / Endpoint Testing
+
+<!-- If web app, find HTTP testing patterns -->
+
+### Test Client Setup
 
-```[language]
-# Source: [conftest_or_setup:lines]
-[fixture_example]
+```[lang]
+// Source: [file:lines]
+[Extract test client/supertest/httpx setup]
 ```
 
-**Scopes**: function | class | module | session
+### Request Pattern
+
+```[lang]
+// Source: [file:lines]
+[Extract API test example]
+```
 
 ---
 
-## Mocking
+## Async Testing
 
-```[language]
-# Source: [test_file:lines]
-[mock_example]
+<!-- If async code exists, find testing pattern -->
+
+```[lang]
+// Source: [file:lines]
+[Extract async test example]
 ```
 
-**Mock**: External APIs, database (for unit tests), file system, time
+**Pattern**: `[async/await | done callback | returns promise]`
 
 ---
 
 ## Parameterized Tests
 
-```[language]
-# Source: [test_file:lines]
-[parameterized_example]
+<!-- Find data-driven test patterns -->
+
+```[lang]
+// Source: [file:lines]
+[Extract parameterized/table-driven test]
 ```
 
 ---
 
-## Integration Tests
+## Coverage
 
-```[language]
-# Source: [test_file:lines]
-[integration_test_example]
-```
+<!-- Extract coverage configuration -->
 
-**Characteristics**: Multiple components, real dependencies (test DB)
+### Configuration
 
----
+**Config file**: `[jest.config / .coveragerc / nyc config]`
+
+| Setting | Value |
+|---------|-------|
+| Threshold | `[percentage or N/A]` |
+| Include | `[paths/patterns]` |
+| Exclude | `[paths/patterns]` |
 
-## Test Commands
+### Generate Report
 
 ```bash
-# Run all tests
-[run_all]
+# Generate coverage report
+[coverage command]
 
-# Run specific file
-[run_file]
+# View HTML report (if available)
+[open coverage/index.html or equivalent]
+```
+
+---
+
+## Test Environment
+
+<!-- Find environment setup for tests -->
+
+### Environment Variables
+
+```[lang]
+// Source: [file:lines] or [.env.test]
+[Extract test environment config]
+```
+
+### Setup/Teardown
 
-# Run with coverage
-[coverage]
+```[lang]
+// Source: [file:lines]
+[Extract global setup/teardown if exists]
 ```
 
 ---
 
-## Coverage
+## Writing New Tests
+
+### Checklist
 
-**Targets**:
-- Overall: [X]%
-- Critical paths: [Y]%
+1. Create test file: `[path pattern]`
+2. Import test utilities: `[common imports]`
+3. Setup fixtures needed
+4. Follow naming: `[test naming pattern]`
+5. Run to verify: `[run single test command]`
 
-**Focus on**: Business logic, error handling, edge cases
+### Template
+
+```[lang]
+// Starter template for new test file
+[Extract or construct minimal test file template]
+```
 
 ---
 
-## Best Practices
+## Common Patterns
 
-| ✅ DO | ❌ DON'T |
-|-------|----------|
-| One assertion per test | Multiple scenarios in one test |
-| Descriptive test names | `test1`, `test2` |
-| Arrange-Act-Assert | Mixed concerns |
-| Mock external dependencies | Real APIs in unit tests |
-| Keep tests fast | Long-running tests |
+| Pattern | When to Use | Example |
+|---------|-------------|---------|
+| `[beforeEach/setUp]` | Reset state per test | `[file:line]` |
+| `[afterAll/teardown]` | Cleanup resources | `[file:line]` |
+| `[test.skip/xtest]` | Temporarily disable | - |
+| `[test.only/fit]` | Run single test (debug) | - |
 
 ---
 
-## References
+## Troubleshooting
 
-- **Tests**: `[test_directory]/`
-- **Fixtures**: `[fixture_location]`
+| Issue | Solution |
+|-------|----------|
+| Tests interfering | Check isolation, add cleanup |
+| Async timeout | Increase timeout or check await |
+| Mock not working | Verify mock path matches import |
+| DB state issues | Check transaction rollback |
 
 ---
+
+## Quick Reference
+
+| Need | Location |
+|------|----------|
+| Test config | `[config file path]` |
+| Fixtures | `[fixtures path]` |
+| Factories | `[factories path]` |
+| Test utilities | `[helpers/utils path]` |
+| Coverage config | `[config path]` |
+
+---

package/dist/agents/plugins/claude/plugin/commands/README.md

@@ -0,0 +1,133 @@
+# Claude Code Plugin Commands
+
+Built-in commands for the CodeMie Claude Code plugin. These commands are automatically available when using `codemie-claude`.
+
+## Project Documentation
+
+### `/codemie-init` - Generate Project Documentation
+
+Analyzes your codebase and generates AI-optimized documentation:
+- Main `CLAUDE.md` file with project-specific workflows
+- Detailed guides in `.codemie/guides/` (only for patterns that exist in your code)
+
+**Usage:**
+```
+/codemie-init
+/codemie-init "focus on API patterns"
+```
+
+**What it does:**
+1. Analyzes project structure, tech stack, and patterns
+2. Detects which categories apply (Architecture, API, Testing, etc.)
+3. Generates guides only for detected patterns (no empty guides)
+4. Creates/updates `CLAUDE.md` with guide references
+5. Preserves existing customizations when updating
+
+**Output:**
+- `CLAUDE.md` (200-300 lines) - Project overview and guide references
+- `.codemie/guides/<category>/*.md` (200-400 lines each) - Detailed patterns
+
+### `/codemie-subagents` - Generate Specialized Agents
+
+Creates project-specific subagent files tailored to your codebase:
+
+**Usage:**
+```
+/codemie-subagents
+```
+
+**Generated Agents:**
+- `unit-tester-agent.md` - Knows your test framework and patterns
+- `solution-architect-agent.md` - Understands your architecture
+- `code-review-agent.md` - Applies your code standards
+- `refactor-cleaner-agent.md` - Uses your cleanup tools
+
+**What it does:**
+1. Reads existing guides from `.codemie/guides/` (if available)
+2. Analyzes project structure, test setup, linting rules
+3. Generates/updates agents in `.claude/agents/`
+4. Preserves custom content when updating existing agents
+
+## Memory Management
+
+### `/memory-add` - Capture Knowledge
+
+Adds important learnings to project documentation for future sessions.
+
+**Usage:**
+```
+/memory-add
+/memory-add "important context about auth flow"
+```
+
+**When to use:**
+- You learned something non-obvious about the project
+- User corrected a pattern or approach
+- You discovered an important architectural decision or gotcha
+
+**What it does:**
+1. Identifies what was learned during the session
+2. Determines scope (project-wide vs component-specific)
+3. Adds structured knowledge to appropriate documentation
+
+**Where it writes:**
+- Project-wide patterns → Root `CLAUDE.md` or main docs
+- Component-specific → Component `CLAUDE.md` or guide section
+
+### `/memory-refresh` - Audit Documentation
+
+Verifies and updates documentation to reflect current implementation.
+
+**Usage:**
+```
+/memory-refresh
+```
+
+**What it does:**
+1. Reviews recent code changes
+2. Compares documentation against actual implementation
+3. Updates only outdated/incorrect sections
+4. Validates all references and examples
+
+**When to use:**
+- After significant refactoring
+- When patterns have evolved
+- Before starting work on unfamiliar code
+- Periodically to keep docs accurate
+
+## Status Command
+
+### `/codemie-status` - Session Information
+
+Displays current session tracking status and metrics.
+
+**Usage:**
+```
+/codemie-status
+```
+
+**Output:**
+```
+CodeMie Session Status
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Session ID:     550e8400...
+Started:        2026-01-12 10:30:45 (15m ago)
+Metrics:        15,234 tokens | 42 tools | 23 files
+Sync:           ✓ Connected (last: 30s ago)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Command Principles
+
+**Project-Aware:** All commands analyze your actual codebase, not generic templates
+
+**Selective Updates:** Only creates/updates documentation when patterns actually exist
+
+**Preserves Customizations:** When updating, keeps user-added content
+
+**Size Conscious:** Enforces line limits to keep documentation scannable:
+- `CLAUDE.md`: 200-300 lines
+- Guides: 200-400 lines each
+- Subagents: 150-300 lines each
+
+**Examples From Code:** Uses real code examples, not hypothetical ones