Skip to content

Prompt Library

The Prompt Library gives you ready-to-use prompts for common tasks. Instead of writing complex integration prompts from scratch, pick a tested template and customize it.

  1. Open the attachments menu (+ button) in the chat input
  2. Select Prompt Library
  3. Browse the available prompts
  4. Click a prompt to insert it into your chat input
  5. Customize the text if needed, then send

Asks the AI to review the code produced by the last requested changes for quality, reusability, and efficiency.

  • Finds redundant code, unused imports, and overly complex logic in recently changed files
  • Suggests simplifications and consolidation opportunities
  • Scoped to the last changes, not the entire codebase

Use this periodically — especially after large refactors or when you’ve added several features in a row.

Finds the single largest .dart file in your project and breaks it into well-organized smaller files.

  • Extracts widgets, models, services, and utilities into separate files
  • Follows your project’s existing folder conventions
  • Only moves code between files — no logic changes, no visual changes
  • Token usage: ~400,000 tokens for a 5,000-line file. Check your balance before running.

Use this when a file has grown too large to navigate easily — typically after many features have been added to the same screen.

Provides a step-by-step prompt for integrating Firebase Analytics into your app.

  • Includes the google-services.json configuration template
  • Sets up basic event tracking
  • Gets you to a working analytics setup quickly

You’ll still need to create a Firebase project and download your own configuration file. See Firebase Setup for the full integration guide.

Adds a GDPR-compliant consent dialog for ad tracking. This is required before showing ads to users in the EU.

  • Displays a consent prompt on first launch
  • Stores the user’s choice
  • Gates ad loading on consent status

Implement this before adding any ad units. Without it, your app may violate EU privacy regulations.

Adds a banner ad to your app using Google AdMob.

  • Uses test ad unit IDs by default — replace with your real IDs before publishing
  • Includes proper ad initialization and lifecycle handling
  • Places the banner at a standard position in your layout

Adds full-screen interstitial ads triggered at natural breakpoints in your app.

  • Uses test ad unit IDs by default
  • Includes loading, display, and error handling logic
  • Best placed at transition points (e.g., after completing a level, between screens)

If you’re adding ads to your app, use the prompts in this order:

  1. AdMob Consent Flow — set up GDPR consent first
  2. AdMob Banner Ad or AdMob Interstitial Ad — add your ad units after consent is in place

The consent flow must be in place before any ads load. Sending the ad prompts without the consent flow will still work technically, but your app won’t be compliant with EU regulations.

Tips for getting the most out of templates

Section titled “Tips for getting the most out of templates”
  • Customize before sending. The prompts are starting points, not rigid scripts. Add details about your specific app — screen names, color preferences, where you want ads placed.
  • Combine with file references. If you know which file should be modified, add an @file: reference to focus the AI. For example, after inserting the Banner Ad prompt, add: “Place the banner at the bottom of @file:lib/screens/home_screen.dart.”
  • Run “Review & Simplify Code” regularly. After every 5-10 prompts, or whenever the AI has made significant structural changes. This keeps your codebase clean and prevents technical debt from accumulating.

Prompting fundamentals

Write effective prompts to get better results when customizing templates or writing your own.