AI-powered storytelling and persistent world platform

Our AI-powered storytelling platform is live and packed with deep features such as campaign persistence and character growth, yet the current feature structure feels heavy. I want a product-design-first rethink of both the player and builder flow so players can reach every capability without feeling the weight of that complexity. Your task starts with auditing the existing screens, mapping how users currently move between campaign setup, in-game actions, and progression dashboards. From there, I need fresh information architecture, wireframes, and a visual direction that presents options clearly and naturally—no hidden layers or puzzling sub-menus—so the journey feels intuitive from the first click. Because the core engine is already built, all recommendations must respect present technical constraints while elevating immersion. Deliverables • Flow diagrams that document today’s pain points and the proposed streamlined paths • Low- and high-fidelity prototypes (Figma preferred) covering web and mobile breakpoints • A concise style guide for icons, typography, and component states to keep future updates consistent • Implementation notes my engineering team can pick up without guesswork I’ll review work against ease of discovery, reduced cognitive load, and visual coherence with our existing brand. If you can balance depth of features with effortless navigation, let’s talk. To add more clarification. Existing site can be provided, currently being domain blocked so that there's no unauthorized traffic. Two personas + one product PLAYER Primary goal: Play sessions, keep the story going, approve canon when it matters App shell mode: Player Mode (default) Mental model: "I'm in a story" Canon rule: Nothing becomes canon without explicit apply (or configured safe auto-apply for MSUP/relationships) BUILDER Primary goal: Configure how play works, inspect/debug AI context, tune templates and state App shell mode: Builder Mode toggle in header Mental model: "I'm operating the engine behind the story" Canon rule: Same as player — builders get more visibility into what happened automatically IMPORTANT DISTINCTION (design backlog) Story Mode / Easy Mode (per-campaign feature toggles — skip relationships, MSUP, memory review) is NOT the same as Player vs Builder app-shell mode. Story Mode is still planned.

Project ID: 40537596