Writing Prompts That Get Better Results

Why Prompt Quality Matters

Every feature Kulp builds is based on your prompt. The more clear, specific, and structured your input is, the better your software will turn out - fewer errors, faster builds, and exactly what you had in mind.

5 Rules for Better Prompting

1. Be Clear, Not Vague

• Bad: “Make a CRM.”

• Good: “Build a CRM with client profiles, follow-up reminders, and a dashboard view.”

2. Include Core Features

List out the main things you want - pages, forms, logic, workflows.

Example:

“Build a blog with user signup, post creation, commenting, and a category filter.”

3. Mention the Tech (If You Care)

Want Supabase? Stripe? Authentication? Say so.

Example:

“Use Supabase for auth and database. Stripe for payments.”

4. Break It Into Steps (If It’s Complex)

If your project is big, start with one part.

“Let’s begin with the landing page and signup flow.”

5. Use the Plan to Guide Your Flow

When features are added via the Plan, it helps Kulp stay consistent. Use that to structure your project.

Prompt Templates You Can Adapt

• Internal Tool:

  “Create a dashboard for employee onboarding with checklist tracking, role-based access, and analytics.”

• Client App:

  “Build a portal where clients can log in, upload files, and get notifications when reviewed.”

• Product MVP:

  “I need an app that lets users submit reviews for local cafes. Include maps, ratings, and filters.”

Things to Avoid

• “Make an app like Airbnb” → Too broad

• “Build a dashboard” → What kind of dashboard? For who?

• Leaving out important logic or integrations

The more Kulp understands, the better it performs.

Final Tip

If you’re unsure what to say, start with voice prompts or use Enhance Prompt to clarify. You don’t need to be a developer - just explain your idea like you're describing it to a smart teammate.