Agent Rules
Configure the Ideavo agent's behavior, coding style, and communication preferences via the AGENTS.md file in your project.
The Ideavo Agent can be configured to align with your project requirements. Rules define how the agent behaves, writes code, and interacts within a project.
How to Configure Rules
AGENTS.md file (create it if it doesn't exist).Define your preferences and constraints — coding style, technology stack, communication verbosity, etc.
Save. The agent automatically loads and applies these rules to your current and future sessions.
Older projects use a .ideavorules file. If neither exists, create a new
AGENTS.md file.
What Rules Can Cover
Coding style
Tabs vs spaces, naming conventions, comment density.
Framework & technology choices
Supabase, Firebase, Clerk, Stripe, and other preferred tools.
Project structure
Folder layouts, module patterns, file organization.
Communication style
Concise vs verbose explanations, preferred response language.
When to Set Rules
- Automatic creation — Ideavo automatically generates a baseline rule set using industry-standard best practices, giving you a strong starting point without manual setup
- Custom instructions — Override or extend defaults by editing rules in chat; useful for team-specific conventions
- Project guidelines — Capture organizational standards such as technology stacks, coding standards, or UI/UX requirements for consistency across contributors
Best Practices
- Start simple — Begin with only your most critical preferences (language, framework, formatting)
- Iterate and refine — Update rules as you discover gaps or inefficiencies
- Promote reusability — Share effective rule sets across similar projects to avoid duplication
- Monitor effectiveness — Continuously evaluate how closely the agent follows your guidelines and adjust if outputs drift
Rules are persistent — once defined, they are applied consistently going forward. Restoring to a previous version will also revert rules to that version's state.