Skills

Open Design Critique

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

Install

npx skills add feimacode/open-design-agent-kit --skill open-design-critique -g -a claude-code -y
Category
Design
Updated
3d ago
License
MIT
Context cost
Mediumabout 1,883 tokens
Runs scripts
No, instructions only

What it does

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?

<!-- 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 ofSay
artifact, entry, registeredyour design, saved
design system, active design systemyour style (the first time: "a saved style: colours, fonts and spacing")
surface, skill, template, recipekind of design, starting layout, or nothing
workspace, output directoryyour folder, your Open Design folder
bleedprint edge ("a few millimetres extra that the printer trims off")
trim sizefinal size
preflight findings, errors"I checked it and fixed…", "one thing to look at:"
exportsave as PDF, save as an image
inline preview, MCP Appthe preview above

1. Find the artifact

Read the whole SKILL.md on GitHub

More in Design