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/compound-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/compound-engineering-plugin/skills/ce-product-pulse/SKILL.md
Generate time-windowed product pulse reports from configured signals.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-promote/SKILL.md
Draft launch or promotion copy for a shipped feature.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-proof/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-prototype/SKILL.md
Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not implementing the real thing.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-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.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-retune/SKILL.md
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 one.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-riffrec-feedback-analysis/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-setup/SKILL.md
Check Compound Engineering health and repo-local config, scaffold a Compound Pack with `pack:<id>`, or draft or refresh coding standards and review docs with `standards`.
EveryIncSkillEveryInc/compound-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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-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.
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-sweep/SKILL.md
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.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncReads credentialsSkillEveryInc/compound-engineering-plugin/skills/ce-test-browser/SKILL.md
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.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-test-xcode/SKILL.md
Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-work/SKILL.md
Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.
Steady36 mentions in 2 weeks
7 projects use a version of this
EveryIncSkillEveryInc/compound-engineering-plugin/skills/ce-worktree/SKILL.md
Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an existing ref.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillEveryInc/compound-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.
EveryIncSkillEveryInc/compound-engineering-plugin/skills/wtf/SKILL.md
Explain the last message, or a supplied file, link, or passage, in plain language a person follows on the first read. Use when the user invokes wtf because they did not follow something. Use ce-explain to investigate how or why code works, and ce-noslop to rewrite prose.
Steady36 mentions in 2 weeks
16 projects use a version of this
EveryIncAGENTS.mdEveryInc/compounding-engineering-plugin/AGENTS.md
This repository is the root of the compound-engineering coding-agent plugin and the marketplace/catalog metadata used to distribute it. It also contains: - the Bun/TypeScript CLI that converts Claude Code plugins into other agent platform formats - shared release and metadata infrastructure for the CLI, marketplace, and plugin AGENTS.md is the canonical repo instruction file. Root CLAUDE.md is a symlink to AGENTS.md so Claude Code and other tools that look for CLAUDE.md still find it at the expected path. Keep that…
EveryIncCLAUDE.mdEveryInc/compounding-engineering-plugin/CLAUDE.md
No summary in the file. Open it to read it.
169 projects use a version of this
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.
