AGENT SKILL

portfolio-review-round

A designer's portfolio, anonymised for a community critique (Reddit, a Discord, a mentor group): a review version with neutral labels, published unlisted, a review post with up to three questions, the pasted feedback tracked as comments, and a follow-up showing what changed.

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

01 前言 Front Matter

od
{ "mode": "prototype", "craft": { "requires": [ "typography", "accessibility-baseline", "anti-ai-slop" ] }, "preview": { "type": "html", "entry": "index.html" }, "scenario": "personal", "design_system": { "requires": true }, "example_prompt": "I want to post my portfolio on r/UXDesign for a critique without my name or my employer on it. Ask about mobile readability and whether the case studies are too long." }
name
portfolio-review-round
tags
[ "portfolio review", "portfolio critique", "roast my portfolio", "anonymous portfolio", "feedback on my portfolio", "作品集评审" ]
emoji
🔍
en_name
Portfolio Review Round
zh_name
作品集社区评审
category
web
scenario
personal
triggers
[ "portfolio review", "portfolio critique", "roast my portfolio", "anonymise my portfolio", "feedback on my portfolio" ]
description
A designer's portfolio, anonymised for a community critique (Reddit, a Discord, a mentor group): a review version with neutral labels, published unlisted, a review post with up to three questions, the pasted feedback tracked as comments, and a follow-up showing what changed.
en_description
A designer's portfolio, anonymised for a community critique (Reddit, a Discord, a mentor group): a review version with neutral labels, published unlisted, a review post with up to three questions, the pasted feedback tracked as comments, and a follow-up showing what changed.

03 SKILL.md 正文

<!-- Kit skill (openspec add-portfolio-share-and-review). -->

Portfolio Review Round

Feedback from strangers, without telling them who you are or where you work, and a visible record of what you changed because of it.

1. The review version

  1. Read the library (get_open_design_library) and pick the projects with the designer (usually the ones the portfolio leads with).
  2. Save a review target with save_open_design_portfolio_target: kind: "review", the community's posting rules pasted as notes, the projects, and review: { community, questions, notWanted }. At most three questions: if the designer gives more, ask which three to keep (the tool refuses four). Ask for a sector word per employer or client ("Grocery company, 2025") and save them as review.labels.
  3. Build it as a portfolio site (the portfolio-site structure) with portfolio: { target: "<slug>" } on every page. The brief's "Anonymise this version" part lists each name, email, profile link, employer, client and live link to replace and the neutral label for each. Its own collection, noindex in every page.
  4. Pictures: the check can't see inside images. Look at each one with the designer; a face, a logo, a name or an internal URL in a screenshot gets a redaction box (save_open_design_project, the asset's redactions) before building.
  5. Check with check_open_design_artifact on every page. review-anonymity errors name the page and where the name is (text, alt text, a file name, <title>, an Open Graph tag or a link target). Fix them all; publish refuses a review version that still names anyone.
  6. Publish unlisted with publish_open_design_artifact: a Claude artifact, or a host where the designer adds a password.

2. The review post

Write review-post.md beside the home page, following the brief and the community's rules: one or two lines of context (the role or level they're aiming at, no name), the questions, the feedback not wanted, and the link. Keep it short: posts that ask three sharp questions get answers to them.

3. Feedback

When the designer pastes replies, split them into points and import them with import_open_design_comments, source: "community", each with the page it is about (page: the entry path of that case study) and the reviewer's name if given. Points that fit no page go to the home page. They become open comments: get_open_design_artifact lists them per page.

Apply the changes on the real portfolio (and the review version), and resolve each point with resolvedCommentIds when you register again. Points the designer decides not to act on: say so and resolve them with a one-line reason.

4. Follow-up

  1. Before the first revision, store the posted version as each page's "before": prepare the page's brief again with baseScreen set to its unlisted address (or a screenshot of the posted page).
  2. After revising, make the before/after page with compare_open_design_before_after (its collectionId): the posted pages beside the revised ones, at desktop and phone size.
  3. Draft follow-up-post.md: thank the thread, then one line per resolved point ("Case studies were hard to read on a phone → body text is 18 px and images stack on small screens"), and the before/after link. Only points that are resolved.

Rules

  • Never post for the designer; they paste the post and the replies.
  • Nothing stricter than unlisted goes in a review version; internal work stays out.
  • Tokens only, from the design system's :root.

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