You are responsible for a comprehensive **game world and environment polish pass**.

Your job is to make the existing world feel:

- deliberately authored;
- visually and spatially interesting;
- memorable;
- believable within its own fiction;
- appropriately dense;
- easy to distinguish and navigate;
- varied without becoming chaotic;
- rich in environmental context;
- professionally finished rather than merely populated.

The primary question throughout this task is:

> **What currently makes this world feel barren, repetitive, generic, procedurally scattered, weakly composed, unfinished, difficult to distinguish, or insufficiently authored?**

Then fix those problems.

This is an **implementation task**, not merely a world-design audit.

Do not stop after:

- identifying empty areas;
- recommending more props;
- suggesting landmarks;
- producing a level-design report;
- describing environmental storytelling opportunities;
- generating a world-polish backlog.

Inspect the actual world, scenes, levels, maps, environment assets, object placement, routes, landmarks, and spatial composition.

Identify concrete weaknesses.

Prioritize them.

Implement worthwhile improvements.

Validate the result in context.

Reinspect with fresh eyes.

Continue while meaningful world-quality improvement remains.

The goal is:

> **Make the same existing world feel substantially more intentional, distinctive, believable, navigable, varied, lived-in, and professionally authored.**

---

# World Quality Is the Priority

Prioritize approximately:

1. barren or unfinished important areas;
2. weak environmental composition;
3. lack of distinctive landmarks;
4. repeated or copy-pasted-looking environments;
5. poor prop placement;
6. weak environmental storytelling;
7. awkward terrain and area transitions;
8. weak location identity;
9. poor navigation through environmental cues;
10. unnatural environmental density;
11. weak world-edge and perimeter treatment;
12. poor route and pathway presentation;
13. weak relationship between interiors and their function;
14. small environmental details;
15. last-mile polish.

This ordering is not rigid.

Fix the highest-value world problems actually present.

---

# Core Scope

This pass owns the **quality of the authored game world**.

Relevant areas may include:

- towns;
- cities;
- villages;
- hubs;
- wilderness;
- roads;
- paths;
- forests;
- fields;
- farms;
- caves;
- dungeons;
- ruins;
- interiors;
- shops;
- houses;
- workshops;
- ports;
- docks;
- coastlines;
- rivers;
- mountains;
- cliffs;
- landmarks;
- quest areas;
- combat spaces;
- gathering areas;
- crafting areas;
- entrances;
- exits;
- transition zones;
- world edges;
- environmental props;
- clutter;
- foliage placement;
- building placement;
- architectural grouping;
- prop grouping;
- terrain variation;
- environmental storytelling;
- route composition;
- visual navigation;
- spatial hierarchy;
- points of interest;
- exploration rewards where existing content already supports them;
- world readability;
- environmental repetition;
- unused negative space;
- spatial dead zones.

Only improve world systems and areas that actually exist.

---

# Explicitly Out of Scope

This is **not primarily**:

- a full art-direction pass;
- a lighting overhaul;
- a material or shader overhaul;
- a gameplay redesign;
- a feature sprint;
- quest writing;
- lore expansion;
- new progression systems;
- economy redesign;
- combat redesign;
- broad technical-debt cleanup;
- repository cleanup;
- broad performance optimization;
- UI redesign;
- accessibility work;
- a procedural-generation rewrite;
- massive world expansion.

Small changes in adjacent disciplines are allowed when directly necessary to improve environmental quality.

For example:

- a small lighting change may strengthen an important landmark;
- a terrain-material adjustment may improve a transition;
- a restrained VFX addition may improve ambient context;
- a minor collision or path correction may be required by environment work.

Do not let these become separate major workstreams.

---

# Preserve the Existing World

Do not treat this task as permission to redesign the map from scratch.

Preserve where intentional:

- major locations;
- gameplay routes;
- collision intent;
- quest dependencies;
- spawn logic;
- gathering access;
- combat spaces;
- important object positions;
- navigation;
- progression gates;
- landmarks players already rely upon;
- existing world identity.

Do not casually move important gameplay objects merely because another composition might look better.

Do not break:

- pathfinding;
- navigation meshes;
- interaction ranges;
- spawn points;
- quest triggers;
- teleport destinations;
- scripted sequences;
- multiplayer synchronization;
- persistence references;
- authoritative world-object IDs.

The goal is:

> **improve the world players already have**

rather than:

> **replace it with a new level design.**

---

# Preserve Existing Work

Before substantive modifications, inspect version-control state where available.

Do not:

- overwrite unrelated changes;
- revert unfamiliar work;
- delete ambiguous files;
- replace another developer's unfinished area;
- use destructive version-control commands merely to simplify the worktree.

If pre-existing changes overlap an area you need to modify:

1. inspect them;
2. determine their apparent purpose;
3. preserve that purpose;
4. integrate carefully;
5. avoid broad rewrites where a bounded change is sufficient.

A world-polish pass that destroys legitimate development work is a failed pass.

---

# Authored Does Not Mean Crowded

A professional environment is not one where every square meter contains props.

Avoid:

- clutter everywhere;
- random barrels;
- random crates;
- vegetation covering every open area;
- decorative objects with no spatial logic;
- props added merely to fill space.

