design-an-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
88
83%
Does it follow best practices?
Impact
98%
1.36xAverage score across 3 eval scenarios
—
The risk profile of this skill
Evaluation results
96%
56%Configuration Library API Design
Structured comparison and synthesis
Interface simplicity dimension
20%
100%
General-purpose vs specialized
30%
100%
Implementation efficiency
10%
100%
Depth dimension
0%
100%
Correct use vs misuse
0%
100%
Prose trade-offs
10%
100%
Divergence highlighted
30%
60%
Synthesis section present
100%
100%
Primary use case fit
100%
100%
Combining elements
100%
100%
100%
19%Job Queue Module Interface Design
Requirements-first design, no implementation
Requirements section first
100%
100%
Problem stated
70%
100%
Callers identified
20%
100%
Key operations listed
100%
100%
Constraints mentioned
100%
100%
Hidden vs exposed
20%
100%
No working implementation
100%
100%
No effort-based evaluation
100%
100%
At least 3 designs
100%
100%
Distinct design shapes
100%
100%
100%
3%Retry Module Interface Design
Parallel sub-agent design generation
At least 3 designs
100%
100%
Interface signatures
100%
100%
Usage examples
100%
100%
Hides complexity
70%
100%
Trade-offs per design
100%
100%
Radically different approaches
100%
100%
Minimal-method design
100%
100%
Maximum-flexibility design
100%
100%
Common-case design
100%
100%
Process documentation
100%
100%
- Repository
- SnowingFox/ai-skills
- Commit
d6882ad
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.