feat(css): add .alert* + layout-helper component classes (LC-555) #524
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/LC-555-alert-classes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
LC-UI-02: shared
.alert*+ layout-helper component classesPhase 1 foundation ticket LC-555 (epic LC-553). Adds the missing shared component vocabulary so utility/admin pages can stop hand-rolling
bg-*-50alert boxes and ad-hoc flex clusters. Pure@layer componentsadditions inassets/tailwind.css.What changed
.alert(bordered soft-surface callout, icon-friendly flex layout) +.alert-success,.alert-warning,.alert-danger,.alert-info. All colors are tokens, so they recolor per theme.-surface-contentforegrounds.text-danger- there is deliberately no--danger-surface-contenttoken (LC-215).--accent-bordertoken exists; a neutral note reads cleanly in all four themes)..lc-toolbar(quiet inset control strip for filter/action bars),.lc-action-row(wrapping right-aligned button cluster for card/form footers),.lc-empty-wrap(centers an empty state within a card/section).Why it is safe
just build-csspasses, which validates every@applyresolves to a real utility (an invalid one would error the build).tailwind-built.cssis unchanged: Tailwind purges these component classes until a template references them, so this is a source-only vocabulary addition (same posture as the phase-1b tokens). The first consuming template (LC-UI-03/04/06/08) rebuilds and emits them, per the repo's existing.btn/.card/.inputconvention.Scope
.alert*to existing pages (replacing the raw boxes) happens in the migration tickets..lc-page-*width utilities are the sibling foundation ticket LC-562.🤖 Generated with Claude Code
https://claude.ai/code/session_011jXpZXXwpB36MvTr6JrGXN