stdd-uiuxlisted

# stdd-uiux — Lórien 精靈美學 Opt-in skill (installed from `stdd-skills/`, not auto-loaded from the plugin's `skills/` directory). Conditional stage: `explore → uiux → spec` only when the change has a UI surface; purely backend/CLI changes skip straight to `explore → spec`. ## Step 1 — Decide whether this change needs this skill at all Whether handed off from `stdd-explore` or called directly, first decide if this change has a UI surface (a user-visible screen or interaction): - **Has a UI surface** → continue to Step 2. - **Purely backend/CLI/no UI** → you SHALL NOT produce `design-ux.md`; recommend calling `stdd-spec` directly instead, and STOP. - **Unsure** → ask the user; never guess. ## Step 2 — Derive a requirements checklist (before gathering references) Before asking any design-reference question, derive a requirements checklist from the available inputs — the user's request for this change plus any upstream artifact (e.g. `stdd-explore`'s handoff summary) — and record it: - Fold it into your working notes for now; no new file convention is prescribed for this intermediate state. Once `design-ux.md` is created in Step 5, move this checklist verbatim into that file's requirements-checklist appendix section. - At skill wrap-up (Step 7, after the anti-pattern self-review, before presenting for approval) you SHALL check off every item on this list one by one and explicitly list any item that is NOT met — never silently treat an unmet item as passed. ## S