design-an-interface

You can design multiple API interfaces by generating three or more radically different module shapes using parallel sub-agents. This process overcomes first-draft bias by comparing simplicity, flexibility, implementation efficiency, and correct-use ergonomics to select the optimal interface.

To avoid first-draft bias in software architecture, use a design-it-twice workflow. This approach forces parallel generation of distinct interface constraints and structured outputs, enabling a prose-based comparison of trade-offs before settling on a module shape.

You compare module shapes by evaluating each option against structured criteria. The comparison emphasizes simplicity, flexibility, implementation efficiency, depth, and correct-use ergonomics to determine the most suitable API design for your constraints.

You generate distinct API design options by using parallel sub-agents to produce radically different interface shapes for the same module goal. Each option includes a signature, usage example, hidden complexity, and trade-offs for consistent evaluation.

You should explore interface options when designing a clean module interface that must balance simplicity, flexibility, and implementation fit. Exploring multiple alternatives prevents premature commitment and improves overall API shape decisions.

API shapes are evaluated using criteria that emphasize simplicity, flexibility, implementation efficiency, depth, and correct-use ergonomics. This structured comparison highlights hidden complexities and trade-offs to synthesize the most suitable module design.