design-os

Build or critique narratives using Storyteller Tactics (Pip Decks). Use when pitching ideas, structuring presentations, framing research share-outs, selling design decisions, motivating teams, or sharpening any story-shaped argument.

Ideate and critique data visualizations using Edward Tufte's principles. Use when designing charts, improving dashboards, checking graphical integrity, reducing chartjunk, or planning small multiples and high-density displays.

Heuristic and WCAG 2.1 AA accessibility review of UX specs, Figma flows, or described interactions. Tied to your design system's accessibility standards.

Review color usage in a design for semantic consistency, token adherence, and accessibility. Works from attached images, specs, or Figma files.

Connect MCPs for real-time tool integration — Figma (primary), Storybook, research tools, and project management

Review microcopy, labels, error messages, and content hierarchy in a design or spec. Grounded in your writing styles, design principles, and component UX guidance.

Prepare a design critique agenda with structured feedback prompts. Grounded in your brief, design system principles, and past critique patterns.

Draft a UX spec with flows, states, edge cases, and component references. Grounded in your Storybook library, design principles, and UX brief.

Critique a Figma file or frame using the Figma MCP. Reads live file data, runs a structured design critique, and optionally posts findings as comments back to Figma.

Pre-handoff readiness check for a UX spec. Verifies completeness before engineering picks it up.

Turn raw critique notes, design sync transcripts, or rough notes into structured meeting summaries with decisions, action items, and open questions.

Generate an HTML/CSS/JS or React prototype using the team's design system components and tokens. Use when the designer wants to quickly explore a layout, interaction pattern, or component state before writing a spec or taking it into Figma. Use for visual explorations, dev reference artifacts, and stakeholder previews.

Turn raw usability session notes, interview transcripts, or evaluation findings into structured insights with themes, quotes, and design implications.

Create a design brief from a problem statement, PRD, or feature idea. Produces a grounded brief tied to your product context, design system, and research.

Critique a design from an attached image — component, page layout, or mobile screen. Grounded in your design system principles and component UX guidance.