Align UI to Design System

Core outcome

Evaluate whether one selected UI surface belongs to the design system that actually exists in its repository without flattening justified product character. Return a bounded, evidence-backed review before changing code unless the user already authorized fixes.

Set the boundary and mode

1. Read the nearest repository instructions and inspect uncommitted work.
2. Name the component or surface under review, its direct dependencies, and its user-facing job. Do not silently expand to the whole repository.
3. Select the mode from the request:
   • Review: Inspect and recommend only. This is the default for review, audit, or “what is off?” requests.
   • Fix: Apply findings the user explicitly authorized. A request to align, normalize, or fix the bounded surface authorizes relevant edits, but not a broader system refactor.
4. Preserve the selected product direction. If the user still wants alternatives, use code-native-ui-ideation instead.

Establish repository authority

Use this evidence order and note conflicts rather than inventing certainty: