design-an-interface

Generate multiple interface designs for APIs, SDKs, CLIs, or UI components with tradeoffs.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill design-an-interface-zaeem-rafiq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-an-interface
Source: https://github.com/zaeem-rafiq/tatheer-swift-sdk/tree/main/.claude/skills/dev-workflow/design-an-interface
Command: npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill design-an-interface-zaeem-rafiq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to decide on the best interface design for APIs, SDKs, CLIs, or UI components because options are rarely compared side-by-side. This Skill generates three or more radically different interface designs to surface tradeoffs and enable informed choices.

Core Features & Use Cases

  • Generate multiple viable interface designs for a given boundary or boundary condition (API, SDK, CLI, UI component).
  • Explicitly evaluate tradeoffs across granularity, control, coupling, flexibility, and discoverability.
  • Use during early architecture discussions to prevent locked-in decisions and accelerate decision making.

Quick Start

Provide three radically different interface designs for an API, module, or SDK and briefly summarize the tradeoffs.

Frequently Asked Questions about design-an-interface

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

FAQPage Schema
How do I compare multiple API designs to evaluate tradeoffs before committing to an architecture?

Generate three or more radically different API interface designs to surface tradeoffs across granularity, control, and coupling early. This approach delivers distinct designs with clear rationale to support informed architecture decisions.

What is the best way to explore SDK boundary options during early architecture discussions?

Exploring SDK boundary options involves generating multiple radically different interface designs to reveal tradeoffs early. This prevents locked-in decisions by explicitly evaluating flexibility and discoverability to accelerate architecture choices.

Can I use this to generate CLI interface options and analyze control versus flexibility tradeoffs?

Yes, you can generate three or more radically different CLI interface designs to analyze tradeoffs. It explicitly evaluates control, flexibility, and discoverability to support clear decisions on command boundaries and architecture.

How do I evaluate UI component architecture boundaries when my team disagrees on the interface design?

Evaluating UI component boundaries involves generating multiple radically different interface designs to compare options side-by-side. This surfaces distinct tradeoffs and rationale, preventing locked-in decisions while accelerating team alignment.

When do I need to generate multiple interface designs instead of picking a single API architecture?

You need multiple interface designs when deciding on architecture or boundaries for APIs, SDKs, CLIs, or UI components. Generating three or more options reveals tradeoffs early, preventing locked-in decisions and accelerating informed choices.

Does this approach work for generating interface designs without requiring specific frameworks or dependencies?

Yes, generating interface designs works without specific dependencies. It applies to APIs, SDKs, CLIs, or UI components when deciding on architecture, delivering distinct designs with rationale and clear tradeoffs to support design decisions.