Understanding how Leo processes your requests helps you communicate more effectively.

​
The Process

When you send a prompt, Leo goes through these steps:

​
1. Understanding

Leo analyzes your request to understand:
  • What you want - The feature or change you’re requesting
  • The context - Your project, existing code, and integrations
  • The outcome - What the result should look like

​
2. Planning

Leo determines:
  • What to build - New features or modifications needed
  • Where to make changes - Which files to create or modify
  • How to connect - Which integrations to use

​
3. Building

Leo creates or modifies code:
  • Writes code - Creates the necessary files
  • Connects integrations - Uses your connected tools
  • Follows patterns - Uses best practices and conventions

​
4. Showing Results

Leo displays:
  • Code changes - What was modified
  • Live preview - How it looks and works
  • Status - Success or any issues

​
What Leo Knows

Leo has access to:
  • Your project code - All files in your project
  • Connected integrations - Odoo, Airtable, etc.
  • Project memories - Important context you’ve saved
  • Chat history - Previous conversations
  • Best practices - Industry standards and patterns

​
How Leo Learns

Leo learns from:
  • Your feedback - Corrections and clarifications
  • Project memories - Context you explicitly save
  • Patterns - Common ways of doing things
  • Iterations - Building on previous work

​
Fullstack Capabilities

Leo can build:
  • Frontend - User interfaces, forms, dashboards
  • Backend logic - Data processing, API calls
  • Integration connections - Connect to your tools via MCP
  • Full applications - Complete workflows from start to finish

​
Limitations

Leo works best when:
  • You’re specific - Clear about what you want
  • You iterate - Build features step by step
  • You provide context - Use memories for important details
Leo may struggle with:
  • Very vague requests - “Make it better” is too unclear
  • Too many features at once - Focus on one thing at a time
  • Conflicting requirements - Be consistent in your requests

​
Tips for Success

  • Describe outcomes - What should happen, not how to build it
  • Use examples - Reference similar features
  • Be patient - Complex features take time
  • Iterate - Build and refine gradually

Best Practices

Learn how to write effective prompts

Common Patterns

See examples of good prompts