Conversation
Brings version bump (0.1.2) and CHANGELOG update back to the integration branch after the v0.1.2 release.
…t classes Inline Tailwind utility chains scattered across 25 components made the HTML hard to read and impossible to maintain consistently. Every button, card header, and badge had its own hand-rolled utility soup, so visual changes required hunting through dozens of files and there was no single source of truth for what a "button" or "card" looked like. Extract all recurring patterns into a BEM component library in app.css using @apply, CSS nesting (Lightning CSS via Tailwind v4), and plain CSS custom properties. No SCSS was introduced — Tailwind v4 with the vite plugin handles nesting natively, avoiding SCSS/PostCSS import conflicts. New BEM blocks: - .badge (--running, --paused, --success, --error, --warning, --info, --primary) — replaces badge-running, badge-paused, etc. - .btn (--sm, --md, --icon) × (--primary, --secondary, --ghost, --success, --danger) — single definition for all button variants - .card, .card__header, .card__header-title, .card__body - .form__label, .form__input, .form__textarea, .form__select - .nav-tab (--main, --sub, --active) — replaces .main-tab and .mem-tab - .mobile-menu, .mobile-menu--open, .mobile-menu__header, .mobile-menu__nav, .mobile-menu__nav-item (--active), .mobile-menu-overlay (--open) — replaces .mobile-nav-item + .open - .alert (--success, --error, --warning, --info) - .chat-bubble (--user, --assistant, --system) - .token-health (--good, --warning, --expired) - .pwa-banner, .pwa-banner__message, .pwa-banner__actions, .pwa-banner__install-btn, .pwa-banner__dismiss-btn - .kg-canvas, .custom-scroll, .tab-scroll, .animate-subtle-pulse All 25 component files updated to use the new class names. Inline utility chains retained only where they express layout context unique to that component rather than a reusable widget appearance. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
app.csswith a full BEM component library using Tailwind v4@apply—.badge,.btn,.card,.form__*,.nav-tab,.mobile-menu,.alert,.chat-bubble,.token-health,.pwa-banner, and moreTest plan
npm run buildinsrc/dashboard/frontend/) succeeds without errors🤖 Generated with Claude Code