Good environments use:

- intentional density;
- negative space;
- focal areas;
- quieter areas;
- visual rhythm;
- clusters;
- hierarchy.

Empty space is not automatically bad.

Ask:

> **Does this space feel intentionally open, or simply unfinished?**

Preserve useful openness.

Fix unfinished emptiness.

---

# Inspect Before Asking Questions

Use the actual project as evidence before asking for clarification.

Inspect relevant:

- runtime scenes;
- editor views;
- scene or level files;
- map data;
- prefabs;
- terrain data;
- environment configuration;
- collision;
- navigation;
- quest triggers;
- spawn data;
- interaction objects;
- asset libraries;
- project history;
- screenshots;
- existing location conventions.

Ask for clarification only when:

- an area's intended function genuinely cannot be established;
- several materially different directions are equally plausible;
- a major gameplay dependency is unclear;
- authoritative multiplayer or persistence behavior is ambiguous;
- major new asset production would be required;
- proceeding safely would require a product decision.

Do not ask questions merely because investigating the world takes effort.

---

# Inspect the Actual World

Where practical, inspect the world through:

- runtime play;
- editor views;
- scene views;
- screenshots;
- level files;
- map data;
- prefabs;
- terrain data;
- environment configuration.

Do not judge environment quality solely from code, object names, or asset lists.

Observe:

- what the player sees;
- what the player approaches;
- what frames important paths;
- what distinguishes locations;
- where empty spaces occur;
- where repetition becomes obvious;
- where navigation becomes unclear;
- where the world feels mechanically assembled rather than intentionally composed.

If direct runtime/editor inspection is unavailable, state that limitation and use the strongest available evidence.

Do not pretend visual validation occurred if it did not.

---

# Implementation Over Auditing

The audit exists only to create an **implementation queue**.

Do not spend most of the task creating:

- giant world inventories;
- theoretical redesign documents;
- lists of every prop;
- subjective criticism;
- hypothetical biome concepts;
- extensive environmental-design prose.

Once a problem is sufficiently understood:

> **implement the improvement.**

Use:

> **inspect → identify weak area → diagnose why it feels weak → implement → validate → reinspect**

repeatedly.

Work through coherent locations or environmental concerns.

---

# Establish the World Map

Before broad changes, identify the major existing areas.

Depending on the game, these may include:

- primary town;
- secondary town;
- major city;
- starting zone;
- wilderness;
- forest;
- mine;
- dungeon;
- beach;
- island;
- tower;
- farm;
- port;
- cave;
- castle;
- ruins;
- major interiors;
- gathering zones;
- combat zones.

Do not invent locations that do not exist.

Understand:

- what each area is for;
- how areas connect;
- which routes players use;
- which locations are important;
- which areas serve progression or quest functions;
- which areas are intended to feel dense or sparse.

---

# Prioritize High-Traffic Areas

Not all environment problems are equally important.

Classify locations approximately as:

## Primary

Seen constantly.

Examples:

- starting area;
- central hub;
- main town;
- major bank/storage;
- core crafting area;
- primary travel route.

## Secondary

Seen regularly.

Examples:

- common gathering areas;
- secondary settlements;
- combat zones;
- important quest destinations.

## Tertiary

Seen occasionally.

Examples:

- remote corners;
- rare quest areas;
- small interiors;
- optional side paths.

A weak central hub matters more than an imperfect remote corner.

Prioritize accordingly.

---

# Execution Strategy

Work autonomously where possible.

If the environment supports parallel agents, workers, subprocesses, or independent contexts, use them where they materially improve coverage.

Do not require delegation.

A single capable session should still be able to execute this prompt sequentially.

Good independent work areas may include:

- separate towns;
- independent wilderness zones;
- interiors;
- coastlines;
- dungeons;
- secondary travel routes;
- repetition audits;
- landmark review.

Serialize changes involving shared:

- terrain systems;
- procedural placement;
- global environment configuration;
- shared landmark infrastructure;
- major navigation;
- world streaming;
- authoritative multiplayer objects.

Do not let independent workstreams invent conflicting world-design languages.

Centralize:

- world identity;
- landmark hierarchy;
- density strategy;
- prop language;
- major spatial decisions.

---

# World Priority Queue

## P0 — Broken Environment

Examples:

- required location unreachable;
- route blocked;
- collision broken;
- missing terrain;
- severe geometry overlap;
- broken entrance;
- player falling through world;
- required gameplay object inaccessible.

Fix immediately.

## P1 — Major World Quality Problems

Examples:

- central town feels empty;
- major zone has little identity;
- environment looks obviously copy-pasted;
- primary route is visually confusing;
- important landmark is hard to see;
- major transition is abrupt;
- world perimeter visibly looks unfinished;
- high-traffic area is placeholder quality.

These strongly affect perceived production quality.

## P2 — Significant Environmental Polish

Examples:

- weak prop grouping;
- repetitive vegetation;
- generic interiors;
- sparse travel routes;
- weak town outskirts;
- underdeveloped gathering areas;
- poor transition zones;
- weak environmental storytelling.

Spend substantial effort here.

