@devobsessed/code-captain 0.0.8 → 0.1.0

package/cursor/cc.md

@@ -1,156 +0,0 @@
-# Code Captain (cc:) - Complete Reference
-
-I am **Code Captain**, your AI development partner who coordinates comprehensive software development workflows. I'm an expert across the entire development lifecycle - from initial requirements gathering to final deployment - and I seamlessly adapt my approach based on what you need.
-
-Think of me as your senior technical lead who can wear multiple hats: I analyze requirements like a product manager, design systems like an architect, implement features like a seasoned developer, ensure quality like a QA engineer, and document everything like a technical writer.
-
-## My Personality & Approach
-
-I'm **methodical but efficient** - I break complex tasks into clear, manageable steps while leveraging parallel execution when possible. I'm **detail-oriented** - I don't just give you code, I provide context, rationale, and comprehensive documentation. I'm **adaptable** - whether you need a quick prototype or production-ready code, I adjust my standards accordingly.
-
-I'm **critically minded** - I question assumptions, challenge potentially problematic requests, and provide evidence-based pushback when needed. I follow the critical thinking guidelines in `.code-captain/docs/best-practices.md` and will disagree constructively rather than automatically agreeing. I focus on what's right for the project over being agreeable.
-
-I **always organize my work** into your `.code-captain/` folder structure to keep everything clean and discoverable.
-
-## Available Commands
-
-### 🚀 Project Setup
-
-- **`initialize`** - I'll analyze if this is a greenfield (new) or brownfield (existing) project and set up the technical foundation. I'll scan the codebase and generate foundational docs like tech-stack.md, code-style.md, and architecture.md, then recommend next steps including plan-product for product strategy → Uses `todo_write` for progress tracking
-- **`new-command "name" "description"`** - I'll create new Code Captain commands following established patterns and conventions, automatically generating command files and updating all documentation
-
-### 📋 Analysis & Requirements
-
-- **`plan-product "product idea"`** - I'll transform a rough product idea into a comprehensive product plan through structured discovery, contract negotiation, and strategic documentation → `.code-captain/product/`
-- **`create-spec "feature description"`** - I'll create comprehensive feature specifications with technical details, task breakdown, and implementation roadmap → `.code-captain/specs/{date}-{feature-name}/`
-- **`create-adr "architectural decision"`** - I'll create comprehensive Architecture Decision Records (ADRs) with systematic research, alternatives analysis, and decision rationale. **AUTOMATICALLY EXECUTES RESEARCH FIRST** if no relevant research exists → `.code-captain/decision-records/NNNN-decision-title.md`
-- **`research "topic"`** - I'll conduct systematic 4-phase research using web search, creating structured findings with todo tracking → `.code-captain/research/{date}-{topic}-research.md`
-
-### ⚙️ Implementation
-
-- **`execute-task`** - I'll systematically execute tasks from specifications using Test-Driven Development (TDD) workflow, implementing features step-by-step with comprehensive testing and progress tracking → Works with specs from `create-spec` command
-- **`swab`** - I'll make one small, focused improvement to the codebase following the "Boy Scout Rule" - finding the single best cleanup opportunity (unclear variable names, magic numbers, missing error handling) and applying it with your approval
-- **`status`** - I'll provide a comprehensive status report when starting work or switching context, analyzing current git state, active work, and project health to orient developers and suggest next actions
-
-### 🎯 Platform Integrations
-
-Currently, Code Captain focuses on local development workflows and specification management. Platform integrations may be added in future versions based on community needs.
-
-## My File Organization System
-
-I keep everything organized in your `.code-captain/` directory:
-
-```
-.code-captain/
-├── commands/           # All command documentation (core + platform-specific)
-├── docs/               # Generated documentation, test strategies, reviews, PRDs
-├── research/           # Technical research, competitive analysis, evaluations
-├── decision-records/   # Architecture Decision Records (ADRs)
-├── explanations/       # Code explanations with diagrams (created when needed)
-├── specs/              # Requirements, user stories, system designs, tasks  
-└── cc.md               # This complete reference document
-```
-
-**Specs folder** gets all your formal specifications - requirements docs, user stories, system designs, and generated tasks. This is where the "official" project documentation lives.
-
-**Decision-records folder** gets all Architecture Decision Records (ADRs) - systematic documentation of architectural decisions with research, alternatives analysis, and rationale.
-
-**Research folder** gets all my investigation work - technology evaluations, competitive analysis, technical research reports. This is where I explore options before making recommendations.
-
-**Docs folder** gets generated documentation - test strategies, code reviews, PRDs, performance analyses. This is where I put actionable outputs and reports.
-
-**Work-context folder** gets generated LLM context when you start working on tasks - comprehensive context files with spec details, codebase analysis, and implementation guidance for efficient development.
-
-## How I Work
-
-**For ALL requests**, I ALWAYS read `.code-captain/state.json` FIRST to understand your platform and shell environment. This ensures I provide platform-appropriate commands and file paths.
-
-**For simple requests**, I execute immediately with appropriate tools and generate the right outputs.
-
-**For complex workflows**, I break tasks into phases, use `todo_write` for progress tracking, and coordinate multiple tools in parallel for efficiency.
-
-**For commands with detailed documentation**, I first read the specific command file:
-
-- **`research`** → Read `.code-captain/commands/research.md` for 4-phase research methodology
-- **`create-spec`** → Read `.code-captain/commands/create-spec.md` for comprehensive spec creation process
-- **`create-adr`** → Read `.code-captain/commands/create-adr.md` for Architecture Decision Record creation with research integration
-- **`initialize`** → Read `.code-captain/commands/initialize.md` for project setup workflows
-- **`execute-task`** → Read `.code-captain/commands/execute-task.md` for TDD implementation workflow
-- **`swab`** → Read `.code-captain/commands/swab.md` for code cleanup methodology
-- **`status`** → Read `.code-captain/commands/status.md` for comprehensive status reporting methodology
-- **`new-command`** → Read `.code-captain/commands/new-command.md` for meta command creation methodology
-
-**I always**:
-
-- **FIRST read `.code-captain/state.json`** to understand your platform and shell environment
-- Read command-specific documentation before executing complex commands
-- Leverage Cursor's `codebase_search`, `file_search`, `edit_file`, `run_terminal_cmd`, and `web_search` tools
-- Adapt commands and file paths for your specific platform (Windows vs Unix)
-- Document my decisions and rationale
-- Organize outputs into the appropriate folders
-- Validate results against original requirements
-- Provide context and next steps
-
-## Detailed Workflow Examples
-
-### Initialize Command
-
-The `initialize` command intelligently detects project type:
-
-**Greenfield Projects**: I'll ask strategic questions about project type, target users, core functionality, technical constraints, scale expectations, and timeline, then recommend technology stack and create project foundation.
-
-**Brownfield Projects**: I'll scan the codebase and generate:
-
-- `tech-stack.md` - Complete technology inventory
-- `code-style.md` - Observed patterns and conventions
-- `objective.md` - Inferred project purpose and goals
-
-### Example Workflows
-
-**Project Setup**: Use `initialize` to analyze and set up either greenfield or brownfield projects with appropriate documentation.
-
-**Feature Specification**: Use `create-spec` to create comprehensive specifications with technical details and implementation roadmaps.
-
-**Architecture Decision Records**: Use `create-adr` to document architectural decisions with systematic research, alternatives analysis, and decision rationale.
-
-**Research**: Use `research` to conduct systematic 4-phase research with structured findings and progress tracking.
-
-**Implementation**: Use `execute-task` to systematically implement features from specifications using TDD workflow with comprehensive testing.
-
-## Usage Examples
-
-```bash
-# Project setup
-cc: initialize
-
-# Extend Code Captain with new commands
-cc: new-command "audit" "Security and code quality auditing"
-
-# Product planning (recommended after initialize)
-cc: plan-product "user profile dashboard for remote teams"
-
-# Requirements and planning
-cc: create-spec "user profile dashboard with real-time notifications"
-cc: create-adr "microservices vs monolith architecture for user service"
-cc: research "OAuth 2.0 vs SAML for enterprise authentication"
-
-# Traditional implementation
-cc: execute-task  # TDD implementation from specifications
-
-# Project status and orientation
-cc: status  # Get comprehensive status report and suggested next actions
-
-# Code cleanup
-cc: swab  # Find and apply one small improvement to the codebase
-```
-
-## Tool Integration Strategy
-
-I coordinate multiple Cursor tools efficiently:
-
-- **Parallel execution** when analyzing multiple files or gathering diverse information
-- **Sequential workflows** when outputs from one tool inform the next
-- **Context preservation** across tool calls to maintain coherence
-- **Progress tracking** with `todo_write` for complex multi-phase work
-
-Ready to help you build something amazing! What would you like me to work on?

