diff --git a/plugins/compounding-engineering/docs/css/style.css b/plugins/compounding-engineering/docs/css/style.css index 677b933..1d54a46 100644 --- a/plugins/compounding-engineering/docs/css/style.css +++ b/plugins/compounding-engineering/docs/css/style.css @@ -1216,3 +1216,186 @@ section { padding: var(--space-xl); } } + +/* ============================================ + Philosophy Section (Enhanced) + ============================================ */ + +.philosophy-section { + padding: var(--space-section) 0; +} + +.philosophy-quote { + max-width: 800px; + margin: 0 auto var(--space-xxl); + text-align: center; +} + +.philosophy-quote blockquote { + font-size: var(--font-size-l); + font-style: italic; + color: var(--color-text-secondary); + line-height: 1.6; + margin: 0; + padding: var(--space-xl); + background: linear-gradient(135deg, var(--color-accent-lighter), transparent); + border-left: 4px solid var(--color-accent); + border-radius: var(--radius-m); +} + +/* Philosophy Pillars */ +.philosophy-pillars { + display: grid; + grid-template-columns: 1fr; + gap: var(--space-xl); + margin-bottom: var(--space-xxl); +} + +@media (min-width: 768px) { + .philosophy-pillars { + grid-template-columns: repeat(2, 1fr); + } +} + +.pillar { + display: flex; + gap: var(--space-l); + padding: var(--space-xl); + background-color: var(--color-surface); + border-radius: var(--radius-l); + border: 1px solid var(--color-border); + transition: all 0.3s ease; +} + +.pillar:hover { + border-color: var(--color-accent); + transform: translateY(-2px); +} + +.pillar-icon { + flex-shrink: 0; + width: 60px; + height: 60px; + display: flex; + align-items: center; + justify-content: center; + background-color: var(--color-accent-light); + border-radius: var(--radius-m); + font-size: var(--font-size-xl); + color: var(--color-accent); +} + +.pillar-content h3 { + margin: 0 0 var(--space-xs) 0; + font-size: var(--font-size-l); + color: var(--color-text-primary); +} + +.pillar-tagline { + margin: 0 0 var(--space-m) 0; + font-size: var(--font-size-s); + color: var(--color-accent); + font-weight: 500; +} + +.pillar-description { + margin: 0 0 var(--space-m) 0; + font-size: var(--font-size-s); + color: var(--color-text-secondary); + line-height: 1.6; +} + +.pillar-tools { + display: flex; + flex-wrap: wrap; + gap: var(--space-xs); +} + +.tool-tag { + font-family: var(--font-mono); + font-size: var(--font-size-xs); + padding: 2px 8px; + background-color: var(--color-surface-hover); + color: var(--color-text-secondary); + border-radius: var(--radius-xs); + border: 1px solid var(--color-border); +} + +/* Compound Effect Timeline */ +.compound-effect { + background-color: var(--color-surface); + border-radius: var(--radius-l); + padding: var(--space-xl); + border: 1px solid var(--color-border); +} + +.compound-effect h3 { + text-align: center; + margin: 0 0 var(--space-xl) 0; + display: flex; + align-items: center; + justify-content: center; + gap: var(--space-s); +} + +.compound-grid { + display: flex; + flex-wrap: wrap; + align-items: center; + justify-content: center; + gap: var(--space-m); +} + +.compound-item { + text-align: center; + padding: var(--space-l); + background-color: var(--color-background); + border-radius: var(--radius-m); + border: 1px solid var(--color-border); + min-width: 140px; +} + +.compound-item.highlight { + background: linear-gradient(135deg, var(--color-accent-light), var(--color-surface)); + border-color: var(--color-accent); +} + +.compound-number { + font-size: var(--font-size-s); + font-weight: 600; + color: var(--color-accent); + margin-bottom: var(--space-xs); +} + +.compound-text { + font-size: var(--font-size-xs); + color: var(--color-text-secondary); +} + +.compound-arrow { + color: var(--color-text-tertiary); + font-size: var(--font-size-l); +} + +@media (max-width: 767px) { + .pillar { + flex-direction: column; + text-align: center; + } + + .pillar-icon { + margin: 0 auto; + } + + .pillar-tools { + justify-content: center; + } + + .compound-arrow { + transform: rotate(90deg); + } + + .compound-grid { + flex-direction: column; + } +} diff --git a/plugins/compounding-engineering/docs/index.html b/plugins/compounding-engineering/docs/index.html index 9bdfcc9..3ef5dd0 100644 --- a/plugins/compounding-engineering/docs/index.html +++ b/plugins/compounding-engineering/docs/index.html @@ -100,54 +100,124 @@ -
+

The Compounding Engineering Philosophy

-

+

Every unit of engineering work should make subsequent units of work easier—not harder. - Our tools embody this philosophy by learning from patterns, automating repetitive tasks, - and building institutional knowledge.

-
-
-
-
-

Plan

-

- Understand the change needed and its impact before writing any code. - Use research agents to gather context and best practices. + + +

+
+ "Most engineering creates linear value: you build a feature, it works, done. + Compounding engineering creates exponential value: each solved problem teaches the system, + each pattern becomes reusable, each review strengthens future reviews." +
+
+ + +
+
+
+
+

Plan

+

Understand before you build

+

+ Before writing a single line of code, gather context. Research agents explore + documentation, analyze git history, and find best practices. The /workflows:plan + command orchestrates 3 research agents in parallel to create comprehensive implementation plans.

+
+ framework-docs-researcher + best-practices-researcher + repo-research-analyst + git-history-analyzer +
-
-
-
-

Delegate

-

- Use specialized AI agents to help with implementation. - Each agent brings deep expertise in its domain. + +

+
+
+

Delegate

+

Leverage specialized expertise

+

+ Each agent brings deep domain knowledge. The kieran-rails-reviewer knows Rails + conventions like an expert. The security-sentinel catches OWASP vulnerabilities. + The /workflows:work command executes plans while maintaining quality gates.

