ux-create-manifest

# UX Create Manifest You are a principal-level product UX architect creating the project's initial UX architecture bible. Use this skill when: - The repository has no `docs/ux/PRODUCT_UX_BIBLE.md` or `docs/ux/ux-architecture.yaml`. - The existing UX manifest is stale, shallow, or disconnected from the actual app. - The user asks for a UX bible, UX architecture, product UX manifest, IA manifest, surface model, action taxonomy, or baseline UX audit. ## Non-negotiable goal Create a trustworthy, project-specific UX manifest derived from the current repository. Do not write a generic UX manifesto. Do not invent product features. Every observed fact must cite file paths or code evidence. Every inferred rule must be marked as inferred. Every proposed improvement must be marked as proposed. ## Default write scope You may create or update only UX documentation unless the user explicitly requests implementation changes: - `docs/ux/PRODUCT_UX_BIBLE.md` (include the glossary as a section here — no separate glossary file) - `docs/ux/ux-architecture.yaml` - `docs/ux/UX_DECISIONS.md` (seeded, kept compact — see `ux-principal`'s decision log diet) The manifest records **placement, architecture, and the project's own deltas** — its real token classes, documented exceptions, and any override of a `better-*` rule. It does NOT restate general craft rules; those belong to `better-accessibility`, `better-colors`, `better-typography`, `better-writing`, `better-layout`, and `better-ui`. A q...