[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CZQHTBCKQ87Y3VEAZWVT0J":3,"skill-same:01M7CZQHTBCKQ87Y3VEAZWVT0J":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M7CZQHTBCKQ87Y3VEAZWVT0J","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 流程\".","qelvora1\u002Fopen-design","qelvora1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F294549645?v=4","01M7CYQMFVAA6E5YHKCNNCBXJS","01M7CYQMGFRBPABV2BSD9VB71Z",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\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":23,"name":5,"triggers":38,"description":46},{"mode":24,"preview":25,"fidelity":28,"platform":29,"scenario":30,"design_system":31,"example_prompt":37},"prototype",{"type":26,"entry":27},"html","index.html","wireframe","auto","design",{"requires":19,"sections":32},[33,34,35,36],"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.",[39,40,41,42,28,43,44,45],"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","29240bc3ff7b5db56f8a41965213220446fcb96d","design-templates\u002Fwireframe-mobile-flow","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fqelvora1","2026-10-01 22:47:24",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add qelvora1\u002Fopen-design --skill wireframe-mobile-flow",{"tool":60,"command":61},"bunx","bunx skills add qelvora1\u002Fopen-design --skill wireframe-mobile-flow",{"tool":63,"command":64},"pnpm","pnpm dlx skills add qelvora1\u002Fopen-design --skill wireframe-mobile-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fwireframe-mobile-flow\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"example.html","REFERENCE","参考文档",17969,"https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fwireframe-mobile-flow\u002Fexample.html",[75,82,89,96,103,112],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7D3A2Y3ZTSPJJSCEHTWDN2P","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7D3A1MHKESXV45VYXKPCDRN","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7D3A0HSH085FTGATVBG43YG","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7D39Y0372ZQ6GTWFAJ7DEVJ","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M7D39SMB0RHRGGQY24YVD8N5","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\".","MIT","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7D39NNKF0JDA1J6ZJJQVVCV","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fqelvora1\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]