glare

Plugin glare from marketplace glare-marketplace in zurb/glare-skills. Commands read from the repo's manifest — 16 days ago.

Skills (61)

• assessment-building-proof

  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

• assessment-guiding-decisions

  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

• assessment-managing-complexity

  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 pla

• assessment-organizing-work

  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

• assessment-reading

  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," "hig

• assessment-scaling-influence

  Use this skill when the user is focused on the Scaling Influence dimension of the Design Assessment — "our proof stays local," "leaders only see final outputs," "design evidence doesn't shape strategy," "we keep re-explaining the same value story," "investment decisions happen without our evidence,"

• assessment-scoring

  Use this skill when the user is asking about how the Design Assessment is scored or measured — "how does the assessment work," "what do the score bands mean," "what's a good design assessment score," "what's Reactive vs Developing vs Functional vs Strong vs Leading," "how are dimension scores calcul

• assessment-using-results

  Use this skill when the user has Design Assessment results and is asking what to do next — "what do we do with our score," "how do we turn the assessment into action," "where should we start," "what's our 30-day next move," "which dimension should we improve first," "how do we run a results review,"

• decision-map

  Use this skill when the user is working with the Glare Decision Map — the four-facet flow that connects user needs to measurable outcomes. Triggers include "Decision Map," "decision flow," "Define Measure Focus Lead," "how do the Glare facets connect," "trace a decision from problem to outcome," "ma

• define-audience

  Use this skill when the user is defining WHO their signals come from in the Define area — picking audiences, evaluating credibility, building Audience Definition Cards, OR formatting a completed Card for a specific reader. Triggers — "who are we designing for," "is this audience credible," the four

• define-collecting

  Use this skill when the user is in the Collecting block — turning raw input into usable signals, OR formatting a completed Collection Brief for a specific reader. Triggers — research mode (Exploratory / Evaluative / Comparative), 5-step process (Intent → Stack → Approach → Techniques → Connect), 12

• define-patterns

  DEPRECATED — Patterns block was archived in Glare v3.5.0 and replaced by Situations. Use `glare:define-situations` instead. This skill remains as a redirect for legacy references. The Situations block keeps the core idea (recurring conditions create meaning around behavior) and extends it with the f

• define-situations

  Use this skill when the user is interpreting collected signals to identify recurring conditions — the new 4th block of Define that replaces the archived Patterns block. Triggers — "I have signals but can't see a pattern," "what does this drop-off mean," "are these signals telling the same story," th

• define-user-needs

  Use this skill when the user is working on the User Needs block of the Define area — naming what users actually need before any solution, OR formatting a completed User Needs output for a specific audience. Triggers — "what user need does this solve," "is this a want or a need," needfinding, the 5 u

• define-ux-metrics

  Use this skill when the user is in the UX Metrics block of the Define area — picking the numbers that prove design worked for a specific decision. Triggers — choosing Attitudinal / Behavioral / Performance / Intelligence metrics; the four lenses (By Type, By Stage, By Time, By Engagement); leading v

• define

  Use this skill when the user is in the Define area of Glare's Decision Map — the "Credibility" stage where teams agree on what matters before building. Triggers — defining user needs, picking audience, gathering evidence, naming recurring situations, or choosing UX metrics; questions like "who are w

