Aider Configuration for Motia Projects

Configure Aider AI coding assistant for Motia framework development with proper context files and documentation references.

Overview

This skill sets up Aider with optimal configuration for working on Motia projects. It ensures the AI has access to project overview, architecture guides, and framework-specific documentation while maintaining flexibility for selective context loading.

Instructions

When setting up Aider for a Motia project, follow these steps:

1. **Create the base `.aider.conf.yml` file** in the project root with the following structure:

```yaml

Aider Configuration for Motia Projects

https://aider.chat/docs/config.html

Read AGENTS.md for project overview and guide references

read:

- AGENTS.md

# Uncomment specific guides as needed for more context:

# - .cursor/rules/motia/api-steps.mdc

# - .cursor/rules/motia/event-steps.mdc

# - .cursor/rules/motia/cron-steps.mdc

# - .cursor/rules/motia/state-management.mdc

# - .cursor/rules/motia/middlewares.mdc

# - .cursor/rules/motia/realtime-streaming.mdc

# - .cursor/rules/motia/virtual-steps.mdc

# - .cursor/rules/motia/ui-steps.mdc

# - .cursor/architecture/architecture.mdc

# - .cursor/architecture/error-handling.mdc

Note: AGENTS.md references all detailed guides in .cursor/rules/

The AI will read those guides when needed based on AGENTS.md instructions

Auto-commit changes (optional, uncomment to enable)

auto-commits: true

Model selection (uncomment your preferred model)

model: gpt-4

model: claude-3-5-sonnet-20241022

Additional context files (optional)

read:

- config.yml

- package.json

```

2. **Verify the `AGENTS.md` file exists** at the project root. This file should contain:

- Project overview and architecture

- References to detailed guides in `.cursor/rules/`

- Instructions for the AI on when to consult specific documentation

3. **Customize context loading based on the task**:

- For API development: Uncomment `api-steps.mdc`

- For event handling: Uncomment `event-steps.mdc`

- For scheduled jobs: Uncomment `cron-steps.mdc`

- For state management: Uncomment `state-management.mdc`

- For middleware development: Uncomment `middlewares.mdc`

- For real-time features: Uncomment `realtime-streaming.mdc`

- For virtual steps: Uncomment `virtual-steps.mdc`

- For UI components: Uncomment `ui-steps.mdc`

- For architecture review: Uncomment `architecture.mdc` and `error-handling.mdc`

4. **Configure optional settings**:

- Enable `auto-commits: true` if you want Aider to automatically commit changes

- Select your preferred model by uncommenting the appropriate `model:` line

- Add project-specific context files (e.g., `config.yml`, `package.json`) to the `read:` list if needed

5. **Validate the configuration**:

- Run `aider --check-config` to verify the configuration is valid

- Ensure all referenced files in the `read:` list exist in the project

6. **Start Aider with the configuration**:

- Run `aider` from the project root

- The configuration will be automatically loaded

Context Management Strategy

The configuration uses a layered approach:

This approach balances comprehensive context with token efficiency.

Example Usage

For API Development

Uncomment `.cursor/rules/motia/api-steps.mdc` in the configuration, then run:

```bash

aider

```

Ask: "Create a new API endpoint for user registration"

For Real-time Features

Uncomment `.cursor/rules/motia/realtime-streaming.mdc`, then run:

```bash

aider

```

Ask: "Implement real-time chat streaming with Server-Sent Events"

For Architecture Review

Uncomment both `.cursor/architecture/architecture.mdc` and `.cursor/architecture/error-handling.mdc`, then run:

```bash

aider

```

Ask: "Review the current error handling strategy and suggest improvements"

Important Notes

Constraints