experience-baselinelisted

Interviews the experience or UX lead about how a product behaves for the people using it — the conditions they work in, the surface states every screen must handle, the component and pattern vocabulary, the words, the accessibility floor, and the interaction budgets — and writes it up as a project experience baseline that every feature inherits. Use this after the product specifications exist and the technical constraints are captured, and before the architecture baseline is written. Trigger it when someone wants to define the design system, establish UX foundations, agree interaction patterns, work out what the product looks like in each state, or set the design ground rules a whole product must follow.
handarbeit/fabrik · ★ 22 · AI & Automation · score 74

Install: claude install-skill handarbeit/fabrik

# Experience Baseline Decide once, for the whole product, what someone sees and what they can be asked to do — so that eleven features do not become eleven products. **Read `../../CONVENTIONS.md` first.** It carries the shared rules — stages, where work is saved, the tree, markers, interview rules, precedence, gates, decision records and the baseline status footer. This skill does not repeat them. This is **stage 4 of 5**. What you produce is the input the architecture baseline needs. ## Why this tier carries the weight A component defined for one feature is reused by six others; a state defined once applies everywhere; a word chosen here appears on forty screens. Note the honest limit: the per-feature experience document this is meant to be inherited by **does not exist yet** (see the tree in `../../CONVENTIONS.md`). Today this baseline is consumed by stage 5 and by whoever builds. Say that rather than promising an assembly step nobody has built. ## Text is what gets built from The output of design work is visual. The thing that builds this product reads files. **Text is authoritative for behaviour; the design file is authoritative for appearance.** Where the two meet — a state's signal is appearance that carries behaviour — record the **distinguishing dimension and its floor**, not the rendering: > "Sync state is distinguished by icon plus word, never colour alone. Legible at arm's > length in poor light. Survives a screen reader and translation." That is implem