Individual skill

expectation-effect-design-cues

Apply in-product expectation cues — typography, animation, spacing, copy tone, micro-interactions, and visual register that signal "this is the kind of product you're using" within seconds of opening it. Use when designing the first-screen experience, picking a typography system, deciding loading-state behavior, choosing animation timing, or polishing the surface details that telegraph product quality. Surface cues set expectations for the whole session and create halo effects (positive or negative) that color every later interaction. Small surface details have outsized impact on perceived overall quality.

plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/expectation-effect-design-cues/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Expectation Effect — design cues

In-product design cues are everything the user sees, hears, and feels in the first few seconds of using the product. Typography, color, spacing, animation timing, copy tone, micro-interaction polish, loading-state behavior — all set expectations almost instantly for what the rest of the experience will be like.

The surface cues matter not because they're the most important parts of the product (they aren't) but because they're the *first* parts of the product. The expectations they set become the lens through which every later interaction is interpreted. A polished first impression makes a slightly slow loading state read as "the system is being thorough." An unpolished first impression makes the same loading state read as "this is broken."

## What the user reads in the first 5 seconds

The user is forming an evaluation in the first few seconds whether you want them to or not. The cues they're reading include:

**Typography quality.** Are the typefaces chosen with intent, or are they default system fonts placed without thought? Are line heights, weights, and sizes coordinated, or do they wander? Typography is the single most-noticed surface cue because text is everywhere on screen, and a weak typography system signals weakness throughout. Conversely, considered typography signals craft instantly.

**Spacing and alignment.** Are elements in deliberate relationships, or do they crowd and float at near-but-not-aligned positions? The "near miss" alignment — where two elements are not quite aligned but clearly trying to be — signals carelessness more strongly than either tight alignment or generous, intentional asymmetry.