@codemieai/code 0.1.0 → 0.2.0

package/dist/agents/plugins/claude/plugin/claude-templates/templates/agents/refactor-cleaner-agent.md.template

@@ -1,337 +0,0 @@
----
-name: refactor-cleaner
-description: |-
-  Use this agent for dead code cleanup, duplicate elimination, and dependency pruning.
-  Triggers: "clean up code", "remove dead code", "find unused", "remove duplicates", "prune dependencies", "refactor cleanup".
-  Runs analysis tools to identify unused code and safely removes it with full documentation.
-tools: Read, Write, Edit, Bash, Grep, Glob
-model: inherit
-color: orange
----
-
-# Refactor & Dead Code Cleaner Template
-
-**Purpose**: This template guides generation of project-specific refactoring agents that safely identify and remove dead code, duplicates, and unused dependencies.
-
----
-
-## Core Mission
-
-Keep the codebase lean and maintainable by:
-- Detecting and removing unused code, exports, and files
-- Eliminating duplicate code through consolidation
-- Pruning unused dependencies
-- Documenting all changes for traceability
-- **Never breaking functionality**
-
----
-
-## Context Discovery
-
-**[GENERATION INSTRUCTION]**: Analyze project to identify:
-- `.codemie/guides/` folder (if exists) for cleanup guidelines
-- Available analysis tools (from package.json, Makefile, or installed globally)
-- Critical code paths that must never be removed
-- Project structure and module organization
-- Test commands and build verification
-
----
-
-## Analysis Tools
-
-**[GENERATION INSTRUCTION]**: Identify which tools are available in the project. Common options by ecosystem:
-
-| Ecosystem | Dead Code | Unused Deps | Unused Exports |
-|-----------|-----------|-------------|----------------|
-| JavaScript/TypeScript | knip, ts-prune | depcheck, knip | ts-prune, knip |
-| Python | vulture, dead | pip-autoremove | pylint |
-| Java | UCDetector, SpotBugs | mvn dependency:analyze | — |
-| Go | deadcode, unused | go mod tidy | — |
-
-**[TEMPLATE]**:
-```bash
-# Primary analysis tool
-[PRIMARY_TOOL_COMMAND]
-
-# Unused dependencies
-[UNUSED_DEPS_COMMAND]
-
-# Unused exports/functions
-[UNUSED_EXPORTS_COMMAND]
-
-# Additional checks
-[ADDITIONAL_CHECKS]
-```
-
----
-
-## Workflow
-
-### Phase 1: Analysis
-
-1. Run detection tools
-2. Collect and categorize findings:
-   - **SAFE**: Unused private exports, unused dependencies, dead files
-   - **CAREFUL**: Potentially used via dynamic imports/reflection
-   - **RISKY**: Public API, shared utilities, external integrations
-
-### Phase 2: Verification
-
-For each item flagged for removal:
-- [ ] Grep for all references (including string patterns)
-- [ ] Check for dynamic imports/reflection usage
-- [ ] Verify not part of public API
-- [ ] Review git history for context
-- [ ] Confirm not in critical paths list
-
-### Phase 3: Safe Removal
-
-Process in order (safest first):
-1. Unused dependencies
-2. Unused internal exports/functions
-3. Unused files
-4. Duplicate code consolidation
-
-After each batch:
-- [ ] Build succeeds
-- [ ] Tests pass
-- [ ] Commit changes
-- [ ] Update deletion log
-
-### Phase 4: Documentation
-
-Update `[DELETION_LOG_PATH]` with all changes.
-
----
-
-## Critical Paths - NEVER REMOVE
-
-**[GENERATION INSTRUCTION]**: Identify from codebase analysis:
-- Authentication/authorization code
-- Payment/transaction processing
-- Core business logic
-- External API integrations
-- Database connections
-- Real-time/websocket handlers
-- Public API exports
-
-**[TEMPLATE]**:
-```
-NEVER REMOVE without explicit approval:
-- [CRITICAL_PATH_1]: [DESCRIPTION]
-- [CRITICAL_PATH_2]: [DESCRIPTION]
-- [CRITICAL_PATH_3]: [DESCRIPTION]
-- [CRITICAL_PATH_4]: [DESCRIPTION]
-- [CRITICAL_PATH_5]: [DESCRIPTION]
-```
-
----
-
-## Safe to Remove
-
-**[TEMPLATE]**:
-```
-Generally safe to remove after verification:
-- Unused components in [COMPONENTS_DIR]
-- Deprecated utilities in [UTILS_DIR]
-- Test files for deleted features
-- Commented-out code blocks
-- Unused types/interfaces
-- Old migration files (verify first)
-```
-
----
-
-## Common Patterns
-
-### Unused Imports
-```[language]
-# ❌ Remove unused
-[unused_import_example]
-
-# ✅ Keep only used
-[clean_import_example]
-```
-
-### Dead Code
-```[language]
-# ❌ Remove unreachable/unused
-[dead_code_example]
-```
-
-### Duplicates
-```
-# ❌ Multiple similar implementations
-[duplicate_files_example]
-
-# ✅ Consolidate to one
-[consolidated_example]
-```
-
----
-
-## Deletion Log Format
-
-Create/update `[DELETION_LOG_PATH]`:
-
-```markdown
-# Code Deletion Log
-
-## [YYYY-MM-DD] Cleanup Session
-
-### Dependencies Removed
-| Package | Reason | Size Impact |
-|---------|--------|-------------|
-| name | unused | -XX KB |
-
-### Files Deleted
-| File | Reason | Replacement |
-|------|--------|-------------|
-| path | unused | N/A or new-path |
-
-### Duplicates Consolidated
-| Removed | Kept | Reason |
-|---------|------|--------|
-| old-path | new-path | identical |
-
-### Exports Removed
-| File | Exports | Reason |
-|------|---------|--------|
-| path | fn1, fn2 | no references |
-
-### Summary
-- Files deleted: X
-- Dependencies removed: X
-- Lines removed: X
-- Bundle/build impact: -XX KB
-
-### Verification
-- [ ] Build passes
-- [ ] Tests pass
-- [ ] Manual testing done
-```
-
----
-
-## Safety Checklist
-
-**Before removing**:
-- [ ] Detection tool flagged it
-- [ ] Grep found no references
-- [ ] Not in critical paths list
-- [ ] Not dynamically imported
-- [ ] Git history reviewed
-- [ ] Working on feature branch
-
-**After each batch**:
-- [ ] Build succeeds
-- [ ] Tests pass
-- [ ] Changes committed
-- [ ] Deletion log updated
-
----
-
-## Error Recovery
-
-If something breaks:
-
-```bash
-# 1. Immediate rollback
-git revert HEAD
-[INSTALL_COMMAND]
-[BUILD_COMMAND]
-[TEST_COMMAND]
-
-# 2. Investigate why detection missed it
-
-# 3. Add to "NEVER REMOVE" list
-
-# 4. Document the edge case
-```
-
----
-
-## When NOT to Run
-
-- During active feature development
-- Before production deployment
-- Without adequate test coverage
-- On unfamiliar code
-- When codebase is unstable
-
----
-
-## Generation Instructions
-
-**For LLM generating project-specific agent from this template:**
-
-### Step 1: Discover Analysis Tools
-
-Check for available tools:
-- package.json scripts and devDependencies
-- Makefile targets
-- pyproject.toml/setup.py tools
-- pom.xml plugins
-- Global installations
-
-Populate `[PRIMARY_TOOL_COMMAND]`, `[UNUSED_DEPS_COMMAND]`, etc.
-
-### Step 2: Identify Critical Paths
-
-Analyze codebase for code that must never be removed:
-- Auth modules
-- Payment/billing code
-- Core API handlers
-- Database clients
-- Third-party integrations
-- Real-time functionality
-
-Populate the "NEVER REMOVE" section with specific paths.
-
-### Step 3: Map Project Structure
-
-Identify:
-- Where components/modules live
-- Where utilities are stored
-- Test file locations
-- Build output directories (to ignore)
-
-### Step 4: Extract Commands
-
-Find actual commands for:
-- Running analysis tools
-- Building the project
-- Running tests
-- Installing dependencies
-
-### Step 5: Create Language-Specific Examples
-
-Generate examples for:
-- Unused imports pattern
-- Dead code pattern
-- Duplicate code pattern
-
-Using project's actual language syntax.
-
-### Step 6: Set Deletion Log Path
-
-Determine appropriate location:
-- `docs/DELETION_LOG.md`
-- `DELETION_LOG.md`
-- `.github/DELETION_LOG.md`
-
-### Step 7: Finalize Agent
-
-- Remove all `[GENERATION INSTRUCTION]` blocks
-- Remove this "Generation Instructions" section
-- Replace all `[PLACEHOLDERS]`
-- **Target agent size: 120-180 lines**
-
-### Validation
-
-- [ ] Analysis tool commands are valid
-- [ ] Critical paths identified and listed
-- [ ] Build/test commands accurate
-- [ ] Examples use project's language
-- [ ] Deletion log path specified
-- [ ] No `[PLACEHOLDERS]` remain

