AGENT SKILL

open-design-portfolio

Build a designer's portfolio from their real work — a work library of projects, facts and images (screenshots, Figma frames, live pages, kit designs) entered once, with privacy levels, redaction and alt text, then a portfolio site or interview deck from it — use whenever the user wants to build, update or tidy a design portfolio, case studies or a body of work to show (job hunting, client pitches, Dribbble or Behance, a portfolio review, a promotion packet), or wants to add a project, screenshots, Figma frames or a live product to their portfolio, even if they don't mention Open Design

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1.1k
Forks
104

01 前言 Front Matter

name
open-design-portfolio
description
Build a designer's portfolio from their real work — a work library of projects, facts and images (screenshots, Figma frames, live pages, kit designs) entered once, with privacy levels, redaction and alt text, then a portfolio site or interview deck from it — use whenever the user wants to build, update or tidy a design portfolio, case studies or a body of work to show (job hunting, client pitches, Dribbble or Behance, a portfolio review, a promotion packet), or wants to add a project, screenshots, Figma frames or a live product to their portfolio, even if they don't mention Open Design

03 SKILL.md 正文

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

Build the designer's work library: their projects, the facts about each and their images, entered once for every portfolio output.

Request: the rest of the user's message (if there is none, ask the user: "What do you design, and which projects should go in?")

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. Read the library first

Call get_open_design_library. If it is empty, start it; if it has projects, work on what the request names and keep everything else as it is.

2. The designer and their projects

  • Owner. Save the designer's name and role with save_open_design_project (owner). Add location, a short bio, email and links only if they gave them.
  • One project at a time. A new project needs a title, their role on it, and a privacy level. Ask which level fits in plain words: "Can this be shown publicly, only to people you send it to, or is it under NDA or internal?" (public, unlisted, internal).
  • Facts come from the designer. Ask for what the reply says is missing: the problem, constraints, team, dates, two or three key decisions with the options they rejected and why, and the outcomes. Ask a few questions at a time, not a form.
  • Never invent facts. No made-up metrics, percentages, team members, clients, dates or quotes. If they don't know a number, record the outcome as qualitative (no number) or estimated if they give a rough one. A missing fact stays missing: say so.

3. Bring the work in

Call import_open_design_work with the project slug and its sources:

  • files they put in the workspace or attached (file, or data for an attachment);
  • Figma frames (figma with the frame link; if the reply says so, read the frame with the Figma connector's get_screenshot and pass the image as data);
  • live products (url), captured at desktop and phone size;
  • kit designs (design).

Look at each image the reply shows and save a short, specific alt text draft (assets: [{ id, alt }]): what the screen shows and why it matters, not "screenshot". Then show the drafts to the designer and save confirmAlt: true for the ones they accept.

If an image shows something private (a customer name, real account numbers, an internal tool), ask whether to blur that part and save redactions boxes for it, or make the image internal.

4. Your own style

If the library has no style, offer once to build one from the designer's current portfolio site, their Figma or Canva files, or screenshots of their work (the open-design-design-system-from-url skill and extract_open_design_design_system), then save it with save_open_design_project (style). A portfolio in the designer's own style reads as theirs; the kit's defaults read as everyone's.

5. Report

Tell the designer, in plain words, which projects are in, what each still lacks (from the reply), and which images are private or blurred. Offer one next step that fits what they're doing: a portfolio site, an interview deck, or a version for one job or client.

6. Build from the library

  • A portfolio site (home, one case study per project, about): the portfolio-site skill. Plan the pages as one collection with flow.kind: "site" (home is the index screen), and pass portfolio: { projects } to every page's prepare_open_design_brief and registration.

  • An interview deck for a 30, 45 or 60 minute slot: the portfolio-interview-deck skill, with portfolio: { projects, length }.

  • A version for one situation (a job ad, a client, a school's rules, promotion criteria): save it as a target with save_open_design_portfolio_target (name, kind, the pasted text as notes, the projects). Show the suggested order and the words each project matched; the designer decides. Then build each of its outputs with portfolio: { target }: the site, the portfolio-pdf skill for a PDF or a school's image set, or the interview deck. Its privacy ceiling holds at export and publish: an internal version (a promotion packet) is a file only; an unlisted one is a Claude artifact or a host where the designer adds a password, which the kit never sets itself.

  • Posting a project (Dribbble, Behance, LinkedIn, Instagram, Upwork, Contra, Fiverr): the portfolio-share-pack skill, one project with portfolio: { projects: ["<slug>"] } and a share format per piece (dribbble-shot, behance-cover, behance-module, linkedin-document, ig-portrait, marketplace-cover). Public work only. Screens with a device come framed. The post text is drafted from the facts.

  • A community critique (Reddit, a Discord, a mentor group): the portfolio-review-round skill. A review target makes an anonymised, unlisted version (the check and publish refuse any name, employer or link left in it) and review-post.md with at most three questions; pasted replies go in with import_open_design_comments (source: "community") and a follow-up shows what changed.

The brief lists each project's facts, the pictures it may show with their markup, and the process records the kit has; build only from those. The check then reports what a reviewer would notice first: the first screen on a phone, case-study length and summary, unconfirmed alt text, page weight, broken live links, anything internal, and a talk that runs long.

04 同仓库更多 Skills

feimacode
feimacode/open-design-agent-kit

youtube-clipper

YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

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".

★ 1.1k
feimacode
feimacode/open-design-agent-kit

wpds

WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

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.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

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.

★ 1.1k
feimacode
feimacode/open-design-agent-kit

web-clone

网站复刻 / 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互/WebGL/Canvas/Three.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树,覆盖静态站 / React-Vue-Next 内容站 / WebGL-Canvas 重前端站三大分支,并强制核对任何 AI 二手分析里的可执行代码。

★ 1.1k