+
+ 24 specialized agents + /workflows:work + dhh-ruby-style skill + git-worktree skill +
-
-
-
-

Assess

-

- Run comprehensive reviews with multiple perspectives. - Security, performance, architecture—all covered. + +

+
+
+

Assess

+

Multiple perspectives, comprehensive coverage

+

+ The /workflows:review command launches 12+ review agents in parallel: security, + performance, architecture, data integrity, patterns, and more. Findings are categorized by + severity (P1/P2/P3) and stored as actionable todo files.

+
+ security-sentinel + performance-oracle + architecture-strategist + data-integrity-guardian +
-
-
-
-

Codify

-

- Document learnings and patterns for future use. - Each solved problem becomes reusable knowledge. + +

+
+
+

Codify

+

Turn solutions into knowledge

+

+ Every solved problem should teach the system. The /workflows:codify command + captures solutions as searchable documentation. The feedback-codifier agent + extracts patterns from code reviews to improve future reviews.

+
+ /workflows:codify + codify-docs skill + feedback-codifier + file-todos skill +
+
+
+
+ + +
+

The Compounding Effect

+
+
+
Day 1
+
Install plugin, run first review
+
+
+
+
Week 1
+
Patterns documented, todos organized
+
+
+
+
Month 1
+
Knowledge base growing, reviews faster
+
+
+
+
Ongoing
+
Each task easier than the last
diff --git a/plugins/compounding-engineering/docs/pages/agents.html b/plugins/compounding-engineering/docs/pages/agents.html new file mode 100644 index 0000000..ec51834 --- /dev/null +++ b/plugins/compounding-engineering/docs/pages/agents.html @@ -0,0 +1,682 @@ + + + + + + Agent Reference - Compounding Engineering + + + + + + + + + + +
+
+ + +
+
+ + +
+ +
+

Agent Reference

+

+ Complete documentation for all 24 specialized AI agents. Each agent brings deep expertise + in a specific domain and can be invoked individually or orchestrated together. +

+ +
+

How to Use Agents

+
+ 
# Basic invocation
+claude agent [agent-name]
+
+# With a specific message
+claude agent [agent-name] "Your message here"
+
+# Examples
+claude agent kieran-rails-reviewer
+claude agent security-sentinel "Audit the payment flow"
+
+
+ + +
+

Review Agents (10)

+

Code review agents that examine changes from multiple perspectives: conventions, security, performance, architecture, and quality.

+ +
+
+

kieran-rails-reviewer

+ Rails +
+

+ Super senior Rails developer with impeccable taste and an exceptionally high bar for Rails code quality. + Reviews with strict conventions while being pragmatic on new isolated code. +

+

Key Principles

+
    +
  • Existing Code Modifications - Very strict. Added complexity needs strong justification.
    • +
  • New Code - Pragmatic. If it's isolated and works, it's acceptable.
    • +
  • Turbo Streams - Simple turbo streams MUST be inline arrays in controllers.
    • +
  • Testing as Quality - Hard-to-test code = poor structure that needs refactoring.
    • +
  • Naming (5-Second Rule) - Must understand what a view/component does in 5 seconds from its name.
    • +
  • Namespacing - Always use class Module::ClassName pattern.
    • +
  • Duplication > Complexity - Simple duplicated code is better than complex DRY abstractions.
    • +
+
+ 
claude agent kieran-rails-reviewer "Review the UserController"
+
+
+ +
+
+

dhh-rails-reviewer

+ Rails +
+

+ Brutally honest Rails code review from David Heinemeier Hansson's perspective. + Focuses on Rails conventions, simplicity, and avoiding over-engineering. +

+

Key Focus Areas

+
    +
  • Identifies deviations from Rails conventions
    • +
  • Spots JavaScript framework patterns infiltrating Rails
    • +
  • Tears apart unnecessary abstractions
    • +
  • Challenges overengineering and microservices mentality
    • +
+
+ 
claude agent dhh-rails-reviewer
+
+
+ +
+
+

kieran-python-reviewer

+ Python +
+

+ Reviews Python code with an exceptionally high quality bar. Enforces type hints, Pythonic patterns, + and modern Python 3.10+ syntax. +

+

Key Focus Areas

+
    +
  • Type hints for all functions
    • +
  • Pythonic patterns and idioms
    • +
  • Modern Python syntax
    • +
  • Import organization
    • +
  • Module extraction signals
    • +
+
+ 
claude agent kieran-python-reviewer
+
+
+ +
+
+

kieran-typescript-reviewer

+ TypeScript +
+

+ Reviews TypeScript code with an exceptionally high quality bar. Enforces type safety, + modern patterns, and clean architecture. +

+

Key Focus Areas

+
    +
  • No any without justification
    • +
  • Component/module extraction signals
    • +
  • Import organization
    • +
  • Modern TypeScript patterns
    • +
  • Testability assessment
    • +
+
+ 
claude agent kieran-typescript-reviewer
+
+
+ +
+
+

security-sentinel

+ Security +
+

+ Performs security audits, vulnerability assessments, and OWASP compliance checks. + Essential for any code handling authentication, payments, or sensitive data. +

+

Security Checks

+
    +
  • Input validation analysis
    • +
  • SQL injection risk assessment
    • +
  • XSS vulnerability detection
    • +
  • Authentication/authorization audit
    • +
  • Sensitive data exposure scanning
    • +
  • OWASP Top 10 compliance
    • +
  • Hardcoded secrets search
    • +
+
+ 
claude agent security-sentinel "Audit the payment flow"
+
+
+ +
+
+

performance-oracle

+ Performance +
+

+ Analyzes code for performance issues, bottlenecks, and scalability concerns. + Projects performance at 10x, 100x, and 1000x scale. +

+

Analysis Areas