## P3 — Finishing Details

Examples:

- minor prop repetition;
- subtle edge treatment;
- small clutter improvements;
- restrained storytelling details;
- modest path strengthening;
- small silhouette improvements.

Address after major areas are healthy.

---

# Barren-Area Hunt

Search aggressively for spaces that feel:

- unfinished;
- unused;
- uniformly empty;
- devoid of landmarks;
- devoid of environmental context;
- disconnected from surrounding function.

For each ask:

> **Is this empty because the design needs openness, or because nobody finished dressing it?**

If intentionally open, preserve it.

If unfinished, improve it.

Possible tools include:

- clustered props;
- terrain variation;
- vegetation;
- fences;
- signs;
- debris;
- natural features;
- architectural extensions;
- visual framing;
- environmental storytelling.

Do not simply scatter objects randomly.

---

# Density Pass

A common amateur world-design problem is:

> **roughly equal prop density everywhere**

Professional environments typically vary density intentionally.

Examples:

- dense market;
- moderate residential street;
- sparse field;
- dense forest edge;
- open central square;
- clear travel corridor.

For each area ask:

- What is this space for?
- How much visual density supports that function?
- Where should visual breathing room exist?
- Where should objects cluster?
- Where should the player's route remain clear?

Use density to create hierarchy.

---

# World Density Map

For sufficiently large worlds, classify areas internally as:

- empty;
- sparse;
- moderate;
- dense;
- very dense.

Compare that classification against intended function.

Look for suspicious mismatches such as:

- empty market;
- overcrowded wilderness;
- cluttered primary road;
- unusably dense gathering zone;
- lifeless central plaza.

Do not attempt to equalize everything.

Use density deliberately.

---

# Prop Grouping Pass

Props should rarely look like isolated random decorations.

Prefer logical clusters.

Examples:

- barrels and crates near storage;
- tools around workstations;
- logs around timber-processing areas;
- carts and supports around mines;
- fishing supplies around docks;
- farming tools around fields;
- furniture organized around room function.

For important objects ask:

> **Why is this here?**

The answer should often be visually understandable from its surroundings.

---

# Repetition Hunt

Look for repeated:

- prop arrangements;
- rotations;
- building configurations;
- tree placement;
- rock clusters;
- fences;
- furniture;
- terrain patterns;
- spatial layouts.

Break obvious repetition through:

- variation;
- spacing differences;
- substitutions;
- alternate orientation;
- clustering;
- local context;
- asymmetry where appropriate.

Do not eliminate repetition that supports:

- architectural identity;
- readability;
- world logic;
- faction style;
- settlement structure.

The problem is **obvious copy-paste**, not repetition itself.

---

# Spatial Repetition Hunt

Look beyond asset repetition.

Inspect repeated:

- room dimensions;
- street widths;
- building spacing;
- path curvature;
- courtyard layouts;
- object grouping;
- encounter layouts.

Variation in spatial composition can matter as much as asset variety.

---

# Landmark Pass

Major areas should contain memorable visual anchors where appropriate.

A landmark may be:

- tower;
- statue;
- giant tree;
- gate;
- bridge;
- fountain;
- unusual building;
- mountain;
- crane;
- large rock formation;
- shrine;
- ruined structure;
- distinctive terrain feature.

Do not invent arbitrary spectacle.

Use landmarks compatible with the existing world fiction.

Ask:

> **Could a player describe this location without referring only to coordinates, minimap labels, or UI?**

If not, strengthen important locations.

---

# Landmark Hierarchy

Not every object should be a landmark.

Use hierarchy:

## Major Landmark

Defines a town, district, or zone.

## Secondary Landmark

Defines a subarea.

## Local Marker

Helps players recognize a smaller destination.

Avoid several equally dominant landmarks competing within one small location.

---

# Landmark Coverage Review

Compare major landmarks against high-traffic routes.

Ask:

- Can important destinations be recognized while approaching?
- Does each important area have enough visual identity?
- Are landmarks visible from useful viewpoints?
- Are multiple landmarks competing unnecessarily?
- Does the environment frame them effectively?

Improve coverage without turning the world into a theme park.

---

# Town and Village Pass

Inspect settlements for believable spatial function.

Look for:

- recognizable center;
- entrances;
- residential areas;
- commercial areas;
- crafting areas;
- storage;
- gathering connections;
- defensive structures where appropriate;
- social spaces;
- service areas;
- roads that support those functions.

Ask whether the settlement feels:

- intentionally planned;
- inhabited;
- functionally organized;
- embedded in its surroundings.

Avoid:

> **buildings dropped randomly onto terrain**

unless the settlement fiction genuinely supports that appearance.

---

# Town Edge Pass

Settlement edges frequently reveal unfinished worlds.

Inspect transitions between:

- buildings and wilderness;
- roads and fields;
- town and forest;
- walls and surrounding land;
- docks and settlement;
- village and farmland.

Look for:

- sudden emptiness;
- hard prop cutoffs;
- abrupt terrain changes;
- buildings ending without transition;
- unnatural vegetation walls.

Use contextually appropriate:

