[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736MHPPF5X92P32JZ26D4TH":3,"skill-same:01M736MHPPF5X92P32JZ26D4TH":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M736MHPPF5X92P32JZ26D4TH","wireframes",null,"Create, refine, review, critique, or iterate on low-fidelity grey wireframes under `stardust\u002Fwireframes\u002F**\u002F*.html` — structure, hierarchy, section order, spatial relationships, annotations, section metadata (`data-section`\u002F`data-intent`\u002F`data-layout`), and multi-page fragment\u002Freuse mapping (`data-fragment*`). Rendered from briefings. No brand required. Optional stage: users can skip to `\u002Fstardust:prototype` for branded layout directly. Use when the user wants to validate page structure before visual design, annotate a wireframe, mark reusable fragments across pages, when the user asks to change, refine, refactor, review, improve, polish, critique, or iterate on structure, section order, or block placement, or whenever the user asks to modify a file under `stardust\u002Fwireframes\u002F**\u002F*.html`.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-wireframes\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wireframes\ndescription: \"Create, refine, review, critique, or iterate on low-fidelity grey wireframes under `stardust\u002Fwireframes\u002F**\u002F*.html` — structure, hierarchy, section order, spatial relationships, annotations, section metadata (`data-section`\u002F`data-intent`\u002F`data-layout`), and multi-page fragment\u002Freuse mapping (`data-fragment*`). Rendered from briefings. No brand required. Optional stage: users can skip to `\u002Fstardust:prototype` for branded layout directly. Use when the user wants to validate page structure before visual design, annotate a wireframe, mark reusable fragments across pages, when the user asks to change, refine, refactor, review, improve, polish, critique, or iterate on structure, section order, or block placement, or whenever the user asks to modify a file under `stardust\u002Fwireframes\u002F**\u002F*.html`.\"\nlicense: Apache-2.0\nmetadata:\n  version: \"0.1.0\"\n---\n\n# Wireframes\n\nTurn approved briefings into **grey, structural** wireframes — boxes, bars, shapes — so the user can validate page structure (section order, hierarchy, density, spatial relationships) before committing to visual design.\n\nThis stage is **optional**. A user who already has a clear structural vision can skip straight to `\u002Fstardust:prototype`.\n\n## When to use this skill\n\n- The user wants to validate page structure before visual design — section order, hierarchy, density, spatial relationships.\n- The user asks to annotate a wireframe or mark reusable fragments across pages.\n- The user asks to change, refine, review, critique, or iterate on any file under `stardust\u002Fwireframes\u002F**\u002F*.html`.\n- The user types `\u002Fstardust:wireframes`.\n\n## Do NOT use this skill\n\n- For branded visual design, colors, typography, or final proportions. Hand off to `prototype`.\n- For page copy or intent. Hand off to `briefings`.\n- When the user explicitly wants to skip straight to branded design — suggest `\u002Fstardust:prototype` instead.\n\n## Pre-flight\n\nRun the procedure in [`..\u002F_shared\u002Fpreflight.md`](..\u002F_shared\u002Fpreflight.md) first.\n\n## Contract\n\n**Needs (reads if present):**\n- `stardust\u002Fbriefings\u002F{page}.md` (one or more)\n- `.impeccable.md` (tone for annotations)\n\n**Produces:**\n- `stardust\u002Fwireframes\u002F{page}.html` (grey, annotated)\n\n**If missing:**\n- No briefings → prompt the user for a one-line page intent, synthesize a minimal briefing, stamp provenance on both the briefing and the wireframe, and proceed.\n- No `.impeccable.md` → annotations use neutral-technical tone.\n- Brand is intentionally not read at this stage.\n\n---\n\n## Phase 1: Plan\n\nFor each page with an approved briefing:\n\n1. Read the page briefing from `stardust\u002Fbriefings\u002F{page}.md`.\n2. Read the site briefing from `stardust\u002Fbriefings\u002F_site.md` if it exists (including the Content Reuse Map).\n3. Plan the page's sections — UX discovery:\n   - If the `impeccable` plugin is installed (`\u002Fimpeccable shape` is registered), delegate section planning to `\u002Fimpeccable shape`.\n   - Otherwise, use the \"For wireframe section planning\" pattern in [`..\u002F_shared\u002Ffallback-brainstorm.md`](..\u002F_shared\u002Ffallback-brainstorm.md). Per [`..\u002F_shared\u002Fsoft-deps.md`](..\u002F_shared\u002Fsoft-deps.md), impeccable fallback runs silently.\n   Either path answers: what sections does this page need, what's the visual hierarchy, and how does the user flow through the content.\n   - `\u002Fshape` produces a design brief — use this as the structural plan.\n4. For multi-page sites, plan the information architecture across all pages before wireframing individual ones:\n   - **If `\u002Fwrite-plan` is registered in this session** (detect per [`..\u002F_shared\u002Fsoft-deps.md`](..\u002F_shared\u002Fsoft-deps.md)): delegate IA planning to `\u002Fwrite-plan`, seeded with the site briefing and the list of pages. Use its output as the multi-page structural plan.\n   - **Otherwise (superpowers not installed):** announce the fallback **exactly once per session** using the verbatim text from [`..\u002F_shared\u002Fsoft-deps.md`](..\u002F_shared\u002Fsoft-deps.md) (\"superpowers announcement\") — unless it was already announced earlier in this session. Then sketch the IA inline: list pages, their primary content type, and the shared sections between them, and confirm with the user before moving on.\n\n## Phase 2: Render (Grey Mode)\n\nRender each wireframe as visual HTML in grey mode:\n\n- **Pure grey layout:** boxes, bars, shapes. No brand colors, no real fonts (system-ui is fine).\n- Background: light grey (#f5f5f5); elements in shades of grey.\n- Placeholder text as grey bars; images as grey rectangles with labels.\n- **Annotations are required** — every block gets a short italic `.note` or `.caption` describing what it represents, so the reviewer can evaluate the flow without guessing. Repeated items (pipeline nodes, host tiles, card grids) carry identifying labels (\"01 · brand\", \"Claude Code\"), not generic numbers. See [wireframe-guide.md](reference\u002Fwireframe-guide.md) Annotations section.\n- Shows: section order, relative sizing, content density, spatial relationships.\n- Each section gets `data-section`, `data-intent`, `data-layout` attributes so the design stage can pick up the structure.\n- For multi-page sites: add `data-fragment`, `data-fragment-role`, and `data-fragment-source` attributes to reusable content sections — see [wireframe-guide.md](reference\u002Fwireframe-guide.md) Content Reuse & Fragments section.\n- Include the JSON metadata block linking to the briefing (with `fragments` map for multi-page sites).\n- Write to `stardust\u002Fwireframes\u002F{page}.html`.\n\nIf the upstream briefing was synthesized (provenance comment present, or generated during this pre-flight), carry forward a provenance block on the wireframe per [`..\u002F_shared\u002Fskill-contract.md`](..\u002F_shared\u002Fskill-contract.md).\n\nFollow the full rendering rules in [wireframe-guide.md](reference\u002Fwireframe-guide.md).\n\n## Phase 3: Serve\n\nWireframes are self-contained HTML files. **Open each file in the designer's default browser immediately after writing** per [`..\u002F_shared\u002Fskill-contract.md`](..\u002F_shared\u002Fskill-contract.md) *Opening HTML artifacts*. On macOS: `open stardust\u002Fwireframes\u002F{page}.html`. Do not rely on the designer to open it manually.\n\nIf multiple wireframes were rendered in this phase (multi-page run), open each one so the designer can review in tabs.\n\nIn pipeline-automation mode (no designer present), skip the open.\n\n## Phase 4: Approval Gate\n\nSoft gate — the user approves structure, not visuals.\n\nPresent the wireframe and ask: \"Does this structure match what you had in mind? What should change?\"\n\nCommon feedback:\n- **\"Swap these sections\"** → Reorder, re-render.\n- **\"Add a section for [X]\"** → Add new section with data attributes, re-render.\n- **\"This section is too big\u002Fsmall relative to the rest\"** → Adjust proportions, re-render.\n- **\"I want something interactive here\"** → Add `data-interactive` attribute.\n\nIterate until the user approves. Then:\n1. If `stardust\u002Fbrand-profile.json` exists: \"Wireframes approved. Run `\u002Fstardust:prototype` to upgrade them to branded prototypes.\"\n2. If not: \"Wireframes approved. Run `\u002Fstardust:brand` to capture your brand, then `\u002Fstardust:prototype` to layer it onto these wireframes.\"\n\n**Pipeline automation:** When invoked as part of a full pipeline run, auto-approve and continue.\n\n## Why Wireframes Before Design\n\nWireframes let you make **structural** decisions (what goes where, in what order, at what relative size) without being distracted by **visual** ones (what colors, fonts, and proportions). Separating the two means each decision gets full attention.\n\nUsers who already know the structure can skip this stage entirely and go briefings → design.\n\n## Artifacts Written\n\n| File | Description |\n|------|-------------|\n| `stardust\u002Fwireframes\u002F{page}.html` | Grey structural wireframes — self-contained HTML |\n","# Wireframes\n\nTurn approved briefings into **grey, structural** wireframes — boxes, bars, shapes — so the user can validate page structure (section order, hierarchy, density, spatial relationships) before committing to visual design.\n\nThis stage is **optional**. A user who already has a clear structural vision can skip straight to `\u002Fstardust:prototype`.\n\n## When to use this skill\n\n- The user wants to validate page structure before visual design — section order, hierarchy, density, spatial relationships.\n- The user asks to annotate a wireframe or mark reusable fragments across pages.\n- The user asks to change, refine, review, critique, or iterate on any file under `stardust\u002Fwireframes\u002F**\u002F*.html`.\n- The user types `\u002Fstardust:wireframes`.\n\n## Do NOT use this skill\n\n- For branded visual design, colors, typography, or final proportions. Hand off to `prototype`.\n- For page copy or intent. Hand off to `briefings`.\n- When the user explicitly wants to skip straight to branded design — suggest `\u002Fstardust:prototype` instead.\n\n## Pre-flight\n\nRun the procedure in [`..\u002F_shared\u002Fpreflight.md`](..\u002F_shared\u002Fpreflight.md) first.\n\n## Contract\n\n**Needs (reads if present):**\n- `stardust\u002Fbriefings\u002F{page}.md` (one or more)\n- `.impeccable.md` (tone for annotations)\n\n**Produces:**\n- `stardust\u002Fwireframes\u002F{page}.html` (grey, annotated)\n\n**If missing:**\n- No briefings → prompt the user for a one-line page intent, synthesize a minimal briefing, stamp provenance on both the briefing and the wireframe, and proceed.\n- No `.impeccable.md` → annotations use neutral-technical tone.\n- Brand is intentionally not read at this stage.\n\n---\n\n## Phase 1: Plan\n\nFor each page with an approved briefing:\n\n1. Read the page briefing from `stardust\u002Fbriefings\u002F{page}.md`.\n2. Read the site briefing from `stardust\u002Fbriefings\u002F_site.md` if it exists (including the Content Reuse Map).\n3. Plan the page's sections — UX discovery:\n   - If the `impeccable` plugin is installed (`\u002Fimpeccable shape` is registered), delegate section planning to `\u002Fimpeccable shape`.\n   - Otherwise, use the \"For wireframe section planning\" pattern in [`..\u002F_shared\u002Ffallback-brainstorm.md`](..\u002F_shared\u002Ffallback-brainstorm.md). Per [`..\u002F_shared\u002Fsoft-deps.md`](..\u002F_shared\u002Fsoft-deps.md), impeccable fallback runs silently.\n   Either path answers: what sections does this page need, what's the visual hierarchy, and how does the user flow through the content.\n   - `\u002Fshape` produces a design brief — use this as the structural plan.\n4. For multi-page sites, plan the information architecture across all pages before wireframing individual ones:\n   - **If `\u002Fwrite-plan` is registered in this session** (detect per [`..\u002F_shared\u002Fsoft-deps.md`](..\u002F_shared\u002Fsoft-deps.md)): delegate IA planning to `\u002Fwrite-plan`, seeded with the site briefing and the list of pages. Use its output as the multi-page structural plan.\n   - **Otherwise (superpowers not installed):** announce the fallback **exactly once per session** using the verbatim text from [`..\u002F_shared\u002Fsoft-deps.md`](..\u002F_shared\u002Fsoft-deps.md) (\"superpowers announcement\") — unless it was already announced earlier in this session. Then sketch the IA inline: list pages, their primary content type, and the shared sections between them, and confirm with the user before moving on.\n\n## Phase 2: Render (Grey Mode)\n\nRender each wireframe as visual HTML in grey mode:\n\n- **Pure grey layout:** boxes, bars, shapes. No brand colors, no real fonts (system-ui is fine).\n- Background: light grey (#f5f5f5); elements in shades of grey.\n- Placeholder text as grey bars; images as grey rectangles with labels.\n- **Annotations are required** — every block gets a short italic `.note` or `.caption` describing what it represents, so the reviewer can evaluate the flow without guessing. Repeated items (pipeline nodes, host tiles, card grids) carry identifying labels (\"01 · brand\", \"Claude Code\"), not generic numbers. See [wireframe-guide.md](reference\u002Fwireframe-guide.md) Annotations section.\n- Shows: section order, relative sizing, content density, spatial relationships.\n- Each section gets `data-section`, `data-intent`, `data-layout` attributes so the design stage can pick up the structure.\n- For multi-page sites: add `data-fragment`, `data-fragment-role`, and `data-fragment-source` attributes to reusable content sections — see [wireframe-guide.md](reference\u002Fwireframe-guide.md) Content Reuse & Fragments section.\n- Include the JSON metadata block linking to the briefing (with `fragments` map for multi-page sites).\n- Write to `stardust\u002Fwireframes\u002F{page}.html`.\n\nIf the upstream briefing was synthesized (provenance comment present, or generated during this pre-flight), carry forward a provenance block on the wireframe per [`..\u002F_shared\u002Fskill-contract.md`](..\u002F_shared\u002Fskill-contract.md).\n\nFollow the full rendering rules in [wireframe-guide.md](reference\u002Fwireframe-guide.md).\n\n## Phase 3: Serve\n\nWireframes are self-contained HTML files. **Open each file in the designer's default browser immediately after writing** per [`..\u002F_shared\u002Fskill-contract.md`](..\u002F_shared\u002Fskill-contract.md) *Opening HTML artifacts*. On macOS: `open stardust\u002Fwireframes\u002F{page}.html`. Do not rely on the designer to open it manually.\n\nIf multiple wireframes were rendered in this phase (multi-page run), open each one so the designer can review in tabs.\n\nIn pipeline-automation mode (no designer present), skip the open.\n\n## Phase 4: Approval Gate\n\nSoft gate — the user approves structure, not visuals.\n\nPresent the wireframe and ask: \"Does this structure match what you had in mind? What should change?\"\n\nCommon feedback:\n- **\"Swap these sections\"** → Reorder, re-render.\n- **\"Add a section for [X]\"** → Add new section with data attributes, re-render.\n- **\"This section is too big\u002Fsmall relative to the rest\"** → Adjust proportions, re-render.\n- **\"I want something interactive here\"** → Add `data-interactive` attribute.\n\nIterate until the user approves. Then:\n1. If `stardust\u002Fbrand-profile.json` exists: \"Wireframes approved. Run `\u002Fstardust:prototype` to upgrade them to branded prototypes.\"\n2. If not: \"Wireframes approved. Run `\u002Fstardust:brand` to capture your brand, then `\u002Fstardust:prototype` to layer it onto these wireframes.\"\n\n**Pipeline automation:** When invoked as part of a full pipeline run, auto-approve and continue.\n\n## Why Wireframes Before Design\n\nWireframes let you make **structural** decisions (what goes where, in what order, at what relative size) without being distracted by **visual** ones (what colors, fonts, and proportions). Separating the two means each decision gets full attention.\n\nUsers who already know the structure can skip this stage entirely and go briefings → design.\n\n## Artifacts Written\n\n| File | Description |\n|------|-------------|\n| `stardust\u002Fwireframes\u002F{page}.html` | Grey structural wireframes — self-contained HTML |\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25},"0.1.0","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-wireframes","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add kalash33\u002Fkstack --skill wireframes",{"tool":40,"command":41},"bunx","bunx skills add kalash33\u002Fkstack --skill wireframes",{"tool":43,"command":44},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill wireframes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-wireframes\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"reference\u002Fwireframe-guide.md","REFERENCE","参考文档",8256,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-wireframes\u002Freference\u002Fwireframe-guide.md",[55,63,70,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]