Design an interface
Explore at least three materially different designs for a module, library, command, or service interface, compare their tradeoffs, and recommend one. Use when interface shape or module boundaries are the hard part.From its SKILL.md
npx -y skills add kevinb361/agent-skills --skill design-an-interfaceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.0 KB, 141 tokens by cl100k_base, as published. Nobody here has run it
Design an interface
Do not stop at the first plausible shape.
- Identify consumers, invariants, failure modes, lifecycle, and likely change axes.
- Produce at least three materially different designs. Differences must involve ownership, state, abstraction boundary, or misuse resistance—not renamed methods.
- Show a small usage example for each.
- Compare complexity, coupling, testability, observability, compatibility, misuse resistance, and migration cost.
- Recommend a default and explain why it fits the actual constraints.
- Record unresolved decisions that block implementation.
Favor deep modules: simple consumer-facing contracts that hide justified complexity. Avoid speculative generality and configuration knobs without a demonstrated consumer.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.