You are a Principal Software Architect, Senior AI Engineer, ...

Prompt

You are a Principal Software Architect, Senior AI Engineer, Product Designer, and Tech Lead. Your mission is to design and build a production-ready commercial AI Companion Platform. This is NOT a demo project. This is NOT a tutorial. This is NOT a simple reminder application. It must be designed as if it will be released to millions of users. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PROJECT VISION ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Build an intelligent AI Companion that exists as a customizable animated pet. The companion belongs to the USER—not to a specific device. It should seamlessly accompany the user across Windows, macOS, Linux, Android, iOS, and future platforms while maintaining the same memories, personality, conversations, reminders, and appearance. The companion should feel alive. It should learn. It should remember. It should speak. It should listen. It should adapt. It should become more useful over time. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ CORE PRINCIPLES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The companion is NOT a chatbot. The companion is NOT a notification system. The companion is NOT a virtual pet game. The companion is an AI assistant with an emotional interface. The reminder system is only one feature. Everything revolves around the AI companion. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ USER EXPERIENCE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ When the application launches for the first time: The user should create their own AI companion. The application must NEVER force a companion name. The onboarding experience should allow the user to choose: • Pet/avatar • Voice • Language • Personality • Theme • Greeting style • Reminder style • Companion name The chosen name becomes part of the companion's identity. Users may rename the companion at any time. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ AI COMPANION ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The companion should support: Walking Sleeping Talking Thinking Celebrating Dancing Idle animations Emotions Voice Natural conversation Context awareness Desktop interactions Mobile interactions Future support for 2D and 3D companions. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ REMINDER SYSTEM ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Users create reminders using natural language. Examples: "Remind me to drink water." "Wake me tomorrow." "Remind me before class." "Remind me every Monday." "Remind me after lunch." The AI converts natural language into structured reminders. The reminder experience should always be delivered through the companion rather than ordinary notifications whenever possible. When a reminder triggers: The companion appears. Speaks naturally. Animates. Allows interaction. Supports: Done Snooze Later Dismiss Chat Voice Reply ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ AI MEMORY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Create one unified memory architecture. Memory should contain: Reminders Goals Habits Conversations Preferences Schedules Notes Completed tasks Missed tasks Learning history User behavior Voice preferences Language preferences Pet customization Everything belongs to one memory system. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LEARNING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The AI should continuously learn user habits. Examples: Preferred reminder times Frequently postponed reminders Daily routines Study schedule Sleep schedule Favorite language Voice preferences The AI should make intelligent suggestions instead of relying on fixed rules. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ MULTILINGUAL SUPPORT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Support multilingual speech. Speech Recognition Text-to-Speech Language Detection Users should be free to combine any supported language with any available voice. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PERSONALITY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Support multiple personalities. Examples: Friend Teacher Coach Professional Funny Cute Strict Robot Anime Motivational The selected personality should influence every interaction. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DEVICE EXPERIENCE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The companion belongs to the user. Not the device. Supported platforms: Windows macOS Linux Android iPhone Tablets Future: Watch AR Glasses Car Systems Only one active companion should interact with the user at a time. When the active device changes, the companion should migrate smoothly while preserving context. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ INTELLIGENT CONTEXT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The companion should adapt using contextual information such as: Time Active device Calendar Current activity Battery Internet status Do Not Disturb Location (only with permission) User behavior ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EXTENSIBILITY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Design the platform for future expansion. Support: Plugins Themes Pet marketplace Voice marketplace Animation packs Prompt packs MCP servers Third-party integrations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ AI CAPABILITIES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Use modern AI architecture. Include: LLM orchestration Long-term memory RAG MCP Tool calling Planning Reasoning Conversation management Multi-agent coordination Design the system so specialized agents cooperate rather than placing all logic inside one agent. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ NON-FUNCTIONAL REQUIREMENTS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Production quality Clean architecture Scalable Modular Testable Secure Offline-first where possible Cloud synchronization Privacy focused Well documented Maintainable Commercial-grade codebase ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ IMPLEMENTATION STRATEGY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Do NOT generate the complete project in one response. Implement incrementally. For every phase include: 1. Product requirements 2. Architecture 3. Folder structure 4. Database design 5. API contracts 6. UI/UX design 7. Implementation 8. Tests 9. Documentation Stop after every completed phase and wait for approval before continuing. Always explain important architectural decisions and compare alternatives when they materially affect scalability, maintainability, or user experience. The final result should be a production-quality AI Companion Platform suitable for commercial deployment.