Agent skill

Design Review Panel

by matthiasn in matthiasn/lotti

Run a multi-agent design review on a UI surface — capture reproducible baseline screenshots, then rate them with a panel of design experts (one agent per craft dimension) and, optionally, a panel of…

GPL-3.0Auto-check passedMedia & Creative

Install Design Review Panel

skills CLI
$ npx skills add matthiasn/lotti --skill design-review-panel -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install matthiasn/lotti design-review-panel --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/matthiasn/lotti.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/design-review-panel .claude/skills/design-review-panel && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-review-panel
GitHub stars
1.2k
Token cost
~1.6k tokens
SKILL.md length
660 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
GPL-3.0

At a glance

Run a multi-agent design review on a UI surface — capture reproducible baseline screenshots, then rate them with a panel of design experts (one agent per craft dimension) and, optionally, a panel of…

  • Works in 5 steps: Baseline screenshot first. Use the… → Rate the baseline with BOTH panels up… → Iterate with the expert panel until… → …
  • Redesigning a screen/modal/dialog and the user wants grounded
  • SKILL.md covers The loop, The two panels, Grounding rules (give these to… and Running it, plus 1 more section
  • Runs JavaScript scripts from its folder

What it does

Design Review Panel is an agent skill from matthiasn/lotti. Run a multi-agent design review on a UI surface — capture reproducible baseline screenshots, then rate them with a panel of design experts (one agent per craft dimension) and, optionally, a panel of user personas with different cognitive styles. Iterate implement → re-screenshot → re-rate until every panel hits a numeric target (e.g. avg ≥8/10). Use when polishing or redesigning a screen/modal/dialog and the user wants grounded, scored design feedback ("summon the design panel", "rate this with the experts", "run…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `panel_workflow.js`).

It sits in Media & Creative, covering Design review and critique. The repository describes itself as: A private logbook with a staff of personal AI assistants. Agents read what you record and propose what to do next — you approve the changes. End-to-end encrypted sync between… The licence is GPL-3.0.

When your agent uses it

  • Redesigning a screen/modal/dialog and the user wants grounded
  • Scored design feedback (summon the design panel
  • Rate this with the experts
  • Run the persona panel)

Example prompts

  • “summon the design panel”
  • “rate this with the experts”
  • “run the persona panel”
  • “/design-review-panel”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Baseline screenshot first. Use the app-screenshots skill / the
  2. Rate the baseline with BOTH panels up front. Get grounded starting
  3. Iterate with the expert panel until experts clear the bar. Bring the
  4. Adjudicate genuine tradeoffs with the user (AskUserQuestion) instead
  5. Harden to PR-ready once converged: tests, l10n, feature README, a

What it can do on your machine

Read from SKILL.md and the folder at commit a80a35f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (JavaScript), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design Review Panel loads about 1.6k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 660 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from matthiasn/lotti at commit a80a35f, republished under its GPL-3.0 licence (© matthiasn). 660 words, ~1,591 tokens.

Download SKILL.mdSave it as .claude/skills/design-review-panel/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
design-review-panel
description
Run a multi-agent design review on a UI surface — capture reproducible baseline screenshots, then rate them with a panel of design experts (one agent per craft dimension) and, optionally, a panel of user personas with different cognitive styles. Iterate implement → re-screenshot → re-rate until every panel hits a numeric target (e.g. avg ≥8/10). Use when polishing or redesigning a screen/modal/dialog and the user wants grounded, scored design feedback ("summon the design panel", "rate this with the experts", "run the persona panel").
argument-hint
<surface to review, e.g. 'AI popup model picker'>

Design Review Panel

A repeatable, grounded process for design polish and redesign work. It pairs two parallel agent panels — design experts (craft dimensions) and, optionally, user personas (cognitive styles) — and drives them against real screenshots the agents actually Read, iterating to a numeric target.

This is how the user wants UI/design tasks run. The numeric target is the success condition: keep iterating until both panel averages clear the bar (the workflow's cleared flag).

The loop

mermaid
stateDiagram-v2
    [*] --> Baseline
    Baseline --> RateBaseline: capture reproducible PNGs (app-screenshots)
    RateBaseline --> Implement: both panels score the current state
    Implement --> Rescreenshot: apply highest-leverage fixes (design-system tokens only)
    Rescreenshot --> Rerate: regenerate the SAME shots
    Rerate --> Implement: either panel average < target
    Rerate --> Harden: both panel averages ≥ target
    Harden --> [*]: tests, l10n, README, changelog.d fragment, analyzer clean, PR
  1. Baseline screenshot first. Use the app-screenshots skill / the test/test_utils/screenshot_harness.dart captureInApp harness to render the surface at phone and desktop, dark (add light + large-text shots when accessibility is in scope). Reproducible PNGs are mandatory — the panels are only as honest as the pixels they read.
  2. Rate the baseline with BOTH panels up front. Get grounded starting scores before changing anything. Never carry over scores from a previous session — re-rate on a freshly regenerated PNG every time (grounded re-rating reliably deflates inflated prior numbers).
  3. Iterate with the expert panel until experts clear the bar. Bring the persona panel into the loop once experts reach ≥8 so the two converge together. Each iteration: implement → regenerate the exact same screenshots → re-rate.
  4. Adjudicate genuine tradeoffs with the user (AskUserQuestion) instead of silently picking a side — before declaring a conflict irreducible, hunt for a both-sides fix (one change that serves two opposed reviewers).
  5. Harden to PR-ready once converged: tests, l10n, feature README, a changelog.d/ fragment (never CHANGELOG.md or the flatpak metainfo directly — those belong to the release), analyzer zero-warning, formatter, PR on latest main.

The two panels

Design-expert panel (always)

One agent per craft dimension. Default lenses (adapt to the surface):

  • Visual hierarchy / IA — what reads primary/secondary/tertiary; scent.
  • Design-system consistency — tokens, spacing rhythm, component reuse; does the surface feel like ONE system or bolted-together parts.
  • Color / contrast / semantics — palette restraint, status-by-more-than-color.
  • Typography — ramp, weight contrast, measure, rhythm.
  • Spacing / density / rhythm — padding, alignment, optical balance.
  • Interaction / task-flow — taps-to-goal, affordances, dead-ends, the "1-tap to the common case" promise.
User-persona panel (on by default — pass includePersonas: false to skip)

Different cognitive styles stress the surface as real users:

  • ADHD / clutter-sensitive — needs "what now" instant; abandons noise.
  • Power user — counts seconds, allergic to wasted space/steps.
  • Low-vision / low-confidence — large text, strong contrast, fears irreversible taps.
  • Minimalist aesthete — wants calm, uniform, restrained.
  • Non-technical novice / second-language — reads copy literally; jargon and ambiguous labels break them.

Personas return a verdict (would-use / would-struggle / would-abandon) plus blockers / frictions / delights. Experts return a 1–10 score per surface plus severity-tagged issues with evidence + a concrete fix.

Show full SKILL.md (242 more words)Show less

Grounding rules (give these to every agent verbatim)

  • Read every screenshot path. Base every visual claim on actual pixels. Panels hallucinate failures when they don't — forbid it.
  • No invented measurements. Don't fabricate px gaps or contrast ratios; if you can't measure it, describe it qualitatively and tie it to something visible.
  • Every issue carries evidence — a named screenshot ("picker_desktop: …") or a file:line. Code claims (e.g. "hardcodes spacing") require Reading the file and citing the line.
  • Grumpy, calibrated scoring: 10 = ship-grade, nothing to fix; 8 = good, only polish left; 6 = usable but rough; 4 = several real problems; ≤3 = broken. Do not be generous.
  • List test-rig artifacts to IGNORE (stand-in nav bars, tofu glyphs, folded-hour bands) so the panel doesn't score the harness.

Running it

Drive both panels as a Workflow so the agents run in parallel and return structured scores. A parameterized reference script lives next to this file: panel_workflow.js — pass args describing the surface, screenshot paths, source files, expert lenses, personas, and includePersonas / target. Adapt the lenses and persona prompts to the surface; keep the schema and the iterate-to-target loop.

Workflow({ scriptPath: ".claude/skills/design-review-panel/panel_workflow.js", args: { ...see file header... } })

Read the returned synthesis, apply the must-fixes, regenerate the same screenshots, and re-run until the returned cleared is true (both panel averages meet the target). Then delete the scratch capture test and test/screenshots/ (per the app-screenshots skill) unless the user asks to keep them.

See also

  • app-screenshots — the reproducible capture harness this skill depends on.
  • AskUserQuestion — for adjudicating genuine, irreducible design tradeoffs.

© matthiasn, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/design-review-panel of matthiasn/lotti.

  • SKILL.md
  • panel_workflow.js

Open the folder on GitHubat commit a80a35f

Compare with similar skills

Design Review Panel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design Review Panel compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design Review Panel this skillmatthiasn/lotti1.2k—~1.6kAutomated safety check: PassGPL-3.0
Consult ClaudeEpicenterHQ/epicenter4.8k—~2kAutomated safety check: PassCustom licence
System Atlasinkboard/system-atlas430—~2.3kAutomated safety check: PassMIT
Design Image Studiokangarooking/design-image-studio102—~1.5kAutomated safety check: PassMIT
Kicad Reviewmixelpixx/Konnect927—~3.2kAutomated safety check: PassAGPL-3.0
Design AuditUniClipboard/UniClipboard1.9k—~554Automated safety check: PassAGPL-3.0

Similar skills

  • Consult Claude

    EpicenterHQ/epicenter

    Assign Claude Code a read-only investigation, recommendation, or finished text draft.

    4.8k GitHub stars~2k tokensUpdated 3 days ago
    Media & CreativeAuto-check passed
  • System Atlas

    inkboard/system-atlas

    Build and maintain an explorable, progressively-disclosed isometric "atlas" of a system's architecture — an interactive page (hover to read, click to pin, go inside for steps, moving data packets…

    430 GitHub stars~2.3k tokensUpdated 1 mo ago
    Media & CreativeAuto-check passed
  • Design Image Studio

    kangarooking/design-image-studio

    Directly generate design-oriented AI images with strong creative direction and prompt engineering.

    102 GitHub stars~1.5k tokensUpdated 5 mo ago
    Media & CreativeAuto-check passed
  • Kicad Review

    mixelpixx/Konnect

    Design review and validation workflow for KiCAD projects via MCP tools.

    927 GitHub stars~3.2k tokensUpdated 5 days ago
    Media & CreativeAuto-check passed
  • Design Audit

    UniClipboard/UniClipboard

    定期审计代码库的工程设计问题(高心智复杂度、单一真相源被破坏、catch-all 胖接口、死代码、散落魔法字面量、泄漏抽象、资源生命周期靠环形缓冲)与可优化点,范围限定为自上次审计以来的 git churn,每条发现都落到 file:line 并对照本项目自己的 VISION.md / 各级 AGENTS.md / memory…

    1.9k GitHub stars~554 tokensUpdated today
    Media & CreativeAuto-check passed
  • L1 AI Design Review

    PaperMoonuu/Design-workflow-skills

    L1 × AI 设计评审:对已完成的单页、局部 UI 设计稿进行小型迭代评审,识别影响面、状态遗漏、文案与一致性风险,并给出 P0/P1/P2 建议和验收清单。用户提供 Figma 链接、截图、前后设计稿或可评审原型,并要求设计走查、风险评审或开发前 UI 检查时使用;不用于设计前方案预检、完整多页面流程或 L2 开发交付。

    316 GitHub stars~492 tokensUpdated 19 days ago
    Media & CreativeAuto-check passed

More from matthiasn/lotti

All 10 skills in this repo
  • Add, complete, or audit a locale across a Flutter application's ARB catalogs and a localized Docusaurus manual, including generated localization code, locale selectors, native platform declarations…

    1.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Maintain a Docusaurus product manual whose prose, navigation, localized page trees, screenshots, coverage metadata, and release build must stay aligned with the application.

    1.2k GitHub stars~930 tokensUpdated today
    Auto-check passed
  • App Screenshots

    matthiasn/lotti

    Capture in-app screenshots of a widget or flow at mobile + desktop sizes — offline, deterministic, real fonts and icons — using the reusable screenshot harness.

    1.2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Beads

    matthiasn/lotti

    A skill your agent uses for authorized Lotti maintainer work that needs private durable task tracking, issue dependencies, blocker management, multi-session handoff, or shared agent memory.

    1.2k GitHub stars~589 tokensUpdated today
    Auto-check passed
  • Release

    matthiasn/lotti

    Cut a Lotti release — assemble the changelog.d/ fragments into CHANGELOG.md and the Flathub metainfo, bump the version, open the release PR, then tag.

    1.2k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Tutorial Videos

    matthiasn/lotti

    Build, debug, extend, localize, or publish the automated tutorial videos — the workbench that drives the real Linux app under Xvfb (virtual mic, live Voxtral transcription, task-agent proposals)…

    1.2k GitHub stars~2.2k tokensUpdated today
    Auto-check: notes

Questions about Design Review Panel

What does Design Review Panel do?

Run a multi-agent design review on a UI surface — capture reproducible baseline screenshots, then rate them with a panel of design experts (one agent per craft dimension) and, optionally, a panel of…. Design Review Panel is an agent skill from matthiasn/lotti. Run a multi-agent design review on a UI surface — capture reproducible baseline screenshots, then rate them with a panel of design experts (one agent per craft dimension) and, optionally, a panel of user personas with different cognitive styles.

When should I use Design Review Panel?

Design Review Panel fits situations like: redesigning a screen/modal/dialog and the user wants grounded; scored design feedback (summon the design panel; rate this with the experts; run the persona panel).

How do I install Design Review Panel in Claude Code?

Run `npx skills add matthiasn/lotti --skill design-review-panel -a claude-code`. Or copy the skill folder (.claude/skills/design-review-panel in matthiasn/lotti) into .claude/skills/design-review-panel in your project. Claude Code loads it when a task matches its description.

How do I install Design Review Panel in Codex?

Run `npx skills add matthiasn/lotti --skill design-review-panel -a codex`. Or copy the skill folder (.claude/skills/design-review-panel in matthiasn/lotti) into .agents/skills/design-review-panel in your project. Codex loads it when a task matches its description.

Can I use Design Review Panel in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add matthiasn/lotti --skill design-review-panel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-review-panel, .gemini/skills/design-review-panel, .github/skills/design-review-panel and .opencode/skills/design-review-panel in your project.

What does Design Review Panel need to run?

Going by SKILL.md and its folder, Design Review Panel needs JavaScript for the scripts in its folder. Our summary lists: Node.js.

Does Design Review Panel access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design Review Panel safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design Review Panel use?

Design Review Panel is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design Review Panel use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design Review Panel?

Skills that share tags, products or a category with Design Review Panel: Consult Claude (EpicenterHQ/epicenter, 4.8k stars), System Atlas (inkboard/system-atlas, 430 stars), Design Image Studio (kangarooking/design-image-studio, 102 stars) and Kicad Review (mixelpixx/Konnect, 927 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design Review Panel?

matthiasn (a GitHub user) maintains it in matthiasn/lotti, which has 1,199 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.

Source: matthiasn/lotti on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.