What problem does it solve?
The QJudge UI Carbon Owner centralizes Carbon-first styling rules, Storybook synchronization, and overflow/layout stability to prevent inconsistent component visuals, broken stories, and unexpected dual-scroll or clipping behavior across the frontend.
Core Features & Use Cases
- Carbon-first enforcement: mandate token-driven spacing, typography, and colors while preventing direct overrides of Carbon internals.
- Storybook & registry ownership: require colocated stories, minimal meaningful story sets, and registry updates alongside component changes.
- Overflow and layout stability: provide proven patterns (full-bleed admin shell, split pane, header/body) and acceptance criteria to ensure a single vertical scroll owner and stable clipping across themes.
- Checks and handoffs: reference a style-check command and define clear cross-skill handoffs for architecture and CI/release responsibilities.
Quick Start
Review the Carbon policy and overflow playbook, update the component stories and registry in the same change, and run the style check before creating a pull request.