pattern-engineer-non-functionallisted

# pattern-engineer-non-functional Non-functional guardrails for production-code authoring — the ISO-25010 / ISTQB quality characteristics (performance efficiency, reliability, scalability, resource utilization) that the functional happy path never exercises. Like the other engineer pattern skills, this is a quiet reference catalogue: the agent reads it to know which bounds to build in, *not* a checklist to walk through with the user. Reviewer feedback (`pattern-reviewer-non-functional`) is the user-facing channel; this skill exists so most findings never happen. > **This skill is spec-gated by design.** Most projects that install the plugin are early-stage and declare *no* non-functional acceptance criteria — and that is fine. You always build in the **thin floor** below (the bounds that are latent correctness bugs the moment real data arrives), but you do NOT speculatively add load tests, caching layers, or capacity engineering for a requirement the slice never stated. The heavier targets are pulled into scope only when the slice body declares a non-functional AC (a latency / throughput / capacity / availability clause). Build to the spec — no more, no less. ## When to activate - Writing or editing production code that: issues a DB query, serves a list/collection endpoint, accepts a request body or file upload, makes an outbound HTTP/DB call, runs inside an async handler, processes a queue/worker message, renders a large collection in the UI, or implements a behavior who