Aider Configuration Setup
This skill helps you create and customize `.aider.conf.yml` configuration files for the Aider AI pair programming tool. It covers all available configuration options including model selection, API settings, git integration, UI customization, and workflow preferences.
What This Skill Does
Generates comprehensive Aider configuration files tailored to your development environment and preferences. The configuration file can be placed in your home directory for global settings or at the root of a git repository for project-specific settings.
Instructions
Follow these steps to create an Aider configuration file:
1. Determine Configuration Scope
Ask the user whether this is a global configuration (home directory) or project-specific (git repo root)Identify the target file path: `~/.aider.conf.yml` or `./.aider.conf.yml`2. Gather Core Requirements
Ask the user about their essential preferences:
**Model Selection:**
Which LLM model to use for main chat? (e.g., `claude-3-7-sonnet-20250219`, `gpt-4o`, `codestral/codestral-latest`)Do they need a separate weak model for commit messages/summaries?Do they need a separate editor model?**API Configuration:**
Which API providers are they using? (OpenAI, Anthropic, custom endpoints)Note: API keys should be stored in `.env` files, not in the YAML config**Git Integration:**
Enable auto-commits? (default: true)Enable file watching for AI coding comments? (default: false)Auto-lint after changes? (default: true)Test command to run after changes?**UI Preferences:**
Dark mode or light mode?Code theme preference? (e.g., `github-dark`, `monokai`, `solarized-dark`)Enable streaming responses? (default: true)3. Generate Base Configuration
Create a `.aider.conf.yml` file with the user's specified settings. Include:
Model configuration section with selected modelsGit settings (auto-commits, dirty-commits, file watching)Output settings (dark-mode, code-theme, colors)Comment out optional/advanced settings for user reference4. Add Advanced Options (If Needed)
Based on user requirements, uncomment and configure:
**Repomap Settings:**
`map-tokens`: Control repo map size (0 to disable)`map-refresh`: How often to refresh (auto/always/files/manual)**Cache Settings:**
`cache-prompts`: Enable prompt caching`cache-keepalive-pings`: Keep cache warm**Linting/Testing:**
`lint-cmd`: Specify language-specific lint commands`test-cmd`: Command to run tests`auto-test`: Enable automatic testing**History Files:**
`input-history-file`: Chat input history location`chat-history-file`: Chat history location`llm-history-file`: LLM conversation log**Voice Settings:**
`voice-format`: Audio format (wav/webm/mp3)`voice-language`: ISO 639-1 language code5. Validate Configuration
Ensure YAML syntax is correctVerify that uncommented options have valid valuesConfirm no API keys are in the file (should be in `.env`)Check that file paths are appropriate for the user's OS6. Provide Usage Instructions
Include a comment block at the top of the generated file explaining:
Where to place the file (home directory or git root)How to store API keys in `.env` fileHow to override settings with command-line flagsLink to Aider documentation: https://aider.chat/docs/config/Example Usage
**User Request:** "Create an Aider config for my project using Claude Sonnet with dark mode and auto-commits disabled"
**Generated Configuration:**
```yaml
Aider Configuration File
Place at git repo root or home directory
API keys go in .env file: https://aider.chat/docs/config/dotenv.html
model: claude-3-7-sonnet-20250219
dark-mode: true
code-theme: github-dark
auto-commits: false
watch-files: false
Uncomment to customize:
weak-model: claude-3-5-haiku-20241022
auto-lint: true
test-cmd: pytest
map-tokens: 1024
```
Important Constraints
1. **Never include API keys** in the YAML file - always direct users to use `.env` files
2. **Comment out unused options** rather than deleting them for user reference
3. **Use valid YAML syntax** - strings with special characters need quotes
4. **Respect defaults** - only specify settings that differ from defaults
5. **Platform awareness** - file paths and commands may differ by OS
6. **Model availability** - verify model names are current and accessible
7. **Boolean values** - use lowercase `true`/`false` in YAML
8. **List syntax** - use YAML array format for multi-value options
Notes
The configuration file lists ALL valid Aider configuration entries as referenceSettings can be overridden with command-line flags when running AiderProject-specific configs (git root) take precedence over global configs (home directory)Many settings have sensible defaults and don't need to be specifiedDeprecated options are included for reference but should not be used in new configs