Skills(41)

agent-browser—Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

agent-native-architecture—Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.

agent-native-audit—Run comprehensive agent-native architecture review with scored principles

andrew-kane-gem-writer—This skill should be used when writing Ruby gems following Andrew Kane's proven patterns and philosophy. It applies when creating new Ruby gems, refactoring existing gems, designing gem APIs, or when clean, minimal, production-ready Ruby library code is needed. Triggers on requests like "create a gem", "write a Ruby library", "design a gem API", or mentions of Andrew Kane's style.

ce:brainstorm—Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.

ce:compound—Document a recently solved problem to compound your team's knowledge

ce:compound-refresh—Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, when pattern docs no longer reflect current code, or when multiple docs seem to cover the same topic and might benefit from consolidation.

ce:ideate—Generate and critically evaluate grounded improvement ideas for the current project. Use when asking what to improve, requesting idea generation, exploring surprising improvements, or wanting the AI to proactively suggest strong project directions before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on this project', 'surprise me with improvements', 'what would you change', or any request for AI-generated project improvement suggestions rather than refining the user's own idea.

ce:plan—Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. For exploratory or ambiguous requests where the user is unsure what to do, prefer ce:brainstorm first.

ce:review—Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.

ce:work—Execute work efficiently while maintaining quality and finishing features

ce:work-beta—[BETA] Execute work with external delegate support. Same as ce:work but includes experimental Codex delegation mode for token-conserving code implementation.

changelog—Create engaging changelogs for recent merges to main branch

claude-permissions-optimizer—Optimize Claude Code permissions by finding safe Bash commands from session history and auto-applying them to settings.json. Can run from any coding agent but targets Claude Code specifically. Use when experiencing permission fatigue, too many permission prompts, wanting to optimize permissions, or needing to set up allowlists. Triggers on "optimize permissions", "reduce permission prompts", "allowlist commands", "too many permission prompts", "permission fatigue", "permission setup", or complaints about clicking approve too often.

deploy-docs—Validate and prepare documentation for GitHub Pages deployment

dhh-rails-style—This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.

document-review—Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.

dspy-ruby—Build type-safe LLM applications with DSPy.rb — Ruby's programmatic prompt framework with signatures, modules, agents, and optimization. Use when implementing predictable AI features, creating LLM signatures and modules, configuring language model providers, building agent systems with tools, optimizing prompts, or testing LLM-powered functionality in Ruby applications.

every-style-editor—This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.

feature-video—Record a video walkthrough of a feature and add it to the PR description. Use when a PR needs a visual demo for reviewers, when the user asks to demo a feature, create a PR video, record a walkthrough, show what changed visually, or add a video to a pull request.

frontend-design—Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.

gemini-imagegen—This skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.

git-clean-gone-branches—Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.

git-commit—Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.

git-commit-push-pr—Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Also use when the user says "update the PR description", "refresh the PR description", "freshen the PR", or wants to rewrite an existing PR description. Produces PR descriptions that scale in depth with the complexity of the change, avoiding cookie-cutter templates.

git-worktree—This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.

lfg—Full autonomous engineering workflow

onboarding—Generate or regenerate ONBOARDING.md to help new contributors understand a codebase. Use when the user asks to 'create onboarding docs', 'generate ONBOARDING.md', 'document this project for new developers', 'write onboarding documentation', 'vonboard', 'vonboarding', 'prepare this repo for a new contributor', 'refresh the onboarding doc', or 'update ONBOARDING.md'. Also use when someone needs to onboard a new team member and wants a written artifact, or when a codebase lacks onboarding documentation and the user wants to generate one.

orchestrating-swarms—This skill should be used when orchestrating multi-agent swarms using Claude Code's TeammateTool and Task system. It applies when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns.

proof—Create, edit, comment on, and share markdown documents via Proof's web API and local bridge. Use when asked to "proof", "share a doc", "create a proof doc", "comment on a document", "suggest edits", "review in proof", or when given a proofeditor.ai URL.

rclone—Upload, sync, and manage files across cloud storage providers using rclone. Use when uploading files (images, videos, documents) to S3, Cloudflare R2, Backblaze B2, Google Drive, Dropbox, or any S3-compatible storage. Triggers on "upload to S3", "sync to cloud", "rclone", "backup files", "upload video/image to bucket", or requests to transfer files to remote storage.

report-bug-ce—Report a bug in the compound-engineering plugin

reproduce-bug—Systematically reproduce and investigate a bug from a GitHub issue. Use when the user provides a GitHub issue number or URL for a bug they want reproduced or investigated.

