design-direction

Synthesize locked design-crit decisions into direction.html, decisions.md, and overview.html.

3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/metedata/design-crit --skill design-direction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-direction
Source: https://github.com/metedata/design-crit/tree/main/skills/design-direction
Command: npx skills add https://github.com/metedata/design-crit --skill design-direction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a completed design critique into a single, actionable design direction and handoff package so teams can stop managing fragmented decisions and start building. It verifies that all enabled facets are resolved, synthesizes locked decisions into a coherent narrative, and produces the canonical deliverables needed for implementation.

Core Features & Use Cases

  • Prerequisite verification: Reads .design-crit/state.json to ensure enabled facets are locked or offers options to continue, skip, or auto-decide unresolved facets.
  • Context-efficient synthesis: Loads brief and compact summaries first, then streams locked facet HTML and feedback one facet at a time to assemble focused sections without exhausting context.
  • Deliverable generation: Produces a polished .design-crit/direction.html, a versioned .design-crit/decisions.md, an optional .design-crit/design-tokens.json when token-producing facets exist, and an updated .design-crit/overview.html for handoff.
  • Handoff guidance: Summarizes outputs and suggests implementation steps based on state.json > project.tech_stack, then opens the direction document for review.
  • Use case: Finalizing a multi-facet design crit for a product team and exporting the design direction, tokens, decision logs, and wireframe gallery for engineers and stakeholders.

Quick Start

Run the design-direction skill to synthesize the locked crit into a direction document and export the deliverables into the .design-crit directory.

Frequently Asked Questions about design-direction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synthesize design critique decisions into a final design direction?

To synthesize design critique decisions into a design direction, the skill reads locked facet states and feedback from .design-crit/state.json. It then generates a coherent narrative by streaming locked facet HTML and feedback to assemble focused sections without exhausting context.

What files do I need for a design handoff package from a completed critique?

A design handoff package requires reading .design-crit/state.json, brief summaries, and crit-session summaries. The process outputs a polished direction.html, a versioned decisions.md, an updated overview.html, and optionally a design-tokens.json file when token-producing facets exist.

Can I export design tokens automatically from locked wireframe critiques?

Yes, you can export design tokens automatically from locked wireframe critiques. The skill generates an optional .design-crit/design-tokens.json file directly from the synthesis process if token-producing facets are present and locked within the critique state.

What happens if my design critique facets are not locked before synthesis?

If design critique facets are not locked before synthesis, the skill verifies enabled facets and offers options to continue, skip, or auto-decide unresolved facets. This ensures you can still generate the final design direction document without manually locking every component.

How does design direction synthesis manage context limits with multiple feedback sessions?

Design direction synthesis manages context limits by loading brief and compact summaries first. It then streams locked facet HTML and feedback one facet at a time, assembling focused sections sequentially to prevent exhausting the available context window.

Does the design handoff process suggest implementation steps for engineers?

Yes, the design handoff process suggests implementation steps for engineers. It summarizes the generated outputs and provides guidance based on project.tech_stack defined in state.json, then opens the direction document for immediate stakeholder review.