Engineering practices are becoming installable

Addy Osmani packaged Google's engineering culture into agent-skills: 24 skills across a 6-phase lifecycle, with eight slash commands (/spec, /plan, /build, /test, /review, /webperf, /code-simplify, /ship) that map to the full development loop.

Each skill has the same anatomy: process steps, anti-rationalization tables (rebuttals for "I'll add tests later"), red flags, and verification gates. The engineering principles are baked in — Hyrum's Law for API design, Chesterton's Fence for simplification, the Beyoncé Rule for testing ("if you liked it, you shoulda put a test on it"), 80/15/5 test pyramid ratios.

What makes it interesting isn't the content — most experienced engineers know these practices. It's the format. When engineering culture is encoded as structured markdown, the floor rises. Junior developers running these skills get senior-level guardrails without senior-level experience. The agent doesn't skip tests because it's in a hurry. It doesn't rationalize away code review.

Works across Claude Code, Cursor, Gemini CLI, and anything that accepts markdown.