Frontend Design

Route user-visible frontend work through the smallest design path that protects the product, then verify the affected interface honestly.

Route Before Loading References

1. Set the authority boundary:
   • Review: inspect and report findings. Do not edit files or turn the review into a redesign unless the user asks.
   • Change: implement the requested local change and non-destructive checks.
2. For a change, choose its design intensity:
   • Preserve: a bug fix, state change, refactor, or maintenance task whose rendered language should remain stable.
   • Adapt: a component, form, content region, or bounded layout change that should extend the existing product language.
   • Direct: a new surface, new product, or substantial redesign that needs an explicit direction.

When the boundary is unclear, choose the lowest intensity that fully covers the authorized change. Escalate only when the request or inspected product evidence requires a new visual language, a substantial hierarchy change, or a redesign. Review depth follows the reviewed scope; it is not a fourth intensity level.

Preserve Fast Path

Do not load references for Preserve work.