RIB Creative LogoRib Creative Docs
Cmd K
IntroductionPrompting best practices

Introduction / Getting started

Prompting best practices

Write clear prompts that produce better apps and edits.

Prompting best practices

Good prompts help RIB Creative understand what you want, avoid accidental changes, and produce work that is easier to review.

The basic prompt structure

Use this structure for most requests:

  1. Goal: What outcome do you want?
  2. Scope: What should change?
  3. Constraints: What should stay the same?
  4. Details: What copy, behavior, data, or style matters?
  5. Review: What should the agent summarize or verify?

Copyable prompt template

Goal:
I want to [describe the result].

Scope:
Change only [page, component, flow, or files].

Keep:
Do not change [navigation, database, styling system, existing behavior, etc.].

Details:
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

Review:
After the change, summarize what changed, what I should test, and any risks.

Good prompts

Use specific prompts like:

Create a landing page section for a bookkeeping SaaS.
Audience: small business owners.
Tone: clear and trustworthy.
Include: headline, short supporting text, 3 benefit bullets, and one CTA.
Keep the existing page header and footer unchanged.

Fix the mobile layout on the dashboard filters.
The filters should wrap cleanly on small screens.
Do not change the desktop layout.
After editing, tell me which viewport sizes I should review.

Prompts to avoid

Avoid vague prompts like:

  • "Make this better."
  • "Improve the design."
  • "Fix all bugs."
  • "Build the whole app."
  • "Make it like another product."

These prompts force the agent to guess. Guesses can lead to extra work, higher usage, and changes you did not intend.

When to use planning first

Use a planning prompt before large or risky changes:

Before changing code, create a plan for adding a booking flow.
Include the pages, data needed, user steps, edge cases, and risks.
Do not implement yet.

Planning is useful when the request affects:

  • Multiple pages.
  • Authentication or permissions.
  • Payments.
  • Data storage.
  • Publishing.
  • Existing user flows.

How to reduce AI mistakes

  • Give the agent a clear target.
  • Ask for one change at a time.
  • State what must not change.
  • Review previews before continuing.
  • Ask for a summary of files and behavior changed.
  • Use examples when copy or style matters.

FAQ

Should I include screenshots?

Use screenshots when the issue is visual, layout-related, or hard to describe. For behavior, text instructions are usually more precise.

Should I ask for one change or many?

Start with one clear change. Batch related changes only when they share the same goal and review path.

What if I do not know the technical terms?

Describe the user experience. For example: "When someone clicks the button, show a form and save the message" is better than guessing a technical implementation.

Next steps