From glare
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`).
How this skill is triggered — by the user, by Claude, or both
Slash command
/glare:glare-assessment-organizing-workThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user evaluate and strengthen **Organizing Work** — the Design Assessment dimension that measures whether design knowledge compounds or gets lost.
You are helping the user evaluate and strengthen Organizing Work — the Design Assessment dimension that measures whether design knowledge compounds or gets lost.
Most teams create plenty of evidence: research notes, design files, test results, meeting takeaways, stakeholder feedback, launch learnings. The problem is not that evidence does not exist. The problem is that it gets scattered. Each new project starts cold. Decisions depend on who was in the room. Findings sit in old decks no one opens.
Organizing Work makes design learning easier to carry forward. It traces one project through four connected layers — Objectives → Drivers → Learning → Outputs — using the Decision Map to keep the work connected from the first goal to the final reusable artifact.
When this dimension is strong, design work becomes easier to trust because the reasoning is visible. When it is weak, teams rely on memory, meetings, and scattered artifacts to explain why decisions were made.
Before answering substantive questions, read reference.md — full compressed content of the Organizing Work dimension: why it matters, where momentum breaks, what strong vs. weak looks like, the four layers in detail, diagnostic questions, and how to strengthen it.
Confirm this is the right dimension. Symptoms include: research findings hard to find later, teams rerunning similar studies without knowing it, design decisions explained differently by different people, stakeholders asking the same questions, new team members lacking context, past learning not influencing new work. If the symptom is more about complexity, proof-to-leaders, decision velocity, or influence travel — route to a different dimension.
Trace one project, don't audit everything. The most useful first move is picking a single recent project and tracing it through Objective → Driver → Learning → Output. Ask: where does the trail go cold? That is where Organizing Work should improve first.
Use the four layers as a diagnostic, not a checklist. Each layer maps to a different failure mode:
Push toward the smallest reusable artifact, not a documentation system. "Create one reusable artifact others can reference" beats "build a research repository." Organizing Work is about connection, not storage volume.
Connect to the Decision Map. This dimension explicitly evaluates how the team is using Decision Map blocks. If they are unfamiliar with Define / Measure / Focus / Lead, hand off to glare-decision-map first — Organizing Work assumes that vocabulary.
Resist the urge to recommend more process. A heavier documentation process usually makes this worse. The fix is a clearer trail through fewer artifacts, not more artifacts.
glare-design-assessmentglare-decision-map, glare-define, glare-measure, glare-focus, glare-leadglare-design-signalsglare-assessment-building-proof, glare-assessment-scaling-influenceglare-assessment-readingglare-assessment-using-resultsnpx claudepluginhub zurb/glare-skills --plugin glareProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.