What problem does it solve?
This Skill eliminates the risk of inconsistent, non-performant, and inaccessible React/TypeScript frontend code by providing standardized implementation patterns, mandatory quality gates, and alignment with the ol_ui_library component catalogue, reducing rework and ensuring all UI deliverables meet WCAG 2.2 AA accessibility standards and Core Web Vitals performance targets.
Core Features & Use Cases
- Standardized Frontend Conventions: Extends the javascript-data-engineer skill with React/TypeScript-specific rules including SOLID component architecture, state co-location guidelines, Atomic Design construction order, and strict naming conventions to ensure consistency across all UI work.
- Mandatory Quality Gates: Enforces pre-ship validation for type checking, linting (including accessibility and React hooks rules), unit and end-to-end testing, Storybook compilation, and Lighthouse performance audits to catch issues before code is merged.
- Pre-Built UX Journey Patterns: Provides implementation templates for high-frequency OntoLedgy workflows including document upload, multi-step pipeline wizards, real-time monitoring dashboards, and results review interfaces, plus data visualisation patterns for Recharts and ECharts with real-time data support.
- ol_ui_library Alignment: Enforces reuse of existing library components to avoid duplication, with clear contribution guidelines for new general-purpose components that meet accessibility and design token standards.
- Use Case: A team building a pipeline monitoring dashboard can use this skill to implement accessible, performant React components that reuse existing ol_ui_library atoms, pass all quality gates, and include real-time log streaming and interactive charts without introducing architectural debt.
Quick Start
Use the ui-engineer skill to implement a React document upload component that reuses the ol_ui_library FileDropZone organism, includes React Testing Library unit tests, and passes all accessibility and performance quality gates.