[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7896FVRZFR5APREJP8SNSS1":3,"skill-same:01M7896FVRZFR5APREJP8SNSS1":53},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7896FVRZFR5APREJP8SNSS1","rewrite-plan",null,"Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.","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\u002Fplugins\u002F_official\u002Fatoms\u002Frewrite-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rewrite-plan\ndescription: Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.\nod:\n  scenario: code-migration\n  mode: planning\n---\n\n# Rewrite plan\n\nSpec §20.3 \u002F §21.3.2: scenario 4 (design → deliverable production\ncode) requires a contract-shaped rewrite plan before the agent\nstarts editing files. The plan is **the audit trail** every\nsubsequent stage references; without it the patch path slides into\n\"refactor everything that looks wrong\" and the build breaks in\nunreviewable ways.\n\n## Inputs\n\n- `code\u002Findex.json` from `code-import`.\n- `token-map\u002F*.json` from `token-map`.\n- The active design system DESIGN.md (already in prompt).\n- The user's tune intent (typically a short brief).\n\n## Output\n\n```text\nproject-cwd\u002F\n└── plan\u002F\n    ├── plan.md           # human-readable narrative\n    ├── ownership.json    # { file: '...', layer: 'leaf' | 'shared' | 'route' | 'shell' }\n    ├── steps.json        # ordered { id, files[], rationale, risk: 'low' | 'medium' | 'high' }[]\n    └── meta.json         # { generatedAt, atomDigest, tokenMapDigest }\n```\n\n`steps.json` is the input `patch-edit` reads one entry per\niteration. `ownership.json` is the source of truth for \"which\nfiles belong to a single component vs. shared infrastructure\";\n`patch-edit` refuses to touch a `shell`-tier file unless the\nmatching step has `risk: 'high'` and the user explicitly confirmed.\n\n## Convergence\n\nThe atom completes when `plan.md` is non-empty AND `steps.json`\ncontains at least one step.\n\n## Anti-patterns the prompt fragment forbids\n\n- Plans that include \"rewrite the whole component library\" as a\n  single step. Break into per-component steps.\n- Plans that don't classify ownership.\n- Plans that don't list a `build-test` step at the end.\n\n## Status\n\nReserved id, prompt-only fragment in v1. The component-mapping\nheuristic + ownership classifier land in spec §16 Phase 7.\n","# Rewrite plan\n\nSpec §20.3 \u002F §21.3.2: scenario 4 (design → deliverable production\ncode) requires a contract-shaped rewrite plan before the agent\nstarts editing files. The plan is **the audit trail** every\nsubsequent stage references; without it the patch path slides into\n\"refactor everything that looks wrong\" and the build breaks in\nunreviewable ways.\n\n## Inputs\n\n- `code\u002Findex.json` from `code-import`.\n- `token-map\u002F*.json` from `token-map`.\n- The active design system DESIGN.md (already in prompt).\n- The user's tune intent (typically a short brief).\n\n## Output\n\n```text\nproject-cwd\u002F\n└── plan\u002F\n    ├── plan.md           # human-readable narrative\n    ├── ownership.json    # { file: '...', layer: 'leaf' | 'shared' | 'route' | 'shell' }\n    ├── steps.json        # ordered { id, files[], rationale, risk: 'low' | 'medium' | 'high' }[]\n    └── meta.json         # { generatedAt, atomDigest, tokenMapDigest }\n```\n\n`steps.json` is the input `patch-edit` reads one entry per\niteration. `ownership.json` is the source of truth for \"which\nfiles belong to a single component vs. shared infrastructure\";\n`patch-edit` refuses to touch a `shell`-tier file unless the\nmatching step has `risk: 'high'` and the user explicitly confirmed.\n\n## Convergence\n\nThe atom completes when `plan.md` is non-empty AND `steps.json`\ncontains at least one step.\n\n## Anti-patterns the prompt fragment forbids\n\n- Plans that include \"rewrite the whole component library\" as a\n  single step. Break into per-component steps.\n- Plans that don't classify ownership.\n- Plans that don't list a `build-test` step at the end.\n\n## Status\n\nReserved id, prompt-only fragment in v1. The component-mapping\nheuristic + ownership classifier land in spec §16 Phase 7.\n",{"od":23,"name":5,"description":7},{"mode":24,"scenario":25},"planning","code-migration","main","0467f0e19df12a6994ec7fb20ff6e9e23cd704e7","plugins\u002F_official\u002Fatoms\u002Frewrite-plan","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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add bluesman1971\u002Fopen-design --skill rewrite-plan",{"tool":39,"command":40},"bunx","bunx skills add bluesman1971\u002Fopen-design --skill rewrite-plan",{"tool":42,"command":43},"pnpm","pnpm dlx skills add bluesman1971\u002Fopen-design --skill rewrite-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Frewrite-plan\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"open-design.json","REFERENCE","参考文档",824,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Frewrite-plan\u002Fopen-design.json",[54,63,71,78,85,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]