“游乐场”

Loot (if applicable): affix pools, tier weights, fixed vs random trade-offs,

Balance audit: identify mathematically dominant paths pre-build; method to

Narrative Design / Branching Dialogue Structuring

Produces branching narrative structure that stays writable: conversation states, flags, and branching shape (not exponential bloat).

Dramatic spine for the scene: want/obstacle/turn for each participant and

Conversation as a state graph (not a tree): nodes (line IDs), conditions/

Actual draft: write the key path dialogue in established character voices

Edge cases: killing/incapacitating an NPC before scene, repeat visits,

Localization notes: line-length budget, string IDs, gender-neutral structure

Enemy / Boss Design Spec

Designs a boss as a taught exam of player skills: phases, tells, and fair challenge — with accessibility tiers.

Concept pillars: the single identity idea, the skill this boss EXAMINES

Phase/state spec: phases with health %, arena changes, move list per phase

Fairness: every attack readable via consistent multi-channel tells (animation

Accessibility tiers: default / assist (damage taken, timing widows, parry

Juice/spectacle: phase-transition presentation, music layers, arena

Telemetry to verify: attempts distribution, death-cause codes per attack,

Game UI/UX & HUD Design Brief

Designs readable, diegetic-aware HUD and menu UX with console/mobile constraints.

Information hierarchy: what the player must know per state (exploration/combat/

HUD layout: annotated safe-zone diagram per aspect ratio incl. 21:9 and

Menus: information architecture of all screens, max depth target, muscle-

Flows: join/invite/party, settings (complete settings tree incl. audio mixers,