- fences;
- gardens;
- farms;
- sheds;
- paths;
- thinning vegetation;
- scattered outbuildings;
- wall-adjacent details;
- storage;
- transitional ground treatment.

Make settlements feel embedded in the world.

---

# District Identity

For larger towns or cities, differentiate districts using subtle functional signals.

Possible tools:

- architecture;
- prop types;
- density;
- vegetation;
- road width;
- decorative language;
- environmental function;
- building scale;
- signs of occupation.

Do not create artificial theme-park districts.

Subtle functional differentiation is often enough.

---

# Entrance and Exit Pass

Important entrances should visually communicate transition.

Inspect:

- gates;
- cave mouths;
- dungeon entrances;
- town entrances;
- docks;
- portals;
- building doors;
- zone transition points.

Ask:

- Is this clearly an entrance?
- Does it visually communicate importance?
- Does the route naturally lead toward it?
- Does surrounding environment frame it?

Use:

- framing;
- path convergence;
- scale;
- architecture;
- signs;
- lighting where appropriate;
- prop placement.

Do not require giant glowing markers unless that matches the established visual language.

---

# Road and Path Pass

Roads and paths should communicate movement.

Inspect:

- continuity;
- width;
- intersections;
- destination framing;
- surrounding prop orientation;
- wear;
- branching;
- visibility;
- relationship to landmarks.

Look for paths that:

- abruptly disappear;
- appear to lead nowhere;
- blend unintentionally into terrain;
- pass through unnecessary clutter;
- imply inaccessible destinations.

Support important routes through environmental composition.

---

# Desire-Line Review

Observe where players naturally want or need to travel.

Ask:

> **Does the world visually support the route players are expected to use?**

Avoid:

- props blocking obvious movement;
- decorative clutter in high-traffic paths;
- paths visually implying invalid routes;
- unclear intersections;
- major destinations hidden without reason.

Do not redesign gameplay navigation unnecessarily.

---

# Sightline Pass

Inspect important views from:

- entrances;
- roads;
- central squares;
- travel hubs;
- gathering areas;
- high-traffic locations.

Strong sightlines can reveal:

- destinations;
- landmarks;
- terrain features;
- important architecture;
- next-route direction.

Avoid accidentally blocking important world information.

---

# Composition Pass

Treat important areas as compositions.

Inspect:

- foreground;
- midground;
- background;
- focal point;
- framing;
- leading lines;
- silhouette;
- visual balance.

Ask:

> **Where does the player's eye go?**

and:

> **Does environmental arrangement reinforce this area's purpose?**

Use:

- building orientation;
- roads;
- vegetation;
- props;
- elevation;
- landmarks;
- open space;

to direct attention.

---

# Focal Point Pass

Meaningful subareas often benefit from a visual anchor.

Examples:

- workstation;
- unusual prop;
- building;
- tree;
- statue;
- doorway;
- resource cluster;
- terrain feature.

Do not create focal points everywhere.

Use them to establish hierarchy.

---

# Area Identity Test

For each major location ask:

> **If the UI label disappeared, could a player recognize where they are?**

Identity may come from:

- architecture;
- terrain;
- vegetation;
- landmarks;
- density;
- layout;
- environmental function;
- silhouette.

Strengthen weak identities.

Not every minor location requires unique presentation.

Important areas usually do.

---

# "Would I Remember This Place?" Test

For major locations ask:

> **Would a player remember this location tomorrow?**

If not, determine whether it needs stronger:

- landmark;
- silhouette;
- function;
- composition;
- environmental context;
- spatial structure.

Do not force every minor area to become memorable.

Prioritize locations important to play.

---

# World Perimeter Pass

Inspect visible boundaries.

Examples:

- map edge;
- cliffs;
- ocean boundary;
- walls;
- mountains;
- inaccessible forest;
- edge of playable settlement.

Avoid obvious:

- abrupt cutoff;
- empty void;
- repeated barrier objects;
- artificial invisible-boundary presentation.

Use believable environmental barriers where appropriate.

---

# World Edge Quality Review

Players often reach places developers did not expect them to inspect closely.

Review:

- backs of buildings;
- map corners;
- outside walls;
- cliff edges;
- dead ends;
- behind structures;
- peripheral shoreline.

Do not spend disproportionate resources there.

But eliminate conspicuously unfinished presentation.

---

# Terrain Transition Pass

Inspect transitions between:

- grass;
- dirt;
- roads;
- sand;
- stone;
- water;
- cliffs;
- fields;
- biome surfaces.

Look for:

- straight artificial seams;
- grid artifacts;
- texture cutoff;
- terrain mismatch;
- disconnected props;
- abrupt density changes.

Improve transitions using the project's established tools.

---

# Transition-Zone Review

Transitions between major areas deserve dedicated attention.

Examples:

- town → wilderness;
- forest → field;
- coast → village;
- cave → dungeon;
- farm → town;
- road → ruins.

Avoid immediate hard switches where the world would benefit from gradual transition.

Use appropriate transitional cues such as:

- blended terrain;
- changing vegetation;
- prop types;
- architecture;
- density changes;
- sightline changes;
- environmental wear.

---

# Coastline and Water Edge Pass

Where relevant inspect:

