[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79M8NJTC75ZJCS5855WSH8Y":3,"skill-same:01M79M8NJTC75ZJCS5855WSH8Y":50},{"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":30,"commitSha":31,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79M8NJTC75ZJCS5855WSH8Y","game-jam",null,"Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours, cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.","mistervaibhav\u002Fskills","mistervaibhav","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41189028?v=4","01M79KACH05EG9FMM6DQVHAVK9","Vaibhav Singh","01M79KACJB3431Y8CFJQ02MTTM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fgame-jam\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: game-jam\ndescription: >\n  Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours,\n  cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game\n  Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.\nlicense: Apache-2.0\ncompatibility: Engine-agnostic process skill; submission steps assume itch.io-hosted jams.\nmetadata:\n  engine: none\n  category: workflows\n  difficulty: beginner\n---\n\n# Game Jam\n\nTurn a theme and a fixed deadline into a finished, submitted game. This is a planning and\nscope-control playbook, not engine code: the win condition is *something submitted and\nplayable*, not *the game you imagined*.\n\n## When to use\n\n- Use when entering a timed jam (Ludum Dare, GMTK Jam, Global Game Jam, a weekend jam),\n  scoping a 48-hour build, or deciding what to cut to hit a deadline.\n- Use when the user asks \"what can I actually build in a weekend\" or \"how do I submit to\n  this jam\".\n\n**When *not* to use:** building the *core loop* in engine code (use the engine skill —\n`godot-2d-movement`, `phaser-core`, etc. — or a genre skill like `platformer`); throwaway\nexperiments with no deadline (use `prototype-fast`); shipping a commercial release (use\n`steam-publish` \u002F `itch-publish`).\n\n## Core workflow\n\n1. **Read the rules before the theme drops.** Confirm the jam's *length*, *theme reveal\n   time*, *submission deadline (with timezone)*, whether teams\u002Fpre-made assets\u002Fengines are\n   allowed, and whether ratings require you to rate other entries. Missing one of these\n   disqualifies an otherwise-finished game.\n2. **Prep the boring parts in advance** (allowed by most jams): empty project that builds\n   and exports, input + a title\u002Fend screen stub, an export pipeline you've run once, and a\n   font\u002FSFX source you're licensed to use. Day-one time is too precious to spend here.\n3. **Theme → one sentence.** Brainstorm 10 ideas in 15 minutes, then commit to **one**\n   expressible as: *\"You [verb] to [goal] while [constraint].\"* If you can't say it in one\n   sentence, it's too big.\n4. **Scope to the clock, not the idea.** Use the budget table below. Pick **one** core\n   mechanic and **one** \"hook\". Everything else is a stretch goal.\n5. **Build the vertical slice first.** Get a 30-second playable loop (start → play → lose\u002Fwin\n   → restart) running early. A complete tiny loop beats a half-built big one.\n6. **Reserve the last ~20% of the clock for shipping**, not features. Export, test the build\n   on a clean path, capture screenshots, write the page. Builds always break at hour 47.\n7. **Submit early, update if time remains.** Upload a working build *well before* the\n   deadline; most jam pages let you swap the file until it closes. A submitted mediocre game\n   scores; an unsubmitted great one does not.\n\n## Patterns\n\n### 1. Scope budget by jam length (plan backwards from the deadline)\n\n```text\n              | 48-hour jam            | 72-hour jam           | 1-week jam\n--------------|------------------------|-----------------------|------------------------\nCore mechanic | 1, proven by hour 6    | 1-2                   | 2-3 interacting\nLevels\u002Fcontent| 1 hand-made or gen'd   | 3-5                   | 8-12 + progression\nArt           | placeholder\u002F1 palette  | cohesive 1-artist set | themed set + UI\nAudio         | 3-5 SFX + 1 loop       | SFX + 1-2 tracks      | adaptive music\nSHIP BUFFER   | last 8-10 h            | last 12-16 h          | last full day\n```\n\n### 2. The 48-hour timeline (concrete blocks)\n\n```text\nH0-2    Ideate -> lock ONE-sentence concept -> name the core mechanic + win\u002Flose.\nH2-8    Core loop in code with primitives (boxes\u002Fcircles). Make it playable, no art.\nH8-12   Sleep. (Tired code is tomorrow's bug list.)\nH12-24  Content: 1 level\u002Fencounter, tune difficulty, add the \"hook\" feature.\nH24-30  Sleep + playtest with one other person; cut anything not landing.\nH30-38  Art + audio pass. Juice: screenshake, hit-stop, tween, particles, SFX.\nH38-44  Bug-fix freeze: no new features. Fix only crashes + soft-locks.\nH44-48  EXPORT, test the build clean, screenshots, write page, SUBMIT (by ~H46).\n```\n\n### 3. Feature triage — decide fast, decide out loud\n\n```text\nFor every feature ask, in order:\n  1. Does the core loop work WITHOUT it?   -> if yes, it's a stretch goal, not MVP.\n  2. Can a player tell it's missing?       -> if no, cut it.\n  3. Is it \u003C 30 min of work?               -> if no, defer past the ship buffer.\nDefault answer under deadline pressure is CUT. You can always add in a post-jam version.\n```\n\n### 4. Pre-submission build check (run on a clean copy, not your dev folder)\n\n```text\n[ ] Build runs from an extracted zip on a path with NO engine\u002FIDE installed.\n[ ] Controls are shown on-screen or on the page (jurors won't read your mind).\n[ ] No dev console errors; no soft-lock; restart works.\n[ ] Web build (if any) is set to the platform's playable-in-browser mode.\n[ ] Page has: 1-line pitch, controls, screenshots, credits + asset licenses.\n[ ] File uploaded and the submission is actually attached to the JAM, not just the page.\n```\n\n## Pitfalls\n\n- **Scope creep is the #1 jam killer.** If the core loop isn't playable by the first third\n  of the clock, cut features now, not later.\n- **No ship buffer.** Exporting, zipping, and writing the page reliably takes 1-3 hours and\n  always surfaces a build bug. Treat the deadline as ~2 hours earlier than it is.\n- **Submitting to the page but not the jam.** On itch.io a jam entry is a separate\n  *submission* linked from the jam page — uploading the game alone does not enter it.\n- **Untested export.** \"Works in the editor\" is not \"works in the build.\" Test the exported\n  artifact on a clean path; missing assets and wrong working directories are classic.\n- **Unlicensed assets.** Music\u002Ffonts\u002Fsprites pulled from the web can violate jam rules and\n  break later distribution. Use assets you're licensed for and list them in the credits.\n- **Polishing before the loop is fun.** Juice multiplies fun; it can't create it. Get the\n  loop right with placeholders first.\n\n## References\n\n- For the throwaway-vs-keep prototyping mindset and greyboxing technique, read the\n  `prototype-fast` skill.\n- For the actual upload mechanics (project page, channels, `butler push`), read\n  `itch-publish`.\n\n## Related skills\n\n- `prototype-fast` — validate a mechanic quickly before committing jam hours to it.\n- `itch-publish` — create the page and upload the build (most jams are hosted on itch.io).\n- Engine cores (`phaser-core`, `love2d-core`, `godot-gdscript`, …) and genre skills\n  (`platformer`, `roguelike`, …) — build the actual loop the jam scopes around.\n","# Game Jam\n\nTurn a theme and a fixed deadline into a finished, submitted game. This is a planning and\nscope-control playbook, not engine code: the win condition is *something submitted and\nplayable*, not *the game you imagined*.\n\n## When to use\n\n- Use when entering a timed jam (Ludum Dare, GMTK Jam, Global Game Jam, a weekend jam),\n  scoping a 48-hour build, or deciding what to cut to hit a deadline.\n- Use when the user asks \"what can I actually build in a weekend\" or \"how do I submit to\n  this jam\".\n\n**When *not* to use:** building the *core loop* in engine code (use the engine skill —\n`godot-2d-movement`, `phaser-core`, etc. — or a genre skill like `platformer`); throwaway\nexperiments with no deadline (use `prototype-fast`); shipping a commercial release (use\n`steam-publish` \u002F `itch-publish`).\n\n## Core workflow\n\n1. **Read the rules before the theme drops.** Confirm the jam's *length*, *theme reveal\n   time*, *submission deadline (with timezone)*, whether teams\u002Fpre-made assets\u002Fengines are\n   allowed, and whether ratings require you to rate other entries. Missing one of these\n   disqualifies an otherwise-finished game.\n2. **Prep the boring parts in advance** (allowed by most jams): empty project that builds\n   and exports, input + a title\u002Fend screen stub, an export pipeline you've run once, and a\n   font\u002FSFX source you're licensed to use. Day-one time is too precious to spend here.\n3. **Theme → one sentence.** Brainstorm 10 ideas in 15 minutes, then commit to **one**\n   expressible as: *\"You [verb] to [goal] while [constraint].\"* If you can't say it in one\n   sentence, it's too big.\n4. **Scope to the clock, not the idea.** Use the budget table below. Pick **one** core\n   mechanic and **one** \"hook\". Everything else is a stretch goal.\n5. **Build the vertical slice first.** Get a 30-second playable loop (start → play → lose\u002Fwin\n   → restart) running early. A complete tiny loop beats a half-built big one.\n6. **Reserve the last ~20% of the clock for shipping**, not features. Export, test the build\n   on a clean path, capture screenshots, write the page. Builds always break at hour 47.\n7. **Submit early, update if time remains.** Upload a working build *well before* the\n   deadline; most jam pages let you swap the file until it closes. A submitted mediocre game\n   scores; an unsubmitted great one does not.\n\n## Patterns\n\n### 1. Scope budget by jam length (plan backwards from the deadline)\n\n```text\n              | 48-hour jam            | 72-hour jam           | 1-week jam\n--------------|------------------------|-----------------------|------------------------\nCore mechanic | 1, proven by hour 6    | 1-2                   | 2-3 interacting\nLevels\u002Fcontent| 1 hand-made or gen'd   | 3-5                   | 8-12 + progression\nArt           | placeholder\u002F1 palette  | cohesive 1-artist set | themed set + UI\nAudio         | 3-5 SFX + 1 loop       | SFX + 1-2 tracks      | adaptive music\nSHIP BUFFER   | last 8-10 h            | last 12-16 h          | last full day\n```\n\n### 2. The 48-hour timeline (concrete blocks)\n\n```text\nH0-2    Ideate -> lock ONE-sentence concept -> name the core mechanic + win\u002Flose.\nH2-8    Core loop in code with primitives (boxes\u002Fcircles). Make it playable, no art.\nH8-12   Sleep. (Tired code is tomorrow's bug list.)\nH12-24  Content: 1 level\u002Fencounter, tune difficulty, add the \"hook\" feature.\nH24-30  Sleep + playtest with one other person; cut anything not landing.\nH30-38  Art + audio pass. Juice: screenshake, hit-stop, tween, particles, SFX.\nH38-44  Bug-fix freeze: no new features. Fix only crashes + soft-locks.\nH44-48  EXPORT, test the build clean, screenshots, write page, SUBMIT (by ~H46).\n```\n\n### 3. Feature triage — decide fast, decide out loud\n\n```text\nFor every feature ask, in order:\n  1. Does the core loop work WITHOUT it?   -> if yes, it's a stretch goal, not MVP.\n  2. Can a player tell it's missing?       -> if no, cut it.\n  3. Is it \u003C 30 min of work?               -> if no, defer past the ship buffer.\nDefault answer under deadline pressure is CUT. You can always add in a post-jam version.\n```\n\n### 4. Pre-submission build check (run on a clean copy, not your dev folder)\n\n```text\n[ ] Build runs from an extracted zip on a path with NO engine\u002FIDE installed.\n[ ] Controls are shown on-screen or on the page (jurors won't read your mind).\n[ ] No dev console errors; no soft-lock; restart works.\n[ ] Web build (if any) is set to the platform's playable-in-browser mode.\n[ ] Page has: 1-line pitch, controls, screenshots, credits + asset licenses.\n[ ] File uploaded and the submission is actually attached to the JAM, not just the page.\n```\n\n## Pitfalls\n\n- **Scope creep is the #1 jam killer.** If the core loop isn't playable by the first third\n  of the clock, cut features now, not later.\n- **No ship buffer.** Exporting, zipping, and writing the page reliably takes 1-3 hours and\n  always surfaces a build bug. Treat the deadline as ~2 hours earlier than it is.\n- **Submitting to the page but not the jam.** On itch.io a jam entry is a separate\n  *submission* linked from the jam page — uploading the game alone does not enter it.\n- **Untested export.** \"Works in the editor\" is not \"works in the build.\" Test the exported\n  artifact on a clean path; missing assets and wrong working directories are classic.\n- **Unlicensed assets.** Music\u002Ffonts\u002Fsprites pulled from the web can violate jam rules and\n  break later distribution. Use assets you're licensed for and list them in the credits.\n- **Polishing before the loop is fun.** Juice multiplies fun; it can't create it. Get the\n  loop right with placeholders first.\n\n## References\n\n- For the throwaway-vs-keep prototyping mindset and greyboxing technique, read the\n  `prototype-fast` skill.\n- For the actual upload mechanics (project page, channels, `butler push`), read\n  `itch-publish`.\n\n## Related skills\n\n- `prototype-fast` — validate a mechanic quickly before committing jam hours to it.\n- `itch-publish` — create the page and upload the build (most jams are hosted on itch.io).\n- Engine cores (`phaser-core`, `love2d-core`, `godot-gdscript`, …) and genre skills\n  (`platformer`, `roguelike`, …) — build the actual loop the jam scopes around.\n",{"name":5,"license":15,"metadata":24,"description":28,"compatibility":29},{"engine":25,"category":26,"difficulty":27},"none","workflows","beginner","Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours, cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.\n","Engine-agnostic process skill; submission steps assume itch.io-hosted jams.","main","6d4e3296d58b2720c5b1026197cd069b1dde4789","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills","https:\u002F\u002Fgithub.com\u002Fmistervaibhav","Software Engineer","2026-07-24 17:16:42",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add mistervaibhav\u002Fskills --skill game-jam",{"tool":42,"command":43},"bunx","bunx skills add mistervaibhav\u002Fskills --skill game-jam",{"tool":45,"command":46},"pnpm","pnpm dlx skills add mistervaibhav\u002Fskills --skill game-jam","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fgame-jam\u002FSKILL.md",true,[],[51,59,67,75,82,89],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79NZDV5781GA6SJMN1QPXB4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79NZ8SEVWT4WYD49BV980YW","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", or \"type hierarchy\". Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","MIT","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79NYVQS5NYHH36NXF2AHP8B","web-haptics","Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fweb-haptics\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fweb-haptics\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79NY8AMC62DDRSH21WKXJVE","visual-novel","Build a visual novel: a branching script, character and background display, a text box with choices, save\u002Fload, backlog, and skip\u002Fauto. Use for a VN, dating sim, or branching story game.","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fvisual-novel\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79NWFM5R9QC9Y2AT40EHF44","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", or \"navigation problems\". Covers Nielsen's 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79NVSG7AB3MSFT8Y6EEHG1B","unreal-packaging","Package and ship an Unreal Engine 5 project: the Platforms menu Package Project flow, build configurations (Development vs Shipping), cooking content, packaging settings and the Game Default Map, and command-line builds with RunUAT BuildCookRun. Use when packaging a build, making a shipping build, cooking content, configuring packaging settings, or when the user mentions package Unreal, cook content, shipping build, or BuildCookRun.","https:\u002F\u002Fgithub.com\u002Fmistervaibhav\u002Fskills\u002Fblob\u002Fmain\u002Funreal-packaging\u002FSKILL.md",[],[]]