The canonicalization rules and the clear duplicate families found during the front-end inventory.
8a17b3e1-1200-4d24-9a71-000000000012
Component Reference
Rule 01 — Reuse Before Adding
Before adding CSS, search this page by friendly name, GUID, class, and purpose. Use the canonical class unchanged when it already fits.
1
Search → Reference → Reuse
Friendly names support conversation. GUIDs support exact links. Classes support implementation.
Friendly Name
Rule 01 — Reuse Before Adding
GUID
8a17b3e1-1201-4d24-9a71-000000001201
Use in
Every Future Front-End Task
Show Class & CSS
Class / ReferenceNo new classCanonical CSS
/* Search /styles first. Add a variant only when behavior or meaning is materially different. */
Source: app/styles/canonical.css. Existing shared components are identified when they remain the live implementation.
Component Reference
Map 01 — Button Families
Several route-level button names currently describe the same visual jobs. The guide intentionally exposes one button per job; these legacy selectors are migration aliases, not separate components.