AI-powered development tools for code review, research, design, and workflow automation.
Visually compares live UI implementation against Figma designs and provides detailed feedback on discrepancies. Use after writing or modifying HTML/CSS/React components to verify design fidelity.
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
Detects and fixes visual differences between a web implementation and its Figma design. Use iteratively when syncing implementation to match Figma specs.
Creates or updates README files following Ankane-style template for Ruby gems. Use when writing gem documentation with imperative voice, concise prose, and standard section ordering.
Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.
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.
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.
Run comprehensive agent-native architecture review with scored principles
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.
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.
External network access
Connects to servers outside your machine
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Codex-first derivative of Compound Engineering that preserves the ce:* workflow surface while making AGENTS.md, CONTINUITY.md, .beads/, and handoff/beads.jsonl first-class.
/plugin marketplace add apollostreetcompany/codex-compound
/plugin install compound-engineering
/add-plugin compound-engineering
This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode, Codex, Factory Droid, Pi, Gemini CLI, GitHub Copilot, Kiro CLI, Windsurf, OpenClaw, and Qwen Code.
Until the standalone npm package is published, run these commands from a checkout with bun run src/index.ts .... The examples below show the intended installed command name.
# convert the compound-engineering plugin into OpenCode format
bunx codex-compound install compound-engineering --to opencode
# convert to Codex format
bunx codex-compound install compound-engineering --to codex
# convert to Factory Droid format
bunx codex-compound install compound-engineering --to droid
# convert to Pi format
bunx codex-compound install compound-engineering --to pi
# convert to Gemini CLI format
bunx codex-compound install compound-engineering --to gemini
# convert to GitHub Copilot format
bunx codex-compound install compound-engineering --to copilot
# convert to Kiro CLI format
bunx codex-compound install compound-engineering --to kiro
# convert to OpenClaw format
bunx codex-compound install compound-engineering --to openclaw
# convert to Windsurf format (global scope by default)
bunx codex-compound install compound-engineering --to windsurf
# convert to Windsurf workspace scope
bunx codex-compound install compound-engineering --to windsurf --scope workspace
# convert to Qwen Code format
bunx codex-compound install compound-engineering --to qwen
# auto-detect installed tools and install to all
bunx codex-compound install compound-engineering --to all
When developing and testing local changes to the plugin:
Claude Code — add a shell alias so your local copy loads alongside your normal plugins:
# add to ~/.zshrc or ~/.bashrc
alias claude-dev-ce='claude --plugin-dir ~/code/codex-compound/plugins/compound-engineering'
One-liner to append it:
echo "alias claude-dev-ce='claude --plugin-dir ~/code/codex-compound/plugins/compound-engineering'" >> ~/.zshrc
Then run claude-dev-ce instead of claude to test your changes. Your production install stays untouched.
Codex — point the install command at your local path:
bun run src/index.ts install ./plugins/compound-engineering --to codex
Other targets — same pattern, swap the target:
bun run src/index.ts install ./plugins/compound-engineering --to opencode
| Target | Output path | Notes |
|---|---|---|
opencode | ~/.config/opencode/ | Commands as .md files; opencode.json MCP config deep-merged; backups made before overwriting |
codex | ~/.codex/prompts + ~/.codex/skills | Claude commands become prompt + skill pairs; canonical ce:* workflow skills also get prompt wrappers; deprecated workflows:* aliases are omitted |
droid | ~/.factory/ | Tool names mapped (Bash→Execute, Write→Create); namespace prefixes stripped |
pi | ~/.pi/agent/ | Prompts, skills, extensions, and mcporter.json for MCPorter interoperability |
gemini | .gemini/ | Skills from agents; commands as .toml; namespaced commands become directories (workflows:plan → commands/workflows/plan.toml) |
copilot | .github/ | Agents as .agent.md with Copilot frontmatter; MCP env vars prefixed with COPILOT_MCP_ |
kiro | .kiro/ | Agents as JSON configs + prompt .md files; only stdio MCP servers supported |
openclaw | ~/.openclaw/extensions/<plugin>/ | Entry-point TypeScript skill file; openclaw-extension.json for MCP servers |
windsurf | ~/.codeium/windsurf/ (global) or .windsurf/ (workspace) | Agents become skills; commands become flat workflows; mcp_config.json merged |
qwen | ~/.qwen/extensions/<plugin>/ | Agents as .yaml; env vars with placeholders extracted as settings; colon separator for nested commands |
All provider targets are experimental and may change as the formats evolve.
npx claudepluginhub apollostreetcompany/codex-compound --plugin compound-engineeringClaude Code plugin for rp-mini context engineering: MCP tools, context-builder subagent, workflow skills, and optional warm hook.
Personalized coding tutorials that use your actual codebase for examples with spaced repetition quizzes
AI-powered development tools. 29 agents, 24 commands, 18 skills, 1 MCP server for code review, research, design, and workflow automation.
Language-agnostic engineering workflows. Includes 20 specialized agents, 33 commands, 43 skills, and 5 toolbox presets. Now includes relay orchestration for fresh-context task execution with quality gates and compound learning.
Compound Engineering workflow: PRD-driven sprints, isolated worktrees, hook-enforced safety, automated learning. Skills become /vini-workflow:plan, /vini-workflow:compound, etc.
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
One plugin to bridge and delegate across Claude Code, Codex CLI, and Gemini CLI — single-source AGENTS.md, shared skills, mirrored hooks and MCP servers, and full Claude↔Codex bidirectional delegation.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses