interface-design

To design a minimal interface, identify the consumer need first and draft a contract that captures required behavior while keeping the surface area small. This consumer-first approach maximizes substitution and testability without unnecessary abstraction.

Consumer-first interface design defines abstractions from the perspective of the code consuming them, rather than the provider. Apply this approach whenever you define a protocol, trait, abstract class, or any new type boundary between components.

Yes, you can apply Go-derived interface design principles across Go, Clojure, Java, Kotlin, TypeScript, and Python. The skill translates core concepts into language-specific idioms to guide concrete outcomes in each context.

The best way to review an existing abstraction is to check for consumer ownership, minimal surface area, and any data leakage. Evaluate whether the interface avoids unneeded abstraction and truly supports swapping implementations.

Your TypeScript interface likely increases cognitive load because it exposes a large surface area or introduces unneeded abstraction. Designing a minimal, consumer-facing contract reduces maintenance by capturing only the required behavior.

You should avoid using an abstract class or any abstraction boundary when there is no genuine need to swap implementations or when it causes data leakage. Introduce a new type boundary only if it serves a concrete consumer need.