@every-env/compound-plugin 0.1.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,37 @@
+{
+  "name": "every-marketplace",
+  "owner": {
+    "name": "Kieran Klaassen",
+    "url": "https://github.com/kieranklaassen"
+  },
+  "metadata": {
+    "description": "Plugin marketplace for Claude Code extensions",
+    "version": "1.0.0"
+  },
+  "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 27 specialized agents, 23 commands, and 14 skills.",
+      "version": "2.27.0",
+      "author": {
+        "name": "Kieran Klaassen",
+        "url": "https://github.com/kieranklaassen",
+        "email": "kieran@every.to"
+      },
+      "homepage": "https://github.com/kieranklaassen/compound-engineering-plugin",
+      "tags": ["ai-powered", "compound-engineering", "workflow-automation", "code-review", "quality", "knowledge-management", "image-generation"],
+      "source": "./plugins/compound-engineering"
+    },
+    {
+      "name": "coding-tutor",
+      "description": "Personalized coding tutorials that build on your existing knowledge and use your actual codebase for examples. Includes spaced repetition quizzes to reinforce learning. Includes 3 commands and 1 skill.",
+      "version": "1.2.1",
+      "author": {
+        "name": "Nityesh Agarwal"
+      },
+      "homepage": "https://github.com/kieranklaassen/compound-engineering-plugin",
+      "tags": ["coding", "programming", "tutorial", "learning", "spaced-repetition", "education"],
+      "source": "./plugins/coding-tutor"
+    }
+  ]
+}

package/.github/workflows/deploy-docs.yml

@@ -0,0 +1,39 @@
+name: Deploy Documentation to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'plugins/compound-engineering/docs/**'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: 'plugins/compound-engineering/docs'
+
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

package/AGENTS.md

@@ -0,0 +1,48 @@
+# Agent Instructions
+
+This repository contains a Bun/TypeScript CLI that converts Claude Code plugins into other agent platform formats.
+
+## Working Agreement
+
+- **Branching:** Create a feature branch for any non-trivial change. If already on the correct branch for the task, keep using it; do not create additional branches or worktrees unless explicitly requested.
+- **Safety:** Do not delete or overwrite user data. Avoid destructive commands.
+- **Testing:** Run `bun test` after changes that affect parsing, conversion, or output.
+- **Output Paths:** Keep OpenCode output at `opencode.json` and `.opencode/{agents,skills,plugins}`.
+- **ASCII-first:** Use ASCII unless the file already contains Unicode.
+
+## Adding a New Target Provider (e.g., Codex)
+
+Use this checklist when introducing a new target provider:
+
+1. **Define the target entry**
+   - Add a new handler in `src/targets/index.ts` with `implemented: false` until complete.
+   - Use a dedicated writer module (e.g., `src/targets/codex.ts`).
+
+2. **Define types and mapping**
+   - Add provider-specific types under `src/types/`.
+   - Implement conversion logic in `src/converters/` (from Claude → provider).
+   - Keep mappings explicit: tools, permissions, hooks/events, model naming.
+
+3. **Wire the CLI**
+   - Ensure `convert` and `install` support `--to <provider>` and `--also`.
+   - Keep behavior consistent with OpenCode (write to a clean provider root).
+
+4. **Tests (required)**
+   - Extend fixtures in `tests/fixtures/sample-plugin`.
+   - Add spec coverage for mappings in `tests/converter.test.ts`.
+   - Add a writer test for the new provider output tree.
+   - Add a CLI test for the provider (similar to `tests/cli.test.ts`).
+
+5. **Docs**
+   - Update README with the new `--to` option and output locations.
+
+## When to Add a Provider
+
+Add a new provider when at least one of these is true:
+
+- A real user/workflow needs it now.
+- The target format is stable and documented.
+- There’s a clear mapping for tools/permissions/hooks.
+- You can write fixtures + tests that validate the mapping.
+
+Avoid adding a provider if the target spec is unstable or undocumented.

package/CLAUDE.md

