This skill turns a jam theme and a deadline into a submitted, playable game. The agent records the jam rules in a JAM.md file, helps the user commit to a one-sentence concept, builds the smallest playable loop first and cuts features on schedule.
It reserves the last fifth of the clock for shipping and runs the export checks itself: a clean-folder launch, a package listing and a rules review. The user decides the concept, plays the build and presses submit.
What You Get
- A scope budget table for 48-hour, 72 to 96 hour and one-week jams
- A 48-hour timeline from concept lock to submission around hour 46
- A feature triage rule that defaults to cutting under deadline pressure
- A JAM.md skeleton with the deadline in UTC and local time, rules, concept, MVP, stretch list and cut log
- A verify list for the exported build and a gotcha list covering late scope, untested exports and the difference between uploading to a game page and entering the jam
- Dated notes on Ludum Dare, GMTK 2026 and Global Game Jam 2027 rules
Common Use Cases
- Starting a 48-hour jam and deciding what fits in the clock
- Cutting features when the core loop is late
- Checking an exported build before the submission deadline
- Finding which jam rules on AI assets, platforms and upload locks apply
What Makes It Unique
The skill treats the win condition as a build attached to the jam before it closes. It records rule details that have disqualified finished games, such as upload locks, AI asset rules and the difference between a game page upload and a jam entry, and it asks the user to treat the deadline as two hours earlier than it is.
Under The Hood
The agent loads the SKILL.md and reads sibling skills only when pointed to them. It asks the user for the jam page address and reads that page, so it can fetch a web page, then writes a JAM.md planning file in your project. It runs the engine’s command line export, unzips the result into a temporary folder and launches it, or serves it on localhost and opens it in a headless browser, and lists the zip contents. It does not upload or submit anything; the user plays the build and submits.