Interface Design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill interface-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/code-quality/skills/interface-design ~/.claude/skills/interface-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Interface Design Creating contracts that are precise, minimal, and business-focused. ## Context You are helping the engineer design interfaces. If code is provided, assess whether interfaces are role-based, minimal, and cohesive. A good interface is a promise to clients. ## Domain Context - **Role-Based**: An interface should represent one role; avoid "fat" interfaces - **Minimal**: Include only methods the client actually calls; every method is a burden - **Cohesive**: All methods serve the same purpose; unrelated methods signal bad design - **Explicit Contracts**: Clients know what to expect and what can fail - **Change Isolation**: Changes to implementation don't ripple to clients ## Instructions 1. **Identify Clients**: Who uses this interface? What do they actually need? 2. **List Required Methods**: Only methods clients call; omit implementation details 3. **Check Cohesion**: Do all methods work toward the same goal? If not, split the interface 4. **Verify Minimal**: Can you remove any method without breaking clients? If yes, remove it 5. **Document Contracts**: What do methods guarantee? What can fail? Use structured comments 6. **Check Mutability**: Should some methods be on a separate "mutator" interface? 7. **Review Generics**: Do generic parameters complicate the contract? If yes, simplify 8. **Plan Evolution**: How will this interface change? Make room for extension without breaking ## Anti-Patterns
Details
- Skill name
interface-design- Repository
- sethdford/claude-skills
- Path
engineer/code-quality/skills/interface-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Interface Design skill do?
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
How do I install the Interface Design skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Interface Design popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Jobs to Be Done
48sethdford/claude-skills
Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.
Input Validation Patterns
48sethdford/claude-skills
Design and implement input validation patterns (whitelisting, boundary checks, type validation) to prevent injection and buffer overflow attacks.
Lessons Learned
48sethdford/claude-skills
Conduct post-incident reviews to document lessons learned and implement process improvements preventing recurrence.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.