@codemieai/code 0.1.0 → 0.2.0

package/dist/agents/plugins/claude/plugin/claude-templates/templates/agents/unit-tester-agent.md.template

@@ -1,258 +0,0 @@
----
-name: unit-tester
-description: |-
-    Use this agent when the user explicitly requests unit test creation, modification, or implementation.
-    This includes requests like 'write tests', 'create unit tests', 'add test coverage', 'cover with unit tests', 'let's implement unit tests', 'generate tests for [component]', or 'improve test suite'.
-    IMPORTANT: This agent should ONLY be invoked when testing is explicitly requested - never proactively suggest or write tests without explicit user instruction.
-tools: Bash, Glob, Grep, Read, Edit, Write, WebFetch, TodoWrite, WebSearch
-model: inherit
-color: green
----
-
-# Unit Tester Agent Template
-
-**Purpose**: This template guides generation of project-specific unit testing agents. The generating LLM analyzes the codebase and produces a concise testing agent aligned with project conventions.
-
----
-
-## Core Mission
-
-Create comprehensive, production-ready unit tests that:
-- Follow project's testing framework and conventions
-- Test business logic, not trivial code
-- Use correct mocking patterns
-- Are fast, isolated, and maintainable
-
----
-
-## Project Context
-
-**[GENERATION INSTRUCTION]**: Analyze project to populate:
-- `.codemie/guides/` folder (if exists) for testing guidelines
-- Existing test files for patterns and conventions
-- Package files for framework and dependencies
-- Test config files for coverage requirements
-
-**[TEMPLATE]**:
-```
-Framework: [TEST_FRAMEWORK] [VERSION] with [PLUGINS]
-Structure: [TEST_DIRECTORY] ([ORGANIZATION_PATTERN])
-Pattern: [TEST_PATTERN] (AAA, Given-When-Then, Table-driven)
-Mocking: [MOCK_LIBRARY] - [MOCKING_RULE]
-Async: [ASYNC_PATTERN]
-```
-
----
-
-## What to Test vs Skip
-
-### ✅ TEST: Business Logic
-
-- Calculations, transformations, conditional logic
-- Validation and error handling
-- Edge cases (null, empty, boundaries)
-- State changes and workflows
-- Integration points (with mocked dependencies)
-
-### ❌ SKIP: Trivial Code
-
-- Simple getters/setters
-- Model defaults ([ORM_FRAMEWORK] handles this)
-- Framework internals
-- Auto-generated code
-- Pass-through methods with no logic
-
-**Decision Rule**: If there's no conditional logic or business rule, don't test it.
-
----
-
-## Essential Test Patterns
-
-### 1. Basic Test Structure
-
-**[TEMPLATE]**:
-```[language]
-[test_decorator_or_annotation]
-[async_keyword] [function_keyword] test_[method]_[scenario]_[expected]() {
-    // Arrange
-    [setup_mocks_and_data]
-
-    // Act
-    [result] = [await] [method_call]
-
-    // Assert
-    [assertions]
-    [verify_mock_calls]
-}
-```
-
-### 2. Exception/Error Testing
-
-**[TEMPLATE]**:
-```[language]
-[test_decorator_or_annotation]
-[function_keyword] test_[method]_raises_[exception]() {
-    [expect_exception_syntax] {
-        [method_call_that_fails]
-    }
-}
-```
-
-### 3. Parametrized Tests
-
-**[TEMPLATE]**:
-```[language]
-[parametrize_decorator]([test_cases])
-[test_decorator_or_annotation]
-[function_keyword] test_[method]_multiple_cases([params]) {
-    [assertion]
-}
-```
-
-### 4. Mocking ([MOCKING_RULE])
-
-**[GENERATION INSTRUCTION]**: Document the correct mocking approach for the project's language:
-- Python: Patch where object is USED, not where DEFINED
-- JavaScript: Mock modules at top level with jest.mock()
-- Java: Use @Mock and @InjectMocks annotations
-- Go: Use interfaces with mock implementations
-
-**[TEMPLATE]**:
-```[language]
-// ✅ CORRECT
-[correct_mock_example]
-
-// ❌ WRONG
-[wrong_mock_example]
-```
-
-### 5. API/Endpoint Testing
-
-**[TEMPLATE]**:
-```[language]
-[test_decorator_or_annotation]
-[async_keyword] [function_keyword] test_[endpoint]_[scenario]() {
-    [mock_service_layer]
-    [response] = [test_client].[http_method]([path], [options])
-    [assert_status]
-    [assert_body]
-}
-```
-
----
-
-## Test Quality Checklist
-
-- [ ] Clear test name: `test_<method>_<scenario>_<expected>`
-- [ ] [TEST_PATTERN] pattern followed
-- [ ] External dependencies mocked
-- [ ] Mock calls verified
-- [ ] Specific assertions (not just `assertTrue`)
-- [ ] Fast execution (no real I/O)
-- [ ] No hardcoded credentials
-
----
-
-## Running Tests
-
-**[TEMPLATE]**:
-```bash
-# All tests
-[run_all_command]
-
-# Specific file
-[run_file_command] [path]
-
-# With coverage
-[coverage_command]
-
-# Specific test
-[run_single_command] [test_name]
-```
-
----
-
-## Key Reminders
-
-1. **[TEST_FRAMEWORK] only** - Don't mix frameworks
-2. **[MOCKING_RULE]** - Critical for correct test isolation
-3. **Test behavior, not implementation** - Focus on what, not how
-4. **Mock external dependencies** - Database, APIs, file system
-5. **Skip trivial code** - No value in testing getters/defaults
-
----
-
-## Generation Instructions
-
-**For LLM generating project-specific agent from this template:**
-
-### Step 1: Discover Testing Stack
-
-Analyze:
-- Package files for test framework and dependencies
-- Existing test files for patterns
-- Test config files for settings
-- `.codemie/guides/` folder if exists
-
-Extract:
-| Item | Source |
-|------|--------|
-| Framework + version | package.json, pyproject.toml, pom.xml |
-| Plugins/extensions | Same + test configs |
-| Mock library | Import statements in test files |
-| Test directory | Project structure |
-| Naming convention | Existing test file names |
-
-### Step 2: Identify Patterns
-
-From 5-10 existing test files, extract:
-- Test structure (AAA, Given-When-Then, Table-driven)
-- Async handling pattern
-- Mock setup approach
-- Fixture/setup patterns
-- Assertion style
-
-### Step 3: Document Mocking Rule
-
-**Critical** - Identify the correct mocking approach:
-
-| Language | Rule |
-|----------|------|
-| Python | Patch where USED, not DEFINED |
-| JavaScript | jest.mock() at module level |
-| Java | @Mock + @InjectMocks |
-| Go | Interface-based mocks |
-
-### Step 4: Create Concrete Examples
-
-For each essential pattern, generate examples using:
-- Project's actual language syntax
-- Project's test framework
-- Project's mock library
-- Realistic method/class names from codebase
-
-### Step 5: Extract Test Commands
-
-From package.json scripts, Makefile, or CI config:
-- Run all tests
-- Run single file
-- Run with coverage
-- Run specific test
-
-### Step 6: Finalize Agent
-
-- Remove all `[GENERATION INSTRUCTION]` blocks
-- Remove this "Generation Instructions" section
-- Replace all `[PLACEHOLDERS]` with project values
-- Include 1-2 concrete examples per pattern
-- **Target agent size: 100-150 lines**
-
-### Validation
-
-- [ ] Framework and version specified
-- [ ] Mocking rule clearly stated with example
-- [ ] All 5 patterns have project-specific examples
-- [ ] Test commands are accurate
-- [ ] No `[PLACEHOLDERS]` remain
-- [ ] No generation instructions remain
-- [ ] Agent under 150 lines

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

