[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D93EKV2PN716W7P9BPR63R":3,"skill-same:01M7D93EKV2PN716W7P9BPR63R":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":71},"01M7D93EKV2PN716W7P9BPR63R","portfolio-review-round",null,"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.","feimacode\u002Fopen-design-agent-kit","feimacode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264390570?v=4","01M7D3HQSP5EP4Z4JECTSQ7EBD","Feima Code","01M7D3HQT72Q4EVQJP89MR9WP1",1129,"MIT","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Flocal\u002Fskills\u002Fportfolio-review-round\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: portfolio-review-round\nzh_name: \"作品集社区评审\"\nen_name: \"Portfolio Review Round\"\nemoji: \"🔍\"\ndescription: \"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.\"\nen_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.\"\ncategory: web\nscenario: personal\ntags: [\"portfolio review\", \"portfolio critique\", \"roast my portfolio\", \"anonymous portfolio\", \"feedback on my portfolio\", \"作品集评审\"]\ntriggers:\n  - \"portfolio review\"\n  - \"portfolio critique\"\n  - \"roast my portfolio\"\n  - \"anonymise my portfolio\"\n  - \"feedback on my portfolio\"\nod:\n  mode: prototype\n  craft:\n    requires:\n      - typography\n      - accessibility-baseline\n      - anti-ai-slop\n  scenario: personal\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: true\n  example_prompt: \"I want to post my portfolio on r\u002FUXDesign for a critique without my name or my employer on it. Ask about mobile readability and whether the case studies are too long.\"\n---\n\n\u003C!-- Kit skill (openspec add-portfolio-share-and-review). -->\n# Portfolio Review Round\n\nFeedback from strangers, without telling them who you are or where you work, and a visible record of what you changed because of it.\n\n## 1. The review version\n\n1. **Read the library** (`get_open_design_library`) and pick the projects with the designer (usually the ones the portfolio leads with).\n2. **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`.\n3. **Build it** as a portfolio site (the `portfolio-site` structure) with `portfolio: { target: \"\u003Cslug>\" }` 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.\n4. **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.\n5. **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, `\u003Ctitle>`, an Open Graph tag or a link target). Fix them all; publish refuses a review version that still names anyone.\n6. **Publish unlisted** with `publish_open_design_artifact`: a Claude artifact, or a host where the designer adds a password.\n\n## 2. The review post\n\nWrite `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.\n\n## 3. Feedback\n\nWhen 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.\n\nApply 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.\n\n## 4. Follow-up\n\n1. 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).\n2. After revising, make the before\u002Fafter page with `compare_open_design_before_after` (its `collectionId`): the posted pages beside the revised ones, at desktop and phone size.\n3. 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\u002Fafter link. Only points that are resolved.\n\n## Rules\n\n- Never post for the designer; they paste the post and the replies.\n- Nothing stricter than unlisted goes in a review version; internal work stays out.\n- Tokens only, from the design system's `:root`.\n","\u003C!-- Kit skill (openspec add-portfolio-share-and-review). -->\n# Portfolio Review Round\n\nFeedback from strangers, without telling them who you are or where you work, and a visible record of what you changed because of it.\n\n## 1. The review version\n\n1. **Read the library** (`get_open_design_library`) and pick the projects with the designer (usually the ones the portfolio leads with).\n2. **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`.\n3. **Build it** as a portfolio site (the `portfolio-site` structure) with `portfolio: { target: \"\u003Cslug>\" }` 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.\n4. **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.\n5. **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, `\u003Ctitle>`, an Open Graph tag or a link target). Fix them all; publish refuses a review version that still names anyone.\n6. **Publish unlisted** with `publish_open_design_artifact`: a Claude artifact, or a host where the designer adds a password.\n\n## 2. The review post\n\nWrite `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.\n\n## 3. Feedback\n\nWhen 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.\n\nApply 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.\n\n## 4. Follow-up\n\n1. 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).\n2. After revising, make the before\u002Fafter page with `compare_open_design_before_after` (its `collectionId`): the posted pages beside the revised ones, at desktop and phone size.\n3. 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\u002Fafter link. Only points that are resolved.\n\n## Rules\n\n- Never post for the designer; they paste the post and the replies.\n- Nothing stricter than unlisted goes in a review version; internal work stays out.\n- Tokens only, from the design system's `:root`.\n",{"od":24,"name":5,"tags":38,"emoji":45,"en_name":46,"zh_name":47,"category":48,"scenario":34,"triggers":49,"description":7,"en_description":7},{"mode":25,"craft":26,"preview":31,"scenario":34,"design_system":35,"example_prompt":37},"prototype",{"requires":27},[28,29,30],"typography","accessibility-baseline","anti-ai-slop",{"type":32,"entry":33},"html","index.html","personal",{"requires":36},true,"I want to post my portfolio on r\u002FUXDesign for a critique without my name or my employer on it. Ask about mobile readability and whether the case studies are too long.",[39,40,41,42,43,44],"portfolio review","portfolio critique","roast my portfolio","anonymous portfolio","feedback on my portfolio","作品集评审","🔍","Portfolio Review Round","作品集社区评审","web",[39,40,41,50,43],"anonymise my portfolio","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fcontent\u002Flocal\u002Fskills\u002Fportfolio-review-round",104,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit","https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=feima.open-design-agent-kit","https:\u002F\u002Fgithub.com\u002Ffeimacode","2026-11-14 17:32:48",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":36},[61,64,67],{"tool":62,"command":63},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill portfolio-review-round",{"tool":65,"command":66},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill portfolio-review-round",{"tool":68,"command":69},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill portfolio-review-round","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Flocal\u002Fskills\u002Fportfolio-review-round\u002FSKILL.md",[],[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DDR9C4RR6E8F46YBJ8MW64","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DDR57XHXAFBGKX3SYTGSJB","writing-guidelines","Review docs\u002Fprose 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\".","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DDR2RM4F3FM5642JZBGJSF","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fwpds\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7DDQX3G9QDCBV5GGZGQ1NZN","weread-year-in-review-video-template","WeRead-inspired HyperFrames video template for vertical annual reading reports,\npersonal reading dashboards, book-note recaps, and shareable year-in-review\nstories. Use when users want a 9:16 HTML-to-MP4 reading report with warm paper\ntexture, editorial Chinese typography, book-page metaphors, data highlights,\nand deterministic motion.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweread-year-in-review-video-template\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7DDQRGJEHQST6TXDH6ZAV5G","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.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7DDQKADVPZW1Z1HTVKXY542","web-clone","网站复刻 \u002F 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互\u002FWebGL\u002FCanvas\u002FThree.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 \u002F React-Vue-Next 内容站 \u002F WebGL-Canvas 重前端站三大分支，并强制核对任何 AI 二手分析里的可执行代码。","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[]]