What problem does it solve? Working on the HFS web UI requires knowing a strict architecture: Askama templates, htmx fragments, vendored assets, no SPA frameworks, and enforced design rules. This Skill gives an AI the operational knowledge to modify the helios-ui crate correctly without violating its conventions. ## Core Features & Use Cases - Route and handler guidance: Documents every /ui route, the full-page vs htmx-fragment pattern, and how handlers stay thin by delegating to helios-rest and helios-persistence. - Design system rules: Explains the layered app.css vocabulary, canonical component classes, and the Playwright/axe-core test gates that fail on undefined classes or accessibility violations. - Testing workflow: Covers the inner Rust test ring (cargo test -p helios-ui) and the outer Playwright e2e ring, including the no-JS and WCAG 2.2 AA requirements. - Use Case: Ask the AI to add a new htmx-driven page to the FHIR server UI; it will scaffold the template from _scaffold.html, register the route, reuse canonical CSS classes, and add the route to the e2e route list. ## Quick Start Use the work-with-ui skill to add a new htmx-powered page to the HFS web UI following its template and CSS conventions.