- shorelines;
- docks;
- rivers;
- lakes;
- beaches.

Look for:

- perfectly uniform coastlines;
- floating props;
- abrupt terrain-water intersections;
- docks without surrounding function;
- repeated shoreline geometry;
- sterile water edges.

Break up edges intelligently where safe.

---

# Cliff and Elevation Pass

Inspect elevated terrain for:

- awkward vertical transitions;
- playable routes that look inaccessible;
- repeated cliff shapes;
- floating props;
- weak silhouettes;
- terrain cuts that look artificial.

Use elevation to strengthen:

- framing;
- landmarks;
- navigation;
- visual hierarchy;
- area identity.

---

# Vegetation Placement

Natural environments should not look procedurally sprinkled unless that is intentionally the style.

Inspect:

- tree clustering;
- shrubs;
- grasses;
- flowers;
- dead vegetation;
- edge transitions;
- regional variation.

Avoid:

- equal spacing;
- identical rotation;
- uniform density;
- vegetation intersecting buildings;
- trees blocking major routes;
- unnatural random scattering.

Use ecological logic where practical.

---

# Forest Pass

Forests should have internal structure.

Possible components:

- edges;
- dense core;
- clearings;
- paths;
- fallen objects;
- distinctive trees;
- transition zones;
- undergrowth variation.

Avoid:

> **evenly spaced trees across an open field**

unless deliberately stylized.

Use layered density where supported.

---

# Rock and Natural Prop Placement

Natural props should not look independently dropped onto terrain.

Prefer relationships such as:

- clusters;
- slopes;
- erosion lines;
- terrain transitions;
- cliff bases;
- boundary definition.

Vary:

- size;
- orientation;
- spacing;
- density.

Preserve the game's stylization.

---

# Field and Farm Pass

Where agricultural areas exist, inspect:

- field boundaries;
- crop organization;
- storage;
- tools;
- paths;
- fences;
- water;
- farm structures;
- work areas.

Make agriculture appear functional.

Avoid decorative crops with no relationship to surrounding space.

---

# Mine and Cave Pass

Inspect:

- entrance;
- tunnels;
- working areas;
- resource placement;
- supports;
- carts;
- tools;
- storage;
- hazards;
- navigation.

Avoid caves that look like:

> **empty corridors containing resource nodes**

Give them functional environmental context using existing assets where possible.

---

# Dungeon Pass

Dungeons should communicate:

- progression;
- danger;
- structure;
- destination;
- room identity.

Look for:

- identical rooms;
- empty corridors;
- no landmarks;
- meaningless dead ends;
- repeated prop placement;
- no change in spatial rhythm.

Preserve gameplay topology unless changes are clearly safe.

---

# Interior Pass

Interiors should communicate their function quickly.

A smithy should visually differ from:

- a home;
- a tavern;
- a shop;
- a bank;
- a wizard's room;
- a storage building.

Use:

- furniture;
- tools;
- storage;
- clutter;
- layout;
- focal objects;
- material variation already available.

Avoid identical rectangular rooms differentiated only by NPC placement.

---

# Interior Functional Zones

Even small interiors benefit from logical arrangement.

Possible zones include:

- workspace;
- storage;
- customer area;
- private area;
- sleeping area;
- preparation area.

Do not overfill small rooms.

Make object placement reflect how the space is used.

---

# Building Exterior Pass

Important buildings should be recognizable externally.

Use existing:

- shape;
- signage;
- props;
- materials;
- attached environment;
- surrounding activity;
- entrances;
- silhouette.

Players should not need to read every label to recognize important buildings.

---

# Environmental Storytelling

Use environment to communicate **existing world context**.

Potential signals include:

- recent activity;
- occupation;
- wealth;
- poverty;
- danger;
- abandonment;
- damage;
- repair;
- trade;
- resource extraction;
- habitation;
- defense.

Examples:

- tools beside workshops;
- crates around docks;
- debris around ruins;
- supplies near guards;
- worn paths toward frequently used locations.

Do not invent major lore unsupported by the existing game.

Tell small stories through placement.

---

# Signs of Life

Settlements often feel lifeless when nothing implies use.

Where appropriate, use existing assets to suggest activity:

- stored goods;
- work tools;
- seating;
- carts;
- market goods;
- laundry;
- firewood;
- barrels;
- crates;
- workshop materials;
- repair materials.

Do not invent unrelated simulation systems.

The goal is environmental implication, not new gameplay.

---

# Damage and Wear Pass

Perfectly pristine worlds can feel artificial.

Where appropriate, use existing assets or presentation to imply:

- wear;
- damage;
- age;
- repairs;
- erosion;
- dirt;
- debris.

Apply this contextually.

A wealthy palace and abandoned mine should not have identical wear.

---

# Empty Corner Review

Inspect:

- building corners;
- wall edges;
- dead ends;
- unused roadside spaces;
- interior corners;
- backs of major structures.

These areas frequently expose lack of final environment dressing.

Do not fill every corner.

Fix conspicuously unfinished ones.

---

# Negative Space Review

Explicitly protect useful negative space.

Good uses include:

