open-design-new
Start a new design by picking what to make (prototype, app screens, mobile app, slides, document, wireframe, animation, résumé, research, data report, poster, social post, diagram), then build it with the right recipe
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.1k
- Forks
- 104
01 前言 Front Matter
- name
- open-design-new
- description
- Start a new design by picking what to make (prototype, app screens, mobile app, slides, document, wireframe, animation, résumé, research, data report, poster, social post, diagram), then build it with the right recipe
03 SKILL.md 正文
<!-- generated:open-design-agent-kit -->
Start a new design with Open Design.
Request: the rest of the user's message (if there is none, ask the user: "What do you want to make, and what is it for?")
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. Pick the surface
Call list_open_design_skills with surface: "list" to get the kinds of thing Open Design can make (surfaces, each with an id, label and description) and the goals, plain-language aims such as "Promote an event" or "Get hired", each with the surfaces it leads to.
- If the request starts with or clearly names a surface (by id or label, e.g. "wireframe", "diagram", "a poster"), use that surface.
- If it says what the design is for but names no surface ("help me get a UX job"), take the goal that fits.
- If it is empty or too vague to tell, show the user the goals (label and description) and ask one question: "What's it for?". Stop until they answer. Show the surfaces instead only if they ask what kinds of thing you can make.
- Once you have a goal, call
list_open_design_skillswithgoalset to its id and use the surface markeddefault, unless the request points at another of that goal's surfaces. Ask which one only when the goal leads to several and you can't tell.
2. Ask what's missing
Call list_open_design_skills with surface set to the chosen id. The result has the surface's questions and its entries.
Each question has options, a default and what the answer changes. Ask only the ones the request, the conversation and the workspace don't already answer, all at once, in one short message, as multiple choice, and accept "you pick" (then use the question's default). Ask at most three. If the request already says enough, don't ask anything: "a printed A3 poster for our jazz night on 4 May, dark and moody" gets no questions; "a poster for our event" gets a few.
If no design system is active and the request names no look, also call recommend_open_design_design_systems with what you know (the surface, what it's for, how it should feel). If its result has questions, add the ones the request doesn't answer to that same message, still three in total at most, surface questions first. Use its first recommendation as the designSystemId in step 3, and say which style you used and that they can pick another.
Keep the answers by question id, and note anything you decide without asking (a theme, a layout, how many sections) as a short assumption.
3. Build it
- If the surface has a
prompt(for exampleopen-design-posteroropen-design-social-post), follow that flow from its first step with the user's request as the brief. In Copilot Chat it's the/command of the same name; in Claude Code and Codex it's the skill of the same name. - For
app-screens, when the workspace has an app of its own, callscan_open_design_appfirst and show the user what it found; if they agree, save it as the design system so the screens use the app's tokens and components. A redesign of a screen that exists passes its screenshot or URL asbaseScreen. A flow (flow-*entries) plans its screens and links once and passes the sameflowandcollectionIdon every screen. - Otherwise pick the entry that best fits the request. Entries come in curated order: the recipe first, then its remixable example when there is one. To start from a rendered example (an entry with
remixable: true), callremix_open_design_example; otherwise callprepare_open_design_briefwith its id, the brief, any recommendeddesignSystemId, theanswersand yourassumptions(up to six), and follow the general Open Design flow: write the files, register the artifact withbrief(the request in one line astext, plus the sameanswersandassumptions), then check it withcheck_open_design_artifactbefore saying it's done. - When you present the design, list your assumptions in one sentence and invite a change: "I assumed a dark theme and one sign-up button; say if you want otherwise."
Never pick an entry marked stub: true.
04 同仓库更多 Skills
youtube-clipper
YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.
writing-guidelines
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
wpds
WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.
weread-year-in-review-video-template
WeRead-inspired HyperFrames video template for vertical annual reading reports, personal reading dashboards, book-note recaps, and shareable year-in-review stories. Use when users want a 9:16 HTML-to-MP4 reading report with warm paper texture, editorial Chinese typography, book-page metaphors, data highlights, and deterministic motion.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.
web-clone
网站复刻 / 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互/WebGL/Canvas/Three.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树,覆盖静态站 / React-Vue-Next 内容站 / WebGL-Canvas 重前端站三大分支,并强制核对任何 AI 二手分析里的可执行代码。