You're offline — showing cached data

MC-5018

Create MC design system primitives
2026-06-13 07:37:45 SAST
Home Board MC-5018

Create MC design system primitives

Create a lightweight shadcn-like design system for Mission Control's actual Flask/Jinja/vanilla-JS stack. Goal: - Stop MC UI workers from freelancing page-specific HTML/CSS. - ...
State Done Next Action Closed Owner Luci Runtime Closed Age 22h ago
MC-5018
Ticket is done; runtime is closed. · profile claude_opus_1m_medium

Description

MC-5018
Create a lightweight shadcn-like design system for Mission Control's actual Flask/Jinja/vanilla-JS stack. Goal: - Stop MC UI workers from freelancing page-specific HTML/CSS. - Provide approved primitives that future UI tickets must compose. - Improve visual consistency and reduce repeated design QA failures. Recommended implementation: 1. Add shared MC design tokens CSS for color, typography, spacing, radius, shadow, focus, and status semantics. 2. Add reusable Jinja macros/partials for primitives: - button - card - badge/status chip - page header - toolbar/action group - form field/input/select - modal/drawer shell - empty state - ticket/action card 3. Add a /design-system or equivalent preview route showing every primitive in desktop and mobile-friendly states. 4. Migrate one real MC surface slice (Board card or Ticket detail header/action panel) to prove the primitives work in production context. 5. Document the rule: future MC UI work should use these primitives unless an exception is documented. Design direction: - Linear x Vercel x Sentry x Raycast. - Clean operational SaaS, not generic Bootstrap/admin dashboard. - Dense but readable, strong hierarchy, compact actions, polished status chips, mobile-first proof. Required skills/gates for worker: - Load dev-loop before source edits. - Use creative/popular-web-designs for Linear/Vercel/Sentry/Raycast reference language. - Use creative/worker-design-gate before implementation. - Use devops/mc-design-qa for final evidence. Acceptance criteria: - Shared tokens/primitives exist and are used by at least one real MC page slice. - Preview route renders all primitives and states. - Desktop and 390px mobile screenshots attached for preview route and migrated real slice. - No low-contrast buttons/chips, single-letter wrapping, inaccessible focus states, or page-level mobile overflow. - Relevant regression/browser checks pass. - Final ticket comment includes evidence paths and PASS/FAIL design verdict. Routing: - MC ticket is source of truth. - Implementation may be routed through the internal Kanban/Codex builder, but not as a direct untracked Kanban-only task. Expected check-in: within 2 hours of worker pickup with screenshot baseline and implementation plan.

Activity

done
Luci is working...
Live
No activity yet
Help