Run any Skill in Manus with one click

open-world-design

Stars23

Forks1

UpdatedJune 28, 2026 at 22:47

Use when designing, generating, or reviewing the spatial side of an open world — macro-layout and terrain, landmarks and sightlines, biome identity, verticality, navigation/wayfinding, signal color, exploration pull, and spatial pacing (the wonder→fear gradient, tension/release). Also use to diagnose a world that feels empty, samey, or like marker-following "icon vomit". Triggers on "open world", "world map", "world layout", "wayfinding", "triangle rule", "make the world feel alive", "points of interest", "icon vomit", "fast travel".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rondorkerin

rondorkerin/gamestack

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name

open-world-design

description

Open-World Design

How to build open worlds that pull players through the world itself — landmarks, sightlines, and terrain that create curiosity — rather than pushing them down a dotted line to a waypoint.

When to use this

Laying out a region or macro-map (terrain, landmarks, biomes, routes)
Designing or auditing navigation and wayfinding
Diagnosing a world that feels empty, samey, or like a checklist
Tuning the emotional pacing of exploration

Scope

This skill owns the spatial discipline. Adjacent concerns live in sibling skills, cross-linked from the guide:

What fills the space and how to generate it → procedural-generation, procgen-review
Quests in that space → narrative-and-quest-design
Progression/gating math → rpg-systems
Lore the space carries → worldbuilding-and-lore
General reward/flow theory → game-design-fundamentals

How the pieces fit

GUIDE.md — the why, with exemplars and citations: terrain as a communication system, gravity & flow, interconnection, biome identity, verticality, diegetic navigation, signal color, exploration pull, spatial pacing.
CHECKLIST.md — the what to do: Do/Don't items plus the "test for" criteria you can run against a map or a generated region.

The one idea to anchor on

Make every patch of the map either visibly promising or quietly hiding something worth finding. A great open world guides through the world, not the HUD. If the player is watching a minimap arrow instead of the horizon, the world has become an obstacle between them and a waypoint — and you've lost.

Start with GUIDE.md, then apply CHECKLIST.md.

More from this repository

same repository

gamestack-upgrade

rondorkerin/gamestack

Check whether the installed gamestack plugin is behind the marketplace's latest version and update it in place. Use when asked to "upgrade gamestack", "update gamestack", "check for gamestack updates", "is gamestack up to date", "auto update the plugin", "gamestack upgrade", or "what's new in gamestack". Pure plugin-maintenance utility — no design bible, no engine detection, nothing game-specific.

2026-06-3023

iteration-loop

rondorkerin/gamestack

Use when bringing any system — visual (terrain/biome/dungeon/town/castle/character/enemy/NPC/spell-fx), systemic (balance/economy/difficulty), or narrative (lore/quests) — up to fidelity with its intended target through repeated cycles, in any engine. Covers the generic Reference → Diff → Prioritize → Generate/Implement → Verify loop, a preview-harness pattern for screenshotting/inspecting a system in isolation, the animation-can't-be-eyeballed-from-one-frame problem (contact-sheet capture), the external-asset/content-request escalation (when generation is the wrong tool — e.g. animations, trees), the two playtesting channels — human playtesters and an AI playtester that self-verifies via logs/screenshots through a "playtester API" — a human-checkpoint/batching pattern for scaling a generated visual change (including a cheap-mockup gate before heavyweight 3D/tileset generation), and an asset-pack organization + browsable-studio/explorer pattern for what gets approved. Also use to diagnose a project that's gen

2026-06-3023

game-design-process

rondorkerin/gamestack

The orchestrator for designing a game end to end. Use when starting or steering a game's design — "I'm making a game", "where do I start", "design this game with me", "what's next in the design", or running headless to take a concept to generated, reviewed content. Engine-agnostic; tuned for procedural / AI-authored games (e.g. a procgen open-world RPG in Godot). Sequences the pipeline and names which knowledge/process skill to pull at each phase. Stops at design/spec — does not write gameplay code.

2026-06-3023

procgen-review

rondorkerin/gamestack

