Writing Effective Prompts

Learn techniques for writing prompts that get better results from AI in Firebuzz.

The quality of AI responses depends heavily on how you communicate your requests. Clear, specific prompts lead to better results with fewer iterations. This guide covers proven techniques for getting the most out of AI assistance.

Core Principles

Be Specific

Vague requests lead to generic results. Include details about what you want.

Instead of this

"Make it better"

Try this

"Change the hero section headline to be more action-oriented and add a subheadline explaining the main benefit"

Instead of this

"Add some social proof"

Try this

"Add a testimonials section below the features with 3 cards showing customer photos, quotes, and company names"

Describe Visual Changes Clearly

When requesting design changes, include specific details:

Colors — "Use the brand's primary blue (#3B82F6)" or "Make the background a light gray"
Sizes — "Make the headline larger" or "Reduce padding to 16px"
Spacing — "Add more space between sections" or "Tighten the gap between the icon and text"
Layout — "Center the content" or "Arrange items in a 3-column grid"

Use Design Mode to select specific elements when your description might be ambiguous. This tells the AI exactly which element you're referring to.

One Change at a Time

For complex modifications, break your request into steps:

Instead of this

"Redesign the entire page with a new hero, features section, testimonials, and footer"

Try this

Start with: "Add a hero section with a headline, subheadline, and CTA button" Then: "Add a features section below the hero with 4 feature cards" Then: "Add a testimonials section with 3 customer quotes"

This approach lets you review each change and provide feedback before moving on.

Prompt Techniques

Reference Existing Elements

Point to what's already on the page:

"Change the hero button color to match the navigation"
"Make the feature icons larger like the ones in the pricing section"
"Use the same card style from the testimonials section for the team cards"

Provide Context

Explain the purpose behind your request:

"This is a SaaS landing page for project management software targeting small teams"
"The audience is enterprise buyers who need detailed feature information"
"We want to emphasize the free trial offer"

Use Examples

Reference patterns or styles you like:

"Create a hero section similar to Stripe's homepage — clean, minimal, with a product screenshot"
"Style the pricing cards like a comparison table with highlighted recommended plan"

Structure Complex Requests

For multi-part requests, use numbered lists:

Please update the features section:
1. Change the layout to a 2x2 grid
2. Add icons above each feature title
3. Use the brand's secondary color for the icon backgrounds
4. Add a subtle hover effect on each card

Model-Specific Tips

Different AI models respond better to different prompting styles:

Claude Models (Haiku, Sonnet, Opus)

Claude responds well to structured, detailed requests:

Use clear sections in longer prompts
Provide explicit constraints and boundaries
State what you don't want as well as what you do want

Create a pricing section with these requirements:
- 3 pricing tiers (Basic, Pro, Enterprise)
- Highlight the Pro tier as recommended
- Include a feature comparison list
- Do NOT add a free tier

GPT Models (GPT-5, Codex, Mini)

GPT works well with markdown-style formatting:

Use headers and bullet points
Include code snippets when relevant
Be explicit about output format

## Task
Add a contact form to the page

## Requirements
- Fields: Name, Email, Message
- Email field should validate format
- Submit button with loading state

Gemini Models (2.5 Pro, Flash, 3 Pro)

Gemini excels with hierarchical, well-organized prompts:

Use clear heading structure
Define scope at the start
Break complex tasks into explicit steps

# Goal
Improve the hero section conversion rate

# Current Issues
- Headline is too generic
- CTA doesn't stand out
- Missing social proof

# Requested Changes
1. Write a more specific, benefit-focused headline
2. Make the CTA button larger with a contrasting color
3. Add a small "Trusted by 10,000+ teams" badge below the CTA

Common Prompt Patterns

Adding New Sections

Add a [section type] section [location] with:
- [specific element 1]
- [specific element 2]
- [styling preferences]

Example:

Add a FAQ section below the pricing with:
- 6 common questions about our service
- Expandable accordion style
- Use the same typography as the features section

Modifying Existing Elements

Update the [element] to:
- [change 1]
- [change 2]
Keep [what should stay the same]

Example:

Update the navigation to:
- Add a "Pricing" link after "Features"
- Make the CTA button more prominent with a filled style
Keep the logo and other links as they are

Fixing Issues

The [element] has [problem]. Please [solution].

Example:

The mobile menu isn't closing when a link is clicked. Please add logic to close the menu on navigation.

What to Avoid

These patterns often lead to poor results or wasted iterations.

Vague adjectives — "Make it pop" or "Make it more modern" without specifics
Contradictory requests — "Make it minimal but add lots of information"
Assuming context — The AI doesn't remember what you discussed yesterday
Multi-page changes — Focus on one page at a time
Unrealistic expectations — "Make it look exactly like Apple's website"

Writing Effective Prompts

Instead of this

Try this

Instead of this

Try this

Instead of this

Try this

How long should my prompts be?

Should I include technical details?

What if the AI doesn't understand my request?

Can I reference images or screenshots?

Do I need to be polite to the AI?

On this page