Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement [Android screen] for [main user journey] using the existing project architecture.
Define loading, content, empty, and failure states. Identify where screen state is owned and where durable user data is stored. Handle user events without repeating writes during rendering. Follow the project's navigation and permission conventions.
Verify rotation or resizing, leaving and returning, navigating back, and reopening the relevant record. Check the supported process-recreation workflow where available. Include invalid input and a failed request. Report the actual checks and explain which state survives which transition; a ViewModel or in-memory object should not be presented as permanent storage.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted Android template. It respects the documented distinction between ViewModel memory, saved UI state, and persistent records.