Best Practices
Last updated July 1, 2025
Build MVP First and add features incrementally
- Build your Minimum Viable Product (MVP) first
- Add one feature at a time after MVP is complete
- This approach maintains application stability, makes tracking bugs easier, optimizes credit usage, and provides clear checkpoints for your development process
Simplify Complex Ideas
When working with complex project concepts:
- Start with a simpler version of your concept
- Break complex projects into small, manageable parts
- Implement each part step by step
- Test thoroughly before moving to the next component
- Gradually increase complexity only after basics work
Modularize Complex Projects
- Split into smaller tasks
- Push to GitHub between stages
- Avoid exceeding context limit
Application Design Customization
To customize your application's design:
- Describe desired layout, colors, and typography in your prompts
- Reference existing designs as inspiration
- Specify preferred UI frameworks or components
- Review the generated design and request refinements as needed
Save Credits with Smart Rollback Usage
To optimize your credit consumption:
- Use Rollback to delete unnecessary messages
- Choose "Erase messages only" to keep generated code intact
- This reduces credit consumption, keeps your session clean and focused, and maintains progress while clearing context
Handle Looping or High-Credit Usage
When facing agent loops or excessive credit usage:
- Push your current code to GitHub
- Start a new chat with a fresh environment
- Pull your code from GitHub to continue building
- Resume development with a clean context
Use Rollback to Resolve Persistent Issues
When encountering repeated errors or getting stuck:
- Use Rollback to return to the last stable point
- Provide a new, clearer prompt focusing on the issue
- Be more specific about your requirements
- Break the problem into smaller, more manageable parts
How to optimize application performance
To ensure your application runs efficiently:
- Break code into modular components
- Reduce unnecessary database calls
- Implement lazy loading techniques
- Compress assets for faster loading
- Review and optimize critical rendering paths
Managing Credits
Choose E1 when you need reliable, comprehensive testing without user intervention.
Choose E1.1 when you want cost-effective, flexible testing with better third-party integration support, and don't mind being more hands-on with the process. E1.1 uses lesser credits by decoupling front-end testing and letting the user choose.
To manage your project's credit budget:
- Click the (+) icon at the top of the chat interface to increase your budget
- You can allocate up to 100 credits per individual task
- For larger projects exceeding 100 credits:
- Save your current progress-> Start a new task ->Reference your GitHub repository in the new task
- Monitor your credit usage in the credits display at the top of the interface
- Plan your development to efficiently use available credits
Credit Management Tips:
- Break large projects into logical modules across multiple tasks
- Use GitHub to maintain continuity between tasks
- Focus each task on specific features or components
- Provide clear references to previous work when starting new tasks
For any questions or assistance, feel free to email us at support@emergent.sh