Skip to content
Vibe Bro’sENCYCLOPEDIA

VIBE BRO’S PROMPT PLAYBOOK

Audit Android state restoration

Find where an interface recreation or process loss can discard user progress.

Your build starts here

Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.

THE COMPLETE TEMPLATE
Audit state handling for [Android journey]. Expected behavior after interruption is [specific outcome].

List each important value and classify it as transient UI state, recoverable draft, or durable application data. Trace its owner and restoration path. Inspect activity or screen recreation, navigation, lifecycle-aware work, and the data loaded after a later launch.

Reproduce the relevant interruption cases with the project's supported tooling. Check how restoration handles a record that changed or disappeared elsewhere. Fix concrete loss or duplication within scope, then repeat the cases. Report what was verified and any environment-dependent scenarios that remain open.

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.

Editorial review · October 28, 2026

Supported: Original, unexecuted audit template. Android directly supports its configuration-change/process-death distinction; the requested device scenarios remain checks to perform.

Read the content review record.

Keep the momentum going