← ClaudeAtlas

develop-like-everylisted

Develop the way Every (the company) does: compound engineering, plan-first 80/20, boring Rails under aggressive AI leverage. Use when the user wants Every-style engineering decisions, code review in Every's voice, or asks to "develop like Every". Profiled 2026-07-11 from public sources.
marcusrbrown/dev-like · ★ 2 · AI & Automation · score 71
Install: claude install-skill marcusrbrown/dev-like
# Develop like Every > Profiled as of 2026-07-11 · consent tier: self-published · full bibliography in [references/sources.md](references/sources.md). Cultures drift — if this is more than ~6 months old, re-run `/dev-like every` to refresh. ## Core principle "Each unit of engineering work should make subsequent units easier — not harder" [[CEP README]](https://github.com/EveryInc/compound-engineering-plugin). Roughly 80% of effort goes to planning and review, 20% to execution [[guide]](https://every.to/guides/compound-engineering). ## Principles 1. Plan-first, 80/20 — most effort before code [[guide]](https://every.to/guides/compound-engineering) 2. Compound every unit of work into reusable repo knowledge [[CEP]](https://github.com/EveryInc/compound-engineering-plugin) 3. Simplify as an explicit pipeline step, not an afterthought [[CEP]](https://github.com/EveryInc/compound-engineering-plugin) 4. One person + agents ≈ a team; design workflows for that ratio [[podcast transcript]](https://every.to/podcast/transcript-how-two-engineers-ship-like-a-team-of-15-with-ai-agents) 5. Boring stack, radical process [[SF Ruby keynote]](https://sfruby.com/) 6. Agent-native parity — if a human can run tests, read logs, or open a PR, the agent should be able to as well [[guide]](https://every.to/guides/compound-engineering) 7. Safety nets over gatekeeping — trust comes from tests, automated review, monitoring, and rollback, not line-by-line babysitting [[guide]](https://every.to/guides/