# Agent Rules





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 [#how-to-configure-rules]

<Steps>
  <Step>
    Open the 

    **Code Editor**

     in your project.
  </Step>

  <Step>
    Navigate to the 

    `AGENTS.md`

     file (create it if it doesn't exist).
  </Step>

  <Step>
    Define your preferences and constraints — coding style, technology stack,
    communication verbosity, etc.
  </Step>

  <Step>
    Save. The agent automatically loads and applies these rules to your current
    and future sessions.
  </Step>
</Steps>

<Callout type="info">
  Older projects use a `.ideavorules` file. If neither exists, create a new
  `AGENTS.md` file.
</Callout>

### What Rules Can Cover [#what-rules-can-cover]

<Cards>
  <Card title="Coding style" icon="<MdOutlineCode />" description="Tabs vs spaces, naming conventions, comment density." />

  <Card title="Framework & technology choices" icon="<FaReact />" description="Supabase, Firebase, Clerk, Stripe, and other preferred tools." />

  <Card title="Project structure" icon="<FaFolderOpen />" description="Folder layouts, module patterns, file organization." />

  <Card title="Communication style" icon="<RiSpeakAiLine />" description="Concise vs verbose explanations, preferred response language." />
</Cards>

### When to Set Rules [#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 [#best-practices]

1. **Start simple** — Begin with only your most critical preferences (language, framework, formatting)
2. **Iterate and refine** — Update rules as you 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 and adjust if outputs drift

<Callout type="info">
  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.
</Callout>
