> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Efficient Prompting

> Learn principles and see examples for writing effective prompts when using Replit Agent.

export const WistiaEmbed = ({videoId, title = "Wistia video", playerColor = "FF0000", controlsVisibleOnLoad = false}) => {
  if (!videoId) {
    return null;
  }
  const url = "https://fast.wistia.net/embed/iframe/" + videoId + "?seo=false&playerColor=" + playerColor + "&controlsVisibleOnLoad=" + controlsVisibleOnLoad;
  return <Frame>
      <iframe src={url} title={title} allow="autoplay; fullscreen" allowFullScreen></iframe>
    </Frame>;
};

Effective prompting starts with the outcome you want. Guide [**Agent**](/core-concepts/agent) with clear, simple requests, and you'll go from idea to app faster.

<WistiaEmbed videoId="hsniyd5c7o" title="10 tips for better vibe coding" />

## Quick examples

See the difference between vague and effective prompts:

<AccordionGroup>
  <Accordion title="Fixing code" icon="bug">
    **Vague:** "Fix my code."

    **Effective:** "The sign-in form fails even with the right password. Fix the login flow."

    Start with the broken outcome. Then add the error or file if Agent needs more context.
  </Accordion>

  <Accordion title="Building features" icon="hammer">
    **Vague:** "Make a website."

    **Effective:** "Build a simple portfolio site with Home, About, and Contact pages."

    Focus on the result you want, plus the few details that matter most.
  </Accordion>

  <Accordion title="Performance improvements" icon="gauge-high">
    **Vague:** "Don't make it slow."

    **Effective:** "Make the dashboard load faster when there are lots of orders."

    Describe the improvement you want. Let Agent choose the implementation unless you have a strong preference.
  </Accordion>

  <Accordion title="UI changes" icon="paintbrush">
    **Vague:** "Add animation."

    **Effective:** "Add a subtle fade-in to the hero image when the page loads."

    Name the part of the app and the effect you want.
  </Accordion>

  <Accordion title="Complex systems" icon="server">
    **Vague:** "Build the backend."

    **Effective:** "Add sign-in, profiles, and a way for people to save their progress."

    Ask for the product outcome first. Add technical details only if they are important.
  </Accordion>
</AccordionGroup>

## Core principles

<Frame>
  <img src="https://mintcdn.com/replit/0ixNWaRF232g0Gwn/images/tutorials/10-tips.png?fit=max&auto=format&n=0ixNWaRF232g0Gwn&q=85&s=21e1e7269802faa767fef0187bdb6e3d" alt="Ten tips for effective prompting with Replit Agent" width="1259" height="1101" data-path="images/tutorials/10-tips.png" />
</Frame>

### Plan first

<Tip>Before you prompt, decide what success looks like. A simple plan leads to better prompts.</Tip>

Write down the main outcome, then the next few milestones.

**Instead of:** "Build a task manager app."

**Try:** "Build a simple task manager where I can add, complete, and delete tasks."

Then use follow-up prompts to refine it.

### Build incrementally

[**Checkpoints**](/core-concepts/agent/checkpoints-and-rollbacks) happen automatically as Agent works. If something breaks, you can roll back and try a different approach.

**Instead of:** "Build a complete e-commerce platform."

**Try:** "Start with a simple online store with sign-in and product pages." Then add cart, checkout, and admin tools in follow-up prompts.

### Be specific

Say what you want to happen and include the details that change the result.

**Instead of:** "Add a contact form."

**Try:** "Add a contact page with name, email, and message fields. Send submissions to my email."

### Use positive language

State what you *want*, not what to avoid.

**Instead of:** "Don't make the user profile page confusing."

**Try:** "Make the profile page clean and easy to scan. Show the name, email, join date, and an Edit profile button."

### Keep it simple

Use short, direct language. Add implementation details only when they matter.

**Instead of:** "Implement the necessary server-side infrastructure to facilitate the dynamic generation and retrieval of user-generated content artifacts."

**Try:** "Let people write and publish blog posts."

## Working with context

### Provide relevant files

Share only the files or references Agent needs.

**Instead of:** (Attaching everything) "Implement the user profile page based on our design system."

**Try:** "Create the user profile page and match this mockup: \[attach `profile_mockup.jpg`]. Use the colors from our design doc: \[URL]."

<Tip>Start a new chat when switching to unrelated tasks. This prevents confusion from accumulated context.</Tip>

### Show examples

Reduce ambiguity with examples, screenshots, or sample data.

**Instead of:** "Make the product cards look better."

**Try:** "Make the product cards look like this screenshot: image, name, price, and an Add to cart button."

## Debugging effectively

When something breaks, include:

* The **exact** error message
* Relevant code snippets
* File names where the error occurs
* What you were trying to achieve
* Steps you've already tried

**Instead of:** "My login page is broken."

**Try:** "The login page shows 'User not found' even with valid credentials. It happens on `/login`. Please fix it."

## Ask for guidance

<Tip>Switch to Plan mode to explore options before building. Ask Agent about libraries, approaches, and trade-offs.</Tip>

**Instead of:** "Add payments."

**Try:** "What's the simplest way to add credit card payments to my app on Replit?"

## Iterate on your prompts

Your first prompt might not be perfect. If the result isn't right:

* Add more detail
* Provide an example
* Simplify the instruction
* Try a different way of explaining

**Initial:** "Add a header to my site."

**Refined:** "Create a sticky header component with the site logo on the left and navigation links (Home, About, Contact) on the right."

## Summary

Effective prompting comes down to:

* **Planning** before you prompt
* **Building** incrementally — checkpoints happen automatically as Agent works
* **Describing outcomes** clearly
* **Providing context** through examples and relevant files
* **Iterating** when results aren't quite right

Keep prompts short, outcome-focused, and easy to follow, and you'll build faster with Agent.