UI And Design Changes

Read First

• /ops/style-design.md
• /ops/requirements.md
• Relevant ADRs for the component or behavior being changed.

Rules

• No silent UX or visual design changes.
• Document IA, token, component, or behavior changes in /ops or an ADR before implementation.
• CSS lives in src/styles/NN-<concern>.css (the number is the cascade order; tokens are in 01-base.css). Edit the part that owns the component; a new part needs a number that keeps the cascade right.
• Use existing CSS tokens and component patterns.
• JavaScript must remain ESM.
• Icons in src/assets/icons/ must have viewBox and inherit currentColor.
• Preserve accessibility: focus states, labels, keyboard behavior, and reduced-motion behavior.

Checks

• npm run check:assets
• npm run build
• npm run test:playwright

Pipeline

Check the result on localhost with preview-site, then release-check — layout and client JS changes need npm run test:playwright.

Design rules that outlive the change belong in /ops/style-design.md or an ADR via ia-nav-adr.