Usage Guide

Interacting with the VibeMap Conversational Agent is designed to be natural and intuitive. You can use standard English to ask questions or request changes.

Opening the Chat Interface

You can access the Conversational Agent from anywhere in your project dashboard:

1. Sidebar: Click the chat icon in the project sidebar to open the chat panel.

2. Keyboard Shortcut: Use Cmd + K (Mac) or Ctrl + K (Windows) to quickly open the command and chat interface.

Core Interaction Patterns

The agent understands several types of requests:

1. Simple Questions

Ask about the current state of your project.

• "Show me all the features I've created."

• "What are the main user roles in this project?"

• "Explain the current database schema."

2. Generation Requests

Request new content to be generated.

• "Create 5 more user stories for the checkout feature."

• "Generate additional personas for a mobile user."

• "Add a new feature for social login."

3. Modification Requests

Update existing items using natural language.

• "Change the priority of the login feature to high."

• "Update the 'Admin' persona to include technical expertise."

• "Add a 'price' column to the 'products' table in the schema."

4. Destructive Requests

The agent handles deletions with care.

• "Delete the old analytics feature."

• "Remove the guest user story about guest checkout."

Advanced Referencing (Tags)

While the agent is excellent at understanding context, you can be more precise using tags:

• @ Mentions: Reference specific entities.

  • "Create user stories for @features:checkout-system"

  • "Update the @personas:admin-user"

• # Tags: Specify the entity type.

  • "Generate more #user-stories"

  • "Show me all #pages"

Confirmation Workflow

For operations that modify your project (especially deletions), the agent will:

1. Analyze: Detect all primary changes and cascade impacts.

2. Warn: Display a detailed confirmation dialog showing exactly what will be affected.

3. Confirm: Require you to click "Confirm" or "Proceed" before any database changes are made.

Pro Tips for Effective Interaction

• Be Specific: Instead of "add more stories," try "add 3 user stories for the @features:payment-gateway focusing on error cases."

• Context Matters: The agent looks at your current page. If you're on the Features tab, it prioritizes feature-related context.

• Sequential Requests: You can build on previous answers. "Now add acceptance criteria for the first story you just generated."