design-an-interface

Interface design exploration requires framing the problem, identifying callers, and enumerating constraints before generation. This discovery process ensures diverse design options and supports presenting divergent designs with explicit trade-offs.

The best way to compare module interface options is to dispatch parallel Explore agents to produce distinct interface contracts. Candidates are presented sequentially to highlight hidden trade-offs and synthesize a winning contract fitting dominant call sites.

Yes, you can generate parallel interface designs for early-stage module architecture. This approach applies to tasks where a new surface is being shaped or options must be compared across several candidates to prevent locking in a single contract too early.

Yes, you need to run discovery before generating interface contracts. The workflow explicitly requires framing the problem, identifying callers, and enumerating constraints before dispatching Explore agents to produce distinct interface designs.

Generating a single interface contract too early causes design problems by locking in a specific shape without comparing alternatives. Exploring multiple candidates reveals hidden trade-offs across depth and ease of correct use, ensuring a more robust module design.