super-ux plugin

Single entry point for the verbal identity, status first, then the next action

Seed docs/brand/ with a proposed voice pack and sweep interface strings into the registry

Lint docs/brand/ and its declared sources for voice, term, fact and string drift

Carry a positioning, pricing or naming change through the whole brand pack

Write or edit copy for a named surface in the recorded voice

Single entry point for all UX work, status across every layer, then the next action

Audit the codebase against scenarios and flows at quick, standard or deep depth

Diagnose docs/ux against the current contract and name what the tooling cannot read

Design, reverse-engineer or improve user flows, screen states and mockups

Build or update personas, jobs, journeys and stories in docs/ux/foundation.md

Initialize the full UX chain for this project, from vision to scenarios

Lint docs/ux for broken traces, orphans, missing frames and drift

Install the scenario-first hard rule and the docs/ux/ skeleton

Update the UX chain after a user-facing change, or test a feature idea against it

Write docs/ux/vision.md and install the vision-alignment rule

Use when defining or checking how a product speaks: tone of voice, terminology, canonical facts, register. Triggers: "tone of voice" / "тон оф войс", "brand voice" / "голос бренда", "брендбук", "наша терминология". Not for writing the text (copywriting). Refusal phrase "no brand" / «без бренда».

Use when writing text a user reads: UI strings, landings, store listings, posts, ads, email. Triggers: "напиши текст", "App Store description" / "описание для App Store", "video hook" / "хук ролика". Not for the voice (brand-voice) or look (sheleg-design). Refusal phrase "no brand" / «без бренда».

Use when verifying the codebase against the UX scenario base (batched, evidence-backed, report in docs/ux/audits/). Triggers: "ux audit" / "UX-аудит", "run the scenarios" / "прогони по сценариям". Not for a whole-project audit (project-audit) or editing scenarios (ux-scenarios).

Use when designing how users move through a product: flows, screen states, wireframes, Figma mockups, funnels, paywalls. Triggers: "юзер флоу", "add a screen" / "добавь экран", "mockups" / "макеты". Not for the visual system (sheleg-design). Refusal phrase "no scenarios" / «без сценариев».

Use when defining who uses a product and why (docs/ux/foundation.md): personas, actors, JTBD, journeys, stories, capabilities, churn. Triggers: "jtbd" / "джобы", "customer journey" / "карта пути", "персоны", "ретеншн", "отток". Not for flows or screens (ux-flows).

Use when writing UX scenarios (docs/ux/scenarios.md): a new feature, a user-facing behavior change, a move to scenario-driven development. Triggers: "ux scenarios" / "сценарии использования", "новая фича". Not for an empty project (vision first). Refusal phrase "no scenarios" / «без сценариев».

Use when a project needs its product vision (what it is, why it exists, what it refuses to become), written to docs/ux/vision.md with an alignment rule. Triggers: "vision" / "видение", "product vision" / "продуктовое видение", "define product direction". Not for personas or jobs (ux-foundation).