This document discusses the importance of consistency in API design and the need for API style guides. It notes that initially one person may design an API, but over time inconsistencies creep in as more people contribute. This leads to wasted time for both users and designers. The document advocates defining a style guide with clear rules that are discussed, shared, and enforced to maintain consistency across an organization's APIs. It also briefly describes tools that can help automate style guide rule validation.