design-elevation

Interrogate design-spec.md across five lenses to produce a structured elevation spec.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mojwang/macbook-dev-setup --skill design-elevation-mojwang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-elevation
Source: https://github.com/mojwang/macbook-dev-setup/tree/main/config/skills/design-elevation
Command: npx skills add https://github.com/mojwang/macbook-dev-setup --skill design-elevation-mojwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates rigorous interrogation of a design-spec.md to ensure intent is understood, decisions are defensible, and outcomes are traceable through signals, techniques, and references.

Core Features & Use Cases

  • Interrogate design specs across five lenses (Purpose, Audience, Context, Uniqueness, Restraint) to produce a structured elevation.
  • Leverage companion files SIGNALS.md, TECHNIQUES.md, REFERENCES.md, and MOTION-SYSTEM.md to guide design decisions.
  • Output a complete design-spec.md that includes design parameters, techniques, tokens, and a verification checklist.
  • Use cases include design-system docs, product design reviews, and architecture of design decisions.

Quick Start

Run this skill on a design-spec.md to generate a complete design-elevation spec.

Frequently Asked Questions about design-elevation

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

FAQPage Schema
How do I interrogate a design spec to ensure design decisions are traceable?

A design-spec elevation interrogates your design-spec.md across five lenses—Purpose, Audience, Context, Uniqueness, and Restraint—to produce a structured, traceable specification with defensible design decisions.

What is a design spec elevation and when do I need one for design-system docs?

A design spec elevation interrogates design-spec.md to capture intent across five lenses, producing a traceable specification with parameters, techniques, tokens, and a verification checklist for design-system docs and product reviews.

How do I generate a verification checklist for motion, contrast, and layout decisions?

Generate a verification checklist by interrogating your design-spec.md; the output specifies design parameters, token guidance, and a checklist to validate motion, contrast, and layout decisions for your project.

Can I use companion files like SIGNALS.md and MOTION-SYSTEM.md to guide design parameters?

Yes, the design spec elevation leverages companion files SIGNALS.md, TECHNIQUES.md, REFERENCES.md, and MOTION-SYSTEM.md to orchestrate signals, techniques, references, and motion rules into your final design parameters.

What's the best way to structure a design spec for product design reviews?

The best way to structure a design spec for product reviews is interrogating design-spec.md across five lenses, yielding a complete specification with parameters, technique selections, token guidance, and a verification checklist.

Does this design spec interrogation approach work without external dependencies?

Yes, the design spec interrogation operates dependency-free, requiring only a design-spec.md input and companion files to produce a structured elevation with traceable parameters and a verification checklist.