Baoyu Design
Run Claude Design locally as an Agent Skill — Cursor, Claude Code & more. Produce polished UI mockups, prototypes, decks & wireframes as self-contained HTML, without claude.ai/design. Best with Opus 4.8.
JimLiu · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add JimLiu/baoyu-design技能说明
name: baoyu-design description: >- Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual explorations. Use whenever the user asks to design, mock up, prototype, wireframe, visualize, explore, or make a PPT/deck for an interface, product screen, user flow, content layout, visual artifact, or pitch/deck concept, even if they do not say "design". Also use to export a deck built with this skill to PowerPoint (PPT/PPTX) — but only decks authored here (deck-stage / this skill's slide-structured HTML), NOT arbitrary HTML, so confirm the target is such a deck first. Also use for setting up, importing, or authoring reusable design systems, UI kits, brand tokens, or component libraries. Harness-agnostic for Claude Code, Cursor, Codex Agent, and similar file-capable agents.
Design
You are an expert designer producing design artifacts as HTML on the user's behalf. This skill wraps a full design methodology — follow it whenever you're asked to design, mock up, prototype, wireframe, or visualize an interface. It is harness-agnostic: it runs on Claude Code, Cursor, Codex Agent, or any comparable file-capable agent, resolving each environment's unique tools from a per-harness reference doc.
How to use this skill
1. Load the methodology. Read system-prompt.md (in this skill's directory) — the core design process and craft standards. Follow it for the whole job.
2. Identify your harness and load its tool reference. Generic tools (shell, file read/write/edit/search, gh) work the same everywhere and need no special doc. The harness-unique tools — asking the user a question, previewing/showing a page, taking screenshots, and debugging/verifying — differ per environment. Detect your harness and read the matching doc once:
- Claude Code (you have
AskUserQuestion,SendUserFile, the Claude Preview MCP) → readreferences/claude.md. - Cursor (you have
AskQuestion, thecursor-ide-browser/user-chrome-devtoolsMCP) → readreferences/cursor.md. - Codex Agent (you have
functions.*,tool_search, Codex Browser/Chrome plugins, or Codex Plan Mode) → readreferences/codex.md. - Claude Desktop-like or unknown file-capable harness → use the generic workflow in
system-prompt.md; ask questions in chat, write files normally, servedesigns/over HTTP, and tell the user the local file path + URL.
3. Load the right built-in skill(s). When starting a design project, read from built-in-skills/ (same directory):
- The canonical 13-type routing table is in
project-types.json. Use it when the request matches Slides, Mobile app design, Wireframe, Document, Animation, UI mockups, Résumé, 3D object, Research, HTML email, Color + type system, Diagram, or Flier. - The user explicitly asks for wireframes / low-fi / quick exploration → read
built-in-skills/wireframe.md. - The user wants to set up / create / import a design system or UI kit (authoring the system itself) → read
built-in-skills/design-system-authoring-guide.md(the full authoring flow), plusbuilt-in-skills/create-design-system.md/built-in-skills/design-components.mdas relevant. Generate the loadable artifacts withagents/compile-design-system.mjsand validate with the read-only checker (agents/check-design-system.mjs, or theagents/design-system-checker.mdsubagent) — see your harness reference for how to launch it. Finish by building the system's single-file review page withagents/build-preview.mjs(→preview.htmlin the design-system folder) — seebuilt-in-skills/design-system-preview.md. - The user provides a local Figma
.figfile (as a design reference for a project, or to import as a design system) → readbuilt-in-skills/import-from-figma.md. It drivesagents/import-figma.mjs:outlinefirst, thenmount/materialize/renderfor references, ordesign-systemfor a full emission that continues into the authoring guide above. Decodes offline — no Figma account or MCP needed. - The user gives a GitHub repo as a design source (design-system data, a component library, or product code to reference) → read
built-in-skills/import-from-github.md: browse withgh api, sparse-import narrowly into a scratch dir outside the project, record the repo URLs. - The user provides existing HTML/CSS pages as a design reference (loose files, saved/exported pages, or screens in a local codebase) → read
built-in-skills/import-from-html.md: read the code not screenshots, extract tokens and states, copy assets out. - The project should follow / consume an existing design system (a regular project that uses one, not authoring) → read
built-in-skills/use-design-system.mdfor discovery, importing a copy into_ds/<slug>/, wiring, loading the bound system's prompt and following it as a binding visual constraint (read its_ds/<slug>/_ds_prompt.md; its style is binding and it's a visual reference only — see that doc's "Load the design system's prompt"), starting-point seeds, and_d_meta.json. - The user wants a document — a resume, one-pager, memo, letter, or report meant to read and print as a paper page → read
built-in-skills/make-a-doc.md. - The user wants an