Aider Configuration for Blazor Component Library

This skill provides a production-ready Aider configuration optimized for Blazor component library development. It sets up Aider with architect mode, prompt caching, and comprehensive project documentation access.

What This Configuration Does

Instructions

1. Create the Configuration File

Create a file named `.aider.conf.yml` in the root of your git repository with the following content:

```yaml

##########################################################

Aider Configuration for Blazor Component Library

##########################################################

#################

Model Settings:

Use architect edit format for complex structural changes

architect: true

Specify the model to use for commit messages and summaries

#weak-model: xxx

Specify the model to use for editor tasks

#editor-model: xxx

#################

Cache Settings:

Enable caching of prompts to reduce costs

cache-prompts: true

Number of 5min pings to keep prompt cache warm (optional)

#cache-keepalive-pings: 0

##################

Output Settings:

Use colors suitable for dark terminal background

dark-mode: true

###############

Git Settings:

Disable adding .aider* to .gitignore (manage manually)

gitignore: false

Enable auto-commit of LLM changes

#auto-commits: true

Enable commits when repo is dirty

#dirty-commits: true

########################

Fixing and committing:

Enable automatic linting after changes

#auto-lint: true

Specify lint commands for C#

#lint-cmd: "csharp: dotnet format --verify-no-changes"

Enable automatic testing after changes

#auto-test: false

#################

Other Settings:

Specify read-only files for AI context

read:

- .editorconfig

- README.md

- .ai/index.md

- .ai/ai-instructions.md

- .ai/csharp-coding-standards.md

- .ai/dotnet-conventions.md

- .ai/environment.md

- .ai/project-structure.md

- .ai/references.md

- .ai/shell-commands.md

- .ai/tools.md

Enable shell command suggestions

#suggest-shell-commands: true

```

2. Create Supporting Documentation Structure

For optimal AI context, create an `.ai/` directory with these documentation files:

```bash

mkdir -p .ai

```

Create these files in `.ai/` directory:

3. Set Up API Keys

Create a `.env` file in your git root (not tracked in version control):

```bash

OpenAI API Key

OPENAI_API_KEY=your-openai-key-here

Anthropic API Key (for Claude models)

ANTHROPIC_API_KEY=your-anthropic-key-here

```

4. Usage Examples

**Start Aider with specific files:**

```bash

aider src/Components/Button.razor src/Components/Button.razor.cs

```

**Start Aider with all dirty files:**

```bash

aider

```

**Generate a commit for pending changes:**

```bash

aider --commit

```

**Run with a single message:**

```bash

aider --message "Add a new Icon component with size variants"

```

**Lint and fix files:**

```bash

aider --lint src/Components/*.cs

```

5. Key Features Explained

**Architect Mode:**

**Prompt Caching:**

**Read-Only Files:**

Customization Options

**Change the AI model:**

```yaml

model: claude-3-5-sonnet-20240620

or

model: gpt-4o

```

**Enable automatic testing:**

```yaml

auto-test: true

test-cmd: "dotnet test"

```

**Add C# linting:**

```yaml

auto-lint: true

lint-cmd: "csharp: dotnet format --verify-no-changes"

```

**Adjust repository map size:**

```yaml

map-tokens: 2048 # Default is 1024

```

Important Notes

For Blazor-Specific Workflows

This configuration is optimized for:

The read-only documentation files provide the AI with context about your project's conventions without risking modifications to those standards.