Run this to review a batch of procedurally- or AI-generated game content (dungeons, regions, quests, items, NPCs, lore, history) before it's committed. Stands in for the human designer's eye in a headless generation loop. Runs the oatmeal test (perceptual sameness), the fanfic/retell test (is it worth retelling), a cross-instance sameness scan (structural/thematic duplication), an intentionality gate (who/what/why + completion arc), and an anti-pattern gate. Outputs a structured pass/fail verdict with specific fixes routed back to the generator. Triggers on "review generated content", "check for sameness", "procgen review", "oatmeal test", "is my generated content any good", "gate this content".

2026-06-3023

3d-graphics-and-rendering

rondorkerin/gamestack

Use when designing, choosing, or reviewing the rendering layer of any real-time 3D (or 2D-with-lighting) game — the rasterization pipeline, PBR vs stylized/NPR materials, the forward/deferred/forward+ lighting architecture, global-illumination and shadow choices, culling/LOD/draw-call/overdraw performance budgets, and the post-processing chain (tonemapping, bloom, AO, anti-aliasing). Also use to diagnose a scene that's GPU-bound or CPU-bound, shadow acne or peter-panning, pop-in, overdraw blowout, blown-out or washed-out tonemapping, or content that looks visually incoherent across generated scenes. Triggers on "rendering pipeline", "PBR", "metallic roughness", "deferred vs forward", "forward+", "global illumination", "GI", "lightmaps", "light probes", "SDFGI", "shadow maps", "cascaded shadows", "shadow acne", "peter panning", "frustum culling", "occlusion culling", "LOD", "pop-in", "draw calls", "batching", "instancing", "overdraw", "CPU bound", "GPU bound", "tonemapping", "ACES", "bloom", "SSAO", "ambient o

2026-06-3023

animation-systems

rondorkerin/gamestack

Use when designing, speccing, or reviewing a character/object motion system in ANY engine — the rig and skeleton, skinning (linear blend vs dual-quaternion, the candy-wrapper artifact), forward vs inverse kinematics, IK solvers (two-bone, FABRIK, CCD, look-at), blend trees and blend spaces (1D/2D), animation state machines, additive layers and upper/lower-body splits, ragdoll and active ragdoll, procedural IK foot placement on uneven terrain, secondary motion (spring bones, cloth, hair), motion matching, animation compression and bone-count budgets, root motion vs in-place, and the anticipation/active/recovery timing decomposition with animation-canceling. Also use to diagnose feet that slide or float, a mesh that pinches when it twists, blends that pop or moonwalk, characters that feel animation-locked, or a motion library that blows the memory budget. Triggers on "animation system", "skeletal animation", "skinning", "candy wrapper", "dual quaternion", "rigging", "inverse kinematics", "IK", "foot placement",

2026-06-3023

name

open-world-design

description

Open-World Design

How to build open worlds that pull players through the world itself — landmarks, sightlines, and terrain that create curiosity — rather than pushing them down a dotted line to a waypoint.

When to use this

Laying out a region or macro-map (terrain, landmarks, biomes, routes)
Designing or auditing navigation and wayfinding
Diagnosing a world that feels empty, samey, or like a checklist
Tuning the emotional pacing of exploration

Scope

This skill owns the spatial discipline. Adjacent concerns live in sibling skills, cross-linked from the guide:

What fills the space and how to generate it → procedural-generation, procgen-review
Quests in that space → narrative-and-quest-design
Progression/gating math → rpg-systems
Lore the space carries → worldbuilding-and-lore
General reward/flow theory → game-design-fundamentals

How the pieces fit

GUIDE.md — the why, with exemplars and citations: terrain as a communication system, gravity & flow, interconnection, biome identity, verticality, diegetic navigation, signal color, exploration pull, spatial pacing.
CHECKLIST.md — the what to do: Do/Don't items plus the "test for" criteria you can run against a map or a generated region.

The one idea to anchor on

Make every patch of the map either visibly promising or quietly hiding something worth finding. A great open world guides through the world, not the HUD. If the player is watching a minimap arrow instead of the horizon, the world has become an obstacle between them and a waypoint — and you've lost.

Start with GUIDE.md, then apply CHECKLIST.md.