design-reviewer

Reviews proven product specs to detect inconsistent behavior among same-kind elements.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/happysasha18/live-spec --skill design-reviewer-happysasha18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-reviewer
Source: https://github.com/happysasha18/live-spec/tree/main/skills/design-reviewer
Command: npx skills add https://github.com/happysasha18/live-spec --skill design-reviewer-happysasha18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A spec can be internally consistent yet still hide design flaws: two elements a user treats the same way may behave differently, and no sentence in the spec ever groups them, so no proof pass can catch the divergence. This Skill reads a spec that has already passed formal verification and questions the design itself, surfacing undeclared same-kind groupings and behavioral divergences as recommendations or questions. ## Core Features & Use Cases - Similarity lens: Builds its own inventory of elements a person acts on, writes role sentences, proposes same-kind groups, and checks whether members behave alike. - Standing lenses: Runs motion-parity checks (entry mirrors exit, every object type and position behaves alike) and named-part checks (guarantees read across viewport bands, user states, locales) without waiting for matching role sentences. - Non-blocking findings: Every finding is a recommendation or a question with two concrete objects, a shared role, and a recommended default; it never blocks a landing. - Use Case: After the prover verifies a photo-gallery spec, run this Skill to catch that tapping a portrait opens it full-screen while the cover photo, used the same way, has no defined behavior. ## Quick Start Ask the agent to review the design of the proven spec, for example: "review the design of this spec and check whether similar elements behave the same."

Frequently Asked Questions about design-reviewer

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

FAQPage Schema
How do I check whether similar features in a spec behave consistently?▼

Run a design review pass after the spec passes formal verification. It builds an inventory of elements a person acts on, groups them by role sentences, and flags members missing behaviors their siblings carry.

What is the difference between a spec prover and a design review?▼

A prover checks that the spec holds together as written, catching missing states and false claims. A design review judges the design behind a proven spec, finding same-kind divergences no sentence ever declared.

Does a design review finding block a commit or release?▼

No. Every finding is a recommendation or a question carrying two concrete objects and a recommended default. The loop is bounded at three progressing rounds and never holds up a landing.

When should the design review run in a spec-driven pipeline?▼

It runs right after the prover's pass at the prove station: a full review after FULL mode, a scoped review when a surface is added, and it stands down at feature intake and the push gate.

What are the limitations of a design review on a spec?▼

It cannot judge a spec that does not yet hold together as written, since proving the text is the prover's job. It also stays silent on weak signals, unclear groupings, and differences a spec sentence already decides.