Writing Effective Prompts

Learn how to describe products, users, flows, and design direction so condoo.Vibe builds closer to what you imagined the first time.

The quality of what condoo.Vibe builds depends partly on how clearly you communicate what you want.

You don't need to learn a special prompting language or write technical specifications. But giving condoo.Vibe the right context helps your AI product team understand your goals, make better decisions, and build closer to what you imagined.

This guide shows you how to write effective prompts for websites, applications, features, design changes, and more complex product work.

Think in outcomes, not code

A good condoo.Vibe prompt starts with what you want the product to accomplish.

You usually don't need to tell condoo.Vibe exactly how to implement it.

Instead of:

Create a React component with a form containing five input fields and POST the data to an API endpoint.

Try:

Add a quote request form to the construction website. Visitors should enter their name, email, phone number, project type, budget, and a short description of their project. Save each request so it can be viewed later from the admin dashboard.

The second prompt gives condoo.Vibe something more valuable: the desired product behavior.

condoo.Vibe can determine the implementation required to achieve it.

The four parts of a strong prompt

For larger requests, a useful structure is:

Context → Goal → Requirements → Direction

Context

Tell condoo.Vibe what you're working on and who it's for.

I'm building a CRM for a real estate agency with a team of agents.

Goal

Explain what you want to accomplish.

I want agents to have one place to manage potential buyers and sellers.

Requirements

Describe the important things users should be able to do.

Agents should be able to create leads, assign leads to team members, change lead status, add notes, schedule follow-ups, and search or filter the lead list.

Direction

Add any important experience or design preferences.

Keep the interface professional and easy to scan. Use a clean table on desktop and cards on mobile.

Combined:

I'm building a CRM for a real estate agency with a team of agents. I want agents to have one place to manage potential buyers and sellers. Agents should be able to create leads, assign leads to team members, change lead status, add notes, schedule follow-ups, and search or filter the lead list. Keep the interface professional and easy to scan. Use a clean table on desktop and cards on mobile.

That's a strong condoo.Vibe prompt.

Be specific where it matters

More words don't automatically make a better prompt.

The goal is to give condoo.Vibe useful information.

Too vague

Build me a CRM.

condoo.Vibe has to make many assumptions about what kind of CRM you need.

Better

Build a CRM for a real estate agency. Agents should be able to manage leads, properties, deals, and follow-ups. Include a dashboard showing active leads, pipeline value, upcoming follow-ups, and recent activity.

Now condoo.Vibe understands the industry, users, core resources, and dashboard requirements.

Tell condoo.Vibe who the user is

Knowing who will use the product can change how condoo.Vibe approaches the experience.

Instead of:

Build an appointment booking system.

Try:

Build an appointment booking system for a beauty salon. Customers should be able to choose a service, select a stylist, see available appointment times, and book online. Salon staff should have a dashboard for managing appointments.

You've now identified two different users:

• Customers
• Salon staff

That gives condoo.Vibe much more context for designing the application.

Describe important user flows

For applications, describe what should happen from the user's perspective.

For example:

A new customer should be able to create an account, choose a subscription plan, complete payment, and then be taken to their dashboard.

Or:

When an agent creates a new lead, they should be able to assign it to another team member and schedule a follow-up without leaving the lead page.

User flows help condoo.Vibe understand how different parts of your application should work together.

Give condoo.Vibe design direction

You can describe how you want the application to feel without specifying every CSS property.

For example:

Make the website feel premium, modern, and architectural. Use generous whitespace, strong typography, large professional construction photography, and subtle animations. Avoid making it feel like a generic template.

Or:

Design the dashboard like a premium B2B SaaS product. Keep information dense but easy to scan, with clear hierarchy and minimal visual clutter.

You can describe:

• Visual style
• Brand personality
• Layout preferences
• Colors
• Typography
• Density
• Animation
• Mobile behavior

Use references carefully

You can describe products or design styles that communicate the direction you're looking for.

For example:

I want the dashboard to feel polished and minimal like a modern enterprise SaaS product, with strong information hierarchy and generous spacing.

The goal isn't necessarily to copy another product.

References should help communicate qualities such as:

clean, editorial, playful, enterprise, minimal, luxurious, technical, bold, or approachable.

Break complex work into stages

You don't need to build an entire sophisticated product in one instruction.

For complex applications, working in stages often gives you more opportunities to review important decisions.