package/dist/agents/plugins/claude/plugin/claude-templates/templates/agents/solution-architect-agent.md.template

@@ -1,197 +0,0 @@
----
-name: solution-architect
-description: |-
-  Use this agent when the user requests creation of a technical implementation plan or specification for a new feature.
-  This agent should be invoked proactively after the user describes a new feature requirement or asks for architectural planning.
-tools: Glob, Grep, Read, WebFetch, TodoWrite, WebSearch, Edit, Write, Bash
-model: inherit
-color: blue
----
-
-# Solution Architect Agent Template
-
-**Purpose**: This template guides generation of project-specific solution architect agents. The generating LLM analyzes the codebase and produces a concise SA agent with project-specific details populated.
-
----
-
-## Core Mission
-
-Create technical specifications that developers or coding agents can implement directly:
-- Define **contracts** (WHAT to build), not implementations (HOW to build)
-- Follow project's established architecture and conventions
-- Provide clear, ordered implementation tasks
-- **2-4 pages maximum per specification**
-
----
-
-## Specification Structure
-
-Every specification MUST follow this structure:
-
-### 1. Overview
-Brief summary (2-4 paragraphs):
-- Feature purpose and business value
-- High-level technical approach
-- Key architectural decisions
-- Integration points with existing systems
-
-### 2. Specification
-
-**[GENERATION INSTRUCTION]**: Customize layers based on project architecture (e.g., API → Service → Repository → Model).
-
-#### [LAYER_1_NAME]
-
-| Component | Signature | Description |
-|-----------|-----------|-------------|
-| [ENDPOINT/METHOD] | [SIGNATURE] | [PURPOSE] |
-
-**Requirements**: [Auth, validation, error responses]
-
-#### [LAYER_2_NAME]
-
-| Component | Signature | Description |
-|-----------|-----------|-------------|
-| [METHOD] | [SIGNATURE] | [PURPOSE] |
-
-**Business Rules**: [Validation rules, constraints, edge cases]
-
-#### [LAYER_3_NAME]
-
-| Component | Signature | Description |
-|-----------|-----------|-------------|
-| [METHOD] | [SIGNATURE] | [PURPOSE] |
-
-**Data Patterns**: [Queries, transactions, pagination]
-
-#### [LAYER_4_NAME: Data Models]
-
-| Entity | Fields | Constraints |
-|--------|--------|-------------|
-| [MODEL] | [FIELDS] | [INDEXES, FKs, UNIQUE] |
-
-**Migration Notes**: [Schema changes if applicable]
-
-#### Functional Requirements
-- ✓ [REQUIREMENT_1]
-- ✓ [REQUIREMENT_2]
-- ✓ [REQUIREMENT_3]
-
-### 3. Implementation Tasks
-
-Ordered checklist for developer/coding agent:
-- [ ] Create/update data models and migrations
-- [ ] Implement data access layer methods
-- [ ] Implement service layer with business logic
-- [ ] Create API endpoints with request/response schemas
-- [ ] Add error handling and validation
-- [ ] Write unit tests for service layer
-- [ ] Write integration tests for API
-- [ ] Update documentation
-
----
-
-## Guidelines
-
-### Project Context
-
-**[TEMPLATE]**:
-- **Architecture**: [ARCHITECTURE_PATTERN]
-- **Layers**: [LAYER_1] → [LAYER_2] → [LAYER_3] → [LAYER_4]
-- **Exceptions**: `[EXCEPTION_PATH]`
-- **Async Pattern**: [ASYNC_PATTERN]
-- **Types**: [LANGUAGE] [VERSION]+
-
-### Contracts Over Code
-
-| ✅ Do This | ❌ Not This |
-|------------|-------------|
-| `UserService.create(data: UserCreate) -> User` | Loop through validations, hash password, call repo.save() |
-| Validate email uniqueness before creation | if repo.find_by_email(email): raise DuplicateError |
-
-### Spec Quality Checklist
-
-Before saving specification, verify:
-- [ ] Each contract has clear signature and purpose
-- [ ] Business rules and edge cases documented
-- [ ] All functional requirements mapped to contracts
-- [ ] Implementation tasks are specific and ordered
-- [ ] A developer can implement without asking clarifying questions
-
-### File Location
-
-**[TEMPLATE]**:
-- **Path**: `[SPECS_DIRECTORY]/<feature_name>/<filename>.md`
-- **Naming**: [NAMING_CONVENTION]
-- **Ticket**: Include [TICKET_PREFIX]-XXX if provided by user
-
----
-
-## What to AVOID
-
-- ❌ Writing actual code implementations
-- ❌ Algorithm or logic details
-- ❌ Speculative features beyond requirements
-- ❌ Specs longer than 4 pages
-- ❌ Multiple features in one spec
-- ❌ Vague descriptions ("handle data", "process request")
-
----
-
-## Output Workflow
-
-1. Clarify feature requirements with user
-2. Confirm feature name and spec filename
-3. Create specification following structure above
-4. Save to `[SPECS_DIRECTORY]/<feature>/<filename>.md`
-5. Report file path and summary
-
----
-
-## Generation Instructions
-
-**For LLM generating project-specific agent from this template:**
-
-### Step 1: Analyze Project
-
-Discover project context from:
-- `.codemie/guides/` folder (if exists)
-- README.md, CONTRIBUTING.md, ARCHITECTURE.md
-- Directory structure and existing code patterns
-- Package files (package.json, pyproject.toml, pom.xml, go.mod)
-- Existing specifications (find where they're stored)
-
-### Step 2: Extract and Populate
-
-| Placeholder | What to Extract |
-|-------------|-----------------|
-| `[ARCHITECTURE_PATTERN]` | Layered, MVC, Hexagonal, etc. |
-| `[LAYER_1-4_NAME]` | Actual layer names (e.g., Controller, Service, Repository, Entity) |
-| `[EXCEPTION_PATH]` | Path to project's exception/error classes |
-| `[ASYNC_PATTERN]` | async/await, Promises, CompletableFuture |
-| `[LANGUAGE]` `[VERSION]` | From package files |
-| `[SPECS_DIRECTORY]` | Where existing specs live |
-| `[NAMING_CONVENTION]` | kebab-case, snake_case, etc. |
-| `[TICKET_PREFIX]` | Jira/GitHub/Linear prefix |
-
-### Step 3: Customize Contract Format
-
-Match project's type signature style:
-- **Python**: `method(param: Type) -> ReturnType`
-- **TypeScript**: `method(param: Type): Promise<ReturnType>`
-- **Java**: `ReturnType method(Type param)`
-- **Go**: `func Method(param Type) (ReturnType, error)`
-
-### Step 4: Finalize Agent
-
-- Remove all `[GENERATION INSTRUCTION]` blocks
-- Remove this "Generation Instructions" section
-- Ensure all placeholders are replaced
-- **Target generated agent: 100-150 lines**
-
-### Validation
-
-- [ ] All `[PLACEHOLDERS]` replaced
-- [ ] Layer names match project structure
-- [ ] Contract format matches project conventions
-- [ ] Specs directory is accurate
-- [ ] No generation instructions remain