design-an-interface

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

Updated May 7, 2026
One-click install
npx skills add https://github.com/hgxszhj/mattpocock_skills --skill design-an-interface-hgxszhj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-an-interface
Source: https://github.com/hgxszhj/mattpocock_skills/tree/main/skills/deprecated/design-an-interface
Command: npx skills add https://github.com/hgxszhj/mattpocock_skills --skill design-an-interface-hgxszhj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate multiple radically different interface designs for a module using parallel sub-agents to accelerate API design and comparison.

Core Features & Use Cases

  • Spawn 3+ sub-agents simultaneously to produce radically different interface designs.
  • Capture interface signatures, usage examples, and what each design hides internally.
  • Facilitate side-by-side evaluation and synthesis to choose the best approach.

Quick Start

Launch the design-an-interface skill to generate three radically different interface designs for your module and compare them.

Frequently Asked Questions about design-an-interface

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

FAQPage Schema
How do I generate multiple API interface designs for comparison?

You can generate multiple API interface designs by spawning 3+ parallel sub-agents that produce radically different module shapes, capturing signatures, usage examples, and hidden internals for side-by-side evaluation.

What is the best way to compare different module architecture options?

Comparing module architecture options is best done by generating radically different interface designs in parallel, then performing a structured evaluation and synthesis to choose the best approach.

Can I use multi-agent parallelism to explore API design decisions?

Yes, you can use multi-agent parallelism to explore API design decisions by coordinating 3+ sub-agents to simultaneously generate diverse interface options and capture what each design hides internally.

How do I evaluate which interface design hides the right implementation details?

You evaluate interface designs by comparing the captured signatures and usage examples from each parallel sub-agent, analyzing what each module shape hides internally to synthesize the best approach.

When should I use parallel sub-agents for interface generation?

You should use parallel sub-agents for interface generation when you need to explore diverse API design options rapidly and want a structured evaluation to compare radically different module shapes side-by-side.