layers-surface

/layers-surface

Assumes /layers-intro has been loaded. This skill is a library of techniques, not a script — see "How to use these skills" there.

The surface layer is where everything decided below becomes something a person actually encounters: words, sounds, visuals, physical affordances, motion, feedback. It's the most medium-specific layer, but the decisions that matter most first are universal — they hold whether the surface is a screen, voice interface, physical device, or service touchpoint.

Surface problems are often symptoms of deeper ones. The central discipline here is telling apart issues you can fix at the surface from issues that need a lower layer revisited.

The decisions this layer makes

• Whether the surface honours the vocabulary and objects from the conceptual model
• Whether every affordance from the breadboard is present — and whether any surface element has no model behind it
• Whether the emotional register fits the jobs users are doing
• How the user knows what happened, what's in progress, and what went wrong
• What's most prominent, and whether it should be
• Whether everything is accessible to the users who need it

Disciplines — what keeps the surface honest

• Surface fix vs deeper-layer issue. The key judgement: is this something to fix in the copy/layout, or a symptom whose root is in the conceptual model or interaction flow? Wrong vocabulary may be a rewrite — or a model that never settled the term. Route deeper issues back to the relevant skill rather than patching the symptom.
• Terms match the ubiquitous language. Flag direct violations (a model term used inconsistently), unlisted terms (surface words not in the model — add to model, or remove as noise), and tone misalignments.
• Object consistency. No shapeshifters (same object in significantly different forms across contexts), no masked objects (a form where the user can't recognise the object type).
• Completeness both ways. Every breadboard affordance is present; no surface element exists with no model or flow behind it (those are interaction decisions that slipped through — route to /layers-interaction-flow).
• Errors diagnose, explain, recover. "Something went wrong" fails all three. Flag every error state that doesn't do all three.
• Prominence reflects importance. What the flow needs the user to notice is what stands out; nothing prominent that shouldn't be.
• Accessibility is decided, not defaulted.
• Emotional register matches the emotional and social jobs from user needs — not the product's benefit framed as the user's.