super-ux

Shape: static. The chain is fixed — foundation, flows, screens, scenarios — and every layer is a committed file. `/ux-audit` batches on the fly, and the batch list is printed before the run so what executed is recoverable.

/super-ux — what the interface must do

• when: there is user-facing behaviour
• decline it: «без сценариев».

If super-ux is installed, all work on the product and its interface goes through the chain — scenarios and their validation first, the interface second. Not only screens: product decisions, funnels, onboarding, payment steps — anything with a user and a path. docs/ux/scenarios.md is the source of truth for user-facing behaviour; no file → offer /ux before touching UI. A change to user-facing behaviour updates the scenarios in the same change. Checking code against them is /ux-audit, with file:line evidence.

The boundary — "this has a user." NOT through the chain: internal scripts, migrations with no interface, data work, infrastructure. Drawing a scenario for a cron job is how you teach an agent to route around the chain.

Refusal phrase: «без сценариев».

Among the routers: super-ux decides what the interface must do; sheleg-design how it looks; copywriting how it sounds.

/copywriting — how it sounds

• when: text a user of the product will read
• decline it: «без бренда» or «черновиком».

If super-ux is installed, any text a user of the product will read is written through copywriting — interface strings, errors, empty states, landing pages, pricing, blog, user-facing changelog, posts, store listings, ads, email. Its first act is to read the brand pack (docs/brand/voice.md, terminology.md, facts.md); no pack → /brand-init before writing, not after.

The boundary — "it ships to a user of the product." NOT through the skill: a commit or PR description, code comments, a README for developers, internal docs, an answer in chat. Running the brandbook over a CHANGELOG line for developers is the fastest way to teach an agent to route around it.

Refusal phrase: «без бренда» or «черновиком». It applies to work that WOULD have crossed the boundary: write directly and say the pack was skipped on request, rather than skipping it silently.

Among the routers: sheleg-design decides how it looks; copywriting how it sounds. Neither waits for the other — both read the scenarios, not each other's output — but where they land on one screen, compare the two before shipping: a label the layout has no room for is right in each and wrong on the screen. A landing page passes both plus task-pipeline; a social post passes copywriting alone and changes no repository.