resolve-pr-feedback—Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.

setup—Configure project-level settings for compound-engineering workflows. Currently a placeholder — review agent selection is handled automatically by ce:review.

slfg—Full autonomous engineering workflow using swarm mode for parallel execution

test-browser—Run browser tests on pages affected by current PR or branch

test-xcode—Build and test iOS apps on simulator using XcodeBuildMCP. Use after making iOS code changes, before creating a PR, or when verifying app behavior and checking for crashes on simulator.

todo-create—Use when creating durable work items, managing todo lifecycle, or tracking findings across sessions in the file-based todo system

todo-resolve—Use when batch-resolving approved todos, especially after code review or triage sessions

todo-triage—Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items

written by Forgecat

Forgecat

compound-engineering

AI-powered development tools for code review, research, design, and workflow automation.

Installation

npx forgecat install @forgecat/everyinc_compound-engineering-plugin

Skills / Agents / Commands

skills/ — 37 reusable skills for planning, review, bug triage, browser testing, and workflow automation.
agents/ — 42 specialist agents across research, review, design, and workflow domains.

Details

Field	Value
Author	Kieran Klaassen
Original repository	https://github.com/EveryInc/compound-engineering-plugin
Version	`0.0.0`
Original commit	`a6183ed`
License	`MIT`
Source platform	Cursor

Compatibility

Platforms

Platform	Status
Claude Code	Partial
Cursor	Tested
Codex	Partial

written by original source

Compounding Engineering Plugin

AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last.

Components

Component	Count
Agents	50+
Skills	40+

Skills

Core Workflow

The primary entry points for engineering work, invoked as slash commands:

Skill	Description
`/ce:ideate`	Discover high-impact project improvements through divergent ideation and adversarial filtering
`/ce:brainstorm`	Explore requirements and approaches before planning
`/ce:plan`	Create structured plans for any multi-step task -- software features, research workflows, events, study plans -- with automatic confidence checking
`/ce:review`	Structured code review with tiered persona agents, confidence gating, and dedup pipeline
`/ce:work`	Execute work items systematically
`/ce:compound`	Document solved problems to compound team knowledge
`/ce:compound-refresh`	Refresh stale or drifting learnings and decide whether to keep, update, replace, or archive them

Git Workflow

Skill	Description
`git-clean-gone-branches`	Clean up local branches whose remote tracking branch is gone
`git-commit`	Create a git commit with a value-communicating message
`git-commit-push-pr`	Commit, push, and open a PR with an adaptive description; also update an existing PR description
`git-worktree`	Manage Git worktrees for parallel development

Workflow Utilities

Skill	Description
`/changelog`	Create engaging changelogs for recent merges
`/feature-video`	Record video walkthroughs and add to PR description
`/reproduce-bug`	Reproduce bugs using logs and console
`/report-bug-ce`	Report a bug in the compound-engineering plugin
`/resolve-pr-feedback`	Resolve PR review feedback in parallel
`/sync`	Sync Claude Code config across machines
`/test-browser`	Run browser tests on PR-affected pages
`/test-xcode`	Build and test iOS apps on simulator using XcodeBuildMCP
`/onboarding`	Generate `ONBOARDING.md` to help new contributors understand the codebase
`/todo-resolve`	Resolve todos in parallel
`/todo-triage`	Triage and prioritize pending todos

Development Frameworks

Skill	Description
`agent-native-architecture`	Build AI agents using prompt-native architecture
`andrew-kane-gem-writer`	Write Ruby gems following Andrew Kane's patterns
`dhh-rails-style`	Write Ruby/Rails code in DHH's 37signals style
`dspy-ruby`	Build type-safe LLM applications with DSPy.rb
`frontend-design`	Create production-grade frontend interfaces

Review & Quality

Skill	Description
`claude-permissions-optimizer`	Optimize Claude Code permissions from session history
`document-review`	Review documents using parallel persona agents for role-specific feedback
`setup`	Reserved for future project-level workflow configuration; code review agent selection is automatic

Content & Collaboration

Skill	Description
`every-style-editor`	Review copy for Every's style guide compliance
`proof`	Create, edit, and share documents via Proof collaborative editor
`todo-create`	File-based todo tracking system

Automation & Tools

Skill	Description
`agent-browser`	CLI-based browser automation using Vercel's agent-browser
`gemini-imagegen`	Generate and edit images using Google's Gemini API
`orchestrating-swarms`	Comprehensive guide to multi-agent swarm orchestration
`rclone`	Upload files to S3, Cloudflare R2, Backblaze B2, and cloud storage

