Best Practices

Project Welcome Screen

Why it matters:

The Project Welcome screen is the foundation of your application in Kavia. It’s where you define the key settings and direction of your build—including core features, tech stack, layout, and integrations. Spending a few minutes reviewing this screen properly can save hours later in the development process.

What to check:

1

Project Overview:

Even if your initial prompt was vague, Kavia enhances and refines it into a detailed project description. Review this carefully—make edits if needed to better align with your vision.
2

Core Features:

Kavia automatically extracts and lists essential features for your application. Take time to read through them. You can edit, remove, or add new features directly from this section.
3

Tech Stack:

Confirm that the suggested technologies (frameworks, languages, and databases) are suitable for your project. You can switch tech stacks here before development begins.
4

Page Layout & Theme:

Kavia suggests an initial page layout based on your prompt. Review the structure, flow, and suggested screens, and modify them as needed. You can also change the theme and primary colors to match your brand or preferences.
5

Third-Party Integrations:

The Welcome screen provides options to connect essential services like GitHub, Supabase, Stripe, and others. Be sure to connect the integrations you plan to use from the start—this ensures smooth setup and deployment down the line.

Prompting Best Practices

Great prompts make Kavia work smarter for you. Think of the AI as your development partner—it only builds what you describe. Clear, detailed instructions help avoid bugs, save time, and get closer to your intended result.

Tips for Writing Effective Prompts:

1

Be Specific:

Mention exactly what page, component, or interaction you’re targeting.
  • On the /settings/profile page, add a form that lets users upload a profile picture and update their email address.
2

Use Natural Language:

Don’t worry about code syntax. Write your requirements the same way you’d explain them to a teammate.
  • Let users choose between light and dark mode. Save their preference in local storage and apply it on every page load.
3

Add Screenshots:

Upload a screenshot when describing layout bugs, spacing issues, or UI problems. This helps the AI understand what needs fixing visually.
4

Set Guardrails:

Tell the AI what not to touch, especially shared or working components.
  • Do not modify the AuthProvider logic in /contexts/AuthContext.tsx. Only update the login form UI.
5

Repeat Important Instructions:

Reinforce key requirements across prompts if they’re critical to the feature. This ensures consistency in long or multi-step builds.
6

Break Work into Chunks:

Avoid combining unrelated tasks. Instead, break them into smaller prompts for better results and testing.
  • Build the page layout
  • Add form fields/UI elements
  • Connect to API or database
  • Add input validation
  • Test the behavior per user type
7

Clarify User Roles:

Always mention which user type a feature is for. This is essential for role-based dashboards or permissions.
  • Only users with the role Student should see the /courses/enrolled page. Instructors should be redirected to /instructor/dashboard.

Use Edit Mode for Quick UI Fixes

Kavia’s Visual Edit Mode is the fastest way to make simple design changes without writing prompts or using AI credits. It’s especially useful for minor UI adjustments and gives you full control with undo support.

When to Use Edit Mode:

1

Change text or button labels

For example, update a button from “Submit” to “Send Request”.
2

Adjust font sizes, colors, spacing

Ideal for quickly aligning visuals to your brand or improving readability.
3

Tweak page layout or alignment

Make layout adjustments such as resizing containers, changing alignment, or shifting sections.
4

Edit multiple elements quickly

Useful when you want to modify several components on a page in one go.
5

Make safe commits without using AI credits

All edits are tracked and reversible, allowing you to test changes confidently.

Stay Strategic

Working with Kavia’s AI can accelerate your development process dramatically—but like any powerful tool, it requires thoughtful use. Sometimes things click instantly, and other times, refining a feature takes a few tries. That’s part of the process.

Why it matters:

Rushing through prompts or skipping validation can lead to confusion or broken workflows later. The last steps in a project often involve the most detail-oriented adjustments—don't underestimate their importance.

What to keep in mind:

1

Break complex tasks into smaller, logical steps. Tackle one thing at a time.

2

Review results carefully and make changes incrementally.

3

Don&spos;t hesitate to rephrase your prompt or retry if the result isn&spos;t quite right.

4

Use the chat to confirm smaller changes before combining them into larger features.

Staying calm and methodical helps you get the best results out of Kavia.

Use the Documentation and Community Resources

Kavia’s documentation isn’t just a manual—it’s your co-pilot. It’s filled with examples, setup guides, prompting strategies, integration tips, and common troubleshooting steps. Whether you're building a new feature or connecting a backend, you’ll often find answers there before needing to rephrase your prompt.

Where to turn:

1

Use the built-in Doc Assistant to ask questions directly inside the documentation.

2

Visit the [Kavia Discord Community] to share your build, ask for tips, or learn how others are using the platform.

3

When your project is ready, consider showcasing it through the Kavia Launch feature to get feedback and visibility.

Never feel stuck—between the docs, AI chat, and community, there’s always help available.

Previous
Tips & Tricks
Next
Troubleshooting

Inspect. Plan. Build.

Transform Enterprise Software Development Process with KAVIA AI

© 2025 KAVIA AI – All Rights Reserved.