design-an-interface

Generate three interface designs with signatures, usage examples, and trade-offs.

12|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/qdzsh/gsd-revamp --skill design-an-interface-qdzsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-an-interface
Source: https://github.com/qdzsh/gsd-revamp/tree/main/src/resources/skills/design-an-interface
Command: npx skills add https://github.com/qdzsh/gsd-revamp --skill design-an-interface-qdzsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing software interfaces is hard because there are often multiple viable shapes, and choosing the best one requires surfacing the design space and evaluating trade-offs.

Core Features & Use Cases

  • Generate three radically different interface designs for a single module or API.
  • Present the designs with contrasting shapes, exposure, and control to help decide where to invest implementation effort.
  • Capture a final recommendation and rationale for future reference in project records.

Quick Start

Ask for three radically different interface designs for a module and a final recommendation.

Frequently Asked Questions about design-an-interface

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

FAQPage Schema
How do I evaluate different API design options for a new module?

Evaluating API design options involves generating three radically different interface designs with contrasting shapes and controls. This surfaces the design space by presenting explicit trade-offs for each option to help you decide where to invest implementation effort.

What is the best way to explore the design space for an unclear software interface?

Exploring the design space for an unclear software interface means creating multiple radically different designs for a single module. Each design includes an interface signature, a usage example, and explicit trade-offs for a final recommendation.

How do I document interface design trade-offs and record the final decision?

Documenting interface design trade-offs involves capturing each design's signature, usage example, and explicit trade-offs. The process concludes by recording a final recommendation and rationale for future reference in project records.

Can I generate multiple UX interface designs for a single API before planning implementation?

Yes, you can generate three radically different UX interface designs for a single API during planning sessions. This helps evaluate multiple design options and highlights where to invest implementation effort before coding begins.

When should I not use a radical design approach for interface planning?

You should avoid radical interface design approaches when the API shape is already clear and only minor adjustments are needed. This method targets planning sessions where the interface shape is unclear and multiple viable options require evaluation.