Aider Configuration Template

Generate a comprehensive `.aider.conf.yml` configuration file for the Aider AI pair programming tool.

What This Skill Does

Creates a fully-commented YAML configuration file that can be placed in your home directory or git repository root to customize Aider's behavior. The configuration covers all aspects of Aider including model selection, API settings, git integration, output styling, testing/linting automation, and more.

Instructions

When the user requests an Aider configuration file:

1. **Understand Requirements**

- Ask which aspects they want to configure (models, git, styling, testing, etc.)

- Determine if they need a minimal config or comprehensive template

- Ask about their preferred models (Claude, GPT-4, DeepSeek, etc.)

- Ask if they use specific API providers or custom endpoints

2. **Generate Configuration**

- Start with the YAML structure: `##########` section headers

- Include commented-out options with `#option: xxx` format

- For array options, show both single and multiple value syntax

- Group related settings under clear section headers

- Add helpful comments explaining what each option does

3. **Key Sections to Include**

- **Main Model**: Primary LLM for coding tasks

- **API Keys**: OpenAI, Anthropic, custom providers

- **Model Settings**: Edit format, architect mode, weak/editor models

- **Cache Settings**: Prompt caching and keepalive

- **Repomap**: Token limits and refresh behavior

- **History Files**: Input/chat/LLM history locations

- **Output Settings**: Colors, themes, streaming, diffs

- **Git Settings**: Auto-commits, attribution, hooks

- **Fixing/Testing**: Lint commands, test commands, auto-fix

- **Voice Settings**: Audio format, language, input device

- **Other**: File arguments, encoding, notifications

4. **Provide Usage Guidance**

- Explain where to place the file (home dir or repo root)

- Note that only OpenAI/Anthropic keys go in YAML (others use .env)

- Mention that multiple values use list syntax

- Suggest starting with a minimal config and expanding as needed

5. **Best Practices**

- Use architect mode (`--architect: true`) for complex refactoring

- Enable auto-linting (`--auto-lint: true`) for cleaner commits

- Set reasonable `--map-tokens` (e.g., 2048-4096) for large repos

- Configure dark/light mode for your terminal

- Use `--attribute-co-authored-by: true` for commit attribution

Example Usage

**User**: "Create an Aider config for Claude Sonnet with auto-linting and dark mode"

**Assistant**:

```yaml

Main model

model: anthropic/claude-3-7-sonnet-20250219

Output settings

dark-mode: true

pretty: true

stream: true

Git settings

auto-commits: true

attribute-co-authored-by: true

Linting

auto-lint: true

lint-cmd:

- "python: ruff check --fix"

- "javascript: eslint --fix"

Repomap

map-tokens: 2048

```

**User**: "I need a full template with all options"

**Assistant**: [Generate complete template with all sections commented out]

Important Notes

Constraints