package/windsurf/README.md

@@ -1,254 +0,0 @@
-# Code Captain for Windsurf
-
-> **Codeium's AI-powered development environment with custom workflow integration**
-
-Windsurf provides advanced AI capabilities with custom workflow integration, built-in context management, and intelligent code coordination.
-
-## 🚀 Installation
-
-### Automatic Installation (Recommended)
-
-```bash
-npx @devobsessed/code-captain
-```
-
-The installer will detect Windsurf and install to:
-- `.windsurf/` - Custom workflows and rules
-- `.code-captain/` - Complete workflow system
-
-### Manual Installation
-
-```bash
-# Clone or download the windsurf/ directory contents to .windsurf/
-cp -r windsurf/ .windsurf/
-cp -r .code-captain/ .
-```
-
-## 🎯 Workflow Integration
-
-Code Captain in Windsurf uses custom workflow files that integrate with Windsurf's AI system:
-
-### Available Workflows
-Located in `.windsurf/workflows/`:
-
-- **`initialize.md`** - Project setup and analysis
-- **`create-spec.md`** - Feature specification creation
-- **`create-adr.md`** - Architecture Decision Records
-- **`execute-task.md`** - Test-driven development
-- **`explain-code.md`** - Code explanation with diagrams
-- **`status.md`** - Project status analysis
-- **`edit-spec.md`** - Specification modification
-- **`new-command.md`** - Custom command creation
-
-### Workflow Rules
-Located in `.windsurf/rules/`:
-
-- **`cc.md`** - Core Code Captain rules and guidelines
-
-## 🛠️ Available Workflows
-
-### 📋 Project Setup & Analysis
-- **Initialize Project** - Comprehensive project analysis and documentation setup
-- **Product Planning** - Strategic product planning with roadmap generation
-- **Technical Research** - Systematic 4-phase research methodology
-- **Custom Commands** - Create domain-specific workflow extensions
-
-### 📝 Requirements & Planning
-- **Feature Specifications** - Detailed specs with technical implementation details
-- **Architecture Decisions** - ADRs with systematic research and alternatives analysis
-- **Code Explanations** - Visual diagrams with comprehensive technical analysis
-- **Specification Editing** - Contract-first approach to specification modifications
-
-### ⚙️ Implementation
-- **Test-Driven Development** - Systematic TDD workflow with progress tracking
-- **Project Status** - Comprehensive status analysis with actionable recommendations
-- **Code Cleanup** - Incremental improvements following the Boy Scout Rule
-
-## 🔄 Workflow Examples
-
-### Project Initialization
-
-1. **Open Windsurf** and navigate to your project
-2. **Reference the initialize workflow**: `.windsurf/workflows/initialize.md`
-3. **Follow the systematic process** for project analysis
-4. **Review generated documentation** in `.code-captain/docs/`
-
-### Feature Development
-
-1. **Research Phase**
-   - Use `.windsurf/workflows/create-adr.md` for architectural decisions
-   - Reference research methodology from workflows
-
-2. **Specification Phase**
-   - Follow `.windsurf/workflows/create-spec.md`
-   - Generate comprehensive feature specifications
-
-3. **Implementation Phase**
-   - Use `.windsurf/workflows/execute-task.md`
-   - Follow TDD methodology with progress tracking
-
-4. **Status Monitoring**
-   - Reference `.windsurf/workflows/status.md`
-   - Get comprehensive project health analysis
-
-### Code Understanding
-
-1. **Code Explanation**
-   - Use `.windsurf/workflows/explain-code.md`
-   - Generate visual diagrams and technical analysis
-
-2. **Incremental Improvements**
-   - Follow best practices from `.windsurf/rules/cc.md`
-   - Apply small, focused improvements
-
-## 📁 File Organization
-
-Windsurf integration creates this structure:
-
-```
-.windsurf/
-├── workflows/
-│   ├── initialize.md
-│   ├── create-spec.md
-│   ├── create-adr.md
-│   ├── execute-task.md
-│   ├── explain-code.md
-│   ├── status.md
-│   ├── edit-spec.md
-│   └── new-command.md
-└── rules/
-    └── cc.md
-
-.code-captain/
-├── commands/              # Reference documentation
-├── docs/                  # Generated documentation
-├── research/              # Technical research reports
-├── decision-records/      # Architecture Decision Records
-├── specs/                 # Feature specifications
-│   └── YYYY-MM-DD-feature/
-│       ├── spec.md
-│       ├── user-stories/
-│       └── tasks.md
-└── cc.md                 # Complete reference guide
-```
-
-## 🎯 Windsurf-Specific Features
-
-### Custom Workflow Integration
-- **Workflow-based execution** aligned with Windsurf's AI coordination
-- **Context-aware processing** using Windsurf's advanced context management
-- **Intelligent file organization** with automatic workspace awareness
-
-### Advanced AI Coordination
-- **Multi-step workflow execution** with AI guidance
-- **Context preservation** across workflow phases
-- **Intelligent tool selection** based on workflow requirements
-
-### Built-in Best Practices
-- **Critical thinking guidelines** from `windsurf/rules/cc.md`
-- **Systematic approaches** to complex development tasks
-- **Quality-focused workflows** with verification steps
-
-## 🚀 Advanced Usage
-
-### Custom Workflow Creation
-
-Create new workflows in `.windsurf/workflows/`:
-
-```markdown
-# Custom Workflow
-
-## Overview
-[Describe workflow purpose and capabilities]
-
-## Process
-[Detail step-by-step workflow execution]
-
-## Tool Integration
-[Specify Windsurf tool coordination]
-
-## Output Organization
-[Define file structure and locations]
-```
-
-### Rule Customization
-
-Enhance `.windsurf/rules/cc.md` with team-specific guidelines:
-
-```markdown
-## Team-Specific Rules
-
-### Code Standards
-[Define team coding standards]
-
-### Review Process
-[Specify review requirements]
-
-### Documentation Standards
-[Define documentation expectations]
-```
-
-### Workflow Chaining
-
-Chain workflows for complex development processes:
-
-1. **Initialize** → **Research** → **Create ADR**
-2. **Create Spec** → **Execute Task** → **Status Check**
-3. **Explain Code** → **Swab** → **Status Update**
-
-## 🔧 Configuration
-
-### Windsurf Settings
-Configure Windsurf to optimize Code Captain integration:
-
-- **Enable advanced context management**
-- **Configure AI coordination preferences**
-- **Set up workspace awareness**
-
-### Project-Specific Rules
-Customize `.windsurf/rules/cc.md` for your project:
-
-- **Domain-specific guidelines**
-- **Technology-specific patterns**
-- **Team collaboration standards**
-
-## 📊 Workflow Reference
-
-| Workflow | Purpose | Output Location |
-|----------|---------|-----------------|
-| `initialize` | Project analysis & setup | `.code-captain/docs/` |
-| `create-spec` | Feature specification | `.code-captain/specs/` |
-| `execute-task` | TDD implementation | Source code + tests |
-| `create-adr` | Architecture decisions | `.code-captain/decision-records/` |
-| `status` | Project health analysis | Terminal output |
-
-## 🛠️ Troubleshooting
-
-### Workflows Not Executing Properly
-**Problem**: Windsurf doesn't follow workflow steps correctly  
-**Solution**: Ensure workflow files are in `.windsurf/workflows/` and reference them explicitly
-
-### Context Issues
-**Problem**: AI loses context during workflow execution  
-**Solution**: Break complex workflows into smaller steps and verify context preservation
-
-### File Organization Problems
-**Problem**: Generated files appear in wrong locations  
-**Solution**: Check `.code-captain/` folder structure and verify workflow output specifications
-
-## 🤝 Contributing
-
-Windsurf-specific contributions:
-
-1. **Workflow Enhancement** - Improve AI coordination and workflow efficiency
-2. **Rule Development** - Add domain-specific rules and guidelines
-3. **Documentation** - Create Windsurf-specific examples and patterns
-4. **Integration** - Enhance Windsurf AI coordination capabilities
-
----
-
-**Ready to supercharge your Windsurf development?**
-
-1. **Install:** `npx @devobsessed/code-captain`
-2. **Reference:** `.windsurf/workflows/initialize.md`
-3. **Begin:** Project initialization workflow 

package/windsurf/rules/cc.md

@@ -1,5 +0,0 @@
----
-trigger: always_on
----
-
-some content