skills.rest
vh2224
vh2224COMMUNITY
Explore all skills by this author →
GitHub

design-an-interface

Design and compare multiple interface options for modules or APIs.

1|Updated Jul 13, 2026
Search Tags:#api design#software architecture#interface design#module boundaries#trade-off analysis
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill design-an-interface-vh2224
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-an-interface
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/design-an-interface
Command: npx skills add https://github.com/vh2224/forge-executor --skill design-an-interface-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when a module, API, or interface is still ambiguous and the first idea is likely not the best. It forces deliberate exploration of the design space so you can compare fundamentally different shapes before committing.

Core Features & Use Cases

  • Multiple Distinct Designs: Produces three or more genuinely different interface options rather than minor variants.
  • Honest Comparison: Evaluates each design in prose for simplicity, depth, generality, efficiency, and misuse risk.
  • Strong Recommendation: Ends with a clear recommendation or hybrid and records the decision for future implementation.
  • Use Case: Ideal for shaping a new module boundary, redesigning a coupled API, or re-cutting a seam discovered during planning.

Quick Start

Ask for three radically different interface designs for your module, then compare them and recommend the best shape.

Frequently Asked Questions about design-an-interface

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design and compare multiple API interfaces for a new module?▼

API interface design requires generating three or more genuinely different module boundary options, evaluating each in prose for simplicity and misuse risk, then selecting a specific recommended shape with recorded trade-off analysis.

What is the best way to plan module boundaries during a refactor?▼

Planning module boundaries involves re-cutting seams by sequentially exploring fundamentally different interface designs, performing honest trade-off analysis, and capturing a specific recommendation for future implementation.

How does trade-off analysis work when redesigning a coupled API?▼

Trade-off analysis for coupled APIs evaluates multiple distinct interface designs across simplicity, depth, generality, efficiency, and misuse risk, ending with a clear recommendation or hybrid design and a recorded decision.

When should I explore different software architecture designs instead of committing to the first idea?▼

You should explore different software architecture designs when a module or API is still ambiguous, forcing deliberate exploration to compare fundamentally different shapes and evaluate misuse risk before committing.

Does this approach produce minor variants of the same interface or fundamentally different shapes?▼

This approach produces three or more genuinely different interface shapes rather than minor variants, ensuring broad exploration of the design space before making a final recommendation for your API.

Related Skills

Explore More Software Engineering Skills→
AtharvaN16AtharvaN16

design-an-interface

Generate multiple divergent interface designs for a specified module using parallel sub-agents.

Community
Advanced
officechbusinessservices-creatorofficechbusinessservices-creator

improve-codebase-architecture

Identify architectural friction and deepen shallow modules to improve testability.

Community
Advanced
koolerkxkoolerkx

api-and-interface-design

Define stable REST and GraphQL contracts with consistent error semantics.

Community
Intermediate
HermeticOrmusHermeticOrmus
89

rapid-prototyping

Generate interactive UI prototypes using 10-Minute and Storyboard patterns.

Community
Intermediate