feat(ui): shared libs/ui design system — tokens, theme, AppShell (U0.1-U0.3)#364
Conversation
…hell (U0.1-U0.3) First slice of Track D (see docs/strategy/roadmap.md). Adds the @auto-code/ui workspace package (libs/* glob), to be consumed by both the Electron desktop and the web app: - tokens/tokens.css: design tokens ported 1:1 from .lazyweb/_desktop-tokens.css (light + [data-theme=dark]); variables only, so importing it is non-breaking. - theme/ThemeProvider.tsx: ThemeProvider + useTheme(), sets data-theme on <html>, resolves system via prefers-color-scheme, persists override in localStorage (works in Electron + web). - shell/AppShell.tsx: layout primitive (sidebar/topbar/main/statusbar slots). Self-contained and presentational (transport-agnostic); apps are NOT wired yet — that and Storybook are follow-up slices. Verified: tsc --noEmit clean; JSON valid. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 24 minutes and 5 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (20)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…egration) Add @auto-code/ui as a workspace dependency of apps/frontend and apps/web-frontend, sync package-lock.json, and import the design tokens once per app entry (import '@auto-code/ui/tokens.css'). Tokens are variables only, so this is non-breaking; it validates that the shared workspace package resolves and builds in both targets. (Also drops the unused @types/react-dom devDep from libs/ui.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…/ui (U0.4) Presentational, data-driven Sidebar mirroring the .lazyweb two-column variant: a 48px icon rail of sections + a context column listing the active section's items (with optional shortcut/badge). nav-config.ts defines SidebarSection/SidebarItem; the app supplies localized labels, icon nodes, and selection handlers. Active section/item highlighted; collapse hides the context column. Verified: libs/ui tsc --noEmit clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
… (U1) Introduces the ports-and-adapters data seam for libs/ui: - client/AutoCodeClient: the AutoCodeClient port (listTasks + optional subscribeTasks), AutoCodeClientProvider/useAutoCodeClient (Context injection), and a shared useTasks() hook (loading/error/reload + live updates). - client/types: UiTask — the lowest-common task shape each app maps into via its adapter. - screens/KanbanBoard: presentational board (status columns + cards, keyboard-accessible), data-agnostic; mirrors the .lazyweb kanban layout. Apps stay decoupled: desktop provides an IPC adapter, web a REST/WS adapter (next slice). Verified: libs/ui tsc --noEmit clean. Runtime validation (Storybook/app adapter) follows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
1 participant
Track D — U0 foundation + app integration (see docs/strategy/roadmap.md, PR #363).
Adds the
@auto-code/uiworkspace package and wires it into both apps to validate the shared-component approach end-to-end.libs/ui (
@auto-code/ui):tokens/tokens.css— design tokens ported 1:1 from.lazyweb/_desktop-tokens.css(light +[data-theme="dark"]), variables only.theme/ThemeProvider.tsx—ThemeProvider+useTheme()(setsdata-themeon<html>, resolvessystem, persists override).shell/AppShell.tsx— layout primitive (sidebar/topbar/main/statusbar slots).Integration:
@auto-code/uiadded as a workspace dependency ofapps/frontend+apps/web-frontend;package-lock.jsonsynced.@auto-code/ui/tokens.css(variables only → non-breaking).Presentational and transport-agnostic;
AutoCodeClient(ports/adapters) arrives at the Kanban pilot (U1). Follow-ups: in-app use of ThemeProvider/AppShell, new Sidebar (U0.4), Storybook (U0.5).Verified:
libs/uitsc --noEmitclean in isolation; CI builds both apps with the workspace package.🤖 Generated with Claude Code