app-quality-patterns

# App Quality Patterns (QP library) > **Style:** Mode-B-lite router. The patterns live in `references/<category>.md` — load ONLY the categories the feature touches. Each pattern: ID · Trigger · Requirement · Verify (copy-ready smoke recipe) · Anti-pattern. ## Purpose Cross-project behavioral "definition of done" requirements that LLM-built apps repeatedly miss. They are not stack guidance (CLI skills own HOW) and not process rules (FLOW_RULES owns those) — they are WHAT must be true of the built feature. Distilled from recurring consumer-project defects; the library grows one table row at a time. ## Category index (load on trigger match) | Category | File | Load when the feature involves | IDs | |---|---|---|---| | State & navigation | `references/state-and-navigation.md` | views with filters / search / sort / pagination / tabs / reports / deep links / browser navigation | QP-01..QP-04 | | Data integrity | `references/data-integrity.md` | create / update / delete flows, related records, caching, retries | QP-10..QP-14 | | UI polish | `references/ui-polish.md` | any user-facing UI: lists, forms, dropdowns, dates | QP-20..QP-24 | ## Integration contract (how patterns reach the lifecycle) | Phase | What happens | Owner | |---|---|---| | Specify | `requirements-specification` scans this index; every matching pattern becomes a spec **AC citing the QP ID** (e.g., "AC4 — filter/report state encoded in URL; refresh restores exact view (QP-01)"). The AC then flows through tasks...