blade-uilisted

# blade-ui ## Positioning — dispatched, not standalone `blade-ui` is the **apply-step executor** for the Blade stack. It is invoked by [`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py) once the design brief is locked, and revisited by `review.py` / `polish.py` during the design-review loop. It does **not** own the flow, does **not** drive the audit, and does **not** lock the design. | Concern | Owner | |---|---| | Audit + token inventory (mandatory pre-step) | [`existing-ui-audit`](../existing-ui-audit/SKILL.md) | | Design brief (layout / states / microcopy) | [`directives/ui/design.py`](../../templates/scripts/work_engine/directives/ui/design.py) | | Universal design heuristics | [`fe-design`](../fe-design/SKILL.md) | | Review + polish loop | [`directives/ui/review.py`](../../templates/scripts/work_engine/directives/ui/review.py) + [`polish.py`](../../templates/scripts/work_engine/directives/ui/polish.py) | ## When to use Cite this skill when: - `state.stack.frontend == "blade"` (or the project is clearly Blade-only without Livewire / Flux) and `directives/ui/apply.py` dispatches to this skill - Editing or creating Blade views, components, partials, layouts, or forms Do NOT use when: - API-only endpoints (use `api-endpoint` skill) - Livewire components (use `livewire` skill — it composes Blade views internally) - Flux UI components (use `flux` skill) - Driving the full UI flow yourself — that is the `directives/ui/` orchestrator