What problem does it solve?
This Skill eliminates the risk of inconsistent, inaccessible, or poorly structured frontend architectures that lead to technical debt, poor user experience, and non-compliant interfaces. It extends the base software-architect skill with frontend-specific guardrails, ensuring UI components are fully decoupled from domain logic, UX journeys include explicit error paths and state preservation, and WCAG 2.2 AA accessibility requirements are baked into design rather than added as an afterthought.
Core Features & Use Cases
- Component Architecture Pattern Selection: Choose and document the appropriate pattern (Atomic Design, Feature-Sliced Design, or Smart/Dumb) for your project, with clear rationale and enforcement of domain logic separation from UI components.
- UX Journey Design for Process-Driven Flows: Map end-to-end user journeys for common frontend workflows (document upload, pipeline kick-off, results review) with explicit entry/exit states, error paths, progress indicators, and backward navigation state preservation.
- Data Visualisation Strategy: Select chart types aligned to user questions, enforce a single chart library per application, and design real-time data update architectures with batching and reconnection strategies.
- Design System and ol_ui_library Alignment: Audit existing component libraries to avoid redundant custom component builds, follow Atomic Design hierarchy for new library contributions, and enforce design token usage for consistent theming.
- Accessibility Architecture: Embed WCAG 2.2 AA and POUR framework requirements into the design phase, including keyboard navigation paths, colour contrast rules, and screen reader compatibility for all user-facing surfaces.
- Use Case: For a new document processing product, use this Skill to define the component architecture, map the upload and results review journeys, select a chart library for pipeline metrics, and ensure all interfaces meet accessibility standards before implementation begins.
Quick Start
Use the ui-architect skill to design the frontend architecture for the new customer onboarding portal, including component pattern selection, upload journey mapping, and WCAG 2.2 AA accessibility requirements.