Aider Conventions
https://github.com/Aider-AI/conventions- Category
- Developer Tools
- Rank
- No. 1954Tools index
Previous survey · No. 1832 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Coding
- Interfaces
- Agent Skill / Plugin
- Builder
- aider-ai
- GitHub
- 206 stars
- Date
About
Community-contributed convention files for Aider — drop in to tell your coding agent how to style code for any language/framework.
What it does
Aider Conventions is a library of written operating policies for an AI pair programmer. Each policy can govern architecture, error handling, testing, documentation, dependencies, or formatting. You select a relevant document, place it beside your project, and supply it to Aider as read-only context.
Why it's ranked here
The collection is useful because its entries encode concrete decisions, not vague requests for better code. The supplied material covers Go, Flutter, Next.js, Bash, Moodle plugins, functional programming, and calendar generation. Quality varies, however, and some entries impose narrow technology choices or questionable blanket rules.
What's good
Several documents are unusually actionable. The Bash guidance covers quoting, error output, debug modes, dry runs, naming, and control-flow layout. The calendar policy requires timezone checks and user approval before generation. Flutter guidance clearly separates presentation, controllers, data access, and routing. Each contribution is also expected to explain its intended use.
Tradeoffs
These are community-authored opinions, not automatically safe defaults. The Flutter policy mandates GetX and Dio, while the Next.js policy mandates Material UI. The Go entry prescribes centralized error handling and suggests vectorized operations, choices that may not suit established projects. Some contribution pages link to convention names that differ from the supplied documents, and one folder states a license different from the repository license.
How to use it well
It suits Aider users who want repeatable project rules and are willing to edit them before adoption. Start with the closest domain entry, compare every mandate against your existing architecture, remove conflicts, then load the result as read-only context. It does not replace linters, formatters, tests, security analysis, or human verification of generated output.
Technical notes+
The root README.md describes a copy-based integration: load CONVENTIONS.md with aider --read-only CONVENTIONS.md, or configure .aider.conf.yml with read-only: CONVENTIONS.md. Content is Markdown rather than an executable package or library. Provided entries include golang/CONVENTIONS.md, flutter/CONVENTIONS.md, moodle500/CONVENTIONS.md, nextjs-ts/CONVENTIONS.md, bash-scripts/CONVENTIONS.md, and icalendar-events/CONVENTIONS.md. The golang/README.md and flutter/README.md links name lowercase, suffixed convention files instead of the supplied uppercase paths. LICENSE.txt contains Apache License 2.0, while moodle500/README.md separately states GPL 3.0.
Observed
- Repository license
- Apache License 2.0 in the root license text; the Moodle contribution separately states GPL 3.0.
- Primary content format
- Markdown convention and explanatory documents.
- Installation surface
- Copy a selected convention document into the target project; no package installation is described.
- Interface
- Aider CLI read-only input or Aider YAML configuration.
- Platform scope
- Provided material covers Go, Flutter, Moodle plugins, Next.js with TypeScript, Bash, functional programming, and iCalendar generation.
- Contribution structure
- Contributors are asked to add a subdirectory containing an explanation and a convention document.
Read from README.md, LICENSE.txt, golang/README.md, flutter/README.md, moodle500/README.md, nextjs-ts/README.md, golang/CONVENTIONS.md, bash-scripts/README.md, flutter/CONVENTIONS.md, moodle500/CONVENTIONS.md, nextjs-ts/CONVENTIONS.md, icalendar-events/README.md, bash-scripts/CONVENTIONS.md, icalendar-events/CONVENTIONS.md, functional-programming/README.md.
What it can do
Provide coding style conventions for specific languages
Programming language or framework name → Convention file with styling rules
Configure code formatting rules for AI coding agents
Convention file and target project → Applied code styling configuration
Install language-specific convention files
Convention file from community repository → Ready-to-use coding style configuration
Override default AI coding agent behavior
Custom convention rules and coding agent → Modified agent behavior following specified conventions
Access community-contributed coding standards
Framework or language requirements → Curated convention files from community
Tags
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.