design-an-interface

Parallel interface design generates multiple radically different API shapes simultaneously to avoid overfitting to a single approach. It surfaces diverse architectural options and presents a structured comparison of trade-offs to support early development decision making.

To compare API design options, coordinate 3+ sub-agents to generate radically different designs in parallel. Each design presents its interface signature, usage pattern, and internal abstractions, which are then evaluated across interface simplicity and flexibility.

You should evaluate multiple design patterns when defining an API, library, or module boundary during early development. This prevents architectural lock-in by forcing radical diversity and synthesizing a recommended posture from distinct design options.

Yes, you can generate radically different interface signatures automatically. By providing a module description, the workflow uses sub-agents to enforce diversity and outputs structured comparisons of interface signatures and internal abstractions without manual brainstorming.

The best way to explore API shapes is to run a design-it-twice workflow. This approach gathers requirements and constraints, generates three or more radically different designs in parallel, and synthesizes a recommended posture by integrating insights from all options.