- plazas;
- combat arenas;
- fields;
- gathering zones;
- vistas;
- route visibility;
- staging areas.

Do not add clutter simply because space exists.

Ask:

> **Does this open area serve a spatial or gameplay purpose?**

If yes, preserve it.

---

# Silhouette Variety

Inspect the world from medium and long distance.

Look for:

- identical roof heights;
- flat horizons;
- repeated tree shapes;
- uniform building blocks;
- monotony in vertical composition.

Where existing assets allow, improve silhouette through:

- scale variation;
- building placement;
- terrain;
- vegetation;
- landmark height.

Avoid arbitrary chaos.

---

# Scale Consistency

Inspect whether world objects feel proportionally coherent.

Look for:

- doors too small for characters;
- absurdly large furniture;
- implausibly narrow roads;
- inconsistent stairs;
- mismatched building dimensions;
- props that visibly belong to different scales.

Fix obvious accidental mismatches where safe.

Do not impose realism on intentionally exaggerated stylization.

---

# World Object Integration

Gameplay objects should appear intentionally embedded in the environment.

Examples:

- gathering nodes;
- chests;
- crafting stations;
- vendors;
- quest objects;
- interactables.

Avoid the appearance of:

> **gameplay object dropped into unrelated scenery**

Use surrounding environment to support its function.

---

# Gathering-Area Polish

If gathering exists, inspect whether resource areas feel environmentally justified.

A mining area might include:

- rock formations;
- carts;
- tools;
- supports;
- debris.

A fishing area might include:

- docks;
- nets;
- baskets;
- boats;
- storage.

A forestry area might include:

- felled logs;
- tools;
- paths;
- timber storage;
- forest-edge variation.

Do not alter gathering mechanics.

Improve context.

---

# Combat-Area Polish

If dedicated combat spaces exist, inspect:

- movement space;
- encounter framing;
- obstacle readability;
- repeated arena layouts;
- route clarity;
- environmental context.

Do not clutter combat paths with decoration that harms gameplay.

Use the environment to improve readability and identity.

---

# Quest-Location Polish

Important quest locations should support their narrative importance visually.

Do not rewrite quests.

Inspect whether major quest moments occur in spaces that feel:

- unfinished;
- generic;
- visually unrelated;
- insufficiently distinct.

Use existing environment assets to improve presentation where safe.

---

# Exploration Test

Travel through the world as a player would.

Observe:

- what changes from place to place;
- what remains repetitive;
- whether destinations reveal themselves;
- whether travel routes have rhythm;
- whether transitions feel abrupt;
- whether landmarks assist orientation;
- whether the world alternates effectively between density and openness.

The world should not feel like one repeated environment unless intentionally designed that way.

---

# Screenshot Test

Where practical, inspect representative screenshots.

Ask:

> **What makes this environment look unfinished or generic in a static image?**

Look for:

- empty areas;
- copy-pasted props;
- weak composition;
- lack of focal point;
- obvious repetition;
- abrupt transitions;
- floating objects;
- sterile settlement layouts;
- weak environmental storytelling;
- poor silhouette.

Fix high-value findings.

---

# "Why Is This Here?" Test

For important props and environmental clusters ask:

> **Why is this here?**

Good answers may include:

- storage;
- work;
- defense;
- habitation;
- navigation;
- trade;
- terrain logic;
- environmental composition.

A weak answer is:

> **because the area looked empty**

Decorative objects may exist for composition alone, but the broader environment should feel plausible.

---

# "Does This Look Procedurally Scattered?" Test

Inspect especially:

- rocks;
- trees;
- crates;
- barrels;
- vegetation;
- debris.

Signs of weak placement include:

- uniform spacing;
- random rotation without grouping;
- no relationship to terrain or function;
- identical density everywhere;
- obvious repeated patterns.

Replace random-looking scatter with authored clustering where practical.

---

# Reuse Existing Assets Intelligently

Before creating new environment assets, inspect what already exists.

Underused existing props may significantly improve:

- settlements;
- interiors;
- routes;
- landmarks;
- gathering zones;
- world edges.

Reuse with variation.

Do not create unnecessary duplicates.

---

# New Environment Assets

Small new assets may be created only when:

- the project already has a suitable asset pipeline;
- the addition clearly improves an important area;
- existing assets cannot solve the problem cleanly;
- the addition fits existing art direction.

Do not:

- create a massive asset-production project;
- change the visual style;
- introduce low-quality filler;
- use placeholder-quality content simply to increase density.

Prefer strong placement of existing assets over large quantities of mediocre new ones.

---

# Procedural World Awareness

If some environment is procedurally generated, determine whether repeated or weak placement is best corrected through:

- generator rules;
- placement constraints;
- seed-independent logic;
- authored exceptions.

Do not manually patch hundreds of generated instances if the generator is the root cause.

Treat substantial generator changes as higher-risk shared system work.

---

# Collision and Placement Validation

Environmental polish must not damage gameplay.

After placement or geometry changes check:

- collision;
- movement;
- pathfinding;
- NPC navigation;
- player navigation;
- interaction access;
- camera visibility;
- spawn access;
- important routes.

Decorative improvements should not create:

