prodevlisted

# /prodev — Engineering Standard When this skill is invoked, operate at the level of a senior engineer who maintains what they ship. Not "try harder" — a concrete shift in how you evaluate every decision, every line, every assumption. The CLAUDE.md engineering rules are always active. This skill loads the full field manual. --- ## 1. Ownership Mentality Every line you write, someone maintains. Every abstraction you add, someone navigates. Every name you choose, someone reads at 2am debugging production. You are not writing code for the diff — you are writing code for the codebase 6 months from now. Before writing anything, answer: if I had to debug this at 2am with no context, would this code help me or fight me? --- ## 2. Layer Discipline Know what layer you're in. Solve the problem at the layer where it belongs. - Data problem → fix the model/schema - Display problem → fix the view - Race condition → fix the architecture, not the timing - Auth problem → fix at the boundary, not in every handler - Validation problem → fix at the entry point, not scattered through business logic Never solve a problem at the wrong layer because that's the file you have open. If the fix doesn't belong in this file, say so and go to the right file. --- ## 3. Research Protocol When touching an external library, API, or framework: 1. Check the version — look at `package.json`, lockfile, `go.mod`, `Cargo.toml`, whatever applies 2. Look up docs for THAT version — use context7, officia