Anything App

Prompting Effectively

Clear, specific prompts help the AI build better apps. Describe the data, user flow, AI features, and visible changes you want instead of relying on a broad one-line idea.

Write specific prompts

Start by explaining what the app should help you do. Then include the important fields, actions, screens, and constraints.

A strong prompt usually includes:

  • The purpose of the app.
  • The information the app should track or display.
  • The actions users need to take.
  • Any AI capability you want, such as chat, text generation, or image analysis.
  • Any visible layout, style, or brand direction.

Good prompt patterns

Use these patterns when describing a new app or a change:

  • Be specific about your data. Mention fields, categories, or attributes clearly.
  • Describe the user flow. Explain what screens, views, or actions you need.
  • Mention AI features explicitly. If you want chat, text generation, image analysis, or another AI feature, say so directly.
  • Start simple, then iterate. Build the core workflow first and add advanced features in follow-up messages.
  • Reference what you see. When changing an existing app, point to visible elements like buttons, cards, lists, or layouts.
  • For visual quality, describe the feeling and structure you want: playful, editorial, premium, dashboard-like, mobile-first, dense, minimal, or highly visual.
  • Describe the outcome instead of prescribing external infrastructure. For example, ask to "save each user's tasks" rather than requesting Supabase, or ask for "reminders" rather than Resend email. The editor can use private cloud data and push notifications that work on the platform.

Generated apps do not need their own login system, backend, or billing setup. They also cannot send external email. If your idea mentions login, password resets, email verification, Stripe plans, or an external database, the editor will build the closest platform-aligned workflow and explain the adaptation. See Platform limitations.

Iterating on results

After the first version appears, test it in preview and describe what should change. You can ask for functional changes, UI adjustments, bug fixes, or refinements.

Examples:

  • "Move the add button to the bottom of the screen."
  • "Change the card layout to a list view."
  • "Add a weekly view with progress charts."
  • "Make the app feel more premium with a darker palette, stronger preview area, and clearer primary actions."

Prompt examples

  • "Track my workouts with exercise name, sets, reps, weight, and date."
  • "I want to add items to a list, mark them as complete, and filter by status."
  • "Use AI to suggest recipes based on ingredients I have."
  • "Let me chat with an AI about my notes."