[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77J5F4MCSA0V2PRXJMR15MM":3,"skill-same:01M77J5F4MCSA0V2PRXJMR15MM":43},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M77J5F4MCSA0V2PRXJMR15MM","wireframe",null,"Explore many ideas with wireframes and storyboards","raaOS\u002Fsystem_prompts_leaks","raaOS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214067397?v=4","01M77HV6K4ZTA4BZAGX00GTW6J","01M77HV6KX55HVRY679V25JXF8",0,"CC0-1.0","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FAnthropic\u002Fclaude-design\u002Fskills\u002Fwireframe\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wireframe\ndescription: \"Explore many ideas with wireframes and storyboards\"\nuser-invocable: true\n---\n\n# Wireframe\n\nHelp the user explore design ideas quickly. Interview them, then generate multiple rough wireframes to map out the design space before committing to a direction. Prioritize breadth over polish: show 3-5 distinctly different approaches for each idea. Use simple shapes, placeholder text, and minimal color to keep the focus on structure and flow. Use a sketchy vibe -- handwritten but readable fonts; b&w with some color; low-fi and simple. Lay the wireframes out as a vertical options stack:\n\nPresent multiple design options as a vertical stack of turns — each turn of options is its own `\u003Csection>`, newest turn at the **top**, and every option gets a stable `{turn}{letter}` id (`1a`, `1b`, `2a`…) that the user references back in chat and you cross-link between turns. Always include `\u003Cmeta name=\"design_doc_mode\" content=\"canvas\">` in `\u003Chelmet>` — the host provides pan\u002Fzoom, so the user can freely zoom out on designs wider than the viewport.\n\n**How to write it** — put one `\u003Cstyle>` block in `\u003Chelmet>`, then one `\u003Csection class=\"dv-turn\">` per turn as a **direct child of the root** (right after `\u003C\u002Fhelmet>`, no wrapper). When the user asks for another round, **insert the new section ABOVE the existing ones** so the latest work sits at the top; never reorder, renumber, or delete earlier turns.\n\n```html\n\u003Chelmet data-dc-atomics>\u003Cmeta name=\"design_doc_mode\" content=\"canvas\">\u003Cstyle>\nbody{margin:0;background:#f0eee9;font-family:system-ui,sans-serif}\n.dv-turn{padding:40px 44px 32px;border-bottom:1px solid rgba(0,0,0,.08);scroll-margin-top:16px}\n.dv-thd{display:flex;align-items:baseline;gap:10px;margin:0 0 20px}\n.dv-tid{font:600 10px ui-monospace,Menlo,monospace;padding:3px 7px;background:#1a1a1a;color:#fff;border-radius:4px;text-decoration:none}\n.dv-tname{font:600 13px\u002F1.2 system-ui,sans-serif;color:#1a1a1a}\n.dv-opts{display:flex;flex-wrap:wrap;gap:28px;align-items:flex-start}\n.dv-opt{flex:none;display:flex;flex-direction:column;gap:9px;scroll-margin-top:16px}\n.dv-oid{font:600 10.5px ui-monospace,Menlo,monospace;padding:3px 7px;background:rgba(0,0,0,.08);color:#1a1a1a;border-radius:5px;text-decoration:none}\n.dv-olabel{display:flex;align-items:baseline;gap:8px;font:400 11px\u002F1.3 system-ui,sans-serif;color:rgba(0,0,0,.55)}\n.dv-card{max-width:100%;background:#fff;border:1px solid rgba(0,0,0,.08);border-radius:8px;box-shadow:0 1px 3px rgba(0,0,0,.06);overflow:hidden}\n.dv-opt:target .dv-oid{background:#2a78d6;color:#fff}\n.dv-next{margin:22px 0 0;font:12px\u002F1.5 system-ui,sans-serif;color:rgba(0,0,0,.5)}\n\u003C\u002Fstyle>\u003C\u002Fhelmet>\n\u003Csection class=\"dv-turn\" id=\"t2\">\n\u003Cdiv class=\"dv-thd\">\u003Ca class=\"dv-tid\" href=\"#t2\">2\u003C\u002Fa>\u003Cspan class=\"dv-tname\">Riffs on \u003Ca class=\"dv-oid\" href=\"#1b\">1b\u003C\u002Fa>\u003C\u002Fspan>\u003C\u002Fdiv>\n\u003Cdiv class=\"dv-opts\">\n\u003Cdiv class=\"dv-opt\" id=\"2a\">\u003Cdiv class=\"dv-olabel\">\u003Ca class=\"dv-oid\" href=\"#2a\">2a\u003C\u002Fa>Tighter spacing\u003C\u002Fdiv>\u003Cdiv class=\"dv-card\" style=\"width:360px\">…design…\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cdiv class=\"dv-opt\" id=\"2b\">…\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\u003Cp class=\"dv-next\">Try next: \"more like \u003Ca class=\"dv-oid\" href=\"#2a\">2a\u003C\u002Fa> but with the serif from \u003Ca class=\"dv-oid\" href=\"#1c\">1c\u003C\u002Fa>\" · \"make \u003Ca class=\"dv-oid\" href=\"#2b\">2b\u003C\u002Fa> full-bleed\" · \"new directions\"\u003C\u002Fp>\n\u003C\u002Fsection>\n\u003Csection class=\"dv-turn\" id=\"t1\">…turn 1, unchanged…\u003C\u002Fsection>\n```\n\n**Rules:** turn section ids are `t1`, `t2`, `t3`…; option ids are `1a`, `1b`, `2a`… and go on the option's **outermost** element (`.dv-opt`), never on the badge — so `#1b` scrolls the whole option into view. Ids are stable forever, never reused or renumbered. Options within a turn sit side-by-side in a wrapping row; don't hand-roll your own pan\u002Fzoom — the host canvas provides it. **Every** option-id reference in the file — turn heading, option label, `.dv-next` line, any prose — is an `\u003Ca class=\"dv-oid\" href=\"#1b\">1b\u003C\u002Fa>` link, never a bare `1b`; in your chat replies, just write `1b`. End each turn with a one-line `.dv-next` of 2–3 plain-English follow-ups the user could paste into chat. Size each `.dv-card` to its content (explicit width is fine); don't use `height:100%`.\n","# Wireframe\n\nHelp the user explore design ideas quickly. Interview them, then generate multiple rough wireframes to map out the design space before committing to a direction. Prioritize breadth over polish: show 3-5 distinctly different approaches for each idea. Use simple shapes, placeholder text, and minimal color to keep the focus on structure and flow. Use a sketchy vibe -- handwritten but readable fonts; b&w with some color; low-fi and simple. Lay the wireframes out as a vertical options stack:\n\nPresent multiple design options as a vertical stack of turns — each turn of options is its own `\u003Csection>`, newest turn at the **top**, and every option gets a stable `{turn}{letter}` id (`1a`, `1b`, `2a`…) that the user references back in chat and you cross-link between turns. Always include `\u003Cmeta name=\"design_doc_mode\" content=\"canvas\">` in `\u003Chelmet>` — the host provides pan\u002Fzoom, so the user can freely zoom out on designs wider than the viewport.\n\n**How to write it** — put one `\u003Cstyle>` block in `\u003Chelmet>`, then one `\u003Csection class=\"dv-turn\">` per turn as a **direct child of the root** (right after `\u003C\u002Fhelmet>`, no wrapper). When the user asks for another round, **insert the new section ABOVE the existing ones** so the latest work sits at the top; never reorder, renumber, or delete earlier turns.\n\n```html\n\u003Chelmet data-dc-atomics>\u003Cmeta name=\"design_doc_mode\" content=\"canvas\">\u003Cstyle>\nbody{margin:0;background:#f0eee9;font-family:system-ui,sans-serif}\n.dv-turn{padding:40px 44px 32px;border-bottom:1px solid rgba(0,0,0,.08);scroll-margin-top:16px}\n.dv-thd{display:flex;align-items:baseline;gap:10px;margin:0 0 20px}\n.dv-tid{font:600 10px ui-monospace,Menlo,monospace;padding:3px 7px;background:#1a1a1a;color:#fff;border-radius:4px;text-decoration:none}\n.dv-tname{font:600 13px\u002F1.2 system-ui,sans-serif;color:#1a1a1a}\n.dv-opts{display:flex;flex-wrap:wrap;gap:28px;align-items:flex-start}\n.dv-opt{flex:none;display:flex;flex-direction:column;gap:9px;scroll-margin-top:16px}\n.dv-oid{font:600 10.5px ui-monospace,Menlo,monospace;padding:3px 7px;background:rgba(0,0,0,.08);color:#1a1a1a;border-radius:5px;text-decoration:none}\n.dv-olabel{display:flex;align-items:baseline;gap:8px;font:400 11px\u002F1.3 system-ui,sans-serif;color:rgba(0,0,0,.55)}\n.dv-card{max-width:100%;background:#fff;border:1px solid rgba(0,0,0,.08);border-radius:8px;box-shadow:0 1px 3px rgba(0,0,0,.06);overflow:hidden}\n.dv-opt:target .dv-oid{background:#2a78d6;color:#fff}\n.dv-next{margin:22px 0 0;font:12px\u002F1.5 system-ui,sans-serif;color:rgba(0,0,0,.5)}\n\u003C\u002Fstyle>\u003C\u002Fhelmet>\n\u003Csection class=\"dv-turn\" id=\"t2\">\n\u003Cdiv class=\"dv-thd\">\u003Ca class=\"dv-tid\" href=\"#t2\">2\u003C\u002Fa>\u003Cspan class=\"dv-tname\">Riffs on \u003Ca class=\"dv-oid\" href=\"#1b\">1b\u003C\u002Fa>\u003C\u002Fspan>\u003C\u002Fdiv>\n\u003Cdiv class=\"dv-opts\">\n\u003Cdiv class=\"dv-opt\" id=\"2a\">\u003Cdiv class=\"dv-olabel\">\u003Ca class=\"dv-oid\" href=\"#2a\">2a\u003C\u002Fa>Tighter spacing\u003C\u002Fdiv>\u003Cdiv class=\"dv-card\" style=\"width:360px\">…design…\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cdiv class=\"dv-opt\" id=\"2b\">…\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n\u003Cp class=\"dv-next\">Try next: \"more like \u003Ca class=\"dv-oid\" href=\"#2a\">2a\u003C\u002Fa> but with the serif from \u003Ca class=\"dv-oid\" href=\"#1c\">1c\u003C\u002Fa>\" · \"make \u003Ca class=\"dv-oid\" href=\"#2b\">2b\u003C\u002Fa> full-bleed\" · \"new directions\"\u003C\u002Fp>\n\u003C\u002Fsection>\n\u003Csection class=\"dv-turn\" id=\"t1\">…turn 1, unchanged…\u003C\u002Fsection>\n```\n\n**Rules:** turn section ids are `t1`, `t2`, `t3`…; option ids are `1a`, `1b`, `2a`… and go on the option's **outermost** element (`.dv-opt`), never on the badge — so `#1b` scrolls the whole option into view. Ids are stable forever, never reused or renumbered. Options within a turn sit side-by-side in a wrapping row; don't hand-roll your own pan\u002Fzoom — the host canvas provides it. **Every** option-id reference in the file — turn heading, option label, `.dv-next` line, any prose — is an `\u003Ca class=\"dv-oid\" href=\"#1b\">1b\u003C\u002Fa>` link, never a bare `1b`; in your chat replies, just write `1b`. End each turn with a one-line `.dv-next` of 2–3 plain-English follow-ups the user could paste into chat. Size each `.dv-card` to its content (explicit width is fine); don't use `height:100%`.\n",{"name":5,"description":7,"user-invocable":23},true,"main","2975a5ac469614541ae22929d43b6da2635e1ee9","Anthropic\u002Fclaude-design\u002Fskills\u002Fwireframe","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks","https:\u002F\u002Fgithub.com\u002FraaOS","2026-11-14 21:19:17",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add raaOS\u002Fsystem_prompts_leaks --skill wireframe",{"tool":36,"command":37},"bunx","bunx skills add raaOS\u002Fsystem_prompts_leaks --skill wireframe",{"tool":39,"command":40},"pnpm","pnpm dlx skills add raaOS\u002Fsystem_prompts_leaks --skill wireframe","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FAnthropic\u002Fclaude-design\u002Fskills\u002Fwireframe\u002FSKILL.md",[],[44,50,57,64,71,78],{"skillNo":45,"name":46,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":47,"categories":48,"keywords":49,"publishedAt":18},"01M77JV1M0ZZTZZREM9Q96TKZZ","model-council","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FPerplexity\u002Fskills\u002Fmodel-council\u002FSKILL.md",[],[],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M77JTYND3ETS9EGCX3B9CW6E","writing-style","Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fwriting-style\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M77JTVWEHY80JC2H1JG1JMQB","write-page","Create or edit requested Page\u002FSpace content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fwrite-page\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M77JTQ5ND23QPF6RJYJPXHSZ","software-engineering","For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work, not a general programming explanation.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fsoftware-engineering\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},"01M77JTM3ZDPCYE8C1FW7G7S2B","slides-artifact","Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation advice or a chat-only outline.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fslides-artifact\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},"01M77JTHTWZN2J27KD2H66XDBZ","slack","Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fslack\u002FSKILL.md",[],[]]