Skip to content
Vibe Bro’sENCYCLOPEDIA

VIBE BRO’S PROMPT PLAYBOOK

Implement a narrow mobile platform capability

Define a shared contract with separate verified platform implementations.

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
Add [device capability] to the existing cross-platform mobile app. The shared user outcome is [outcome], and supported platforms are [platforms].

Inspect the current framework, plugins, and native integration conventions. Define a narrow contract for inputs, result data, errors, cancellation, and unavailable capability. Implement platform-specific behavior where required rather than assuming one permission or lifecycle model fits every target.

Verify success, denial, cancellation, and departure from the foreground on each intended platform that is available. Check that the shared interface handles every returned state. Report deliberate platform differences, configuration needs, and missing target verification separately from completed shared code.

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 native-boundary template. Flutter supports asynchronous channels and explicit capability handling; permission/device fallback requirements are appropriate.

Read the content review record.

Keep the momentum going