For example:

Stage 1

Build the core CRM with leads, contacts, and a dashboard.

Stage 2

Now add a sales pipeline. Deals should move through Qualified, Proposal, Negotiation, Won, and Lost stages.

Stage 3

Add team management. Workspace owners should be able to invite agents and assign leads and deals to them.

Stage 4

Add reporting showing pipeline value, conversion rate, deals won this month, and performance by agent.

You are evolving the product instead of trying to describe every future requirement at once.

Tell condoo.Vibe what to keep

When modifying an existing application, tell condoo.Vibe what shouldn't change when that's important.

For example:

Redesign the hero section to make the headline and CTA more prominent. Keep the existing navigation, colors, typography, and the rest of the homepage unchanged.

This gives condoo.Vibe clear boundaries.

Another example:

Add search and filtering to the customer table. Don't change the existing table columns or customer creation flow.

This is especially useful when your application is already close to what you want.

Give feedback precisely

If something doesn't look or work the way you expected, avoid simply saying:

I don't like this.

Tell condoo.Vibe what needs to improve.

For example:

The hero feels too crowded. Reduce the amount of text, give the headline more breathing room, make the primary CTA more prominent, and reduce the number of elements above the fold.

Or:

The dashboard is difficult to scan. Make the four main KPIs more prominent, move recent activity lower on the page, and give the upcoming tasks section more visual priority.

You don't necessarily need to know the solution.

You can describe the problem you're experiencing, and condoo.Vibe can help determine the solution.

Prompt for behavior, not just appearance

When building applications, don't stop at describing what something should look like.

Explain what should happen.

Instead of:

Add a login page.

Try:

Add authentication. Users should be able to create an account with email and password or sign in with Google. After signing in, take them to their dashboard. Signed-out users shouldn't be able to access dashboard pages.

The second prompt describes the actual product behavior.

Ask condoo.Vibe to think before changing complex features

Some changes affect several parts of an application.

For example:

I want to add multi-tenant workspaces so each company has separate users and data. Don't build this yet. First analyze the existing application and create a plan covering the database changes, authentication, permissions, migration risks, and pages that need to change.

This is where Plan mode becomes particularly useful.

Examples of effective prompts

Website

Build a premium website for a commercial construction company serving businesses in Lagos. Include Home, About, Services, Projects, Safety, Careers, and Contact. The main conversion goal is quote requests. Use strong architectural photography, bold typography, generous whitespace, and a professional corporate feel. Make the site fully responsive.

SaaS application

Build a SaaS application for agencies to manage clients and projects. Users should be able to create a workspace, invite team members, add clients, create projects for each client, assign tasks, track deadlines, and see recent activity from a dashboard. Each workspace's data must remain separate.

Feature

Add a notification center to the existing application. Show unread notifications in the header with a badge. Users should be able to open the notification panel, mark individual notifications as read, or mark all as read. Keep the existing header design.

Improvement

Improve the mobile experience of this page. Keep the desktop layout unchanged. On mobile, stack the cards vertically, make all primary actions full-width, ensure touch targets are easy to tap, and prevent the table from overflowing the viewport.

Fix

The form currently submits but users receive no confirmation. After a successful submission, show a success message, clear the form, and disable the submit button while the request is processing. If submission fails, preserve the user's input and show a clear error message.

A reusable prompt framework

When you're unsure how to structure a complex request, use this:

I'm building [PRODUCT] for [AUDIENCE].

The goal is [OUTCOME].

Users should be able to:
- [REQUIREMENT]
- [REQUIREMENT]
- [REQUIREMENT]

The experience should feel [DESIGN DIRECTION].

Important constraints:
- [CONSTRAINT]
- [CONSTRAINT]

Keep [EXISTING THINGS THAT SHOULD NOT CHANGE].

You don't need to fill every field.

Use only the information relevant to what you're asking condoo.Vibe to do.

The most important rule

Tell condoo.Vibe what you're trying to achieve, not just what you want generated.

condoo.Vibe works best when it understands:

Who is this for? → What problem are we solving? → What should users be able to do? → What should the experience feel like?

From there, your AI product team can make much better implementation decisions.

Next: The four modes

Now that you know how to communicate effectively with condoo.Vibe, learn how to choose the right way for condoo.Vibe to approach your request:

Build → Plan → Explore → Debug

Each mode is designed for a different kind of work.