[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7V4EBZ5ZNFR8ZPF7CPJV9":3,"skill-same:01M7D7V4EBZ5ZNFR8ZPF7CPJV9":80},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M7D7V4EBZ5ZNFR8ZPF7CPJV9","wireframe-mobile-flow",null,"A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames\nlaid out in a row on a board, showing a connected user flow (Onboarding →\nHome feed → Item detail → Confirm). Grey-box content inside each device,\ndashed connector arrows + numbered step labels between screens, and a\ncouple of annotation callouts. Reads like an app flow pinned to a\nwhiteboard before any pixels are committed. Use when the brief asks for\n\"mobile wireframe\", \"app flow\", \"user flow wireframe\", \"lo-fi mobile\",\n\"low fidelity\", \"线框图\", \"移动端线框\", or \"App 流程\".","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\u002Fexamples\u002Fwireframe-mobile-flow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wireframe-mobile-flow\ndescription: |\n  A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames\n  laid out in a row on a board, showing a connected user flow (Onboarding →\n  Home feed → Item detail → Confirm). Grey-box content inside each device,\n  dashed connector arrows + numbered step labels between screens, and a\n  couple of annotation callouts. Reads like an app flow pinned to a\n  whiteboard before any pixels are committed. Use when the brief asks for\n  \"mobile wireframe\", \"app flow\", \"user flow wireframe\", \"lo-fi mobile\",\n  \"low fidelity\", \"线框图\", \"移动端线框\", or \"App 流程\".\ntriggers:\n  - \"mobile wireframe\"\n  - \"app flow\"\n  - \"user flow\"\n  - \"lo-fi mobile\"\n  - \"wireframe\"\n  - \"low fidelity\"\n  - \"移动端线框\"\n  - \"App 流程图\"\nod:\n  mode: prototype\n  platform: auto\n  scenario: design\n  fidelity: wireframe\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: false\n    sections: [color, typography, layout, components]\n  example_prompt: \"Wireframe a lo-fi mobile flow v0.1 — three phone frames in a row (Onboarding → Home feed → Item detail), grey-box screens, dashed step arrows between them, and two annotation callouts.\"\n---\n\n# Wireframe Mobile Flow Skill\n\nProduce a single board showing a mobile app's user flow as a row of lo-fi\nphone frames. The point is the *flow* — how a user moves screen to screen —\nnot the polish of any one screen. Keep the screens clean grey-boxes (not\nscribbly) but keep the connectors and annotations loose and informal.\n\n## Workflow\n\n1. **Skip the DESIGN.md** if it pushes for finished UI. This skill is\n   deliberately low-fidelity: greyboxes, placeholder rects, and bars stand in\n   for real content. Honor type tokens only loosely (system sans for the\n   board, mono for labels and datelines).\n2. **Pick the flow steps** from the brief — typically 3–4 connected screens\n   like Onboarding → Home feed → Item detail → Confirm. Name each step so the\n   connector arrows can carry a numbered, verb-first label (\"① tap Start\",\n   \"② open item\", \"③ add to cart\").\n3. **Lay out the board**, in order:\n   - **Board header** — bold sans title with a pinned \"WIREFRAME v0.1 ·\n     MOBILE\" tag (dashed border, slight rotation) and a mono dateline on the\n     right (date \u002F device \u002F fidelity).\n   - **Phone row** — 3–4 rounded device frames (~240–280px wide) in a\n     horizontal row, each with a notch \u002F status bar. Inside each frame put\n     the greybox content for its step: hero image-placeholder (rect + X),\n     title\u002Fprice bars, list cards (thumbnail X + 2 text bars), category\n     chips, a bottom tab bar, sticky CTA bars, a confirm checkmark — match the\n     screen's role.\n   - **Connectors** — dashed arrows between consecutive phones, each carrying\n     a small mono step label describing the tap that advances the flow.\n   - **Annotations** — 1–2 small sticky \u002F callout notes pinned near a screen\n     to flag intent (\"hero must sell value in 3s\", \"checkout = 1 screen\").\n4. **Write** a single HTML document:\n   - `\u003C!doctype html>` through `\u003C\u002Fhtml>`, CSS inline, no external JS, no\n     external images (CSS\u002FSVG placeholders only).\n   - Use Inter \u002F system-ui for the board and IBM Plex Mono for labels via\n     Google Fonts; a light marker font is allowed for annotations only.\n   - Defined dark device-frame borders, medium-grey content blocks on white\n     screens, and a single accent color for arrows and annotations so the\n     board reads clearly even as a small thumbnail.\n   - `data-od-id` on the header, each phone screen, the connectors, and the\n     annotations.\n5. **Self-check**:\n   - The three main phones are visible in a ~1280px viewport; the flow reads\n     left-to-right.\n   - Screens are clean greyboxes (not scribbly); connectors and stickies are\n     the loose, informal parts.\n   - No near-white-on-white regions — every block has a visible grey fill or\n     border. If a screen renders blank as a thumbnail, raise the contrast.\n\n## Output contract\n\nEmit between `\u003Cartifact>` tags:\n\n```\n\u003Cartifact identifier=\"wireframe-slug\" type=\"text\u002Fhtml\" title=\"Wireframe — Title\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact, nothing after.\n","# Wireframe Mobile Flow Skill\n\nProduce a single board showing a mobile app's user flow as a row of lo-fi\nphone frames. The point is the *flow* — how a user moves screen to screen —\nnot the polish of any one screen. Keep the screens clean grey-boxes (not\nscribbly) but keep the connectors and annotations loose and informal.\n\n## Workflow\n\n1. **Skip the DESIGN.md** if it pushes for finished UI. This skill is\n   deliberately low-fidelity: greyboxes, placeholder rects, and bars stand in\n   for real content. Honor type tokens only loosely (system sans for the\n   board, mono for labels and datelines).\n2. **Pick the flow steps** from the brief — typically 3–4 connected screens\n   like Onboarding → Home feed → Item detail → Confirm. Name each step so the\n   connector arrows can carry a numbered, verb-first label (\"① tap Start\",\n   \"② open item\", \"③ add to cart\").\n3. **Lay out the board**, in order:\n   - **Board header** — bold sans title with a pinned \"WIREFRAME v0.1 ·\n     MOBILE\" tag (dashed border, slight rotation) and a mono dateline on the\n     right (date \u002F device \u002F fidelity).\n   - **Phone row** — 3–4 rounded device frames (~240–280px wide) in a\n     horizontal row, each with a notch \u002F status bar. Inside each frame put\n     the greybox content for its step: hero image-placeholder (rect + X),\n     title\u002Fprice bars, list cards (thumbnail X + 2 text bars), category\n     chips, a bottom tab bar, sticky CTA bars, a confirm checkmark — match the\n     screen's role.\n   - **Connectors** — dashed arrows between consecutive phones, each carrying\n     a small mono step label describing the tap that advances the flow.\n   - **Annotations** — 1–2 small sticky \u002F callout notes pinned near a screen\n     to flag intent (\"hero must sell value in 3s\", \"checkout = 1 screen\").\n4. **Write** a single HTML document:\n   - `\u003C!doctype html>` through `\u003C\u002Fhtml>`, CSS inline, no external JS, no\n     external images (CSS\u002FSVG placeholders only).\n   - Use Inter \u002F system-ui for the board and IBM Plex Mono for labels via\n     Google Fonts; a light marker font is allowed for annotations only.\n   - Defined dark device-frame borders, medium-grey content blocks on white\n     screens, and a single accent color for arrows and annotations so the\n     board reads clearly even as a small thumbnail.\n   - `data-od-id` on the header, each phone screen, the connectors, and the\n     annotations.\n5. **Self-check**:\n   - The three main phones are visible in a ~1280px viewport; the flow reads\n     left-to-right.\n   - Screens are clean greyboxes (not scribbly); connectors and stickies are\n     the loose, informal parts.\n   - No near-white-on-white regions — every block has a visible grey fill or\n     border. If a screen renders blank as a thumbnail, raise the contrast.\n\n## Output contract\n\nEmit between `\u003Cartifact>` tags:\n\n```\n\u003Cartifact identifier=\"wireframe-slug\" type=\"text\u002Fhtml\" title=\"Wireframe — 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":39,"description":47},{"mode":25,"preview":26,"fidelity":29,"platform":30,"scenario":31,"design_system":32,"example_prompt":38},"prototype",{"type":27,"entry":28},"html","index.html","wireframe","auto","design",{"requires":20,"sections":33},[34,35,36,37],"color","typography","layout","components","Wireframe a lo-fi mobile flow v0.1 — three phone frames in a row (Onboarding → Home feed → Item detail), grey-box screens, dashed step arrows between them, and two annotation callouts.",[40,41,42,43,29,44,45,46],"mobile wireframe","app flow","user flow","lo-fi mobile","low fidelity","移动端线框","App 流程图","A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames\nlaid out in a row on a board, showing a connected user flow (Onboarding →\nHome feed → Item detail → Confirm). Grey-box content inside each device,\ndashed connector arrows + numbered step labels between screens, and a\ncouple of annotation callouts. Reads like an app flow pinned to a\nwhiteboard before any pixels are committed. Use when the brief asks for\n\"mobile wireframe\", \"app flow\", \"user flow wireframe\", \"lo-fi mobile\",\n\"low fidelity\", \"线框图\", \"移动端线框\", or \"App 流程\".\n","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fexamples\u002Fwireframe-mobile-flow",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill wireframe-mobile-flow",{"tool":62,"command":63},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill wireframe-mobile-flow",{"tool":65,"command":66},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill wireframe-mobile-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fexamples\u002Fwireframe-mobile-flow\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"example.html","REFERENCE","参考文档",17969,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fexamples\u002Fwireframe-mobile-flow\u002Fexample.html",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"open-design.json",11100,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fexamples\u002Fwireframe-mobile-flow\u002Fopen-design.json",[81,88,95,102,109,116],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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",[],[]]