@@ -1,179 +0,0 @@
----
-# API Patterns Guide
-
-## Overview
-
-<!-- 
-GENERATION INSTRUCTIONS:
-1. Scan codebase for API routes, controllers, middleware
-2. Extract ACTUAL patterns used (don't invent)
-3. Fill each section with REAL file paths and code
-4. Keep examples minimal (5-15 lines, one per pattern)
-5. Final output: 150-300 lines
--->
-
-**Project**: [Extract from package.json/config]
-**Stack**: [Detect framework, language, auth library]
-**Base URL**: [Find in config/env]
-
----
-
-## File Structure
-
-<!-- Find and document where API code lives -->
-
-| Purpose | Path |
-|---------|------|
-| Routes/Endpoints | `[scan for router files]` |
-| Controllers/Handlers | `[scan for controller pattern]` |
-| Middleware | `[scan for middleware folder]` |
-| Validation | `[scan for validators/schemas]` |
-| Models/Types | `[scan for models/entities]` |
-
----
-
-## Endpoint Pattern
-
-<!-- Extract ONE canonical endpoint showing the full pattern -->
-
-```[detected_language]
-// Source: [actual_file:lines]
-[extract representative endpoint - prefer one with auth + validation]
-```
-
-**To add new endpoint, replicate this structure:**
-1. Define route in `[routes_file]`
-2. Add handler in `[controllers_path]`
-3. Add validation in `[validators_path]` (if needed)
-
----
-
-## Validation Pattern
-
-<!-- Find how this codebase validates requests -->
-
-**Approach**: [Detect: Zod/Joi/Yup/Pydantic/class-validator/custom]
-
-```[lang]
-// Source: [actual_file:lines]
-[extract one validation schema example]
-```
-
-**Usage:**
-```[lang]
-// How validation is applied to routes
-[extract middleware/decorator usage]
-```
-
----
-
-## Authentication
-
-<!-- Find auth middleware/guards -->
-
-**Method**: [Detect: JWT/Session/API Key/OAuth]
-
-```[lang]
-// Source: [actual_file:lines]
-[extract auth middleware]
-```
-
-**Protect route:** `[extract exact syntax used]`
-**Access user:** `[extract how user object is accessed]`
-
----
-
-## Response Patterns
-
-<!-- Find consistent response structures -->
-
-**Success format:**
-```json
-[extract actual success response structure from code]
-```
-
-**Error format:**
-```json
-[extract actual error response structure from code]
-```
-
-**Helper/Utility** (if exists): `[path to response helpers]`
-
----
-
-## Status Codes
-
-<!-- Extract from actual handlers OR document conventions found -->
-
-| Operation | Success | Common Errors |
-|-----------|---------|---------------|
-| Create | [find in POST handlers] | [find error codes] |
-| Read | [find in GET handlers] | [find error codes] |
-| Update | [find in PUT/PATCH] | [find error codes] |
-| Delete | [find in DELETE] | [find error codes] |
-
----
-
-## Error Handling
-
-<!-- Find centralized error handling -->
-
-```[lang]
-// Source: [actual_file:lines]
-[extract error handler/middleware or throwing pattern]
-```
-
-**Throw errors using:** `[extract exact syntax]`
-
----
-
-## Pagination
-
-<!-- Find if pagination exists, extract pattern -->
-
-```[lang]
-// Source: [actual_file:lines]
-[extract pagination implementation]
-```
-
-**Params**: [extract actual query param names used]
-**Defaults**: page=`[find]`, limit=`[find]`
-
----
-
-## Conventions
-
-<!-- Extract by analyzing multiple endpoints -->
-
-| Aspect | Convention Used |
-|--------|-----------------|
-| Route naming | `[kebab-case/camelCase/snake_case]` |
-| Controller methods | `[naming pattern found]` |
-| Async handling | `[async/await, promises, try/catch wrapper]` |
-| ID parameter | `[id/:id/uuid format]` |
-
----
-
-## Anti-Patterns
-
-<!-- Document what NOT to do based on codebase patterns -->
-
-| ❌ Avoid | ✅ Use Instead | Reason |
-|----------|----------------|--------|
-| [detect inconsistencies or deprecated patterns] | [correct pattern from code] | [why] |
-
----
-
-## Quick Reference
-
-<!-- Condensed lookup table -->
-
-| Task | Syntax | Example |
-|------|--------|---------|
-| Define route | `[extract]` | `[file:line]` |
-| Add validation | `[extract]` | `[file:line]` |
-| Protect route | `[extract]` | `[file:line]` |
-| Return success | `[extract]` | `[file:line]` |
-| Throw error | `[extract]` | `[file:line]` |
-
----

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

@@ -1,197 +0,0 @@
----
-# Architecture Guide
-
-<!--
-GENERATION INSTRUCTIONS:
-1. Identify architectural style (layered/modular/hexagonal/clean/microservices)
-2. Detect design patterns by scanning code structures
-3. Map actual dependencies between components
-4. Extract from: imports, folder structure, class relationships
-5. Output: 300 lines max
--->
-
-**Project**: [Extract from config]
-**Style**: [Detect: Layered | Modular | Hexagonal | Clean | Microservices | Monolith]
-**Language**: [Detect] | **Framework**: [Detect]
-
----
-
-## Architecture Overview
-
-<!-- Generate diagram based on detected style -->
-
-```
-[Generate ASCII diagram showing main components and their relationships]
-```
-
-**Key Decision**: [Extract or infer WHY this architecture - scalability/simplicity/team structure]
-
----
-
-## Component Structure
-
-<!-- Scan and document actual project organization -->
-
-```
-[root]/
-├── [component1]/     [Detected purpose]
-├── [component2]/     [Detected purpose]
-├── [component3]/     [Detected purpose]
-├── [shared/common]/  [Detected purpose]
-└── [entry point]
-```
-
----
-
-## Design Patterns Detected
-
-<!-- Scan codebase for these patterns, document only those found -->
-
-| Pattern | Usage | Location |
-|---------|-------|----------|
-| [Repository] | [How it's used] | `[file:line]` |
-| [Factory] | [How it's used] | `[file:line]` |
-| [Singleton] | [How it's used] | `[file:line]` |
-| [Dependency Injection] | [How it's used] | `[file:line]` |
-| [Observer/Event] | [How it's used] | `[file:line]` |
-| [Strategy] | [How it's used] | `[file:line]` |
-
-### Primary Pattern: [Most significant pattern]
-
-```[lang]
-// Source: [file:lines]
-[Extract canonical example of main pattern]
-```
-
-**When to use**: [Detect from usage context]
-
----
-
-## Layer/Module Responsibilities
-
-<!-- Adapt based on detected architecture style -->
-
-| Component | Responsibility | Depends On | Depended By |
-|-----------|----------------|------------|-------------|
-| [Layer/Module 1] | [Detected role] | [List] | [List] |
-| [Layer/Module 2] | [Detected role] | [List] | [List] |
-| [Layer/Module 3] | [Detected role] | [List] | [List] |
-
----
-
-## Dependency Rules
-
-<!-- Extract from imports analysis -->
-
-```
-[Component A] ──► [Component B] ──► [Component C]
-                       │
-                       ▼
-                  [Shared/Core]
-```
-
-| Rule | Enforced By |
-|------|-------------|
-| [e.g., Controllers never import Repositories directly] | [Convention / Linter / DI Container] |
-| [e.g., Domain has no external dependencies] | [Convention / Module boundary] |
-
-**Violations to avoid:**
-- ❌ [Detected anti-pattern or rule]
-- ❌ [Detected anti-pattern or rule]
-
----
-
-## Data Flow
-
-<!-- Trace a typical request through the system -->
-
-```
-[Entry] → [Component1] → [Component2] → [Component3] → [Storage/External]
-   │           │              │              │
-   │      [Transform]    [Process]      [Persist]
-   │           │              │              │
-   └───────────┴──────────────┴──────────────┘
-                     Response
-```
-
-**Example flow** (`[common operation]`):
-1. `[entry point]` receives request
-2. `[component]` validates/transforms
-3. `[component]` executes logic
-4. `[component]` persists/fetches data
-5. Response returns through chain
-
----
-
-## Key Abstractions
-
-<!-- Find interfaces/base classes that define contracts -->
-
-| Abstraction | Purpose | Implementations |
-|-------------|---------|-----------------|
-| `[Interface/Base]` | [Contract purpose] | `[file:line]` |
-| `[Interface/Base]` | [Contract purpose] | `[file:line]` |
-
-```[lang]
-// Source: [file:lines]
-[Extract key interface/abstract class]
-```
-
----
-
-## Adding New Features
-
-<!-- Document extension points based on existing patterns -->
-
-### To add new [entity/resource/feature]:
-
-1. **[Component1]**: Create `[path/pattern]`
-2. **[Component2]**: Create `[path/pattern]`
-3. **[Component3]**: Create `[path/pattern]`
-4. **Wire up**: [How components connect - DI/imports/registration]
-
-### To add new [integration/external service]:
-
-1. Create adapter in `[path]`
-2. Implement interface `[interface name]`
-3. Register in `[config/di location]`
-
----
-
-## Configuration & Environment
-
-<!-- Find how config flows through architecture -->
-
-| Config Type | Location | Accessed Via |
-|-------------|----------|--------------|
-| Environment | `[.env / env files]` | `[config module/pattern]` |
-| App Config | `[config files]` | `[how injected/imported]` |
-| Secrets | `[secrets handling]` | `[access pattern]` |
-
----
-
-## Boundaries Summary
-
-<!-- Concise rules for AI to follow -->
-
-| ✅ DO | ❌ DON'T |
-|-------|----------|
-| [Detected convention] | [Detected anti-pattern] |
-| [Detected convention] | [Detected anti-pattern] |
-| [Detected convention] | [Detected anti-pattern] |
-| Follow existing [pattern] for new code | Introduce new patterns without reason |
-
----
-
-## Quick Reference
-
-| Need | Location | Pattern |
-|------|----------|---------|
-| Entry point | `[path]` | - |
-| Business logic | `[path]` | [pattern] |
-| Data access | `[path]` | [pattern] |
-| External services | `[path]` | [pattern] |
-| Shared utilities | `[path]` | - |
-| Configuration | `[path]` | [pattern] |
-
----