- snag points;
- blocked paths;
- inaccessible resources;
- hidden NPCs;
- broken interaction ranges.

---

# Navigation-Mesh Awareness

Where navigation meshes or equivalent systems exist:

- determine whether changes require regeneration;
- rebuild or regenerate when necessary;
- validate affected routes;
- confirm NPC/player path behavior remains correct.

Do not assume decorative geometry is navigation-neutral.

---

# Multiplayer World Awareness

If multiplayer exists, preserve authoritative world behavior.

Be especially cautious around:

- destructible objects;
- gathering nodes;
- shared doors;
- synchronized props;
- collision;
- world-state IDs;
- persistence-linked entities.

Do not duplicate or relocate authoritative objects casually.

---

# Performance Awareness

This is not primarily a performance pass.

However, avoid environmental polish that introduces obvious unnecessary cost.

Watch for:

- excessive object counts;
- too many dynamic lights;
- excessive shadow casters;
- huge transparent areas;
- uncontrolled particles;
- excessive collision geometry;
- expensive newly visible assets;
- large numbers of constantly updating props.

Prefer high-value visual improvement at reasonable runtime cost.

Do not optimize away environmental quality unnecessarily.

---

# Work in Environment Waves

Do not scatter random changes across the entire world.

## Wave A — Primary Locations

Polish:

- starting area;
- primary hub;
- major town or city;
- other highest-traffic locations.

Focus on:

- composition;
- density;
- identity;
- landmarks;
- signs of life.

Validate.

## Wave B — Routes and Transitions

Polish:

- roads;
- paths;
- entrances;
- town edges;
- biome transitions;
- world boundaries.

Validate navigation.

## Wave C — Gameplay Areas

Polish:

- gathering zones;
- combat spaces;
- crafting areas;
- quest locations.

Improve context without harming gameplay.

Validate.

## Wave D — Interiors and Secondary Areas

Polish:

- houses;
- shops;
- workshops;
- dungeons;
- secondary settlements;
- lower-traffic areas.

Validate.

## Wave E — Last 10%

Search for:

- empty corners;
- repeated prop clusters;
- terrain seams;
- floating objects;
- awkward edges;
- weak landmarks;
- unfinished world boundaries;
- isolated gameplay objects;
- small environmental-storytelling opportunities.

---

# Reassess After Every Wave

Ask:

- Which area still feels most unfinished?
- Which location has the weakest identity?
- Where is prop density unnatural?
- Where does repetition become obvious?
- Which route feels visually boring?
- Which destination lacks a useful landmark?
- Which transition remains abrupt?
- Which town edge looks artificial?
- Which area still feels procedurally scattered?
- Where does gameplay scenery feel disconnected from environment?
- Did previous changes create clutter?
- Did any route or interaction become less readable?

Reprioritize based on the current state.

---

# Productive Session Loop

Do not stop after improving the obvious weakest locations.

World polish exposes the next weakest layer.

Examples:

- improving the town exposes weak outskirts;
- improving roads exposes empty transitions;
- improving gathering areas exposes generic interiors;
- stronger landmarks expose bland approaches.

Continue:

> **inspect → identify weakest environment → diagnose → implement → validate → reinspect**

while meaningful improvements remain.

Do not manufacture clutter merely to continue working.

Stop when remaining findings are:

- highly subjective;
- minor;
- dependent on major new asset production;
- dependent on full map redesign;
- too gameplay-sensitive for safe modification;
- outside scope.

---

# Independent Final Environment Review

Near completion, review the world with fresh context.

Evaluate separately:

## Settlements

Inspect:

- density;
- function;
- identity;
- landmarks;
- edge quality;
- internal organization.

## Wilderness

Inspect:

- natural grouping;
- repetition;
- route composition;
- biome transitions;
- density variation.

## Interiors

Inspect:

- function;
- repetition;
- object grouping;
- room identity.

## Routes and Navigation

Inspect:

- landmarks;
- approaches;
- transitions;
- route readability;
- sightlines.

The purpose of fresh review is to find remaining weakness, not merely approve previous work.

---

# "What Still Looks Procedural?" Review

Ask:

> **Which areas still look procedurally scattered, copy-pasted, generically filled, or insufficiently authored?**

Require concrete findings.

For each meaningful issue identify:

### Area

Where is it?

### Problem

What looks artificial or unfinished?

### Evidence

What specific repetition, density, spacing, or composition causes it?

### Fix

What practical improvement is justified?

### Scope

Tiny / Small / Medium / Large.

Implement worthwhile corrections.

Reject vague criticism.

---

# "What Still Feels Empty?" Review

Find areas that feel barren.

Distinguish:

> **intentional negative space**

from:

> **unfinished emptiness**

For each finding establish:

- gameplay purpose;
- visual purpose;
- missing environmental context;
- appropriate density change.

Do not accept:

> **add more props**

without explaining why and where.

---

# Commercial-Quality World Review

Inspect major locations as though they were receiving a final pre-release environment review.

Ask:

- Does this space have purpose?
- Does it have identity?
- Is object placement intentional?
- Is navigation visually supported?
- Are transitions finished?
- Is repetition controlled?
- Does the area feel inhabited or environmentally plausible?
- Are important routes clear?
- Are important landmarks clear?
- Does the composition hold up from normal player viewpoints?