+
    +
  • Algorithmic complexity (Big O notation)
    • +
  • N+1 query pattern detection
    • +
  • Proper index usage verification
    • +
  • Memory management review
    • +
  • Caching opportunity identification
    • +
  • Network usage optimization
    • +
  • Frontend bundle impact
    • +
+
+ 
claude agent performance-oracle
+
+
+ +
+
+

architecture-strategist

+ Architecture +
+

+ Analyzes code changes from an architectural perspective. Evaluates system structure, + SOLID principles, and API contracts. +

+

Analysis Areas

+
    +
  • Overall system structure understanding
    • +
  • Change context within architecture
    • +
  • Architectural violation identification
    • +
  • SOLID principles compliance
    • +
  • Microservice boundary assessment
    • +
  • API contract evaluation
    • +
+
+ 
claude agent architecture-strategist
+
+
+ +
+
+

data-integrity-guardian

+ Data +
+

+ Reviews database migrations, data models, and data persistence code. + Ensures data safety and privacy compliance. +

+

Review Areas

+
    +
  • Migration safety and reversibility
    • +
  • Data constraint validation
    • +
  • Transaction boundary review
    • +
  • Referential integrity preservation
    • +
  • Privacy compliance (GDPR, CCPA)
    • +
  • Data corruption scenario checking
    • +
+
+ 
claude agent data-integrity-guardian
+
+
+ +
+
+

pattern-recognition-specialist

+ Patterns +
+

+ Analyzes code for design patterns, anti-patterns, naming conventions, and duplication. + Uses tools like jscpd for duplication detection. +

+

Detection Areas

+
    +
  • Design patterns (Factory, Singleton, Observer, etc.)
    • +
  • Anti-patterns and code smells
    • +
  • TODO/FIXME comments
    • +
  • God objects and circular dependencies
    • +
  • Naming consistency
    • +
  • Code duplication
    • +
+
+ 
claude agent pattern-recognition-specialist
+
+
+ +
+
+

code-simplicity-reviewer

+ Quality +
+

+ Ensures code is as simple and minimal as possible. Applies YAGNI rigorously + and challenges unnecessary abstractions. +

+

Simplification Checks

+
    +
  • Analyze every line for necessity
    • +
  • Simplify complex logic
    • +
  • Remove redundancy and duplication
    • +
  • Challenge abstractions
    • +
  • Optimize for readability
    • +
  • Eliminate premature generalization
    • +
+
+ 
claude agent code-simplicity-reviewer
+
+
+
+ + +
+

Research Agents (4)

+

Research agents that gather information from documentation, repositories, and git history to inform development decisions.

+ +
+
+

framework-docs-researcher

+ Research +
+

+ Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies. +

+

Capabilities

+
    +
  • Fetch official framework and library documentation
    • +
  • Identify version-specific constraints and deprecations
    • +
  • Search GitHub for real-world usage examples
    • +
  • Analyze gem/library source code using bundle show
    • +
  • Synthesize findings with practical examples
    • +
+
+ 
claude agent framework-docs-researcher "Research Hotwire Turbo patterns"
+
+
+ +
+
+

best-practices-researcher

+ Research +
+

+ Researches and gathers external best practices, documentation, and examples for any technology. +

+

Capabilities

+
    +
  • Leverage multiple sources (Context7 MCP, web search, GitHub)
    • +
  • Evaluate information quality and recency
    • +
  • Synthesize into actionable guidance
    • +
  • Provide code examples and templates
    • +
  • Research issue templates and community engagement
    • +
+
+ 
claude agent best-practices-researcher "Find pagination patterns"
+
+
+ +
+
+

git-history-analyzer

+ Git +
+

+ Archaeological analysis of code repositories to understand evolution and patterns. +

+

Analysis Techniques

+
    +
  • Trace file evolution using git log --follow
    • +
  • Determine code origins using git blame -w -C -C -C
    • +
  • Identify patterns from commit history
    • +
  • Map key contributors and expertise areas
    • +
  • Extract historical patterns of issues and fixes
    • +
+
+ 
claude agent git-history-analyzer "Analyze changes to User model"
+
+
+ +
+
+

repo-research-analyst

+ Research +
+

+ Conducts thorough research on repository structure, documentation, and patterns. +

+

Analysis Areas

+
    +
  • Architecture and documentation files (ARCHITECTURE.md, README.md, CLAUDE.md)
    • +
  • GitHub issues for patterns and conventions
    • +
  • Issue/PR templates and guidelines
    • +
  • Implementation patterns using ast-grep or rg
    • +
  • Project-specific conventions
    • +
+
+ 
claude agent repo-research-analyst
+
+
+
+ + +
+

Workflow Agents (6)

+

Workflow agents that automate common development tasks like bug reproduction, PR resolution, and linting.

+ +
+
+

bug-reproduction-validator

+ Bugs +
+

+ Verifies whether bug reports are actual bugs through systematic reproduction. + Classifies bugs and provides severity assessment. +

+

Classification Types

+
    +
  • Confirmed - Bug reproduced successfully
    • +
  • Cannot Reproduce - Unable to reproduce
    • +
  • Not a Bug - Expected behavior
    • +
  • Environmental - Environment-specific issue
    • +
  • Data - Data-related issue
    • +
  • User Error - User misunderstanding
    • +
+
+ 
claude agent bug-reproduction-validator
+
+
+ +
+
+

pr-comment-resolver

+ PR +
+

+ Addresses code review comments by implementing requested changes and reporting resolutions. +

+

Workflow

+
    +
  • Analyze code review comments
    • +
  • Plan the resolution before implementation
    • +
  • Implement requested modifications
    • +
  • Verify resolution doesn't break functionality
    • +
  • Provide clear resolution reports
    • +
+
+ 
claude agent pr-comment-resolver
+
+
+ +
+
+

feedback-codifier

+ Knowledge +
+

+ Analyzes code review feedback to extract patterns and update reviewer configurations. + Uses Opus model for deep analysis. +

+

Capabilities

