[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M788Z2DKPQFSCM5MP5P097VQ":3,"skill-same:01M788Z2DKPQFSCM5MP5P097VQ":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":65},"01M788Z2DKPQFSCM5MP5P097VQ","release-notes-one-pager",null,"Release notes one-page HTML with highlights, Added, Fixed, Breaking changes,\nKnown issues, and Upgrade note. Writes explicit \"None\" style sections\nwhenever the user does not provide details.","bluesman1971\u002Fopen-design","bluesman1971","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96430007?v=4","01M788AK0TR13JE8ART2WNQZV6","01M788AK1PVB085AS9SP38WWGK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Frelease-notes-one-pager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-notes-one-pager\ndescription: |\n  Release notes one-page HTML with highlights, Added, Fixed, Breaking changes,\n  Known issues, and Upgrade note. Writes explicit \"None\" style sections\n  whenever the user does not provide details.\ntriggers:\n  - \"release notes\"\n  - \"changelog\"\n  - \"what's new\"\n  - \"version update\"\n  - \"change log\"\n  - \"release summary\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: engineering\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: true\n    sections: [color, typography, layout, components]\n  example_prompt: \"Write release notes for v2.3.1 with Added, Fixed, Breaking changes, Known issues, and an Upgrade note.\"\n---\n\n# Release Notes One-Pager Skill\n\nProduce a single-page release notes document in HTML.\n\n## Resource map\n\n```\nrelease-notes-one-pager\u002F\n├── SKILL.md                    ← this file\n├── example.html                ← quality bar and style reference\n├── assets\u002F\n│   └── template.html           ← local seed file to copy to project index.html\n└── references\u002F\n    ├── checklist.md            ← P0 \u002F P1 \u002F P2 gates\n    └── layouts.md              ← local section skeletons\n```\n\nDo not write CSS from scratch unless the user explicitly asks for a bespoke structure.\n\n## Workflow\n\n### Step 0 — Pre-flight\n\n1. Read `assets\u002Ftemplate.html`.\n2. Read `references\u002Flayouts.md`.\n3. Read active `DESIGN.md` and map it to the six `:root` variables.\n\n### Step 1 — Start from the shared seed\n\nCopy `assets\u002Ftemplate.html` to project `index.html`.\n\nUpdate:\n- `\u003Ctitle>`\n- topnav logo text\n- topnav link labels (destinations are pre-wired to `#added`, `#fixed`, `#upgrade-note`)\n- topnav CTA label and `href` destination, or omit the topnav CTA entirely if no real destination exists\n- ensure the topnav link targets exist by adding matching section `id` attributes\n\n### Step 2 — Build release-note structure\n\nInside `\u003Cmain id=\"content\">`, compose this section order:\n\n1. Hero (Layout 1 or 2): version, date, one-sentence summary.\n2. Added (use Layout 7 log-list; section root must include `id=\"added\"`).\n3. Fixed (use Layout 7 log-list; section root must include `id=\"fixed\"`).\n4. Breaking changes (use Layout 7 log-list, or one row explicitly saying \"None\"; section root must include `id=\"breaking-changes\"`).\n5. Known issues (Layout 7 or card list; section root must include `id=\"known-issues\"`).\n6. Upgrade note (short steps list or explicit no-action statement; section root must include `id=\"upgrade-note\"`).\n7. Closing CTA strip (Layout 6).\n\nFor every CTA in the emitted HTML (topnav, hero, closing strip), replace both the visible label and the `href` destination with real, safe values. If no real destination is available, omit the CTA entirely—do not use a placeholder such as `href=\"#\"`, a misleading page-anchor, or `REPLACE_WITH_REAL_URL`. Hero CTAs are optional; only add them when real destinations exist.\n\n### Step 3 — Honesty rules for missing details\n\nIf the user does not provide details, do not invent them. Write explicit placeholders:\n\n- Summary: `No summary provided.`\n- Added: `No additions provided`\n- Fixed: `No fixes provided`\n- Breaking changes: `None`\n- Known issues: `None reported`\n- Upgrade note: `No upgrade actions required based on provided information`\n\nIf release version or date is missing, use `—` and label the field rather than guessing.\n\n### Step 4 — Self-check\n\nRun `references\u002Fchecklist.md`. Every P0 must pass.\n\n### Step 5 — Emit artifact\n\nWrap output as:\n\n```\n\u003Cartifact identifier=\"release-notes-one-pager\" type=\"text\u002Fhtml\" title=\"Release Notes\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact. Nothing after `\u003C\u002Fartifact>`.\n","# Release Notes One-Pager Skill\n\nProduce a single-page release notes document in HTML.\n\n## Resource map\n\n```\nrelease-notes-one-pager\u002F\n├── SKILL.md                    ← this file\n├── example.html                ← quality bar and style reference\n├── assets\u002F\n│   └── template.html           ← local seed file to copy to project index.html\n└── references\u002F\n    ├── checklist.md            ← P0 \u002F P1 \u002F P2 gates\n    └── layouts.md              ← local section skeletons\n```\n\nDo not write CSS from scratch unless the user explicitly asks for a bespoke structure.\n\n## Workflow\n\n### Step 0 — Pre-flight\n\n1. Read `assets\u002Ftemplate.html`.\n2. Read `references\u002Flayouts.md`.\n3. Read active `DESIGN.md` and map it to the six `:root` variables.\n\n### Step 1 — Start from the shared seed\n\nCopy `assets\u002Ftemplate.html` to project `index.html`.\n\nUpdate:\n- `\u003Ctitle>`\n- topnav logo text\n- topnav link labels (destinations are pre-wired to `#added`, `#fixed`, `#upgrade-note`)\n- topnav CTA label and `href` destination, or omit the topnav CTA entirely if no real destination exists\n- ensure the topnav link targets exist by adding matching section `id` attributes\n\n### Step 2 — Build release-note structure\n\nInside `\u003Cmain id=\"content\">`, compose this section order:\n\n1. Hero (Layout 1 or 2): version, date, one-sentence summary.\n2. Added (use Layout 7 log-list; section root must include `id=\"added\"`).\n3. Fixed (use Layout 7 log-list; section root must include `id=\"fixed\"`).\n4. Breaking changes (use Layout 7 log-list, or one row explicitly saying \"None\"; section root must include `id=\"breaking-changes\"`).\n5. Known issues (Layout 7 or card list; section root must include `id=\"known-issues\"`).\n6. Upgrade note (short steps list or explicit no-action statement; section root must include `id=\"upgrade-note\"`).\n7. Closing CTA strip (Layout 6).\n\nFor every CTA in the emitted HTML (topnav, hero, closing strip), replace both the visible label and the `href` destination with real, safe values. If no real destination is available, omit the CTA entirely—do not use a placeholder such as `href=\"#\"`, a misleading page-anchor, or `REPLACE_WITH_REAL_URL`. Hero CTAs are optional; only add them when real destinations exist.\n\n### Step 3 — Honesty rules for missing details\n\nIf the user does not provide details, do not invent them. Write explicit placeholders:\n\n- Summary: `No summary provided.`\n- Added: `No additions provided`\n- Fixed: `No fixes provided`\n- Breaking changes: `None`\n- Known issues: `None reported`\n- Upgrade note: `No upgrade actions required based on provided information`\n\nIf release version or date is missing, use `—` and label the field rather than guessing.\n\n### Step 4 — Self-check\n\nRun `references\u002Fchecklist.md`. Every P0 must pass.\n\n### Step 5 — Emit artifact\n\nWrap output as:\n\n```\n\u003Cartifact identifier=\"release-notes-one-pager\" type=\"text\u002Fhtml\" title=\"Release Notes\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact. Nothing after `\u003C\u002Fartifact>`.\n",{"od":23,"name":5,"triggers":38,"description":45},{"mode":24,"preview":25,"platform":28,"scenario":29,"design_system":30,"example_prompt":37},"prototype",{"type":26,"entry":27},"html","index.html","desktop","engineering",{"requires":31,"sections":32},true,[33,34,35,36],"color","typography","layout","components","Write release notes for v2.3.1 with Added, Fixed, Breaking changes, Known issues, and an Upgrade note.",[39,40,41,42,43,44],"release notes","changelog","what's new","version update","change log","release summary","Release notes one-page HTML with highlights, Added, Fixed, Breaking changes,\nKnown issues, and Upgrade note. Writes explicit \"None\" style sections\nwhenever the user does not provide details.\n","main","0467f0e19df12a6994ec7fb20ff6e9e23cd704e7","design-templates\u002Frelease-notes-one-pager","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fbluesman1971","2026-07-09 04:08:20",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":31},[55,58,61],{"tool":56,"command":57},"npx","npx skills add bluesman1971\u002Fopen-design --skill release-notes-one-pager",{"tool":59,"command":60},"bunx","bunx skills add bluesman1971\u002Fopen-design --skill release-notes-one-pager",{"tool":62,"command":63},"pnpm","pnpm dlx skills add bluesman1971\u002Fopen-design --skill release-notes-one-pager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Frelease-notes-one-pager\u002FSKILL.md",[66,72,78,82],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ftemplate.html","ASSET","资产文件",16612,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Frelease-notes-one-pager\u002Fassets\u002Ftemplate.html",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"example.html","REFERENCE","参考文档",6412,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Frelease-notes-one-pager\u002Fexample.html",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fchecklist.md",2790,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Frelease-notes-one-pager\u002Freferences\u002Fchecklist.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Flayouts.md",12710,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Frelease-notes-one-pager\u002Freferences\u002Flayouts.md",[87,96,104,111,118,125],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M78AMRG8NAGKWKNDQE39ZZFQ","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.","MIT","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M78AMKHTFS149JGEYNQM5AXR","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\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M78AMH25JH2SH3AWTRSDCM9F","venice-video","Video generation and transcription workflows via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-video\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M78AMF0M4FFKFWXFJ9NHTF5M","venice-image-generate","Image generation endpoints and available styles via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-image-generate\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":18},"01M78AMCH68X46SHNZVD284KXS","threejs","Three.js skills for creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":18},"01M78AM7P8WSBZDNZZ42BQHGK7","taste","Brief-time anti-AI-slop taste checklist — read the room and set the\ndesign dials BEFORE generating a landing page, portfolio, or redesign,\nso the first draft doesn't need a post-generation rescue. Use at the\nstart of a visual\u002Fcreative brief, not after the artifact exists.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Ftaste\u002FSKILL.md",[],[]]