Repository navigation
Add the world-design-review skill - #377
Merged
Merged
Conversation
…swered by the doctor, a sweep, the simulator or a lab Ideas adapted with attribution from Scouten2/LevelDesignSkill (MIT) and Youtouch/Game-Design-Skills (Apache-2.0); licence notices in references/borrowed.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a project skill,
world-design-review, at.agents/skills/world-design-review/(symlinked from.claude/skills/, the same waypackage-playthroughlives).What it does. It reviews a world file, a
floor:block, guards, an arc or a world-generation change for design. It starts with the rulings (VISION.md principles and AGENTS.md rules, given as links), then asks questions under these lenses: goal and legibility, fairness ("Tough, never Nasty"), layout, pacing, variety and difficulty. Each lens names where to look and what counts as evidence: a doctor finding, a sweep assertion, a fight-simulator result or a lab score, never "it reads better". Anything else has to be labelled a hand trace. Findings are sorted into three groups: "the engine already enforces", "a doctor finding or sweep should enforce" and "the owner's call".references/principles.md: the design research behind each lens (Nelson, Plotkin, Gilbert, Alexander, Dormans, Cogmind, Left 4 Dead, Compton and others). Each entry has its link and says where it bears on this game, and which ruling wins where the two disagree.references/borrowed.md: checklist items adapted from Scouten2/LevelDesignSkill (MIT) and Youtouch/Game-Design-Skills (Apache-2.0), with their licence notices. Nothing is installed or vendored, and nothing comes from GPL or unlicensed sources.Merge order. The layout lens points to the doctor's lock-aware reachability finding ("is every key reachable without first passing its own lock?"). That finding is being added to
Story::Doctorby a separate change, so this PR should merge after that one.Difficulty numbers are passed on to the engine repository's
fight-numbersskill, which is a separate engine change. No game code, world file or prompt is touched, and no model call was made.