design-an-interface

To design an API interface effectively when multiple viable options exist, generate three radically different interface designs for the module, compare their control flows in prose, and synthesize a final recommendation to guide implementation. This prevents early design lock-in.

Compare different interface designs for a new module by generating three radically different prototypes with diverse interaction patterns, evaluating the divergent approaches against your requirements, and producing a recommendation or hybrid shape to guide implementation.

You need to evaluate divergent approaches for API boundary refactoring when multiple viable options exist for the module shape. Generating three radically different interface designs exposes diverse control flows and surfaces clear interface expectations early before committing to implementation.

Yes, you can separate interface design from implementation by producing three radically different interface designs for the module or API, evaluating the divergent approaches in prose, and documenting a preferred shape to guide the subsequent implementation phase.

Generating multiple interface prototypes reduces design lock-in by producing three radically different interface designs for a single module or API, exposing diverse control flows, and synthesizing a recommended shape that surfaces clear interface expectations early in the planning phase.

Synthesizing a single recommended interface shape limits the final API to one preferred design or hybrid, which may not perfectly capture all viable control flows, but it effectively reduces design lock-in and guides implementation by documenting the preferred shape.