Skip to content

2.5.0

Choose a tag to compare

@NintendaDev NintendaDev released this 24 Oct 11:46
· 101 commits to main since this release
cd6c532

🚀 2.5.0 - Balance, experiments and extension control

Two new game-design skills cover balancing and cheap experiments, and extensions get finer control. Two settings behave differently, so read the next block before you upgrade.

⚠️ Breaking Changes

  • subagents.model.<agent> is now a map of roles - a single value such as model.claude: sonnet is no longer read, so the built-in model applies until you move it under reader, validator or executor. /unikit config update leaves the old line as it is and lists it as skipped.
  • Runs without a terminal no longer install new extension items by themselves - in CI or scripts, add --install-new to unikit-ai update or unikit-ai extension update to install what a new extension version brings. Items you switched off stay off.

⚙️ Subagent Model and Effort

Subagent settings are now split by role (reader, validator, executor), and a new subagents.effort block sets reasoning effort the same way. Edits apply on the next command; unikit-ai update is not needed.

Details
  • A reader collects facts, a validator checks a finished result, an executor produces pralled as .unikit/system/subagent-roles.md
  • Claude Code defaults: sonnet and medium for readers and validators, the session's own for executors; Codex and Antigravity have their own values, and Antigravity has no effort key
  • Words in a request, such as "use opus for the subagents" or "effort high", win over the config for that run
  • The implement and plan coordinators pass model and effort to their workers, sidecars a
  • Cursor, OpenCode, Kimi Code, Qwen Code and Universal / Other pass nothing; set the model in the client itself

✨ Balance Checkpoints

New /unikit-gd-balance keeps a balance document for a topic and hands out one measurement checkpoint at a time. You bring the results back, and it revises the roadmap and issues the next checkpoint.

What's included
  • Documents live in .unikit/gamedesign/balance/; the skill never edits the GDD or code
  • /unikit-plan builds a plan only up to the current checkpoint, with Measure: tasks and a final Hand-back: task
  • /unikit-implement takes the measurements, /unikit-verify checks the report, and /unikit-improve keeps the plan in step with the document
  • A plan waits as ⏳ AWAITING RESULT until the measurements come back
  • A checkpoint can go to /unikit-gd-experiment instead of a direct measurement

✨ Design Experiments

New /unikit-gd-experiment turns a design problem into cheap, testable experiment cards and keeps an honest record of what players showed. /unikit-plan can build a disposable prototype from a card.

What's included
  • Finds at least five ideas and thinks one through (precedents, options, how a test can mislead); a deep pass also searches the web, and nothing is saved before you approve
  • A card can start from a design research or a balance checkpoint and keeps a Based on link that the plan reads
  • Evaluates pasted feedback, chats or files over several rounds
  • Manages the catalog in .unikit/gamedesign/experiments/: list, compare, best, failed, retest, edit, archive, or find a card by its description
  • Plans built from cards run on an experiment/ branch (git.experiment_branch_prefix); /unikit-gd-explore gains an experiment design lens

♻️ Research and Questions

/unikit-gd-explore research is easier to resume and check, and skills now ask questions the same way, with the options listed first.

Details
  • Research records start with an Active Summary and keep a Sessions log; a coherence che
  • ultra <topic> pins the dialogue log and saves extra artifacts
  • A named slice of code can be investigated without a GDD
  • Options and what each one changes are printed as a numbered list, then asked with yourquestions carry no made-up answers
  • /unikit-plan ends with a printed list of next steps instead of a closing question

🧩 Extension Control

Extensions can now add text to base skills at named places, and you choose which of an extension's skills, subagents and MCP servers are installed. Extension authors also get fixed variables for system file paths.

What's included
  • Extension points: a bootstrap anchor in 35 base skills; manifest entries use point and id with optional reference files (UniKit versions before 2.5.0 reject such a manifest)
  • unikit-ai extension add shows a menu in a terminal, or takes --skip-skills, --skip-subagents, --skip-mcp and --yes; new unikit-ai extension select <name> changes the choice later
  • Choices survive update, update --force and init; --install-new and --skip-new now work on update and extension update, and extension list shows Skipped: and Not decided:
  • 28 system-file path variables, such as {{user_questions_contract}}; an unknown {{name}} stays as written and is listed only under --verbose
  • Extension text no longer makes installed skills look locally modified

🐛 Fixes

  • /unikit-verify on an unfinished plan checks only the tasks that were executed, instead of reporting the rest as missing and blocking
  • /unikit-implement asks whether to merge test runs when the scope holds one phase run plus the final full run; it skipped the question before

Full Changelog: 2.4.1...2.5.0