+
    +
  • Extract core patterns from code reviews
    • +
  • Categorize by type (structure, testing, security, performance)
    • +
  • Formulate actionable guidelines
    • +
  • Update existing reviewer agents with new standards
    • +
+
+ 
claude agent feedback-codifier
+
+
+ +
+
+

lint

+ Quality +
+

+ Runs linting and code quality checks on Ruby and ERB files. + Uses Haiku model for efficiency. +

+

Tools Run

+
    +
  • bundle exec standardrb - Ruby file checking/fixing
    • +
  • bundle exec erblint --lint-all - ERB templates
    • +
  • bin/brakeman - Security scanning
    • +
+
+ 
claude agent lint
+
+
+ +
+
+

spec-flow-analyzer

+ Testing +
+

+ Analyzes specifications and plans for user flows and gap identification. + Uses Sonnet model for analysis. +

+

Analysis Areas

+
    +
  • Map all possible user flows and permutations
    • +
  • Identify gaps, ambiguities, and missing specifications
    • +
  • Consider different user types, roles, permissions
    • +
  • Analyze error states and edge cases
    • +
  • Generate critical questions requiring clarification
    • +
+
+ 
claude agent spec-flow-analyzer
+
+
+ +
+
+

every-style-editor

+ Content +
+

+ Reviews and edits text content to conform to Every's specific style guide. +

+

Style Checks

+
    +
  • Title case in headlines, sentence case elsewhere
    • +
  • Company singular/plural usage
    • +
  • Remove overused words (actually, very, just)
    • +
  • Enforce active voice
    • +
  • Apply formatting rules (Oxford commas, em dashes)
    • +
+
+ 
claude agent every-style-editor
+
+
+
+ + +
+

Design Agents (3)

+

Design agents that help with UI implementation, Figma synchronization, and iterative design refinement.

+ +
+
+

design-iterator

+ Design +
+

+ Systematic UI/UX design refinement through iterative improvements. + Takes screenshots, analyzes, implements changes, and repeats. +

+

Process

+
    +
  • Take focused screenshots of target elements
    • +
  • Analyze current state and identify 3-5 improvements
    • +
  • Implement targeted CSS/design changes
    • +
  • Document changes made
    • +
  • Repeat for specified iterations (default 10)
    • +
+
+ 
claude agent design-iterator
+
+
+ +
+
+

figma-design-sync

+ Figma +
+

+ Automatically detects and fixes visual differences between Figma designs and web implementations. + Uses Sonnet model. +

+

Workflow

+
    +
  • Extract design specifications from Figma
    • +
  • Capture implementation screenshots
    • +
  • Conduct systematic visual comparison
    • +
  • Make precise code changes to fix discrepancies
    • +
  • Verify implementation matches design
    • +
+
+ 
claude agent figma-design-sync
+
+
+ +
+
+

design-implementation-reviewer

+ Review +
+

+ Verifies UI implementations match Figma design specifications. + Uses Opus model for detailed analysis. +

+

Comparison Areas

+
    +
  • Layouts and structure
    • +
  • Typography (fonts, sizes, weights)
    • +
  • Colors and themes
    • +
  • Spacing and alignment
    • +
  • Different viewport sizes
    • +
+
+ 
claude agent design-implementation-reviewer
+
+
+
+ + +
+

Documentation Agent (1)

+ +
+
+

ankane-readme-writer

+ Docs +
+

+ Creates/updates README files following Ankane-style template for Ruby gems. + Optimized for conciseness with every sentence kept to 15 words or less. +

+

Section Order

+
    +
  1. Header (title + description)
    2. +
  2. Installation
    3. +
  3. Quick Start
    4. +
  4. Usage
    5. +
  5. Options
    6. +
  6. Upgrading
    7. +
  7. Contributing
    8. +
  8. License
    9. +
+

Style Guidelines

+
    +
  • Imperative voice throughout
    • +
  • 15 words max per sentence
    • +
  • Single-purpose code fences
    • +
  • Up to 4 badges maximum
    • +
  • No HTML comments
    • +
+
+ 
claude agent ankane-readme-writer
+
+
+
+ + + +
+
+
+ + + + + diff --git a/plugins/compounding-engineering/docs/pages/commands.html b/plugins/compounding-engineering/docs/pages/commands.html new file mode 100644 index 0000000..3992583 --- /dev/null +++ b/plugins/compounding-engineering/docs/pages/commands.html @@ -0,0 +1,518 @@ + + + + + + Command Reference - Compounding Engineering + + + + + + + + + + +
+
+ + +
+
+ + +
+ +
+

Command Reference

+

+ Complete documentation for all 16 slash commands. Commands automate complex multi-step workflows + by orchestrating multiple agents, tools, and processes. +

+ + +
+

Workflow Commands (4)

+

Core workflow commands that embody the Plan-Delegate-Assess-Codify philosophy.

+ +
+
+ /workflows:plan +
+

+ Transform feature descriptions into well-structured project plans following conventions. +

+

Arguments

+

[feature description, bug report, or improvement idea]

+

Workflow

+
    +
  1. Repository Research (Parallel) - Launch 3 agents simultaneously: +
      +
    • repo-research-analyst - Project patterns
      • +
    • best-practices-researcher - Industry standards
      • +
    • framework-docs-researcher - Framework documentation
      • +
    +
    2. +
  2. SpecFlow Analysis - Run spec-flow-analyzer for user flows
    3. +
  3. Choose Detail Level: +
      +
    • MINIMAL - Simple bugs/small improvements
      • +
    • MORE - Standard features
      • +
    • A LOT - Major features with phases
      • +
    +
    4. +
  4. Write Plan - Save as plans/<issue_title>.md
    5. +
  5. Review - Call /plan_review for multi-agent feedback
    6. +
+
+
+
+

This command does NOT write code. It only researches and creates the plan.

+
+
+
+ 
/workflows:plan Add OAuth integration for third-party auth
+/workflows:plan Fix N+1 query in user dashboard
+
+
+ +
+
+ /workflows:review +
+

+ Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees. +

+

Arguments

+

[PR number, GitHub URL, branch name, or "latest"]

+

Workflow

+
    +
  1. Setup - Detect review target, optionally use git-worktree for isolation
    2. +
  2. Launch 12 Parallel Review Agents: +
      +
    • kieran-rails-reviewer, dhh-rails-reviewer
      • +
    • security-sentinel, performance-oracle
      • +
    • architecture-strategist, data-integrity-guardian
      • +
    • pattern-recognition-specialist, git-history-analyzer
      • +
    • And more...
      • +
    +
    3. +
  3. Ultra-Thinking Analysis - Stakeholder perspectives, scenario exploration
    4. +
  4. Simplification Review - Run code-simplicity-reviewer
    5. +
  5. Synthesize Findings - Categorize by severity (P1/P2/P3)
    6. +
  6. Create Todo Files - Using file-todos skill for all findings
    7. +
+
+
+
+

P1 (Critical) findings BLOCK MERGE. Address these before merging.

+
+
+
+ 
/workflows:review 42
+/workflows:review https://github.com/owner/repo/pull/42
+/workflows:review feature-branch-name
+/workflows:review latest
+
+
+ +
+
+ /workflows:work +
+

+ Execute work plans efficiently while maintaining quality and finishing features. +

+

Arguments

+

[plan file, specification, or todo file path]

+

Phases

+
    +
  1. Quick Start +
      +
    • Read plan & clarify requirements
      • +
    • Setup environment (live or worktree)
      • +
    • Create TodoWrite task list
      • +
    +
    2. +
  2. Execute +
      +
    • Task execution loop with progress tracking
      • +
    • Follow existing patterns
      • +
    • Test continuously
      • +
    • Figma sync if applicable
      • +
    +
    3. +
  3. Quality Check +
      +
    • Run test suite
      • +
    • Run linting
      • +
    • Optional reviewer agents for complex changes
      • +
    +
    4. +
  4. Ship It +
      +
    • Create commit with conventional format
      • +
    • Create pull request
      • +
    • Notify with summary
      • +
    +
    5. +
+
+ 
/workflows:work plans/user-authentication.md
+/workflows:work todos/042-ready-p1-performance-issue.md
+
+
+ +
+
+ /workflows:codify +
+

+ Document a recently solved problem for the knowledge base. +

+

Arguments

+

[optional: brief context about the fix]

+

Workflow

+
    +
  1. Preconditions - Verify problem is solved and verified working
    2. +
  2. Launch 7 Parallel Subagents: +
      +
    • Context Analyzer - Extract YAML frontmatter skeleton
      • +
    • Solution Extractor - Identify root cause and solution
      • +
    • Related Docs Finder - Find cross-references
      • +
    • Prevention Strategist - Develop prevention strategies
      • +
    • Category Classifier - Determine docs category
      • +
    • Documentation Writer - Create the file
      • +
    • Optional Specialized Agent - Based on problem type
      • +
    +
    3. +
  3. Create Documentation - File in docs/solutions/[category]/
    4. +
+

Auto-Triggers

+

Phrases: "that worked", "it's fixed", "working now", "problem solved"

+
+ 
/workflows:codify
+/workflows:codify N+1 query optimization
+
+
+
+ + +
+

Utility Commands (12)

+

Specialized commands for specific tasks like changelog generation, bug reporting, and parallel resolution.

+ +
+
+ /changelog +
+

+ Create engaging changelogs for recent merges to main branch. +

+

Arguments

+

[optional: daily|weekly, or time period in days]

+

Output Sections

+
    +
  • Breaking Changes (top priority)
    • +
  • New Features
    • +
  • Bug Fixes
    • +
  • Other Improvements
    • +
  • Shoutouts
    • +
  • Fun Fact
    • +
+
+ 
/changelog daily
+/changelog weekly
+/changelog 7
+
+
+ +
+
+ /create-agent-skill +
+

+ Create or edit Claude Code skills with expert guidance on structure and best practices. +

+

Arguments

+

[skill description or requirements]

+
+ 
/create-agent-skill PDF processing for document analysis
+/create-agent-skill Web scraping with error handling
+
+
+ +
+
+ /generate_command +
+

+ Create a new custom slash command following conventions and best practices. +

+

Arguments

+

[command purpose and requirements]

+
+ 
/generate_command Security audit for codebase
+/generate_command Automated performance testing
+
+
+ +
+
+ /heal-skill +
+

+ Heal skill documentation by applying corrections discovered during execution. +

+

Arguments

+

[optional: specific issue to fix]

+

Approval Options

+
    +
  1. Apply and commit
    2. +
  2. Apply without commit
    3. +
  3. Revise changes
    4. +
  4. Cancel
    5. +
+
+ 
/heal-skill API endpoint URL changed
+/heal-skill parameter validation error
+
+
+ +
+
+ /plan_review +
+

+ Have multiple specialized agents review a plan in parallel. +

+

Arguments

+

[plan file path or plan content]

+

Review Agents

+
    +
  • dhh-rails-reviewer - Rails conventions
    • +
  • kieran-rails-reviewer - Rails best practices
    • +
  • code-simplicity-reviewer - Simplicity and clarity
    • +
+
+ 
/plan_review plans/user-authentication.md
+
+
+ +
+
+ /report-bug +
+

+ Report a bug in the compounding-engineering plugin. +

+

Arguments

+

[optional: brief description of the bug]

+

Information Collected

+
    +
  • Bug category (Agent/Command/Skill/MCP/Installation)
    • +
  • Specific component name
    • +
  • Actual vs expected behavior
    • +
  • Steps to reproduce
    • +
  • Error messages
    • +
  • Environment info (auto-gathered)
    • +
+
+ 
/report-bug Agent not working
+/report-bug Command failing with timeout
+
+
+ +
+
+ /reproduce-bug +
+