Beta / Experimental

Skill	Description
`/lfg`	Full autonomous engineering workflow
`/slfg`	Full autonomous workflow with swarm mode for parallel execution

Agents

Agents are specialized subagents invoked by skills — you typically don't call these directly.

Review

Agent	Description
`agent-native-reviewer`	Verify features are agent-native (action + context parity)
`api-contract-reviewer`	Detect breaking API contract changes
`cli-agent-readiness-reviewer`	Evaluate CLI agent-friendliness against 7 core principles
`cli-readiness-reviewer`	CLI agent-readiness persona for ce:review (conditional, structured JSON)
`architecture-strategist`	Analyze architectural decisions and compliance
`code-simplicity-reviewer`	Final pass for simplicity and minimalism
`correctness-reviewer`	Logic errors, edge cases, state bugs
`data-integrity-guardian`	Database migrations and data integrity
`data-migration-expert`	Validate ID mappings match production, check for swapped values
`data-migrations-reviewer`	Migration safety with confidence calibration
`deployment-verification-agent`	Create Go/No-Go deployment checklists for risky data changes
`dhh-rails-reviewer`	Rails review from DHH's perspective
`julik-frontend-races-reviewer`	Review JavaScript/Stimulus code for race conditions
`kieran-rails-reviewer`	Rails code review with strict conventions
`kieran-python-reviewer`	Python code review with strict conventions
`kieran-typescript-reviewer`	TypeScript code review with strict conventions
`maintainability-reviewer`	Coupling, complexity, naming, dead code
`pattern-recognition-specialist`	Analyze code for patterns and anti-patterns
`performance-oracle`	Performance analysis and optimization
`performance-reviewer`	Runtime performance with confidence calibration
`reliability-reviewer`	Production reliability and failure modes
`schema-drift-detector`	Detect unrelated schema.rb changes in PRs
`security-reviewer`	Exploitable vulnerabilities with confidence calibration
`security-sentinel`	Security audits and vulnerability assessments
`testing-reviewer`	Test coverage gaps, weak assertions
`project-standards-reviewer`	CLAUDE.md and AGENTS.md compliance
`adversarial-reviewer`	Construct failure scenarios to break implementations across component boundaries

Document Review

Agent	Description
`coherence-reviewer`	Review documents for internal consistency, contradictions, and terminology drift
`design-lens-reviewer`	Review plans for missing design decisions, interaction states, and AI slop risk
`feasibility-reviewer`	Evaluate whether proposed technical approaches will survive contact with reality
`product-lens-reviewer`	Challenge problem framing, evaluate scope decisions, surface goal misalignment
`scope-guardian-reviewer`	Challenge unjustified complexity, scope creep, and premature abstractions
`security-lens-reviewer`	Evaluate plans for security gaps at the plan level (auth, data, APIs)
`adversarial-document-reviewer`	Challenge premises, surface unstated assumptions, and stress-test decisions

Research

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
`issue-intelligence-analyst`	Analyze GitHub issues to surface recurring themes and pain patterns
`learnings-researcher`	Search institutional learnings for relevant past solutions
`repo-research-analyst`	Research repository structure and conventions
`slack-researcher`	Search Slack for organizational context relevant to the current task

Design

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

Workflow

Agent	Description
`bug-reproduction-validator`	Systematically reproduce and validate bug reports
`lint`	Run linting and code quality checks on Ruby and ERB files
`pr-comment-resolver`	Address PR comments and implement fixes
`spec-flow-analyzer`	Analyze user flows and identify gaps in specifications

Docs

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

Browser Automation

This plugin uses agent-browser CLI for browser automation tasks. Install it globally:

npm install -g agent-browser
agent-browser install  # Downloads Chromium

The agent-browser skill provides comprehensive documentation on usage.

Installation

claude /plugin install compound-engineering

Version History

See the repo root CHANGELOG.md for canonical release history.

License

MIT

heating the forge...

everyinc_compound-engineering-plugin

Who I Am

Agents(50)

Skills(41)

Rules(1)

README.md

compound-engineering

Tags

Installation

Skills / Agents / Commands

Details

Compatibility

Platforms

Compounding Engineering Plugin

Components

Skills

Core Workflow

Git Workflow

Workflow Utilities

Development Frameworks

Review & Quality

Content & Collaboration

Automation & Tools

Beta / Experimental

Agents

Review

Document Review

Research

Design

Workflow

Docs

Browser Automation

Installation

Version History

License

Tags

Creator

Details

Platforms

Models

Dependencies