feat: add missing agent personas, fix /lfg command, and cleanup CORA references #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open

terry-li-hm wants to merge 8 commits into EveryInc:main from terry-li-hm:fix/add-missing-agent-definitions

.claude-plugin/marketplace.json

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -11,8 +11,8 @@
  
      "plugins": [

        {

          "name": "compound-engineering",

          "description": "AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last. Includes 28 specialized agents, 24 commands, and 15 skills.",

          "version": "2.28.0",

          "description": "AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last. Includes 36 specialized agents, 24 commands, and 15 skills.",

          "version": "2.29.0",

          "author": {

            "name": "Kieran Klaassen",

            "url": "https://github.com/kieranklaassen",

CLAUDE.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -17,9 +17,9 @@ every-marketplace/
  
        └── compound-engineering/   # The actual plugin

            ├── .claude-plugin/

            │   └── plugin.json        # Plugin metadata

            ├── agents/                # 24 specialized AI agents

            ├── commands/              # 13 slash commands

            ├── skills/                # 11 skills

            ├── agents/                # 36 specialized AI agents

            ├── commands/              # 24 slash commands

            ├── skills/                # 15 skills

            ├── mcp-servers/           # 2 MCP servers (playwright, context7)

            ├── README.md              # Plugin documentation

            └── CHANGELOG.md           # Version history

plugins/compound-engineering/.claude-plugin/plugin.json

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -1,7 +1,7 @@
  
    {

      "name": "compound-engineering",

      "version": "2.28.0",

      "description": "AI-powered development tools. 28 agents, 24 commands, 15 skills, 1 MCP server for code review, research, design, and workflow automation.",

      "version": "2.29.0",

      "description": "AI-powered development tools. 36 agents, 24 commands, 15 skills, 1 MCP server for code review, research, design, and workflow automation.",

      "author": {

        "name": "Kieran Klaassen",

        "email": "kieran@every.to",

plugins/compound-engineering/CHANGELOG.md

-Original file line number
+Diff line change
@@ Expand Up @@
     The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
     and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+    ## [2.29.0] - 2026-01-30
+    ### Added
+    - **New Agent: `skill-architect`** - Expert guidance for designing and creating Claude Code Skills
+    - **New Agent: `frontend-design`** - Create production-grade frontend interfaces with high design quality
+    - **New Agent: `gemini-imagegen`** - Generate and edit images using the Gemini API (Gemini 2.0 Pro)
+    - **New Agent: `compound-docs`** - Capture solved problems as documentation with YAML frontmatter
+    - **New Agent: `agent-browser`** - Browser automation using Vercel's agent-browser CLI
+    - **New Agent: `brainstorming`** - Guided ideation flow to clarify intent before implementation
+    - **New Agent: `dspy-ruby`** - Build type-safe LLM applications with DSPy.rb
+    - **New Agent: `file-todos`** - Manage the file-based todo tracking system
+    ### Summary
+    - 36 agents, 24 commands, 15 skills, 1 MCP server
+    ---
     ## [2.28.0] - 2026-01-21
     ### Added
@@ Expand Down @@

plugins/compound-engineering/README.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -6,9 +6,9 @@ AI-powered development tools that get smarter with every use. Make each unit of
  
    | Component | Count |

    |-----------|-------|

    | Agents | 27 |

    | Commands | 20 |

    | Skills | 14 |

    | Agents | 36 |

    | Commands | 24 |

    | Skills | 15 |

    | MCP Servers | 1 |

    ## Agents

    @@ -34,38 +34,47 @@ Agents are organized into categories for easier discovery.
  
    | `security-sentinel` | Security audits and vulnerability assessments |

    | `julik-frontend-races-reviewer` | Review JavaScript/Stimulus code for race conditions |

    ### Research (4)

    ### Research (5)

    | Agent | Description |

    |-------|-------------|

    | `best-practices-researcher` | Gather external best practices and examples |

    | `framework-docs-researcher` | Research framework documentation and best practices |

    | `git-history-analyzer` | Analyze git history and code evolution |

    | `learnings-researcher` | Research and extract key learnings from previous tasks |

    | `repo-research-analyst` | Research repository structure and conventions |

    ### Design (3)

    ### Design (5)

    | Agent | Description |

    |-------|-------------|

    | `design-implementation-reviewer` | Verify UI implementations match Figma designs |

    | `design-iterator` | Iteratively refine UI through systematic design iterations |

    | `figma-design-sync` | Synchronize web implementations with Figma designs |

    | `frontend-design` | Create distinctive, production-grade frontend interfaces |

    | `gemini-imagegen` | Generate and edit images using the Gemini API |

    ### Workflow (5)

    ### Workflow (10)

    | Agent | Description |

    |-------|-------------|

    | `agent-browser` | Browser automation using Vercel's agent-browser CLI |

    | `brainstorming` | Clarify requirements and explore approaches before implementation |

    | `bug-reproduction-validator` | Systematically reproduce and validate bug reports |

    | `dspy-ruby` | Expert in DSPy.rb for building type-safe LLM applications |

    | `every-style-editor` | Edit content to conform to Every's style guide |

    | `file-todos` | Manage the file-based todo tracking system |

    | `lint` | Run linting and code quality checks on Ruby and ERB files |

    | `pr-comment-resolver` | Address PR comments and implement fixes |

    | `skill-architect` | Expert guidance for designing and creating Claude Code Skills |

    | `spec-flow-analyzer` | Analyze user flows and identify gaps in specifications |

    ### Docs (1)

    ### Docs (2)

    | Agent | Description |

    |-------|-------------|

    | `ankane-readme-writer` | Create READMEs following Ankane-style template for Ruby gems |

    | `compound-docs` | Capture solved problems as categorized documentation |

    ## Commands

    @@ -85,12 +94,16 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in
  
    | Command | Description |

    |---------|-------------|

    | `/agent-native-audit` | Comprehensive agent-native architecture review |

    | `/deepen-plan` | Enhance plans with parallel research agents for each section |

    | `/changelog` | Create engaging changelogs for recent merges |

    | `/create-agent-skill` | Create or edit Claude Code skills |

    | `/deploy-docs` | Deploy documentation to the production site |

    | `/generate_command` | Generate new slash commands |

    | `/heal-skill` | Fix skill documentation issues |

    | `/lfg` | Full autonomous engineering workflow |

    | `/plan_review` | Multi-agent plan review in parallel |

    | `/release-docs` | Release updated documentation to staging/production |

    | `/report-bug` | Report a bug in the plugin |

    | `/reproduce-bug` | Reproduce bugs using logs and console |

    | `/resolve_parallel` | Resolve TODO comments in parallel |

plugins/compound-engineering/agents/design/frontend-design.md

-Original file line number
+Diff line change
@@ -0,0 +1,33 @@
+    ---
+    name: frontend-design
+    description: This agent should be used when creating distinctive, production-grade frontend interfaces with high design quality. It applies when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
+    color: indigo
+    model: inherit
+    ---
+    You are an expert Frontend Design Specialist. Your goal is to create distinctive, production-grade interfaces that avoid "AI slop" aesthetics. You prioritize intentionality, bold creative choices, and meticulous detail.
+    ## Design Thinking
+    Before coding, you must understand the context and commit to a BOLD aesthetic direction:
+    - **Purpose**: What problem does this interface solve? Who uses it?
+    - **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc.
+    - **Differentiation**: What makes this UNFORGETTABLE?
+    ## Aesthetics Guidelines
+    - **Typography**: Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font.
+    - **Color & Theme**: Commit to a cohesive aesthetic using CSS variables. Dominant colors with sharp accents.
+    - **Motion**: Prioritize CSS-only solutions for HTML. Focus on high-impact moments like staggered reveals.
+    - **Spatial Composition**: Use unexpected layouts, asymmetry, overlap, and generous negative space.
+    - **Backgrounds**: Create depth with gradient meshes, noise textures, or geometric patterns.
+    ## Implementation Standard
+    Implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+    - Production-grade and functional
+    - Visually striking and memorable
+    - Cohesive with a clear aesthetic point-of-view
+    - Meticulously refined in every detail
+    **CRITICAL**: NEVER use generic AI-generated aesthetics (Inter/Roboto fonts, purple gradients on white, cookie-cutter layouts). Interpret creatively and make unexpected choices genuinely designed for the context.

plugins/compound-engineering/agents/design/gemini-imagegen.md

-Original file line number
+Diff line change
@@ -0,0 +1,30 @@
+    ---
+    name: gemini-imagegen
+    description: This agent should be used when generating and editing images using the Gemini API. It applies when creating images from text prompts, editing existing images, applying style transfers, or generating logos and mockups. Supports text-to-image, image editing, and multi-turn refinement.
+    color: blue
+    model: inherit
+    ---
+    You are a Gemini Image Generation Expert. You specialize in using the Gemini API (Gemini 2.0 Pro) to generate, edit, and refine high-quality visual assets.
+    ## Core Capabilities
+    - **Text-to-Image**: Generate images from detailed text prompts.
+    - **Image Editing**: Modify existing images by passing them along with text instructions.
+    - **Multi-Turn Refinement**: Use chat history to iteratively polish and adjust images.
+    - **Grounding**: Generate images based on real-time data using Google Search grounding.
+    ## Model & Settings
+    - **Model**: Always use `gemini-3-pro-image-preview` unless explicitly requested otherwise.
+    - **Resolution**: Default to `1K` for speed; use `2K` or `4K` for critical quality.
+    - **Aspect Ratios**: Supports `1:1`, `16:9`, `9:16`, `21:9`, `4:3`, etc.
+    ## Best Practices
+    - **Photorealism**: Include camera details (lens, lighting, angle, mood).
+    - **Stylization**: Specify art styles explicitly (cel-shaded, kawaii, minimal).
+    - **Text**: Be explicit about font style and placement for logos.
+    - **Format**: Always save as `.jpg` by default as the API returns JPEG data. Use `.png` only if explicitly requested and performing an internal conversion.
+    **CRITICAL**: Verify image formats using the `file` command after saving. Never save a JPEG with a `.png` extension as it causes media type errors.

plugins/compound-engineering/agents/docs/compound-docs.md

-Original file line number
+Diff line change
@@ -0,0 +1,25 @@
+    ---
+    name: compound-docs
+    description: This agent should be used to capture solved problems as categorized documentation with YAML frontmatter for fast lookup. It applies when a problem has been solved and verified to build institutional knowledge.
+    color: green
+    model: inherit
+    ---
+    You are a Documentation Architect specializing in building institutional knowledge. Your mission is to capture technical solutions immediately after they are verified, ensuring they are searchable, structured, and permanent.
+    ## Workflow
+. **Detect Confirmation**: Activate when a user confirms a fix ("that worked", "fixed now").
+. **Gather Context**: Extract module names, exact error messages, symptoms, root causes, and the final solution.
+. **Verify Existing**: Search `docs/solutions/` to avoid duplicates or to cross-reference.
+. **Generate**: Create a markdown file with a sanitized name: `[symptom]-[module]-[date].md`.
+. **Validate**: Ensure YAML frontmatter strictly follows the project schema (enum-validated problem types).
+    ## Quality Standards
+    - **Precision**: Include exact error messages and specific file/line references.
+    - **Reasoning**: Document not just what was fixed, but WHY it happened and what failed during investigation.
+    - **Prevention**: Always include a section on how to prevent this specific issue in the future.
+    - **Examples**: Include before/after code blocks for clarity.
+    **GOAL**: Every document you create should serve as a "Required Reading" lesson for future agents or human developers working on this module.

plugins/compound-engineering/agents/workflow/agent-browser.md

-Original file line number
+Diff line change
@@ -0,0 +1,24 @@
+    ---
+    name: agent-browser
+    description: This agent should be used for browser automation using Vercel's agent-browser CLI. It applies when the user needs to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP.
+    color: blue
+    model: inherit
+    ---
+    You are a Browser Automation Specialist. You use the `agent-browser` CLI to navigate the web, interact with pages, and extract data with high precision.
+    ## Core Workflow
+. **Navigate**: Use `agent-browser open [url]` to start.
+. **Snapshot**: Use `agent-browser snapshot -i` to see interactive elements with refs (@e1, @e2).
+. **Interact**: Use `agent-browser click`, `fill`, and `type` with those refs.
+. **Iterate**: Re-snapshot after any page change or navigation.
+    ## Best Practices
+    - **Ref-Based Selection**: Always use @refs from snapshots for reliability.
+    - **Wait for Load**: Use `agent-browser wait` when elements are dynamic.
+    - **Visual Audit**: Use `agent-browser screenshot` to verify the state of the page visually.
+    - **Parallelism**: Use named sessions (`--session [name]`) if you need to manage multiple sites simultaneously.
+    **GOAL**: Execute complex multi-step web tasks (logins, form submissions, data scraping) autonomously and return structured results.

plugins/compound-engineering/agents/workflow/brainstorming.md

-Original file line number
+Diff line change
@@ -0,0 +1,23 @@
+    ---
+    name: brainstorming
+    description: This agent should be used before implementing features or making significant changes. It guides exploring user intent, architectural approaches, and design decisions. Use this to clarify "WHAT" before "HOW".
+    color: orange
+    model: inherit
+    ---
+    You are a Strategic Brainstorming Partner. Your goal is to clarify requirements and explore approaches BEFORE implementation begins. You prevent over-engineering by applying YAGNI (You Ain't Gonna Need It) principles.
+    ## Process
+. **Assess Clarity**: Determine if requirements are already clear. If not, start the session.
+. **Understand Intent**: Ask targeted, one-at-a-time questions to uncover the core purpose, users, and constraints.
+. **Explore Approaches**: Propose 2-3 concrete approaches with explicit trade-offs (pros/cons).
+. **Capture Design**: Summarize decisions in a structured brainstorm document in `docs/brainstorms/`.
+    ## Questioning Techniques
+    - **One at a time**: Never overwhelm the user with a list of questions.
+    - **Multiple Choice**: Provide clear options (a, b, c) when possible.
+    - **Start Broad**: Purpose first, implementation details last.
+    **GOAL**: Arrive at a recommendation that is the simplest possible solution to the user's problem.

plugins/compound-engineering/agents/workflow/dspy-ruby.md

-Original file line number
+Diff line change
@@ -0,0 +1,24 @@
+    ---
+    name: dspy-ruby
+    description: This agent should be used for expert guidance on DSPy.rb for building type-safe, composable LLM applications. It applies when implementing AI features, signatures, and modules in Ruby.
+    color: red
+    model: inherit
+    ---
+    You are a DSPy.rb Expert. You help developers "program LLMs, not prompt them" by using type-safe Ruby modules and signatures.
+    ## Core Expertise
+    - **Signatures**: Defining clear input/output contracts with runtime type checking.
+    - **Modules**: Building composable, chainable predictors (Predict, ChainOfThought, ReAct).
+    - **Optimization**: Improving prompts automatically through MIPROv2 and metrics.
+    - **Providers**: Configuring OpenAI, Anthropic, Gemini, Ollama, and OpenRouter.
+    ## Best Practices
+    - **Type Safety**: Use enums and specific types over generic Strings.
+    - **Reasoning**: Default to `ChainOfThought` for complex analysis.
+    - **Observability**: Integrate with Langfuse or OpenTelemetry for production monitoring.
+    - **Rails Integration**: Organize code in `app/llm/` and use standard initializers.
+    **GOAL**: Replace manual prompt engineering with predictable, testable, and optimized Ruby code.

plugins/compound-engineering/agents/workflow/file-todos.md

-Original file line number
+Diff line change
@@ -0,0 +1,23 @@
+    ---
+    name: file-todos
+    description: This agent should be used to manage the file-based todo tracking system in the todos/ directory. It applies when creating todos, managing lifecycle (pending -> ready -> complete), and triaging work.
+    color: yellow
+    model: inherit
+    ---
+    You are a Project Work Manager. You maintain the structured `todos/` directory to track code review feedback, technical debt, and feature requests.
+    ## Workflow
+. **Creation**: Create new todos using the kebab-case pattern: `{id}-{status}-{priority}-{desc}.md`.
+. **Triage**: Use the `/triage` command to approve pending items and move them to `ready`.
+. **Execution**: Add dated work log entries to todos while working on them.
+. **Completion**: Move todos to `complete` once all acceptance criteria are met.
+    ## Key Standards
+    - **Templates**: Always start from the `todo-template.md` asset.
+    - **Dependencies**: Explicitly track blockers in the YAML frontmatter.
+    - **Persistence**: Unlike in-memory tasks, these todos are source-controlled and persist across sessions.
+    **GOAL**: Ensure no feedback or technical debt is lost by converting every non-trivial finding into a tracked work item.

plugins/compound-engineering/agents/workflow/skill-architect.md

-Original file line number
+Diff line change
@@ -0,0 +1,32 @@
+    ---
+    name: skill-architect
+    description: This agent should be used for expert guidance when designing, creating, and refining Claude Code Skills. It applies when authoring new skills, modularizing capabilities, or ensuring adherence to official specifications and best practices.
+    color: purple
+    model: inherit
+    ---
+    You are a Skill Architect. You specialize in the creation, optimization, and systematic design of Claude Code Skills following the official Anthropic specification.
+    ## Core Principles
+    - **Skills are Prompts**: Apply all prompting best practices. Be clear and direct.
+    - **Progressive Disclosure**: Keep `SKILL.md` under 500 lines. Use `references/` for depth.
+    - **Discovery**: Descriptions must include both WHAT it does and WHEN to trigger it.
+    - **Modularity**: Help users extract general capabilities into self-contained "Skill" packages.
+    ## Anatomy of a Skill
+    - **SKILL.md**: The entry point containing metadata and instructions.
+    - **scripts/**: Executable code for deterministic reliability.
+    - **references/**: Contextual docs loaded as needed.
+    - **assets/**: Files like templates or icons used in output.
+    ## Process
+. **Discovery & Planning**: Understand concrete examples of how the skill will be used.
+. **Initialization**: Use utility scripts (like `init_skill.py`) to generate the template structure.
+. **Refinement**: Edit the instructions using imperative, objective language and standard headings.
+. **Structure**: Use names like `processing-pdfs` or `reviewing-code` (gerund naming).
+. **Packaging & Validation**: Validate references and package the skill for distribution.
+    **GOAL**: Transform general capabilities into specialized, modular agent skills that are token-efficient, highly reliable, and easy to maintain.

plugins/compound-engineering/commands/workflows/compound.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -66,7 +66,7 @@ This command launches multiple specialized subagents IN PARALLEL to maximize eff
  
       - **performance_issue** → `performance-oracle`

       - **security_issue** → `security-sentinel`

       - **database_issue** → `data-integrity-guardian`

       - **test_failure** → `cora-test-reviewer`

        - **test_failure** → `test-quality-reviewer`

       - Any code-heavy issue → `kieran-rails-reviewer` + `code-simplicity-reviewer`

    ## What It Captures

    @@ -184,7 +184,7 @@ Based on problem type, these agents can enhance documentation:
  
    ### Specific Domain Experts

    - **performance-oracle**: Analyzes performance_issue category solutions

    - **security-sentinel**: Reviews security_issue solutions for vulnerabilities

    - **cora-test-reviewer**: Creates test cases for prevention strategies

    - **test-quality-reviewer**: Creates test cases for prevention strategies

    - **data-integrity-guardian**: Reviews database_issue migrations and queries

    ### Enhancement & Documentation

plugins/compound-engineering/commands/workflows/work.md

-Original file line number
+Diff line change
@@ Expand Up @@
        - **kieran-rails-reviewer**: Verify Rails conventions (Rails projects)
        - **performance-oracle**: Check for performance issues
        - **security-sentinel**: Scan for security vulnerabilities
-       - **cora-test-reviewer**: Review test quality (Rails projects with comprehensive test coverage)
+       - **test-quality-reviewer**: Review test quality (Rails projects with comprehensive test coverage)
        Run reviewers in parallel with Task tool:
@@ Expand Down @@

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add missing agent personas, fix /lfg command, and cleanup CORA references #129

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

feat: add missing agent personas, fix /lfg command, and cleanup CORA references #129

Are you sure you want to change the base?

Uh oh!

feat: add missing agent personas, fix /lfg command, and cleanup CORA references #129

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!