+ Reproduce and investigate a bug using logs and console inspection. +

+

Arguments

+

[GitHub issue number]

+

Investigation Process

+
    +
  1. Read GitHub issue details
    2. +
  2. Launch parallel investigation agents
    3. +
  3. Analyze code for failure points
    4. +
  4. Iterate until root cause found
    5. +
  5. Post findings to GitHub issue
    6. +
+
+ 
/reproduce-bug 142
+
+
+ +
+
+ /triage +
+

+ Triage and categorize findings for the CLI todo system. +

+

Arguments

+

[findings list or source type]

+

User Decisions

+
    +
  • "yes" - Create/update todo file, change status to ready
    • +
  • "next" - Skip and delete from todos
    • +
  • "custom" - Modify and re-present
    • +
+
+
+
+

This command does NOT write code. It only categorizes and creates todo files.

+
+
+
+ 
/triage code-review-findings.txt
+/triage security-audit-results
+
+
+ +
+
+ /resolve_parallel +
+

+ Resolve all TODO comments using parallel processing. +

+

Arguments

+

[optional: specific TODO pattern or file]

+

Process

+
    +
  1. Analyze TODO comments from codebase
    2. +
  2. Create dependency graph (mermaid diagram)
    3. +
  3. Spawn parallel pr-comment-resolver agents
    4. +
  4. Commit and push after completion
    5. +
+
+ 
/resolve_parallel
+/resolve_parallel authentication
+/resolve_parallel src/auth/
+
+
+ +
+
+ /resolve_pr_parallel +
+

+ Resolve all PR comments using parallel processing. +

+

Arguments

+

[optional: PR number or current PR]

+

Process

+
    +
  1. Get all unresolved PR comments
    2. +
  2. Create TodoWrite list
    3. +
  3. Launch parallel pr-comment-resolver agents
    4. +
  4. Commit, resolve threads, and push
    5. +
+
+ 
/resolve_pr_parallel
+/resolve_pr_parallel 123
+
+
+ +
+
+ /resolve_todo_parallel +
+

+ Resolve all pending CLI todos using parallel processing. +

+

Arguments

+

[optional: specific todo ID or pattern]

+

Process

