One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-babysit-pr/SKILL.md
Babysits an open GitHub PR until merge-ready. Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-bakeoff/SKILL.md
Develop independent competing solutions to a defined brief, compare them, and synthesize a winning approach. Use when choosing well requires developing alternatives beyond their current form. Use ce-pov to judge developed material and ce-ideate to discover opportunities.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-brainstorm/SKILL.md
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.
Steady36 mentions in 2 weeks
6 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-commit/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-debug/SKILL.md
Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-doc-review/SKILL.md
Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
Often used withce-explaince-handoffce-prototype
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-dogfood/SKILL.md
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.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-explain/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-ideate/SKILL.md
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).
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-optimize/SKILL.md
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.
Often used withce-explaince-handoffce-prototype
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-plan/SKILL.md
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.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-pov/SKILL.md
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-doc-review for findings review.
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-resolve-pr-feedback/SKILL.md
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 exists.
Often used withce-explaince-handoffce-prototype
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-setup/SKILL.md
Check Compound Engineering health and repo-local config, or scaffold a Compound Pack with `pack:<id>`.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-simplify-code/SKILL.md
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.
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/ce-strategy/SKILL.md
Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.
Steady36 mentions in 2 weeks
6 projects use a version of this
Often used withce-explaince-handoffce-prototype
EveryIncSkillEveryInc/compounding-engineering-plugin/skills/lfg/SKILL.md
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-commit-push-pr for work the user reviews step by step.
Steady36 mentions in 2 weeks
10 projects use a version of this
Often used withce-explaince-handoffce-prototype
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
