glare

Use this skill when the user is focused on the Building Proof dimension of the Design Assessment — "we can't show what changed," "leadership doesn't see our value," "design wins get described without numbers," "our research doesn't connect to business goals," "we measure activity instead of outcomes," "design feels like opinion," or asks about Building Proof's four layers (Research, Intent, Outcome, Impact). Also use when the user wants to evaluate whether design work connects to user outcomes and business results, define what proof should look like before work starts, or strengthen the proof chain from research to impact. Do NOT use when the user wants the broader assessment (`glare-design-assessment`), is in a different dimension (`glare-assessment-organizing-work`, `glare-assessment-managing-complexity`, `glare-assessment-guiding-decisions`, `glare-assessment-scaling-influence`), or is interpreting the score (`glare-assessment-scoring`, `glare-assessment-reading`, `glare-assessment-using-results`).

Use this skill when the user is focused on the Guiding Decisions dimension of the Design Assessment — "we keep relitigating decisions," "reviews end without commitment," "research is interesting but not decisive," "loudest voice wins," "we keep asking for more data," "no one can explain why one path was chosen," or asks about its four areas (Exploratory, Operational, Analytical, Evidential). Also use when matching decision type to evidence type. Do NOT use for the broader assessment (`glare-design-assessment`), a different dimension (`glare-assessment-organizing-work`, `glare-assessment-managing-complexity`, `glare-assessment-building-proof`, `glare-assessment-scaling-influence`), or score interpretation (`glare-assessment-scoring`, `glare-assessment-reading`, `glare-assessment-using-results`). For one design review meeting use `glare-design-review` — single-conversation rubric, not a system dimension.

Use this skill when the user is focused on the Managing Complexity dimension of the Design Assessment — "our work keeps getting tangled," "dependencies surprise us," "we can't tell simple from complex problems," "every project feels overweight," "complicated work has unclear ownership," "we lock plans before we understand the problem," or asks about its three levels (Simple → Complicated → Complex). Also use when matching structure to the kind of work, separating repeatable tasks from uncertain problems, or strengthening how the team handles work that grows across products, teams, systems, and decisions. Do NOT use when the user wants the broader assessment (`glare-design-assessment`), a different dimension (`glare-assessment-organizing-work`, `glare-assessment-building-proof`, `glare-assessment-guiding-decisions`, `glare-assessment-scaling-influence`), or interpreting the score (`glare-assessment-scoring`, `glare-assessment-reading`, `glare-assessment-using-results`).

Use this skill when the user is focused on the Organizing Work dimension of the Design Assessment — "where does design knowledge get lost," "we keep restarting from scratch," "research findings disappear after the deck," "new team members lack context," "we keep rerunning the same studies," "design decisions are explained differently by different people," or asks about its four layers (Objectives → Drivers → Learning → Outputs). Also use when evaluating whether learning compounds across projects, tracing one project from objective to output, or making evidence findable and reusable. Do NOT use for the broader assessment (`glare-design-assessment`), a different dimension (`glare-assessment-managing-complexity`, `glare-assessment-building-proof`, `glare-assessment-guiding-decisions`, `glare-assessment-scaling-influence`), or score interpretation (`glare-assessment-scoring`, `glare-assessment-reading`, `glare-assessment-using-results`).

Use this skill when the user wants to interpret the *shape* of their Design Assessment results across dimensions — "what does our pattern mean," "how do I read these scores together," "we're balanced but low," "we're strong on proof but weak on influence," "we have a strong start, weak finish," "high activity, low impact," "what pattern do we have," or asks how multiple dimension scores work together. Also use when the user describes a specific shape — uneven scores, one strong dimension carrying the others, weak link creating drag — or names a common pattern like "balanced and strong," "weak start strong finish," "strong proof weak influence," "strong decisions weak proof," "strong organization weak complexity," "local strength limited scale." Do NOT use when the user wants to understand how scores are *built* (`glare-assessment-scoring`), is choosing a 30-day next move (`glare-assessment-using-results`), or is in one specific dimension — drop into those instead.