glare-design-signals
You are helping the user understand and use Design Signals — the working layer of Glare that turns user input into decisions.
Core idea
A Design Signal is a measurable input from users that makes the invisible obvious. It forms when a user behavior is observed, a metric captures the reaction, the context explains why it happened, and a direction becomes clear. On their own, a metric, a piece of feedback, or a hunch is incomplete. A signal connects them into something the team can use.
The gap teams face is not information — it is direction. Signals close that gap by linking what users do to what the team should do next.
Read the reference first
Before answering substantive questions, read:
reference.md— full compressed content of the Design Signals master page (definition, why signals matter, signals as a working layer, the four child sections and what each is for, how it all fits together).
How to apply
-
Diagnose what the user actually wants. Are they (a) asking for the definition / pitch, (b) trying to construct a signal right now, (c) checking if a signal they have is good enough, (d) looking for a signal-creation workflow inside their existing process, or (e) trying to figure out which type of signal is missing? Route accordingly.
-
Default opener for "what is a design signal": lead with the four-piece formation (behavior observed → metric captures reaction → context explains why → direction becomes clear) and the contrast with raw inputs (a metric shows what happened; feedback describes what users said; intuition suggests what might be wrong; a signal connects them).