New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Design An Interface

by fossasia in fossasia/eventyay-interpretation

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

Apache-2.0Auto-check passedBackend & APIs

Install Design An Interface

skills CLI
$ npx skills add fossasia/eventyay-interpretation --skill design-an-interface -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fossasia/eventyay-interpretation design-an-interface --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/design-an-interface .claude/skills/design-an-interface && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-an-interface
GitHub stars
1.6k
Used in
9 other repos
Token cost
~842 tokens
SKILL.md length
323 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 5 steps: Gather Requirements → Generate Designs (Parallel Sub-Agents) → Present Designs → …
  • User wants to design an API
  • SKILL.md covers Workflow, Evaluation Criteria and Anti-Patterns
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design An Interface is an agent skill from fossasia/eventyay-interpretation. 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".

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering API design and Subagents. The repository describes itself as: A plugin for live interpretation of video streams. The licence is Apache-2.0.

When your agent uses it

  • User wants to design an API
  • Explore interface options
  • Compare module shapes
  • Mentions design it twice

Example prompts

  • “design it twice”
  • “/design-an-interface”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather Requirements
  2. Generate Designs (Parallel Sub-Agents)
  3. Present Designs
  4. Compare Designs
  5. Synthesize

What it can do on your machine

Read from SKILL.md and the folder at commit 1ca0139. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design An Interface loads about 842 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 323 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~842

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fossasia/eventyay-interpretation at commit 1ca0139, republished under its Apache-2.0 licence (© fossasia). 323 words, ~842 tokens.

Download SKILL.mdSave it as .claude/skills/design-an-interface/SKILL.md (or your agent's skills folder).
name
design-an-interface
description
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".

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.

Prompt template for each sub-agent:

Design an interface for: [module description]

Requirements: [gathered requirements]

Constraints for this design: [assign a different constraint to each agent]
- Agent 1: "Minimize method count - aim for 1-3 methods max"
- Agent 2: "Maximize flexibility - support many use cases"
- Agent 3: "Optimize for the most common case"
- Agent 4: "Take inspiration from [specific paradigm/library]"

Output format:
1. Interface signature (types/methods)
2. Usage example (how caller uses it)
3. What this design hides internally
4. Trade-offs of this 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.

Implementation efficiency: Does interface shape allow efficient implementation? Or force awkward internals?

Depth: Small interface hiding significant complexity = deep module (good). Large interface with thin implementation = shallow module (avoid).

Anti-Patterns

  • Don't let sub-agents produce similar designs - enforce radical difference
  • Don't skip comparison - the value is in contrast
  • Don't implement - this is purely about interface shape
  • Don't evaluate based on implementation effort

© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/design-an-interface of fossasia/eventyay-interpretation.

Open the folder on GitHubat commit 1ca0139

Used in 10 other repositories

We found 13 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 9 other GitHub owners. This page covers the copy in fossasia/eventyay-interpretation, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Design An Interface next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design An Interface compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design An Interface this skillfossasia/eventyay-interpretation1.6k9 repos~842Automated safety check: PassApache-2.0
Design Interfacedanielvm-git/bigpowers256—~914Automated safety check: PassMIT
Feature TrackingJunsW/feature-track108—~339Automated safety check: PassMIT
Auditaustintgriffith/ethskills294—~829Automated safety check: PassNone
Spec Contract Compliance Reviewbbartling/open-fdd172—~1.4kAutomated safety check: PassCustom licence
API DesignerJeffallan/claude-skills12k2 repos~2kAutomated safety check: PassMIT

Similar skills

  • Design Interface

    danielvm-git/bigpowers

    Generate multiple radically different interface designs for a module using parallel sub-agents, then compare trade-offs.

    256 GitHub stars~914 tokensUpdated 15 days ago
    Backend & APIsAuto-check passed

  • Feature Tracking

    JunsW/feature-track

    Maintain portable Feature Track docs for project features. An agent skill from JunsW/feature-track.

    108 GitHub stars~339 tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed

  • Audit

    austintgriffith/ethskills

    Deep EVM smart contract security audit system. An agent skill from austintgriffith/ethskills.

    294 GitHub stars~829 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Spec Contract Compliance Review

    bbartling/open-fdd

    A skill your agent uses to compare any codebase against a specification, API contract, protocol, policy, RFC, security baseline, or product requirements document.

    172 GitHub stars~1.4k tokensUpdated today
    Legal & ComplianceAuto-check passed

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 2 repos~2k tokens
    Backend & APIsAuto-check passed

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    158 GitHub starsUsed in 17 repos~4k tokens
    Backend & APIsAuto-check passed

More from fossasia/eventyay-interpretation

All 41 skills in this repo

  • Git Guardrails Claude Code

    fossasia/eventyay-interpretation

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.

    1.6k GitHub starsUsed in 12 repos~578 tokens
    Auto-check passed

  • Codebase Design

    fossasia/eventyay-interpretation

    Shared vocabulary for designing deep modules. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 35 repos~1.5k tokens
    Auto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 31 repos~2.1k tokens
    Auto-check passed

  • Domain Modeling

    fossasia/eventyay-interpretation

    Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 29 repos~821 tokens
    Auto-check passed

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Auto-check passed

  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Auto-check: warnings

Categories

Questions about Design An Interface

What does Design An Interface do?

Generate multiple radically different interface designs for a module using parallel sub-agents. Design An Interface is an agent skill from fossasia/eventyay-interpretation. Generate multiple radically different interface designs for a module using parallel sub-agents.

When should I use Design An Interface?

Design An Interface fits situations like: user wants to design an API; explore interface options; compare module shapes; mentions design it twice.

How do I install Design An Interface in Claude Code?

Run `npx skills add fossasia/eventyay-interpretation --skill design-an-interface -a claude-code`. Or copy the skill folder (.agents/skills/design-an-interface in fossasia/eventyay-interpretation) into .claude/skills/design-an-interface in your project. Claude Code loads it when a task matches its description.

How do I install Design An Interface in Codex?

Run `npx skills add fossasia/eventyay-interpretation --skill design-an-interface -a codex`. Or copy the skill folder (.agents/skills/design-an-interface in fossasia/eventyay-interpretation) into .agents/skills/design-an-interface in your project. Codex loads it when a task matches its description.

Can I use Design An Interface in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay-interpretation --skill design-an-interface -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-an-interface, .gemini/skills/design-an-interface, .github/skills/design-an-interface and .opencode/skills/design-an-interface in your project.

What does Design An Interface need to run?

SKILL.md names no scripts, command-line tools or credentials: Design An Interface is instructions for the agent only.

Does Design An Interface access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design An Interface safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design An Interface use?

Design An Interface is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design An Interface use?

About 842 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design An Interface?

Skills that share tags, products or a category with Design An Interface: Design Interface (danielvm-git/bigpowers, 256 stars), Feature Tracking (JunsW/feature-track, 108 stars), Audit (austintgriffith/ethskills, 294 stars) and Spec Contract Compliance Review (bbartling/open-fdd, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design An Interface?

fossasia (a GitHub organization) maintains it in fossasia/eventyay-interpretation, which has 1,552 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 5, 2026.

Source: fossasia/eventyay-interpretation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.