docs(game-design): game bible + game-design skill #47
No reviewers
Labels
No labels
alpha:wave-0
alpha:wave-1
alpha:wave-2
alpha:wave-3
area:assets
area:combat
area:ecology
area:infra
area:render
area:scripting
area:ui
area:world
enhancement
epic
migration
post-alpha
roadmap
tech-debt
type:bug
type:chore
type:design
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
marco/IsoMmo!47
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/game-design-skill"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a collaborative game-design skill and the game bible it reads.
docs/game-design/vision.md— the design source of truth: pillars, player fantasy, hard constraints (server-authoritative, cross-platform, friends-scale, art-is-placeholder), and an index of the systems that already exist. Bootstrapped fromCLAUDE.md/docs/architecture.md; a few sections are marked (refine) for the owner to sharpen in their own words..claude/skills/game-design/SKILL.md— interviews the owner across six lenses (player POV, coherence incl. the server-enforceable hard filter, UI/UX, motivation & loop, breakage modes, scope/MVP) over as many rounds as it takes, drafts a design doc, pressure-tests it with a 3–4 agent review panel, then writesdocs/game-design/systems/<name>.mdand opens ONE Forgejo design issue with a player-observable Definition of Done. Stops there — technical breakdown is the separate dev/critical-review workflow.No code changes.