Agent skill · design visual · aiskillstore
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".
Why this skill is useful
Generates multiple distinct interface designs using parallel sub-agents, providing unique perspectives and trade-offs that the AI wouldn't reliably create on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Design an Interface Based on "Design It Twice" from "A Philosophy of Software Design": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare. Workflow 1. Gather Requirements Before designing, understand: [ ] What problem does this module solve? [ ] Who are the callers? (other modules, external users, tests) [ ] What are the key operations? [ ] Any constraints? (performance, compatibility, existing patterns) [ ] What should be hidden inside vs exposed? Ask: "What does this module need to do? Who will use it?" 2. Generate Designs (Parallel Sub-Agents) Spawn 3+ sub-agents simultaneously using Task tool. Each must produce a radically different approach. 3. Present Designs Show each design with: 1. Interface signature - types, methods, params 2. Usage examples - how callers actually use it in practice 3. What it hides - complexity kept internal Present designs sequentially so user can absorb each approach before comparison. 4. Compare Designs After showing all designs, compare them on: Interface simplicity: fewer methods, simpler params General-purpose vs specialized: flexibility vs focus Implementation efficiency: does shape allow efficient internals? Depth: small interface hiding significant complexity (good) vs large interface with thin implementation (bad) Ease of correct use vs ease of misuse Discuss trade-offs in prose, not tables. Highlight where designs diverge most. 5. Synthesize Often the best design combines insights from multiple options. Ask: "Which design best fits your primary use case?" "Any elements from other designs worth incorporating?" Evaluation Criteria From "A Philosophy of Software Design": Interface simplicity: Fewer methods, simpler params = easier to learn and use correctly. General-purpose: Can handle future use cases without changes. But beware over-generalization. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/design-an-interface