[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M782PBESAXT01QTWB5Z8M91F":3,"skill-same:01M782PBESAXT01QTWB5Z8M91F":53},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M782PBESAXT01QTWB5Z8M91F","prototype",null,"Plan and create throwaway static HTML and CSS mockups with shared design tokens before feature implementation. Use for \u002Fprototype, screen mockups, layout exploration, themes, or deciding a project's look and feel.","bradtraversy\u002Fskillpass","bradtraversy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5550850?v=4","01M782H8BT6A97A17XDFHDABWZ","Brad Traversy","01M782H8CDJZW3HYDHX23FA9VF",26,"MIT","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprototype\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prototype\ndescription: Plan and create throwaway static HTML and CSS mockups with shared design tokens before feature implementation. Use for \u002Fprototype, screen mockups, layout exploration, themes, or deciding a project's look and feel.\ndisable-model-invocation: true\n---\n\n# prototype - lock the look before you build\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` using the dashboard activity\ncontract in `AGENTS.md`.\n\nWhere this sits in the workflow:\n\n    plan  ->  \u002Foverview  ->  [prototype]  ->  \u002Ffeature  ->  build\n    (you      (project-      (lock the       (one spec    (real\n     write)    overview.md)   look)           at a time)   code)\n\nPrototyping is a pre-build step, not a feature. It's fast, visual, and throwaway.\nIts one durable output is the theme: a set of CSS theme variables that port into\nthe real app's `globals.css` `@theme` when you build the first UI feature.\nEverything else here gets discarded.\n\n**This skill is plan-first.** Gather the look and the page list, agree on a plan,\nand only then write any files. Never generate mockups before the user approves.\n\n## Step 1 - read what the plan already says\n\nPull the stated look and feel and the screen\u002Froute list from\n`blueprint\u002Fcontext\u002Fproject-overview.md` (its UI\u002FUX section); fall back to the UI\u002FUX section\nof `blueprint\u002Fproject-plan.md` if the overview isn't generated yet. Use this\nas the starting point, so you're refining the user's intent, not asking from\nscratch.\n\n## Step 2 - ask about the look and the pages\n\nWork in plan mode. Ask the user a short set of questions (use the current tool's\nshort user-input prompt for discrete choices when available), seeded with what\nthe plan already says:\n\n- **Look and feel** - confirm or adjust the vibe (light\u002Fdark, minimal\u002Frich,\n  density, editor-like, and so on), and ask for any reference apps or sites they\n  want it to feel like.\n- **Color and type** - any accent color or font direction (for example,\n  mono-forward for code).\n- **Which pages** - which screens to draft now. Default to the key routes from the\n  plan; let the user add, drop, or reorder. Lean to a few, not every screen.\n\nKeep it short. The user's answers, plus the plan, are the brief for the mockups.\n\n## Step 3 - propose the plan, then wait\n\nPresent a short plan and stop for approval:\n\n- the theme direction in a sentence or two (the vibe, accent, fonts), and\n- the list of screens you'll mock, one line each on what each will show (the real\n  states that exercise the theme, not empty shells).\n\nWrite nothing until the user approves. Adjust the plan if they push back.\n\n## Step 4 - lock one theme\n\nOnce approved, write a single shared `prototypes\u002Ftheme.css` that defines the theme\nas CSS variables, following `reference\u002Ftheme-variables.css`: surfaces, text,\naccent, any component-specific states, font stacks, and a small scale. Derive the\nvalues from the agreed brief.\n\nThis file is the deliverable. Keep it the single source of the theme, so tweaking\nit restyles every mockup at once.\n\n## Step 5 - mock each screen\n\nFor each approved screen, write a self-contained `prototypes\u002F\u003Cscreen>.html` that\nlinks `theme.css` and lays out that screen with realistic dummy content and the\nstates that matter (a typing page mid-type with correct\u002Fwrong\u002Fpending chars and a\ncaret; a dashboard with believable stats and history rows; and so on).\n\n- Plain HTML + CSS only. No framework, no build step. A few lines of inline JS for\n  a view toggle is fine; nothing more.\n- Pull every color, font, and spacing value from the `theme.css` variables, never\n  hard-coded. That's what keeps the look consistent and portable.\n- Realistic placeholder content over lorem ipsum. Desktop-first is enough.\n\n## Then stop\n\nTell the user to open the files in a browser and iterate on the look. Point them\nat the concrete next step: run `\u002Ffeature` on the first UI feature - it detects\n`prototypes\u002F`, links these mockups as the spec's Design reference, and makes\nporting `theme.css` into the app's `@theme` its first build step. When the theme\nfeels right the tokens carry into the real stylesheet; the HTML mockups are\nreference and get discarded at that feature's `\u002Fcomplete`.\n\n**Commit `prototypes\u002F`, do not ignore it.** `theme.css` is the durable output and\nuntil it is ported it lives nowhere else, and the mockups are the build reference\nthe next feature needs - both must survive a context clear or a switch between\nmachines. So do not add `prototypes\u002F` to `.gitignore`; it is short-lived in git\n(born here, discarded at the first UI feature's `\u002Fcomplete`), not throwaway that\nnever lands. This skill locks the look, it does not build the app.\n\n## Formatting\n\nFormat the output to match the project's conventions in\n`blueprint\u002Fcontext\u002Fai-interaction.md`: concise, scannable markdown, with lists for\nenumerations and tables for matrices rather than dense paragraphs.\n","# prototype - lock the look before you build\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` using the dashboard activity\ncontract in `AGENTS.md`.\n\nWhere this sits in the workflow:\n\n    plan  ->  \u002Foverview  ->  [prototype]  ->  \u002Ffeature  ->  build\n    (you      (project-      (lock the       (one spec    (real\n     write)    overview.md)   look)           at a time)   code)\n\nPrototyping is a pre-build step, not a feature. It's fast, visual, and throwaway.\nIts one durable output is the theme: a set of CSS theme variables that port into\nthe real app's `globals.css` `@theme` when you build the first UI feature.\nEverything else here gets discarded.\n\n**This skill is plan-first.** Gather the look and the page list, agree on a plan,\nand only then write any files. Never generate mockups before the user approves.\n\n## Step 1 - read what the plan already says\n\nPull the stated look and feel and the screen\u002Froute list from\n`blueprint\u002Fcontext\u002Fproject-overview.md` (its UI\u002FUX section); fall back to the UI\u002FUX section\nof `blueprint\u002Fproject-plan.md` if the overview isn't generated yet. Use this\nas the starting point, so you're refining the user's intent, not asking from\nscratch.\n\n## Step 2 - ask about the look and the pages\n\nWork in plan mode. Ask the user a short set of questions (use the current tool's\nshort user-input prompt for discrete choices when available), seeded with what\nthe plan already says:\n\n- **Look and feel** - confirm or adjust the vibe (light\u002Fdark, minimal\u002Frich,\n  density, editor-like, and so on), and ask for any reference apps or sites they\n  want it to feel like.\n- **Color and type** - any accent color or font direction (for example,\n  mono-forward for code).\n- **Which pages** - which screens to draft now. Default to the key routes from the\n  plan; let the user add, drop, or reorder. Lean to a few, not every screen.\n\nKeep it short. The user's answers, plus the plan, are the brief for the mockups.\n\n## Step 3 - propose the plan, then wait\n\nPresent a short plan and stop for approval:\n\n- the theme direction in a sentence or two (the vibe, accent, fonts), and\n- the list of screens you'll mock, one line each on what each will show (the real\n  states that exercise the theme, not empty shells).\n\nWrite nothing until the user approves. Adjust the plan if they push back.\n\n## Step 4 - lock one theme\n\nOnce approved, write a single shared `prototypes\u002Ftheme.css` that defines the theme\nas CSS variables, following `reference\u002Ftheme-variables.css`: surfaces, text,\naccent, any component-specific states, font stacks, and a small scale. Derive the\nvalues from the agreed brief.\n\nThis file is the deliverable. Keep it the single source of the theme, so tweaking\nit restyles every mockup at once.\n\n## Step 5 - mock each screen\n\nFor each approved screen, write a self-contained `prototypes\u002F\u003Cscreen>.html` that\nlinks `theme.css` and lays out that screen with realistic dummy content and the\nstates that matter (a typing page mid-type with correct\u002Fwrong\u002Fpending chars and a\ncaret; a dashboard with believable stats and history rows; and so on).\n\n- Plain HTML + CSS only. No framework, no build step. A few lines of inline JS for\n  a view toggle is fine; nothing more.\n- Pull every color, font, and spacing value from the `theme.css` variables, never\n  hard-coded. That's what keeps the look consistent and portable.\n- Realistic placeholder content over lorem ipsum. Desktop-first is enough.\n\n## Then stop\n\nTell the user to open the files in a browser and iterate on the look. Point them\nat the concrete next step: run `\u002Ffeature` on the first UI feature - it detects\n`prototypes\u002F`, links these mockups as the spec's Design reference, and makes\nporting `theme.css` into the app's `@theme` its first build step. When the theme\nfeels right the tokens carry into the real stylesheet; the HTML mockups are\nreference and get discarded at that feature's `\u002Fcomplete`.\n\n**Commit `prototypes\u002F`, do not ignore it.** `theme.css` is the durable output and\nuntil it is ported it lives nowhere else, and the mockups are the build reference\nthe next feature needs - both must survive a context clear or a switch between\nmachines. So do not add `prototypes\u002F` to `.gitignore`; it is short-lived in git\n(born here, discarded at the first UI feature's `\u002Fcomplete`), not throwaway that\nnever lands. This skill locks the look, it does not build the app.\n\n## Formatting\n\nFormat the output to match the project's conventions in\n`blueprint\u002Fcontext\u002Fai-interaction.md`: concise, scannable markdown, with lists for\nenumerations and tables for matrices rather than dense paragraphs.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","0007775402258962018a93be4dbf1cbcbc1536d8",".claude\u002Fskills\u002Fprototype",3,"https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass","https:\u002F\u002Fgithub.com\u002Fbradtraversy","traversymedia.com","Full stack web developer and online instructor at https:\u002F\u002Ftraversymedia.com and https:\u002F\u002Fstart.dev","2026-10-06 00:26:26",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add bradtraversy\u002Fskillpass --skill prototype",{"tool":40,"command":41},"bunx","bunx skills add bradtraversy\u002Fskillpass --skill prototype",{"tool":43,"command":44},"pnpm","pnpm dlx skills add bradtraversy\u002Fskillpass --skill prototype","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprototype\u002FSKILL.md",[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"reference\u002Ftheme-variables.css","OTHER","其他",1064,"https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprototype\u002Freference\u002Ftheme-variables.css",[54,60,66,71,77,83],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M782QBBKH3WTBZDE9DP52XH4","plan","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M782Q980Y1KP1J77TNJHD5H8","apply","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002Fskills\u002Fapply\u002FSKILL.md",[],[],{"skillNo":67,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M782Q75AS3P8SW7D819TACVD","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M782Q5WAP9DQH14TEKG5ZFX5","undeclared-network","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fundeclared-network\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M782Q424YF4TAYYX9TCCZCS8","prompt-injection","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fprompt-injection\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":6,"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},"01M782Q28RQV6MJM98J6EN7XFF","missing-manifest","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fmissing-manifest\u002FSKILL.md",[],[]]