• design-assessment

  Use this skill when the user asks about Design Assessment as a top-level concept — "what's our team's design maturity," "score our org," "where is design impact breaking down," "how do I run a design assessment," "what are the five dimensions," or wants the overview (Organizing Work, Managing Comple

• design-review

  Use this skill whenever the user asks about Design Review as a top-level concept in Glare — "what is the SIGNAL framework," "how do I run a better design review," "score a design review call," "evaluate a transcript," "improve our review meetings," or wants the overview of the Design Review section

• design-signals

  Use this skill whenever the user asks about Design Signals as a top-level concept in Glare — "what is a design signal," "why do signals matter," "how is a signal different from a metric," "signals vs feedback," "how do I turn data into a decision," or wants the overview of the Design Signals section

• focus-comparing

  Use this skill when the user is **Comparing** in the Focus facet — placing signals side by side. (v1.3 source is "Compare"; folder keeps "comparing" for install paths.) Triggers — "compare versions," "v1 vs v2," "is this score good or bad," "compare against benchmark," "compare audiences/segments/co

• focus-decisions

  Use this skill when the user is making a **Decision** in the Focus facet — turning signals into action. Triggers — "make the call," "we need to decide," "should we ship this," "should we test another iteration," "should we kill this," "revisit later," "we keep circling," "findings sit in decks," "ex

• focus-initiatives

  Use this skill when the user is naming an **Initiative** in the Focus facet — defining the area of work before methods or comparisons run. Triggers — "what should we focus on," "frame the initiative," "scope the work," "scattered requests," "everything feels important," "connect this redesign to a g

• focus-methods

  Use this skill when the user is choosing a **Method** in the Focus facet — picking the frame to bring data into an initiative. Triggers — "what method should we use," "how should we test this," "how do we frame the data," "we have data but don't know what it means," choosing between competitor analy

• focus

  Use this skill when the user is in the **Focus** facet of the Decision Map — turning signals into direction. Triggers — "what should we focus on," "we have findings but don't know what to do," "decide between concepts," "compare versions," "Initiatives Methods Comparing Decisions," "narrow the work,

• getting-started

  Use whenever the user is new to Glare or asks an intro question — "what is Glare," "how do we start," "conceptual tour," "the six components," "create my first signal," "I have a real decision," "two directions no clear winner," "use Glare with ChatGPT or Gemini," "what is Ray," "prompt vs Skill vs

• lead-business-goals

  Use this skill when the user is anchoring design work to executive pressures — the Business Goals bucket of the Lead facet. Triggers — picking which business pressure a project serves (Growth, Retention, User Experience, Efficiency, Operations), choosing among the 20 measurable goals (e.g., "Achieve

• lead-mapping

  Use this skill when the user is drawing the ladder from user need to business goal — the Mapping bucket of the Lead facet. Triggers — building or auditing a Chain of Proof (User Need → Design KPI → Product KPI → Business KPI → Goal); naming UX metrics as "connective tissue" between product and busin

• lead-results

  Use this skill when the user is closing the loop between learning and leadership trust — the Results bucket of the Lead facet. Triggers — running the Project Work loop (Initiatives → Findings → Decisions → Outcomes); identifying which layer is broken; assessing maturity against the five Dimensions (

• lead-workflows

  Use this skill when the user is translating design signals into the language of a specific business function — the Workflows bucket of the Lead facet. Ships eight cross-functional templates (Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal), each with top metrics, questio

• lead

  Use this skill when the user is connecting design work to business impact — the Lead facet of Glare's Decision Map (formerly "Show" in v1.0). Triggers include proving ROI on design, building executive narratives, mapping Design KPIs to Product KPIs to Business KPIs, anchoring work to business pressu

• master

  Cross-component orchestration across the v3 Glare marketplace — use when the user can't tell which of the 6 components applies, or when their question spans more than one. Triggers — "I'm stuck and don't know where to start," "which Glare skill applies here," "where should I go next," "I lost the th

• measure-concepts

  Use this skill when the user is working on the Concepts move of the Measure area — defining a focused, testable design effort before solutioning. Triggers — framing intent for a redesign, narrowing a big initiative to one actionable bet, mapping a user need from Define against a business goal from L

• measure-findings

  Use this skill when the user is in the Findings move of the Measure area — turning raw data into evidence-backed signals. Triggers — translating drop-off rates, survey scores, heatmaps, or task-success numbers into a finding; tying a finding to a user need (comprehension, usefulness, satisfaction, c

• measure-hunches

  Use this skill when the user is forming a Hunch in the Measure area — turning instinct into a falsifiable, testable hypothesis. Triggers — writing or critiquing a "we believe..." statement, the hunch template *"We believe that [change] for [audience] will [impact] because [reason]"*, the belief prim

• measure-questioning

  Use this skill when the user is drafting, critiquing, or organizing research questions in the Measure area. Triggers — sorting questions into the four types — **People** (habits/behaviors), **Process** (steps/friction), **Product** (clarity/usefulness), **Problem** (barriers); choosing a Mode — **Ex

• measure

  Use this skill when the user is producing evidence within the Decision Map's Measure area — turning intuition into testable signals. Triggers include forming hypotheses or hunches ("we believe that [change] for [audience] will [impact] because [reason]"), writing research questions, running tests, i

• review-align

  Use this skill when the user is working on the Align step of a design review — making ownership and responsibility visible before the call ends. Triggers include "everyone agreed but no one owns it," "responsibility is blurry," "we don't know who's leading vs supporting," "we need someone in the roo

• review-coach

  Use this skill when the user wants to prepare for an upcoming design review or client call, OR coach someone on behavioral improvements after one. Triggers include "prep me for a kickoff," "prep for a design review," "build a call brief," "what should I focus on for this call," "we have past SIGNAL

• review-ground

  Use this skill when the user is working on the Ground step of a design review — anchoring decisions in evidence instead of opinion. Triggers include "the conversation keeps looping on opinion," "people are defending preferences," "we have data but it's not changing the discussion," "feedback is opin

• review-identify

  Use this skill when the user is working on the Identify step of a design review — defining what "better" means in measurable terms, turning vague feedback into a clear outcome, or aligning the room on what success looks like. Triggers include "feedback is all preference," "people keep saying 'better

• review-lock

  Use this skill when the user is working on the Lock step of a design review — converting agreement into forward motion. Triggers include "the call ended without next steps," "we always end with 'we'll follow up'," "no timing was set," "the same conversation keeps coming back," "Lock scored low" (1–2

• review-navigate

  Use this skill when the user is working on the Navigate step of a design review — leading the decision and securing commitment. Triggers include "we keep exploring without choosing," "the team won't make a recommendation," "we have signals but can't pick a direction," "ideas keep being treated equal

• review-rubric

  Use this skill when the user wants to evaluate a design review or client call using the full SIGNAL rubric — scoring call quality, diagnosing where conversations broke down, and producing a structured evaluation report. Triggers include pasting a call transcript, asking to review or score a call, re

• review-run-transcript

  Use this skill when the user wants the practical workflow for evaluating a real design review transcript end-to-end. Triggers include "I have a transcript — what do I do with it," "how do I run a transcript through SIGNAL," "what do I need before scoring a call," "what tool should I use to evaluate

• review-scoring-model

  Use this skill when the user wants the SIGNAL scoring rubric itself — the 1–5 scale per dimension, the score bands /30, the calibration rules, and how to interpret the result. Triggers include "how do I score a design review," "what does a 3 mean for Surface," "what's a Leading score," "score bands,

• review-surface

  Use this skill when the user is working on the Surface step of a design review — exposing the real tension behind the request, naming what is actually breaking, or making consequence visible. Triggers include "the team is reacting to the design before agreeing on the problem," "feedback is scattered

• review-techniques

  Use this skill when the user wants the cross-cutting view of Design Review techniques — the small in-the-moment moves that work across all six SIGNAL letters. Triggers include "what techniques can I use in a design review," "how do I shape feedback in real time," "the conversation is going off the r

• signals-capturing

  Use this skill when the user wants the practical, end-to-end workflow for creating Design Signals inside the work — "how do I capture a signal," "how do we run a fast signal-capture loop," "we always gather feedback too late," "how do I turn this hunch into a real signal," "how do I make signals par

• signals-components

  Use this skill when the user is building or strengthening an individual Design Signal — "what goes into a signal," "anatomy of a signal," "what are the parts of a design signal," "how do I structure a signal," "my signal feels incomplete," "how do I make a signal stronger." Triggers also include the

• signals-quality

  Use this skill when the user is trying to evaluate whether a Design Signal is good enough to act on — "is this signal usable," "is this a signal or just a metric," "how do I know if a signal is strong enough," "weak vs strong signal," "why is our signal not leading to a decision," "should we act on

• signals-types

  Use this skill when the user asks about the **kinds** of Design Signals — "what are the four signal types," "Need Use Prefer Adopt," "what types of signals should we collect," "are we covering the full experience," "we only have one kind of signal," "how do I know which signal type is missing." Trig

• ux-metrics-applying

  Use this skill when the user is putting UX metrics to work inside real product moments — phrases like "applying UX metrics," "using UX metrics in product reviews," "UX metrics in prioritization," "UX metrics for concept comparison," "launch readiness," "UX metrics for AI workflow evaluation," "UX me

• ux-metrics-attitudinal

  Use this skill when the user is working with Attitudinal metrics — how users feel about an experience. Triggers — phrases like "attitudinal metrics," "how users feel," "trust," "satisfaction," "confidence," "desirability," "loyalty," "sentiment," "appeal," "feeling," "expectations," "usefulness," "b

• ux-metrics-behavioral

  Use this skill when the user is working with Behavioral metrics — what users actually do inside the workflow. Triggers — phrases like "behavioral metrics," "what users do," "users hesitate," "users abandon," "navigation breakdowns," "how do users actually move through this," "users repeatedly scan,"

• ux-metrics-mapping

  Use this skill when the user is connecting UX metrics to business outcomes — phrases like "mapping design impact," "design impact," "connect UX to business," "UX metrics to business outcomes," "Situation — Intent — Outcomes — Results," "design impact creates pull," "leading vs lagging indicators," "

• ux-metrics-performance

  Use this skill when the user is working with Performance metrics — efficiency, reliability, and operational friction. Triggers include "performance metrics," "efficiency metrics," "reliability," "operational friction," "how long tasks take," "where users drop off," "abandonment rate," "bounce rate,"

• ux-metrics-stack

  Use this skill when the user is combining multiple UX metrics together to evaluate a workflow or experience — phrases like "UX metric stack," "metric stack," "combine UX metrics," "stack of metrics," "Design Stack," "Research Stack," "feature findability stack," "onboarding stack," "checkout stack,"

• ux-metrics-system

  Use this skill when the user is treating UX metrics as a connected system rather than isolated scores — phrases like "measurement system," "UX metrics as a system," "metrics work together," "metrics form patterns," "operational measurement," "shared visibility across teams," "different dashboards di

• ux-metrics-what-is

  Use this skill when the user asks what a UX metric actually IS or how one is structured — phrases like "what is a UX metric," "what counts as a UX metric," "anatomy of a UX metric," "the four parts of a UX metric," "User Attribute — Data Type — Collection Method — Benchmark," "how is a UX metric bui

• ux-metrics-why

  Use this skill when the user is asking WHY UX metrics matter — phrases like "why do we need UX metrics," "why measure UX at all," "we already have analytics — why add UX metrics," "convince me UX metrics are worth it," "UX metrics business case," "design needs its own signals," "AI changed how produ

• ux-metrics

  Use this skill when the user asks about UX Metrics as a top-level Glare framework — phrases like "what are UX metrics," "the four UX metric types," "Attitudinal — Behavioral — Performance — Intelligence," "AI metrics," "Intelligence metrics," "metrics vs signals vs business KPIs," "how do metrics wo

Similar plugins