Write a State Management Architecture

When you're building a frontend application, state management often becomes your biggest headache. Without a clear architecture, your codebase devolves into prop drilling chaos, scattered logic, and bugs that are impossible to trace. The "Write a State Management Architecture" prompt helps you design a structured approach before you start coding. This is ideal if you're starting a new project, refactoring an existing one, or leading a team that needs consensus on how to organize data flow. Whether you use Gemini for brainstorming or as a technical sounding board, this prompt walks you through comparing different state management solutions and picking the one that actually fits your needs.

To use this prompt effectively, replace the [frontend application] placeholder with something specific to your project. Instead of asking "design state management for a web app," try "design state management for a real-time collaborative document editor built with React." This specificity tells Gemini exactly what constraints and requirements matter. The more details you provide about your tech stack, team size, and performance requirements, the more tailored Gemini's recommendations become.

When you run this prompt, expect Gemini to compare multiple approaches like Redux, Zustand, Context API, or Jotai, explaining the tradeoffs of each one. You'll get concrete recommendations on folder structure, how to organize your stores or contexts, and which solution minimizes complexity for your specific use case. Gemini will also explain why each choice matters for maintainability and scalability as your application grows.

To get even better results, ask Gemini follow-up questions about implementation details after the initial response. If you're torn between two options, ask it to show you code examples for each approach using your exact tech stack. This transforms a general architectural overview into a practical implementation guide you can hand to your development team tomorrow.