design-review is agent-read markdown (skill) from codybrom/clairvoyance: Orchestrates a structured design review, running the other skills as a diagnostic funnel from complexity triage to a full red-flags sweep. Use when the user asks for a comprehensive or prioritized design assessment of a file, module, or PR. Not for an open-ended "anything off here?" or "take a look at this" prompt that names no review goal (use red-flags), a plain diff review before merge or analyzing how code changed over time (use code-evolution), or applying one specific lens (use that skill .
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Design Review Orchestrator
When invoked with $ARGUMENTS, scope the entire review to the specified target. Read the target code first, then proceed through the phases below in order. This skill orchestrates other skills from Clairvoyance (https://clairvoyance.fyi). It works best when the full collection is installed.
This skill does not replace individual lenses. It sequences them into a diagnostic funnel that moves from broad to narrow, skipping work when early phases find nothing actionable.
## Diagnostic Funnel
### Phase 1: Complexity Triage
Apply **complexity-recognition** checks against the target.
- Identify the three symptoms: change amplification, cognitive load, unknown unknowns
- Trace any symptoms to root causes: dependencies or obscurity
- Weight findings by the complexity formula: high-traffic code first
This phase determines whether the target has measurable complexity problems. If it does, subsequent phases diagnose where.
### Phase 2: Structural Review
Apply these lenses to the target's module-level architecture:
- **module-boundaries**: Are the boundaries drawn around knowledge domains or around steps in a process?
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_urzb75kye6cbq5fp
GET https://markdownregistry.com/api/v1/resolve?ref=codybrom/clairvoyance/design-review
GET https://markdownregistry.com/api/v1/blob/0e994e7cd6d02a947201d02a47cf4e4a367380cebbbe58f3c6354281e337aa77
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
codybrom/clairvoyance · skills/abstraction-quality/SKILL.md · Evaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow. Use when…
codybrom/clairvoyance · skills/code-evolution/SKILL.md · Evaluates whether changes to existing code maintain or degrade design quality. Use when the user asks to review a diff…
codybrom/clairvoyance · skills/comments-docs/SKILL.md · Reviews comment quality and documentation practices: the four comment types, comments-first workflow, and comment rot…
codybrom/clairvoyance · skills/complexity-recognition/SKILL.md · Diagnoses whether complexity exists and where it comes from, using the three-symptom, two-root-cause framework. Use…
codybrom/clairvoyance · skills/deep-modules/SKILL.md · Measures module depth: whether the interface is simple relative to the implementation behind it. Use when an interface…
codybrom/clairvoyance · skills/design-it-twice/SKILL.md · Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing…
codybrom/clairvoyance · skills/diagnose/SKILL.md · Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone…
codybrom/clairvoyance · skills/error-design/SKILL.md · Reviews error handling and exception design, applying the "define errors out of existence" principle. Use when…
codybrom/clairvoyance · skills/information-hiding/SKILL.md · Checks for information leakage across module boundaries, including temporal decomposition and false encapsulation. Use…
codybrom/clairvoyance · skills/module-boundaries/SKILL.md · Evaluates where module boundaries are drawn and whether modules should be merged or split. Use when deciding whether to…
codybrom/clairvoyance · skills/naming-obviousness/SKILL.md · Reviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit. Use…
plugin87/ux-ui-agent-skills · .claude/skills/design-review/SKILL.md · Review or audit a design/UI across 6 weighted dimensions with Nielsen's 10 heuristics and a prioritized findings table…
fusengine/agents · plugins/design-expert/skills/design-review/SKILL.md · Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile…
toongri/oh-my-toong-playground · skills/design-review/SKILL.md · Use for advisory design review — steelman antithesis and tradeoff tension analysis. Triggers include "design review"…
eugenelim/agent-ready-repo · packs/experience-design/.apm/skills/design-review/SKILL.md · Use when someone asks to critique an existing rendered screen, flow, or mockup for usability, quality-floor, clarity…
flagrare/agent-skills · plugins/flagrare/skills/design-review/SKILL.md · Evaluate and refine UI the way a senior product designer would, visual hierarchy, spacing and rhythm, typographic…
