Prompt Guidelines

Writing a high-quality project description is the single most important step in Vibemap. The AI uses this "Prompt" as the foundation for generating your personas, features, database schema, and UI code.

Project Creation Form

Writing Effective Project Descriptions

Why Detail Matters

Vibemap's AI subagents are highly sophisticated, but they require context to make intelligent architectural decisions. A vague prompt like "Build an Uber for X" will produce generic results, while a detailed prompt will create a tailored, production-ready scaffold.

Key Elements to Include

1. Core Value Proposition

• What: Clear description of what you're building.

• Why: The problem you're solving or the unique need you're addressing.

• How: High-level approach to solving the problem.

2. Target Users

• Primary Users: The main audience who will use the application.

• Secondary Users: Admins, staff, or third-party stakeholders.

• User Characteristics: Demographics, technical skills, and usage patterns.

3. Core Features

• Must-Haves: Essential functionality for your MVP (Minimum Viable Product).

• Specifics: Instead of "Chat", say "Real-time direct messaging with file attachments".

• Nice-to-Haves: Additional features for future releases to help the AI understand the project's scale.

4. Technical Preferences & Constraints

• Platform: Web, mobile, desktop, or multi-platform.

• Integrations: Mention specific frameworks or third-party APIs (e.g., "Stripe for payments", "Supabase for backend").

• Performance: Specific needs like "Must support high-resolution image uploads" or "Real-time data synchronization".

5. Business Goals & Metrics

• Objectives: What are the primary business goals?

• Success Metrics: How will success be measured (e.g., "User engagement", "Conversion rates")?

Prompt Writing Best Practices

Use the Provided Template

Vibemap prepopulates the text area with a proven structure. We recommend following it:

## What does your app do?
[Focus on the primary solution]

## Who are your target users?
[Define at least 2 distinct user roles]

## What are the core features?
[List 3-5 critical functional requirements]

## What problems does it solve?
[Explain the business value]

Use Specific Language

• Avoid: Vague terms like "user-friendly", "modern", or "fast".

• Use: Action-oriented terms like "drag-and-drop file organization", "two-factor authentication", or "one-click checkout".

Common Mistakes to Avoid

Too Vague

• ❌ Bad: "I want to build a social media app"

• ✅ Good: "I want to build a photo-sharing social media app for photographers to showcase their work and connect with clients"

Missing User Context

• ❌ Bad: "Users can post content"

• ✅ Good: "Photographers can upload high-resolution images with metadata, while clients can browse portfolios and request quotes"

No Technical Specifications

• ❌ Bad: "It should be fast and reliable"

• ✅ Good: "The app should load images in under 2 seconds and support concurrent uploads from 100+ users"

Unclear Business Goals

• ❌ Bad: "Make money"

• ✅ Good: "Generate revenue through premium subscriptions and a commission on client bookings"

Examples of Great Prompts

E-commerce Example

"I want to build a mobile e-commerce app for artisanal coffee roasters. Small-batch roasters should be able to list their current inventory, manage subscription levels for customers, and track shipments. Customers should be able to browse coffee by flavor profile (e.g., fruity, nutty, bold), manage a monthly delivery schedule, and receive push notifications when a new roast is available. The UI should be clean and minimalist, focusing on high-quality product photography. We need integration with Stripe for payments and a dashboard for roasters to see their monthly revenue."

SaaS Project Management Example

"I'm building a project management SaaS application for small marketing agencies. The platform should help teams collaborate on campaigns, track task deadlines, and manage client approvals. Primary users are Project Managers who need oversight and Team Members who need clear task lists. Features should include a Kanban board, time tracking, and a client-facing portal for approvals. It must be web-based and support real-time collaboration."

Optimizing for Quality

• Minimum Length: 50 characters (Required).

• Optimal Length: 300 - 800 characters for a comprehensive project foundation.

• Review: You can always edit your "Current Prompt" later to refine your project as it evolves.

Project Prompting Interface