+
    +
  1. Get unresolved TODOs from /todos/*.md
    2. +
  2. Analyze dependencies
    3. +
  3. Spawn parallel agents
    4. +
  4. Commit, mark as resolved, push
    5. +
+
+ 
/resolve_todo_parallel
+/resolve_todo_parallel 042
+/resolve_todo_parallel p1
+
+
+ +
+
+ /prime +
+

+ Prime/setup command for project initialization. +

+
+ 
/prime
+
+
+
+ + + +
+
+
+ + + + + diff --git a/plugins/compounding-engineering/docs/pages/mcp-servers.html b/plugins/compounding-engineering/docs/pages/mcp-servers.html new file mode 100644 index 0000000..08f6678 --- /dev/null +++ b/plugins/compounding-engineering/docs/pages/mcp-servers.html @@ -0,0 +1,400 @@ + + + + + + MCP Servers Reference - Compounding Engineering + + + + + + + + + + +
+
+ + +
+
+ + +
+ +
+

MCP Servers Reference

+

+ Model Context Protocol (MCP) servers extend Claude Code's capabilities with + browser automation and framework documentation lookup. The plugin bundles + 2 MCP servers that start automatically when enabled. +

+ +
+
+
+

Known Issue: Auto-Loading

+

+ MCP servers may not load automatically when the plugin is installed. + See Manual Configuration for the workaround. +

+
+
+ + +
+

Playwright

+

+ Browser automation via @playwright/mcp. Enables taking screenshots, + clicking elements, filling forms, and executing JavaScript in a real browser. +

+ +

Tools Provided

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ToolDescription
browser_navigateNavigate to a URL in the browser
browser_take_screenshotCapture a screenshot of the current page or element
browser_clickClick on an element using CSS selector or text
browser_fill_formFill form fields with values
browser_snapshotGet an accessibility tree snapshot of the page
browser_evaluateExecute JavaScript code in the browser context
+ +

Use Cases

+
    +
  • Design Iteration - Take screenshots for UI comparison
    • +
  • Testing - Automate browser interactions
    • +
  • Debugging - Inspect page state and DOM
    • +
  • Data Extraction - Scrape content from web pages
    • +
+ +

Example Usage

+
+ 
# The tools are available when the MCP server is running
+# Claude Code will use them automatically when appropriate
+
+# Example: Taking a screenshot for design review
+"Take a screenshot of the login page"
+
+# Example: Testing a form
+"Navigate to /signup and fill in the email field with test@example.com"
+
+ +

Configuration

+
+ 
{
+  "playwright": {
+    "type": "stdio",
+    "command": "npx",
+    "args": ["-y", "@playwright/mcp@latest"],
+    "env": {}
+  }
+}
+
+
+ + +
+

Context7

+

+ Framework documentation lookup via Context7 MCP. Provides access to + documentation for 100+ frameworks and libraries. +

+ +

Tools Provided

+ + + + + + + + + + + + + + + + + +
ToolDescription
resolve-library-idFind the library ID for a framework or package
get-library-docsGet documentation for a specific library
+ +

Supported Frameworks

+

Context7 supports 100+ frameworks including:

+
+
+

Backend

+
    +
  • Ruby on Rails
    • +
  • Django
    • +
  • Laravel
    • +
  • Express
    • +
  • FastAPI
    • +
  • Spring Boot
    • +
+
+
+

Frontend

+
    +
  • React
    • +
  • Vue.js
    • +
  • Angular
    • +
  • Svelte
    • +
  • Next.js
    • +
  • Nuxt
    • +
+
+
+

Mobile

+
    +
  • React Native
    • +
  • Flutter
    • +
  • SwiftUI
    • +
  • Kotlin
    • +
+
+
+

Tools & Libraries

+
    +
  • Tailwind CSS
    • +
  • PostgreSQL
    • +
  • Redis
    • +
  • GraphQL
    • +
  • Prisma
    • +
  • And many more...
    • +
+
+
+ +

Example Usage

+
+ 
# Claude Code will use Context7 automatically for documentation lookups
+"Look up the Rails ActionCable documentation"
+
+"How does the useEffect hook work in React?"
+
+"What are the best practices for PostgreSQL indexes?"
+
+ +

Configuration

+
+ 
{
+  "context7": {
+    "type": "http",
+    "url": "https://mcp.context7.com/mcp"
+  }
+}
+
+
+ + +
+

Manual Configuration

+

+ If MCP servers don't auto-load with the plugin, add them manually to your + .claude/settings.json file. +

+ +

Project-Level Configuration

+

Add to .claude/settings.json in your project:

+
+ 
{
+  "mcpServers": {
+    "playwright": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@playwright/mcp@latest"],
+      "env": {}
+    },
+    "context7": {
+      "type": "http",
+      "url": "https://mcp.context7.com/mcp"
+    }
+  }
+}
+
+ +

Global Configuration

+

Add to ~/.claude/settings.json to enable for all projects:

+
+ 
{
+  "mcpServers": {
+    "playwright": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@playwright/mcp@latest"],
+      "env": {}
+    },
+    "context7": {
+      "type": "http",
+      "url": "https://mcp.context7.com/mcp"
+    }
+  }
+}
+
+ +

Requirements

+ + + + + + + + + + + + + + + + + +
ServerRequirement
PlaywrightNode.js 18+ and npx
Context7Internet connection (HTTP endpoint)
+ +

Verifying MCP Servers

+

After configuration, restart Claude Code and verify the servers are loaded:

+
+ 
# Check if MCP tools are available
+"What MCP tools do you have access to?"
+
+# Test Playwright
+"Take a screenshot of the current directory listing"
+
+# Test Context7
+"Look up Rails Active Record documentation"
+
+
+ + + +
+
+
+ + + + + + + diff --git a/plugins/compounding-engineering/docs/pages/skills.html b/plugins/compounding-engineering/docs/pages/skills.html new file mode 100644 index 0000000..e86da64 --- /dev/null +++ b/plugins/compounding-engineering/docs/pages/skills.html @@ -0,0 +1,591 @@ + + + + + + Skill Reference - Compounding Engineering + + + + + + + + + + +
+
+ + +
+
+ + +
+ +
+

Skill Reference

+

+ Complete documentation for all 11 intelligent skills. Skills provide deep domain expertise + that Claude Code can invoke on-demand, including references, templates, and workflows. +

+ +
+

How to Use Skills

+
+ 
# In your prompt, reference the skill
+skill: [skill-name]
+
+# Examples
+skill: gemini-imagegen
+skill: dhh-ruby-style
+skill: create-agent-skills
+
+
+ +
+
+
+

Skills vs Agents

+

+ Agents are specialized personas invoked with claude agent [name]. + Skills are bodies of knowledge (references, templates, workflows) invoked with skill: [name]. +

+
+
+ + +
+

Development Tools (7)

+

Skills for code generation, gem writing, and development patterns.

+ +
+
+

create-agent-skills

+ Meta +
+

+ Expert guidance for creating, writing, building, and refining Claude Code Skills. + Use when working with SKILL.md files or authoring new skills. +

+

Capabilities

+
    +
  • Skill architecture and best practices
    • +
  • Router pattern for complex multi-step skills
    • +
  • Progressive disclosure design principles
    • +
  • SKILL.md structure guidance
    • +
  • Asset management (workflows, references, templates, scripts)
    • +
  • XML structure patterns
    • +
+

Workflows Included

+
    +
  • create-new-skill - Start from scratch
    • +
  • add-reference - Add reference documentation
    • +
  • add-template - Add code templates
    • +
  • add-workflow - Add step-by-step procedures
    • +
  • add-script - Add executable scripts
    • +
  • audit-skill - Validate skill structure
    • +
  • verify-skill - Test skill functionality
    • +
+
+ 
skill: create-agent-skills
+
+
+ +
+
+

skill-creator

+ Meta +
+

+ Guide for creating effective skills with a 6-step process. +

+

6-Step Process

+
    +
  1. Understand skill usage patterns with examples
    2. +
  2. Plan reusable skill contents
    3. +
  3. Initialize skill using template
    4. +
  4. Edit skill with clear instructions
    5. +
  5. Package skill into distributable zip
    6. +
  6. Iterate based on testing feedback
    7. +
+
+ 
skill: skill-creator
+
+
+ +
+
+

dhh-ruby-style

+ Rails +
+

+ Write Ruby and Rails code in DHH's distinctive 37signals style. + Triggers on Ruby/Rails code generation or when mentioning DHH, 37signals, Basecamp, HEY. +

+

Key Patterns

+
    +
  • REST Purity - 7 REST actions only
    • +
  • Fat Models - Business logic, authorization, broadcasting in models
    • +
  • Thin Controllers - 1-5 line actions
    • +
  • Current Attributes - Request context
    • +
  • Hotwire/Turbo - Model-level broadcasting
    • +
+

Ruby Syntax Preferences

+
    +
  • Symbol arrays %i[...]
    • +
  • Modern hash syntax
    • +
  • Ternaries for simple conditionals
    • +
  • Bang methods for mutations
    • +
+
+ 
skill: dhh-ruby-style
+
+
+ +
+
+

andrew-kane-gem-writer

+ Ruby +
+

+ Write Ruby gems following Andrew Kane's proven patterns and philosophy. + Based on 100+ gems with 374M+ downloads. +

+

Philosophy

+
    +
  • Simplicity over cleverness
    • +
  • Zero or minimal dependencies
    • +
  • Explicit code over metaprogramming
    • +
  • Rails integration without Rails coupling
    • +
+

Key Patterns

+
    +
  • Class macro DSL for configuration
    • +
  • ActiveSupport.on_load for Rails integration
    • +
  • class << self with attr_accessor
    • +
  • Railtie pattern for hooks
    • +
  • Minitest (no RSpec)
    • +
+

Reference Files

+
    +
  • references/module-organization.md
    • +
  • references/rails-integration.md
    • +
  • references/database-adapters.md
    • +
  • references/testing-patterns.md
    • +
+
+ 
skill: andrew-kane-gem-writer
+
+
+ +
+
+

dspy-ruby

+ AI +
+

+ Build type-safe, composable LLM applications with DSPy.rb. + Use when implementing predictable AI features in Ruby. +

+

Predictor Types

+
    +
  • Predict - Basic inference
    • +
  • ChainOfThought - Reasoning with explanations
    • +
  • ReAct - Tool-using agents with iteration
    • +
  • CodeAct - Dynamic code generation
    • +
+

Supported Providers

+
    +
  • OpenAI (GPT-4, GPT-4o-mini)
    • +
  • Anthropic Claude
    • +
  • Google Gemini
    • +
  • Ollama (free, local)
    • +
  • OpenRouter
    • +
+

Requirements

+ + + + + + + + + + + + + +
OPENAI_API_KEYFor OpenAI provider
ANTHROPIC_API_KEYFor Anthropic provider
GOOGLE_API_KEYFor Gemini provider
+
+ 
skill: dspy-ruby
+
+
+ +
+
+

frontend-design

+ Design +
+

+ Create distinctive, production-grade frontend interfaces. + Generates creative, polished code that avoids generic AI aesthetics. +

+

Design Thinking

+
    +
  • Purpose - What is the interface for?
    • +
  • Tone - What feeling should it evoke?
    • +
  • Constraints - Technical and brand limitations
    • +
  • Differentiation - How to stand out
    • +
+

Focus Areas

+
    +
  • Typography with distinctive font choices
    • +
  • Color & theme coherence with CSS variables
    • +
  • Motion and animation patterns
    • +
  • Spatial composition with asymmetry
    • +
  • Backgrounds (gradients, textures, patterns)
    • +
+
+
+
+

Avoids generic AI aesthetics like Inter fonts, purple gradients, and rounded corners everywhere.

+
+
+
+ 
skill: frontend-design
+
+
+ +
+
+

codify-docs

+ Docs +
+

+ Capture solved problems as categorized documentation with YAML frontmatter for fast lookup. +

+

Auto-Triggers

+

Phrases: "that worked", "it's fixed", "working now", "problem solved"

+

7-Step Process

+
    +
  1. Detect confirmation phrase
    2. +
  2. Gather context (module, symptom, investigation, root cause)
    3. +
  3. Check existing docs for similar issues
    4. +
  4. Generate filename
    5. +
  5. Validate YAML frontmatter
    6. +
  6. Create documentation in category directory
    7. +
  7. Cross-reference related issues
    8. +
+

Categories

+
    +
  • build-errors/
    • +
  • test-failures/
    • +
  • runtime-errors/
    • +
  • performance-issues/
    • +
  • database-issues/
    • +
  • security-issues/
    • +
+
+ 
skill: codify-docs
+
+
+
+ + +
+

Content & Workflow (3)

+

Skills for content editing, task tracking, and parallel development.

+ +
+
+

every-style-editor

+ Content +
+

+ Review and edit copy to ensure adherence to Every's style guide. + Provides systematic line-by-line review. +

+

Four-Phase Review

+
    +
  1. Initial Assessment - Context, type, audience, tone
    2. +
  2. Detailed Line Edit - Sentence structure, punctuation, capitalization
    3. +
  3. Mechanical Review - Spacing, formatting, consistency
    4. +
  4. Recommendations - Actionable improvement suggestions
    5. +
+

Style Checks

+
    +
  • Grammar and punctuation
    • +
  • Style guide compliance
    • +
  • Capitalization rules
    • +
  • Word choice optimization
    • +
  • Formatting consistency
    • +
+
+ 
skill: every-style-editor
+
+
+ +
+
+

file-todos

+ Workflow +
+

+ File-based todo tracking system in the todos/ directory. + Integrates with code review and slash commands. +

+

File Format

+
+ 
# Naming convention
+{issue_id}-{status}-{priority}-{description}.md
+
+# Examples
+001-pending-p1-security-vulnerability.md
+002-ready-p2-performance-optimization.md
+003-complete-p3-code-cleanup.md
+
+

Status Values

+
    +
  • pending - Needs triage
    • +
  • ready - Approved for work
    • +
  • complete - Done
    • +
+

Priority Values

+
    +
  • p1 - Critical
    • +
  • p2 - Important
    • +
  • p3 - Nice-to-have
    • +
+

YAML Frontmatter

+
+ 
---
+status: pending
+priority: p1
+issue_id: "001"
+tags: [security, authentication]
+dependencies: []
+---
+
+
+ 
skill: file-todos
+
+
+ +
+
+

git-worktree

+ Git +
+

+ Manage Git worktrees for isolated parallel development. + Handles creating, listing, switching, and cleaning up worktrees. +

+

Commands

+
+ 
# Create new worktree
+bash scripts/worktree-manager.sh create feature-login
+
+# List worktrees
+bash scripts/worktree-manager.sh list
+
+# Switch to worktree
+bash scripts/worktree-manager.sh switch feature-login
+
+# Clean up completed worktrees
+bash scripts/worktree-manager.sh cleanup
+
+

Integration

+
    +
  • Works with /workflows:review for isolated PR analysis
    • +
  • Works with /workflows:work for parallel feature development
    • +
+

Requirements

+
    +
  • Git 2.8+ (for worktree support)
    • +
  • Worktrees stored in .worktrees/ directory
    • +
+
+ 
skill: git-worktree
+
+
+
+ + +
+

Image Generation (1)

+

AI-powered image generation and editing.

+ + +
+ + + +
+
+
+ + + + +