@@ -0,0 +1,380 @@
+# Every Marketplace - Claude Code Plugin Marketplace
+
+This repository is a Claude Code plugin marketplace that distributes the `compound-engineering` plugin to developers building with AI-powered tools.
+
+## Repository Structure
+
+```
+every-marketplace/
+├── .claude-plugin/
+│   └── marketplace.json          # Marketplace catalog (lists available plugins)
+├── docs/                         # Documentation site (GitHub Pages)
+│   ├── index.html                # Landing page
+│   ├── css/                      # Stylesheets
+│   ├── js/                       # JavaScript
+│   └── pages/                    # Reference pages
+└── plugins/
+    └── compound-engineering/   # The actual plugin
+        ├── .claude-plugin/
+        │   └── plugin.json        # Plugin metadata
+        ├── agents/                # 24 specialized AI agents
+        ├── commands/              # 13 slash commands
+        ├── skills/                # 11 skills
+        ├── mcp-servers/           # 2 MCP servers (playwright, context7)
+        ├── README.md              # Plugin documentation
+        └── CHANGELOG.md           # Version history
+```
+
+## Philosophy: Compounding Engineering
+
+**Each unit of engineering work should make subsequent units of work easier—not harder.**
+
+When working on this repository, follow the compounding engineering process:
+
+1. **Plan** → Understand the change needed and its impact
+2. **Delegate** → Use AI tools to help with implementation
+3. **Assess** → Verify changes work as expected
+4. **Codify** → Update this CLAUDE.md with learnings
+
+## Working with This Repository
+
+### Adding a New Plugin
+
+1. Create plugin directory: `plugins/new-plugin-name/`
+2. Add plugin structure:
+   ```
+   plugins/new-plugin-name/
+   ├── .claude-plugin/plugin.json
+   ├── agents/
+   ├── commands/
+   └── README.md
+   ```
+3. Update `.claude-plugin/marketplace.json` to include the new plugin
+4. Test locally before committing
+
+### Updating the Compounding Engineering Plugin
+
+When agents, commands, or skills are added/removed, follow this checklist:
+
+#### 1. Count all components accurately
+
+```bash
+# Count agents
+ls plugins/compound-engineering/agents/*.md | wc -l
+
+# Count commands
+ls plugins/compound-engineering/commands/*.md | wc -l
+
+# Count skills
+ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l
+```
+
+#### 2. Update ALL description strings with correct counts
+
+The description appears in multiple places and must match everywhere:
+
+- [ ] `plugins/compound-engineering/.claude-plugin/plugin.json` → `description` field
+- [ ] `.claude-plugin/marketplace.json` → plugin `description` field
+- [ ] `plugins/compound-engineering/README.md` → intro paragraph
+
+Format: `"Includes X specialized agents, Y commands, and Z skill(s)."`
+
+#### 3. Update version numbers
+
+When adding new functionality, bump the version in:
+
+- [ ] `plugins/compound-engineering/.claude-plugin/plugin.json` → `version`
+- [ ] `.claude-plugin/marketplace.json` → plugin `version`
+
+#### 4. Update documentation
+
+- [ ] `plugins/compound-engineering/README.md` → list all components
+- [ ] `plugins/compound-engineering/CHANGELOG.md` → document changes
+- [ ] `CLAUDE.md` → update structure diagram if needed
+
+#### 5. Rebuild documentation site
+
+Run the release-docs command to update all documentation pages:
+
+```bash
+claude /release-docs
+```
+
+This will:
+- Update stats on the landing page
+- Regenerate reference pages (agents, commands, skills, MCP servers)
+- Update the changelog page
+- Validate all counts match actual files
+
+#### 6. Validate JSON files
+
+```bash
+cat .claude-plugin/marketplace.json | jq .
+cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
+```
+
+#### 6. Verify before committing
+
+```bash
+# Ensure counts in descriptions match actual files
+grep -o "Includes [0-9]* specialized agents" plugins/compound-engineering/.claude-plugin/plugin.json
+ls plugins/compound-engineering/agents/*.md | wc -l
+```
+
+### Marketplace.json Structure
+
+The marketplace.json follows the official Claude Code spec:
+
+```json
+{
+  "name": "marketplace-identifier",
+  "owner": {
+    "name": "Owner Name",
+    "url": "https://github.com/owner"
+  },
+  "metadata": {
+    "description": "Marketplace description",
+    "version": "1.0.0"
+  },
+  "plugins": [
+    {
+      "name": "plugin-name",
+      "description": "Plugin description",
+      "version": "1.0.0",
+      "author": { ... },
+      "homepage": "https://...",
+      "tags": ["tag1", "tag2"],
+      "source": "./plugins/plugin-name"
+    }
+  ]
+}
+```
+
+**Only include fields that are in the official spec.** Do not add custom fields like:
+
+- `downloads`, `stars`, `rating` (display-only)
+- `categories`, `featured_plugins`, `trending` (not in spec)
+- `type`, `verified`, `featured` (not in spec)
+
+### Plugin.json Structure
+
+Each plugin has its own plugin.json with detailed metadata:
+
+```json
+{
+  "name": "plugin-name",
+  "version": "1.0.0",
+  "description": "Plugin description",
+  "author": { ... },
+  "keywords": ["keyword1", "keyword2"],
+  "components": {
+    "agents": 15,
+    "commands": 6,
+    "hooks": 2
+  },
+  "agents": {
+    "category": [
+      {
+        "name": "agent-name",
+        "description": "Agent description",
+        "use_cases": ["use-case-1", "use-case-2"]
+      }
+    ]
+  },
+  "commands": {
+    "category": ["command1", "command2"]
+  }
+}
+```
+
+## Documentation Site
+
+The documentation site is at `/docs` in the repository root (for GitHub Pages). This site is built with plain HTML/CSS/JS (based on Evil Martians' LaunchKit template) and requires no build step to view.
+
+### Documentation Structure
+
+```
+docs/
+├── index.html           # Landing page with stats and philosophy
+├── css/
+│   ├── style.css        # Main styles (LaunchKit-based)
+│   └── docs.css         # Documentation-specific styles
+├── js/
+│   └── main.js          # Interactivity (theme toggle, mobile nav)
+└── pages/
+    ├── getting-started.html  # Installation and quick start
+    ├── agents.html           # All 24 agents reference
+    ├── commands.html         # All 13 commands reference
+    ├── skills.html           # All 11 skills reference
+    ├── mcp-servers.html      # MCP servers reference
+    └── changelog.html        # Version history
+```
+
+### Keeping Docs Up-to-Date
+
+**IMPORTANT:** After ANY change to agents, commands, skills, or MCP servers, run:
+
+```bash
+claude /release-docs
+```
+
+This command:
+1. Counts all current components
+2. Reads all agent/command/skill/MCP files
+3. Regenerates all reference pages
+4. Updates stats on the landing page
+5. Updates the changelog from CHANGELOG.md
+6. Validates counts match across all files
+
+### Manual Updates
+
+If you need to update docs manually:
+
+1. **Landing page stats** - Update the numbers in `docs/index.html`:
+   ```html
+   <span class="stat-number">24</span>  <!-- agents -->
+   <span class="stat-number">13</span>  <!-- commands -->
+   ```
+
+2. **Reference pages** - Each page in `docs/pages/` documents all components in that category
+
+3. **Changelog** - `docs/pages/changelog.html` mirrors `CHANGELOG.md` in HTML format
+
+### Viewing Docs Locally
+
+Since the docs are static HTML, you can view them directly:
+
+```bash
+# Open in browser
+open docs/index.html
+
+# Or start a local server
+cd docs
+python -m http.server 8000
+# Then visit http://localhost:8000
+```
+
+## Testing Changes
+
+### Test Locally
+
+1. Install the marketplace locally:
+
+   ```bash
+   claude /plugin marketplace add /Users/yourusername/every-marketplace
+   ```
+
+2. Install the plugin:
+
+   ```bash
+   claude /plugin install compound-engineering
+   ```
+
+3. Test agents and commands:
+   ```bash
+   claude /review
+   claude agent kieran-rails-reviewer "test message"
+   ```
+
+### Validate JSON
+
+Before committing, ensure JSON files are valid:
+
+```bash
+cat .claude-plugin/marketplace.json | jq .
+cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
+```
+
+## Common Tasks
+
+### Adding a New Agent
+
+1. Create `plugins/compound-engineering/agents/new-agent.md`
+2. Update plugin.json agent count and agent list
+3. Update README.md agent list
+4. Test with `claude agent new-agent "test"`
+
+### Adding a New Command
+
+1. Create `plugins/compound-engineering/commands/new-command.md`
+2. Update plugin.json command count and command list
+3. Update README.md command list
+4. Test with `claude /new-command`
+
+### Adding a New Skill
+
+1. Create skill directory: `plugins/compound-engineering/skills/skill-name/`
+2. Add skill structure:
+   ```
+   skills/skill-name/
+   ├── SKILL.md           # Skill definition with frontmatter (name, description)
+   └── scripts/           # Supporting scripts (optional)
+   ```
+3. Update plugin.json description with new skill count
+4. Update marketplace.json description with new skill count
+5. Update README.md with skill documentation
+6. Update CHANGELOG.md with the addition
+7. Test with `claude skill skill-name`
+
+**Skill file format (SKILL.md):**
+```markdown
+---
+name: skill-name
+description: Brief description of what the skill does
+---
+
+# Skill Title
+
+Detailed documentation...
+```
+
+### Updating Tags/Keywords
+
+Tags should reflect the compounding engineering philosophy:
+
+- Use: `ai-powered`, `compound-engineering`, `workflow-automation`, `knowledge-management`
+- Avoid: Framework-specific tags unless the plugin is framework-specific
+
+## Commit Conventions
+
+Follow these patterns for commit messages:
+
+- `Add [agent/command name]` - Adding new functionality
+- `Remove [agent/command name]` - Removing functionality
+- `Update [file] to [what changed]` - Updating existing files
+- `Fix [issue]` - Bug fixes
+- `Simplify [component] to [improvement]` - Refactoring
+
+Include the Claude Code footer:
+
+```
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+## Resources to search for when needing more information
+
+- [Claude Code Plugin Documentation](https://docs.claude.com/en/docs/claude-code/plugins)
+- [Plugin Marketplace Documentation](https://docs.claude.com/en/docs/claude-code/plugin-marketplaces)
+- [Plugin Reference](https://docs.claude.com/en/docs/claude-code/plugins-reference)
+
+## Key Learnings
+
+_This section captures important learnings as we work on this repository._
+
+### 2024-11-22: Added gemini-imagegen skill and fixed component counts
+
+Added the first skill to the plugin and discovered the component counts were wrong (said 15 agents, actually had 17). Created a comprehensive checklist for updating the plugin to prevent this in the future.
+
+**Learning:** Always count actual files before updating descriptions. The counts appear in multiple places (plugin.json, marketplace.json, README.md) and must all match. Use the verification commands in the checklist above.
+
+### 2024-10-09: Simplified marketplace.json to match official spec
+
+The initial marketplace.json included many custom fields (downloads, stars, rating, categories, trending) that aren't part of the Claude Code specification. We simplified to only include:
+
+- Required: `name`, `owner`, `plugins`
+- Optional: `metadata` (with description and version)
+- Plugin entries: `name`, `description`, `version`, `author`, `homepage`, `tags`, `source`
+
+**Learning:** Stick to the official spec. Custom fields may confuse users or break compatibility with future versions.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Every
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,65 @@
+# Compound Marketplace
+
+A Claude Code plugin marketplace featuring the **Compound Engineering Plugin** — tools that make each unit of engineering work easier than the last.
+
+## Install
+
+```bash
+/plugin marketplace add https://github.com/kieranklaassen/compound-engineering-plugin
+/plugin install compound-engineering
+```
+
+## OpenCode + Codex support (experimental)
+
+This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode and Codex.
+
+```bash
+# convert the compound-engineering plugin into OpenCode format
+bunx @every-env/compound-plugin install compound-engineering --to opencode
+
+# convert to Codex format
+bunx @every-env/compound-plugin install compound-engineering --to codex
+```
+
+Local dev:
+
+```bash
+bun run src/index.ts install ./plugins/compound-engineering --to opencode
+```
+
+OpenCode output is written to `~/.opencode` by default, with `opencode.json` at the root and `agents/`, `skills/`, and `plugins/` alongside it.
+Both provider targets are experimental and may change as the formats evolve.
+Codex output is written to `~/.codex/prompts` and `~/.codex/skills`, with each Claude command converted into both a prompt and a skill (the prompt instructs Codex to load the corresponding skill). Generated Codex skill descriptions are truncated to 1024 characters (Codex limit).
+
+## Workflow
+
+```
+Plan → Work → Review → Compound → Repeat
+```
+
+| Command | Purpose |
+|---------|---------|
+| `/workflows:plan` | Turn feature ideas into detailed implementation plans |
+| `/workflows:work` | Execute plans with worktrees and task tracking |
+| `/workflows:review` | Multi-agent code review before merging |
+| `/workflows:compound` | Document learnings to make future work easier |
+
+Each cycle compounds: plans inform future plans, reviews catch more issues, patterns get documented.
+
+## Philosophy
+
+**Each unit of engineering work should make subsequent units easier—not harder.**
+
+Traditional development accumulates technical debt. Every feature adds complexity. The codebase becomes harder to work with over time.
+
+Compound engineering inverts this. 80% is in planning and review, 20% is in execution:
+- Plan thoroughly before writing code
+- Review to catch issues and capture learnings
+- Codify knowledge so it's reusable
+- Keep quality high so future changes are easy
+
+## Learn More
+
+- [Full component reference](plugins/compound-engineering/README.md) - all agents, commands, skills
+- [Compound engineering: how Every codes with agents](https://every.to/chain-of-thought/compound-engineering-how-every-codes-with-agents)
+- [The story behind compounding engineering](https://every.to/source-code/my-ai-had-already-fixed-the-code-before-i-saw-it)

package/bun.lock

@@ -0,0 +1,30 @@
+{
+  "lockfileVersion": 1,
+  "workspaces": {
+    "": {
+      "name": "compound-plugin",
+      "dependencies": {
+        "citty": "^0.1.6",
+        "js-yaml": "^4.1.0",
+      },
+      "devDependencies": {
+        "bun-types": "^1.0.0",
+      },
+    },
+  },
+  "packages": {
+    "@types/node": ["@types/node@25.0.9", "", { "dependencies": { "undici-types": "~7.16.0" } }, "sha512-/rpCXHlCWeqClNBwUhDcusJxXYDjZTyE8v5oTO7WbL8eij2nKhUeU89/6xgjU7N4/Vh3He0BtyhJdQbDyhiXAw=="],
+
+    "argparse": ["argparse@2.0.1", "", {}, "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q=="],
+
+    "bun-types": ["bun-types@1.3.6", "", { "dependencies": { "@types/node": "*" } }, "sha512-OlFwHcnNV99r//9v5IIOgQ9Uk37gZqrNMCcqEaExdkVq3Avwqok1bJFmvGMCkCE0FqzdY8VMOZpfpR3lwI+CsQ=="],
+
+    "citty": ["citty@0.1.6", "", { "dependencies": { "consola": "^3.2.3" } }, "sha512-tskPPKEs8D2KPafUypv2gxwJP8h/OaJmC82QQGGDQcHvXX43xF2VDACcJVmZ0EuSxkpO9Kc4MlrA3q0+FG58AQ=="],
+
+    "consola": ["consola@3.4.2", "", {}, "sha512-5IKcdX0nnYavi6G7TtOhwkYzyjfJlatbjMjuLSfE2kYT5pMDOilZ4OvMhi637CcDICTmz3wARPoyhqyX1Y+XvA=="],
+
+    "js-yaml": ["js-yaml@4.1.1", "", { "dependencies": { "argparse": "^2.0.1" }, "bin": { "js-yaml": "bin/js-yaml.js" } }, "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA=="],
+
+    "undici-types": ["undici-types@7.16.0", "", {}, "sha512-Zz+aZWSj8LE6zoxD+xrjh4VfkIG8Ya6LvYkZqtUQGJPZjYl53ypCaUwWqo7eI0x66KBGeRo+mlBEkMSeSZ38Nw=="],
+  }
+}