[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D57KDH7B3DP25PAB2WC93B":3,"skill-same:01M7D57KDH7B3DP25PAB2WC93B":74},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":73},"01M7D57KDH7B3DP25PAB2WC93B","blog-post",null,"A long-form article \u002F blog post — masthead, hero image placeholder,\narticle body with figures and pull quotes, author byline, related posts.\nUse when the brief asks for \"blog\", \"article\", \"post\", \"essay\", or\n\"case study\".","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\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fblog-post\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blog-post\ndescription: |\n  A long-form article \u002F blog post — masthead, hero image placeholder,\n  article body with figures and pull quotes, author byline, related posts.\n  Use when the brief asks for \"blog\", \"article\", \"post\", \"essay\", or\n  \"case study\".\ntriggers:\n  - \"blog\"\n  - \"blog post\"\n  - \"article\"\n  - \"essay\"\n  - \"case study\"\n  - \"newsletter\"\n  - \"博客\"\n  - \"文章\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: marketing\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: true\n    sections: [color, typography, layout, components]\n  craft:\n    requires: [typography, typography-hierarchy, typography-hierarchy-editorial, rtl-and-bidi]\n---\n\n# Blog Post Skill\n\nProduce a single long-form article page — editorial layout, no chrome.\n\n## Workflow\n\n1. **Read the active DESIGN.md** (injected above). Lean into the typography\n   tokens — long-form is 70% type, 20% image, 10% chrome.\n2. **Pick the topic** from the brief and write a real article — at least 600\n   words across 4–6 H2 sections. No lorem ipsum.\n3. **Sections**, in order:\n   - **Masthead** — small wordmark + 4–6 nav links, plain.\n   - **Article header** — category eyebrow, headline (display token, large),\n     deck (1–2 sentence subhead), author name + role + date.\n   - **Hero image** — a 16:9 placeholder block using a DS-tinted gradient or\n     solid fill (no external images). Add a 1-line caption underneath.\n   - **Body** — alternating prose paragraphs with at least:\n     - 1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under `dir=\"rtl\"`).\n     - 1 figure (image placeholder + caption).\n     - 1 list (numbered or bulleted).\n     - 1 inline blockquote.\n   - **Author footer** — author avatar (initials in a circle), bio paragraph.\n   - **Related** — 3 cards linking to other posts. Each card: tiny image\n     block, title, 1-line excerpt, date.\n4. **Write** a single HTML document:\n   - `\u003C!doctype html>` through `\u003C\u002Fhtml>`, CSS inline.\n   - Article body uses the DS body font, centered, max-width per DS layout\n     rule (typically 680–720px).\n   - Drop caps (`first-letter`) only if the DS mood is editorial \u002F serif —\n     skip on tech-y DSes.\n   - `data-od-id` on the headline, hero, body, pull quote, related grid.\n5. **Self-check**:\n   - Type hierarchy is unambiguous — H1 is clearly the headline; H2s are\n     section dividers; pull quotes do not compete with H1.\n   - Line length 60–75 chars for body prose.\n   - Accent appears at most twice (eyebrow + pull-quote rule, or one link).\n   - The page reads like a magazine, not a marketing landing.\n\n## Output contract\n\nEmit between `\u003Cartifact>` tags:\n\n```\n\u003Cartifact identifier=\"post-slug\" type=\"text\u002Fhtml\" title=\"Article Title\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact, nothing after.\n","# Blog Post Skill\n\nProduce a single long-form article page — editorial layout, no chrome.\n\n## Workflow\n\n1. **Read the active DESIGN.md** (injected above). Lean into the typography\n   tokens — long-form is 70% type, 20% image, 10% chrome.\n2. **Pick the topic** from the brief and write a real article — at least 600\n   words across 4–6 H2 sections. No lorem ipsum.\n3. **Sections**, in order:\n   - **Masthead** — small wordmark + 4–6 nav links, plain.\n   - **Article header** — category eyebrow, headline (display token, large),\n     deck (1–2 sentence subhead), author name + role + date.\n   - **Hero image** — a 16:9 placeholder block using a DS-tinted gradient or\n     solid fill (no external images). Add a 1-line caption underneath.\n   - **Body** — alternating prose paragraphs with at least:\n     - 1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under `dir=\"rtl\"`).\n     - 1 figure (image placeholder + caption).\n     - 1 list (numbered or bulleted).\n     - 1 inline blockquote.\n   - **Author footer** — author avatar (initials in a circle), bio paragraph.\n   - **Related** — 3 cards linking to other posts. Each card: tiny image\n     block, title, 1-line excerpt, date.\n4. **Write** a single HTML document:\n   - `\u003C!doctype html>` through `\u003C\u002Fhtml>`, CSS inline.\n   - Article body uses the DS body font, centered, max-width per DS layout\n     rule (typically 680–720px).\n   - Drop caps (`first-letter`) only if the DS mood is editorial \u002F serif —\n     skip on tech-y DSes.\n   - `data-od-id` on the headline, hero, body, pull quote, related grid.\n5. **Self-check**:\n   - Type hierarchy is unambiguous — H1 is clearly the headline; H2s are\n     section dividers; pull quotes do not compete with H1.\n   - Line length 60–75 chars for body prose.\n   - Accent appears at most twice (eyebrow + pull-quote rule, or one link).\n   - The page reads like a magazine, not a marketing landing.\n\n## Output contract\n\nEmit between `\u003Cartifact>` tags:\n\n```\n\u003Cartifact identifier=\"post-slug\" type=\"text\u002Fhtml\" title=\"Article Title\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact, nothing after.\n",{"od":24,"name":5,"triggers":43,"description":52},{"mode":25,"craft":26,"preview":32,"platform":35,"scenario":36,"design_system":37},"prototype",{"requires":27},[28,29,30,31],"typography","typography-hierarchy","typography-hierarchy-editorial","rtl-and-bidi",{"type":33,"entry":34},"html","index.html","desktop","marketing",{"requires":38,"sections":39},true,[40,28,41,42],"color","layout","components",[44,45,46,47,48,49,50,51],"blog","blog post","article","essay","case study","newsletter","博客","文章","A long-form article \u002F blog post — masthead, hero image placeholder,\narticle body with figures and pull quotes, author byline, related posts.\nUse when the brief asks for \"blog\", \"article\", \"post\", \"essay\", or\n\"case study\".\n","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fblog-post",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":62,"prompt":72,"zipAvailable":38},[63,66,69],{"tool":64,"command":65},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill blog-post",{"tool":67,"command":68},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill blog-post",{"tool":70,"command":71},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill blog-post","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fblog-post\u002FSKILL.md",[],[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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",[],[]]