プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。プロトタイプ · 30分ごとに更新
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

compound-engineering-plugin Skill

リポジトリ ↗

作者:EveryInc★ 26,123 (whole repo)38 個の skill

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 38 skills

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category コーディング
Maker’s original description
Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more
作者向け:README にバッジを付ける

作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/everyinc-compound-engineering-plugin.svg)](https://mcp.popnx.com/en/skills/everyinc-compound-engineering-plugin)

一緒に使える

同じ作業で AI をサービスにつなぐ MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

作者:morluto広く使われている↓ 38.9万/週★ 46.4万5 日前更新

MCP · サービスにつなぐパソコンで動く

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

作者:fallow-rs広く使われている↓ 244.1万/週★ 5374今日更新

MCP · サービスにつなぐパソコンで動く

似た Skill

同じ種類の作業。Skill 一覧と同じ並び

似たものと比べる
これ
compound-engineering-plugin
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者EveryIncmorlutomultica-aiGraphify-Labsharry0703
Skill 数381111
GitHub スター26,123463,670233,682148,887143,987
最終コード更新2026年11月14日2026年11月17日2026年4月20日2026年11月17日2026年11月16日
ライセンスMITMIT–Apache-2.0MIT

EveryInc による 38 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

This set has 38 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below

Showing 30 of 38 See all on GitHub

  • ce-babysit-pr

    Babysits an open GitHub PR until merge-ready, first judging whether an old PR still belongs. Use when asked to watch a PR over time or update an old one — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.

  • ce-brainstorm

    Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

  • ce-code-review

    Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

  • ce-commit

    Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

  • ce-commit-push-pr

    Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.

  • ce-compound

    Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a rev…

  • ce-compound-refresh

    Old name for refreshing learnings, which now lives in `ce-compound`. Use only when a prompt or standing instruction names `ce-compound-refresh`; use `ce-compound` for every other learnings audit.

  • ce-debug

    Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

  • ce-doc-review

    Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

  • ce-dogfood

    Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

  • ce-explain

    Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.

  • ce-handoff

    Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.

  • ce-ideate

    Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

  • ce-optimize

    Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.

  • ce-plan

    Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

  • ce-polish

    Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.

  • ce-pov

    Judge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach set. Use for an oracle panel to consult other models and reconcile their opinions. Use ce-explain for understanding and ce…

  • ce-product-pulse

    Generate time-windowed product pulse reports from configured signals.

  • ce-promote

    Draft launch or promotion copy for a shipped feature.

  • ce-proof

    Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

  • ce-resolve-pr-feedback

    Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified. Use when addressing feedback already left on a PR, preparing local fixes for a caller to publish, or completing a saved feedback batch. Use ce-code-review for reviewing code before feedback…

  • ce-retune

    Retune a skill corpus for a new model, measurement-first: mine the run archive for a baseline, establish a noise floor, audit the corpus adversarially, then cut in measured passes until a pre-registered bar clears. Requires a benchmark harness that can A/B two builds of the corpus; refuses without…

  • ce-riffrec-feedback-analysis

    Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.

  • ce-setup

    Check Compound Engineering's tools and repo config and fix what it finds, scaffold a Compound Pack with `pack: `, or draft and refresh coding standards and review docs from pull request history. Use when setting up or diagnosing Compound Engineering, or when creating or updating CODING_STANDARDS.md…

  • ce-simplify-code

    Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; use ce-debug for bugs.

  • ce-strategy

    Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

  • ce-sweep

    Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.

  • ce-test-browser

    Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.

  • ce-test-xcode

    Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

  • lfg

    Take a request all the way to done, hands-off, through the right Compound Engineering skills. A code change ends as an open pull request, pushed without stopping. Use only when the user explicitly asks for autonomous end-to-end work or invokes lfg directly. Use ce-plan, ce-work, ce-debug, or ce-com…

Skill と MCP の違い

MCP = 手

AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。

Skill = 手順書

作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。

重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。

使えるアプリ

Claude CodeCodexCursorGemini CLIGitHub CopilotOpenCode

提供元の README と repo のフォルダから判断

インストール

Pick a skill first

This repo has 38 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

The maker’s command installs the whole set of 38
/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering@compound-engineering-plugin

提供元の README から引用。提供元のコードをダウンロードして実行します

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

ログインして投稿

GitHub の情報

GitHub スター
26,123
Stars are for the whole repo, not each skill
提供元
EveryInc
ライセンス
MIT
最終コード更新
2026年11月14日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
30
トピック
compound, engineering