design

Analyze code, component, and API design quality for structural issues.

7|3|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/yzavyas/claude-1337 --skill design-yzavyas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/yzavyas/claude-1337/tree/main/plugins/arch-guild/skills/design
Command: npx skills add https://github.com/yzavyas/claude-1337 --skill design-yzavyas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides engineers and reviewers to evaluate code, component, and API design quality, helping teams identify design issues and align on best practices.

Core Features & Use Cases

  • Abstraction Quality assessment: naming, SRP, leaky abstractions, and Tell, Don't Ask patterns.
  • SOLID Compliance review: checks against SRP, OCP, LSP, ISP, and DIP with practical signals.
  • API Design evaluation: protocol choices (REST, GraphQL, gRPC), consistency, error handling, and versioning considerations.
  • Developer Experience critique: clarity of errors, DX-oriented guidance, and maintainability signals.
  • Output: delivers a structured Design Review with prioritized recommendations and concrete examples.

Quick Start

Provide a module or API surface description and ask for a Design Review focusing on naming, abstractions, SOLID, and DX.

Frequently Asked Questions about design

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

FAQPage Schema
How do I review code for SOLID compliance and naming consistency?

A code design review evaluates abstraction quality, SOLID compliance, naming consistency, and developer experience to surface structural issues. It checks for leaky abstractions, SRP violations, and Tell, Don't Ask patterns to deliver actionable improvement recommendations.

What is the best way to evaluate API design quality across REST and GraphQL protocols?

API design evaluation assesses protocol choices like REST, GraphQL, and gRPC, checking consistency, error handling, and versioning considerations. It provides prioritized recommendations and concrete examples to align API surfaces with best practices.

How does a design review identify leaky abstractions and SRP violations?

A design review identifies leaky abstractions and SRP violations by applying structured criteria to code and component structures. It evaluates naming consistency, Single Responsibility Principle adherence, and Tell, Don't Ask patterns to detect and surface design flaws.

Can I assess developer experience and error clarity for my library?

Yes, you can assess developer experience and error clarity for libraries and services. A design critique evaluates error clarity, DX-oriented guidance, and maintainability signals to provide actionable recommendations that improve the overall developer experience.

What do I need to provide to get a structured design review for my project?

To get a structured design review, you need to provide a module or API surface description. The review then focuses on naming, abstractions, SOLID compliance, and DX to deliver prioritized recommendations with concrete examples for your project.