Convention Over Configuration

Convention over configuration is a software design paradigm that seeks to reduce the number of decisions a developer has to make without sacrificing flexibility. The framework or platform ships with sensible defaults — naming patterns, directory layouts, wiring — so a developer only writes configuration for the parts that deviate from the norm. Popularized by Ruby on Rails, the idea now shapes how frameworks, build tools, and API platforms are designed.

• Sensible defaults - The common case works with little or no configuration, so most projects start productive on day one.
• Configure only the exceptions - Explicit settings are reserved for behavior that departs from the established convention.
• Predictable structure - Shared conventions make codebases legible to newcomers and tools alike, because things live where you expect.
• Less boilerplate - Fewer knobs to set means fewer opportunities for misconfiguration and drift.

In API design, convention over configuration shows up as predictable resource naming, standard status codes, well-known file locations, and default behaviors that let consumers integrate without reading every line of documentation. It is the same instinct behind OpenAPI conventions and governance rulesets — encoding the expected shape of an API as a default so that only intentional deviations require justification. For AI agents integrating with APIs, strong conventions are what make a service predictable enough to consume without human hand-holding.