blade-ui

# blade-ui > **Grounded stack guidance:** pull idiomatic Do/Don't + docs URLs from the > adopted stack corpus before improvising — `./scripts-run > <skills-root>/corpus-grounding/scripts/ground search --manifest > <skills-root>/design-intelligence/data/manifest.json --stack laravel "<topic>"` > (the `laravel` stack file is Blade/UI-scoped, not general Laravel). See > [`design-intelligence`](../design-intelligence/SKILL.md). ## Positioning — dispatched, not standalone `blade-ui` is the **apply-step executor** for the Blade stack. It is invoked by [`directives/ui/apply.ts`](../../templates/scripts/work_engine/directives/ui/apply.ts) once the design brief is locked, and revisited by `review.ts` / `polish.ts` 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.ts`](../../templates/scripts/work_engine/directives/ui/design.ts) | | Universal design heuristics | [`fe-design`](../fe-design/SKILL.md) | | Review + polish loop | [`directives/ui/review.ts`](../../templates/scripts/work_engine/directives/ui/review.ts) + [`polish.ts`](../../templates/scripts/work_engine/directives/ui/polish.ts) | ## When to use Cite this skill when: - `state.stack.frontend == "blade"` (or the project is clearly Blade-only withou...