Ideavo Rules

The Ideavo Agent can be configured and customized to align with your project requirements. Rules define how the agent behaves, writes code, and interacts within a project.

How to Configure Rules

1. Open the Code Editor in your project.
2. Navigate to the .ideavorules file.
3. Define your preferences and constraints in this file (e.g., coding style, technology stack, communication verbosity).
4. Save changes - the Agent will automatically load and apply these rules to your current and future sessions.

Rules can cover

• Coding style (e.g., tabs vs spaces, naming conventions)
• Framework/technology choices (Supabase, Firebase, Clerk, Stripe etc.)
• Project structure (folder layouts, module patterns)
• Communication guidelines (Eg -concise answers vs verbose explanations, English or Spanish response language choice)

When to Set Rules

1. Automatic Creation
   • Ideavo Agent automatically generates a baseline rule set using industry-standard best practices.
   • Provides a strong starting point without requiring manual setup.
2. Custom Instructions
   • You can override or extend the defaults by editing rules in chat.
   • Useful for enforcing team-specific conventions or workflows.
3. Project Guidelines
   • Capture organizational standards such as technology stacks, coding standards, or UI/UX standards.
   • Ensures consistency across multiple projects or contributors.

Best Practices for Ideavo Rule Management

1. Start simple - Begin with only your most critical preferences (e.g., language, framework, formatting rules).
2. Iterate and refine - Update rules as you work with the Agent and discover gaps or inefficiencies.
3. Promote reusability - Share effective rule sets across similar projects to avoid duplication.
4. Monitor effectiveness
   • Continuously evaluate how closely the Agent follows your guidelines.
   • Adjust rules if outputs drift from expectations.

Important Notes

• Access restriction: Editing .ideavorules is available only for paid users.
• Persistence: Once defined, rules are consistently applied going forward. Restoring to previous versions will also revert rules.
• Customization: You can update the file anytime to refine coding standards, adjust project context, or enforce new guidelines.