# Open Design Critique

Get a second opinion on an Open Design artifact from a design critic, judged from its...

- Repository: https://github.com/feimacode/open-design-agent-kit (756 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add feimacode/open-design-agent-kit --skill open-design-critique -g -a claude-code -y`
Codex: `npx skills add feimacode/open-design-agent-kit --skill open-design-critique -g -a codex -y`
Cursor: `npx skills add feimacode/open-design-agent-kit --skill open-design-critique -g -a cursor -y`
Gemini CLI: `npx skills add feimacode/open-design-agent-kit --skill open-design-critique -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add feimacode/open-design-agent-kit`

## Description

Get a second opinion on an Open Design artifact from a design critic, judged from its latest check screenshots, the brief and the design system against a fixed rubric, with one verdict (ship, polish or rework) and at most five fixes, use before telling the user a design is done (the open-design skill's check step), and whenever the user asks for a second opinion, another opinion, a critique or a review of an Open Design artifact, or asks "is this good?

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- generated:open-design-agent-kit -->

Get a design critic's second opinion on one Open Design artifact.

Request: the rest of the user's message (if there is none, ask the user: "Which design should get a second opinion?")

**How to talk to the user.** Many people using Open Design don't write code, so:
- Use the user's own words. If they say "artifact", "design tokens" or give a file path, use those terms back; otherwise use the plain words below.
- Keep the machinery out of replies: no tool names, no ids like `od:prototype:poster-hero`, no internal files (`.artifact.json`, `.comments.json`, `config.json`), and not the words "register", "manifest", "sidecar", "entry" or "surface", unless the user used them first.
- Explain a print term the first time it comes up, in one short clause, and not again.
- Say where a file is the way the user would find it ("in your Open Design folder, under seed-swap-flyer"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.
- End each reply that finishes a step with one line on what they can do next, with at most two options ("Want it in Instagram sizes too, or is it ready to print?").

| Instead of | Say |
|---|---|
| artifact, entry, registered | your design, saved |
| design system, active design system | your style (the first time: "a saved style: colours, fonts and spacing") |
| surface, skill, template, recipe | kind of design, starting layout, or nothing |
| workspace, output directory | your folder, your Open Design folder |
| bleed | print edge ("a few millimetres extra that the printer trims off") |
| trim size | final size |
| preflight findings, errors | "I checked it and fixed…", "one thing to look at:" |
| export | save as PDF, save as an image |
| inline preview, MCP App | the preview above |

## 1. Find the artifact

The rest: https://github.com/feimacode/open-design-agent-kit/blob/HEAD/.agents/skills/open-design-critique/SKILL.md