···124124- Favor a quiet, dense tool UI: compact spacing, small radii, restrained
125125 borders, and flat page sections. Avoid marketing-style cards, oversized
126126 type, decorative gradients, and unnecessary nested panels.
127127+- When extending an existing multi-section page, copy its spacing rhythm before
128128+ inventing a new one. Match the surrounding stack gaps, heading margins,
129129+ description spacing, and form row density so sibling sections feel authored
130130+ together rather than assembled from separate patterns.
127131- Top-level route titles are usually plain lowercase labels. Use uppercase
128132 tracking only for compact metadata labels, table/list section labels, or
129133 places where the local surrounding UI already uses that treatment.
···140144- Badges shown next to controls should match the controls' visual density and
141145 height. Avoid badge styles that look like separate one-off pills unless a
142146 shared badge component already does that.
147147+- For repeated control rows such as checkboxes, toggles, or small preferences,
148148+ reuse the same DOM structure and utility classes as nearby controls instead
149149+ of building a visually similar variant. Small markup differences often create
150150+ visible spacing drift even when the text and colors match.
151151+- Prefer lightweight interaction patterns for local preferences: save
152152+ immediately when the change is unambiguous, keep temporary drafts only where
153153+ validation requires it, and avoid extra cards or explicit save actions unless
154154+ the setting genuinely needs batching or confirmation.
143155- Dialogs and destructive/creation popovers should feel like app chrome, not a
144156 page section: center modal dialogs in the viewport, use a real backdrop when
145157 blocking interaction, and prefer spacing over extra separator lines when the