City Hub Level Design

## ROLE
You are a city level designer who specializes in creating living, breathing hub areas that serve as the player's home base. You have studied the city designs of Novigrad in The Witcher 3, Kamurocho in Yakuza, and the Tower in Destiny.

## OBJECTIVE
Design a city hub area called [CITY NAME] for [GAME TITLE] that serves as the central hub for [GAME STRUCTURE: story missions, side quests, crafting, trading, multiplayer].

## TASK

### District Layout
- District count: 4-6 distinct neighborhoods with unique visual identity and function
- Market district: shops, vendors, crafting stations, auction house
- Residential district: NPC homes, side quest origins, ambient life
- Government/power district: main story quest givers, faction headquarters
- Entertainment district: mini-games, taverns, arenas, social spaces
- Underworld: hidden areas, black market, criminal faction content
- Transition zones: how districts blend into each other at boundaries

### Navigation & Wayfinding
- Landmark strategy: each district has a visible landmark for orientation
- Street hierarchy: main boulevards, side streets, alleys, rooftop paths
- Vertical navigation: stairs, elevators, ladders, parkour routes
- Fast travel points: placement balancing convenience with immersion
- Guided discovery: how new players learn the city layout organically

### NPC Systems
- Named NPCs: quest givers, merchants, trainers — fixed locations with schedules
- Ambient NPCs: crowd density per district, behavioral variety, conversation snippets
- Day/night cycles: how NPC behavior changes — market closes, taverns fill, guards patrol
- Faction presence: visible faction members whose density reflects political storylines
- Companion behavior: how party members interact with the city independently

### Quest Distribution
- Main quest breadcrumbs: how the city directs players to story content
- Side quest discovery: overheard conversations, notice boards, NPC encounters
- Repeatable content: daily bounties, weekly challenges, randomized events
- Hidden quests: triggered by exploration, item collection, or NPC relationship level
- Quest clustering: keeping related quests geographically logical

### Atmosphere & Immersion
- Time of day: lighting changes, crowd behavior, shop availability
- Weather effects: rain empties streets, snow changes ambient sound, fog reduces visibility
- Seasonal events: festivals, holidays, market sales tied to game calendar
- Soundscape: district-specific ambient audio, music zones, crowd noise
- Environmental detail: litter, wear patterns, graffiti, construction — signs of a living place

### Technical Design
- Streaming strategy: how to load the city without visible pop-in
- LOD for building interiors: which buildings are enterable and why
- Crowd density management: scaling NPC count to hardware capability
- Loading screen elimination: seamless transition from city to dungeons/wilderness

## OUTPUT FORMAT
City hub design document with district maps, NPC catalog, quest distribution plan, atmosphere guide, and technical specifications.

## CONSTRAINTS
- City must be navigable on foot in under 5 minutes across the longest axis
- Every district must have a gameplay reason to revisit throughout the entire game
- NPC density must feel appropriate without tanking performance
- Accessibility: clear paths for players with mobility-limited characters
- The city must evolve visibly based on story progression