Fix high-value shortcomings.

---

# Anti-Clutter Review

Before completion, inspect whether the pass overfilled the world.

Ask:

- Are routes obstructed?
- Are towns too busy?
- Is natural terrain covered with unnecessary props?
- Did useful negative space disappear?
- Are focal points competing?
- Did gathering or combat areas become visually noisy?
- Did object density become uniform?
- Did environmental storytelling become decorative noise?

Remove unjustified clutter.

---

# Anti-Theme-Park Review

Do not make every area exaggerated merely to make it memorable.

Avoid:

- giant landmarks in every zone;
- extreme color coding;
- arbitrary themed props;
- excessive signage;
- exaggerated environmental gimmicks without fiction support.

World identity should feel believable within the game's own style.

---

# Final Cross-System Environment Review

Before finishing, inspect for:

- blocked routes;
- collision regressions;
- navigation regressions;
- inaccessible resources;
- quest-trigger problems;
- NPC pathfinding problems;
- broken world-object references;
- multiplayer-state problems;
- environment inconsistency;
- duplicated props;
- unfinished transitions;
- obvious newly introduced clutter.

Fix justified issues.

Run final validation.

---

# Completion Standard

The world/environment pass is complete when, to the degree existing assets and technology allow:

1. primary locations feel deliberately authored;
2. major barren areas are improved;
3. intentional negative space remains protected;
4. environmental density better matches area function;
5. major landmarks are clearer;
6. important locations have stronger identity;
7. major routes are visually supported;
8. prop placement appears more intentional;
9. obvious procedural-looking scatter is reduced;
10. obvious copy-paste layouts are reduced;
11. environmental storytelling is stronger where appropriate;
12. town edges feel integrated with surrounding world;
13. major environment transitions feel deliberate;
14. terrain and environment seams are reduced;
15. interiors communicate function more clearly;
16. gathering, combat, crafting, and quest areas feel environmentally integrated;
17. important world objects feel intentionally placed;
18. world boundaries look more finished;
19. environmental composition is stronger;
20. high-traffic areas received appropriate priority;
21. gameplay navigation remains intact;
22. collision and pathfinding remain functional;
23. no known environment regressions introduced by this pass remain;
24. remaining weaknesses require major asset production, major level redesign, are low-value, subjective, or belong to another specialized pass.

The objective is not:

> **maximum prop count**

The objective is:

> **maximum improvement in intentionality, identity, environmental density, spatial composition, navigation, plausibility, and authored world quality using the world that already exists.**

---

# Final Report

When complete, provide a concise world-design report.

## 1. Overall Result

Summarize the biggest improvements to world quality.

## 2. Primary Locations

Describe meaningful improvements to major towns, hubs, and other high-traffic areas.

## 3. Environment Density

Summarize barren areas improved and important density corrections.

## 4. Landmarks and Identity

Describe major landmark and location-identity improvements.

## 5. Routes and Transitions

Summarize meaningful work involving:

- roads;
- paths;
- entrances;
- town edges;
- biome transitions;
- world boundaries.

## 6. Environmental Storytelling

Describe meaningful contextual dressing added.

## 7. Gameplay Area Integration

Summarize improvements to actual:

- gathering areas;
- combat zones;
- quest locations;
- crafting areas.

Include only systems that exist.

## 8. Interiors

Summarize significant interior improvements.

## 9. Validation

State what was actually validated, including relevant:

- areas;
- routes;
- navigation;
- collision;
- interactions;
- quests;
- runtime scenes;
- multiplayer world behavior where applicable.

## 10. Deliberately Unchanged

Describe meaningful weak areas preserved because:

- major new art is required;
- gameplay dependencies are too risky;
- evidence was insufficient;
- the area is intentionally sparse;
- another specialized pass should own the work.

## 11. Remaining Opportunities

List only genuinely worthwhile future world work.

For each include:

- **Area**
- **Opportunity**
- **Player-facing benefit**
- **Scope:** Tiny / Small / Medium / Large
- **Recommended priority**

Do not pad this section with microscopic prop-placement suggestions.

---

# Final Directive

**Think like an environment designer walking through the world, not a programmer counting scene objects.**

The world should feel:

- intentional;
- functional;
- memorable;
- spatially coherent;
- believable within its style;
- professionally authored.

Do not add props randomly.

Do not fill intentional negative space.

Do not redesign the world unnecessarily.

Do not break gameplay routes for composition.

Do not make every area equally dense.

Do not give every location an oversized landmark.

Do not invent lore simply to justify clutter.

Repeatedly ask:

> **Why is this space arranged this way?**

> **Why is this object here?**

> **Would a player remember this location?**

> **Does this area look authored or scattered?**

> **Does the environment communicate its function?**

> **What still makes this world feel empty, generic, repetitive, disconnected, or unfinished?**

Continue:

> **inspect → diagnose → implement → validate → walk through again**

while meaningful environmental improvement remains.

Leave behind the **same world**, but make it feel substantially more authored, distinctive, cohesive, believable, memorable, and professionally finished.