design-principles

Audit codebases for design principle violations and generate a prioritized DESIGN_AUDIT.md.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill design-principles-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-principles
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/design-principles
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill design-principles-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit a codebase for violations of established software design principles and produce a prioritized, evidence-backed remediation plan that goes beyond linter output.

Core Features & Use Cases

  • Comprehensive Principle Coverage: Evaluates SOLID, DRY, YAGNI, KISS, Law of Demeter, Separation of Concerns, Composition over Inheritance, and the code-relevant 12-Factor subset.
  • Scored Findings with Remediations: Assigns Impact and Effort, computes priorities, and generates a DESIGN_AUDIT.md using a report template.
  • Adversarial Debate for Contested Issues: Runs Red/Blue/White debate on the top contested findings and records concrete refactor proposals or justification comments.
  • Use Case: Run before a large refactor, during tech-debt triage, or when onboarding to an unfamiliar repository to identify high-impact architectural risks.

Quick Start

Run a full design audit of the current repository and generate a prioritized DESIGN_AUDIT.md with scorecard, detailed findings with file:line evidence, debate verdicts for contested items, and a remediation roadmap.

Frequently Asked Questions about design-principles

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

FAQPage Schema
How do I audit my codebase for SOLID, DRY, and other software design principle violations?

A design audit evaluates SOLID, DRY, YAGNI, and KISS violations across your codebase, generating a prioritized DESIGN_AUDIT.md with scored findings, file:line evidence, and concrete remediation steps.

What is the best way to assess technical debt and refactor readiness before a major codebase refactoring?

Assessing refactor readiness requires running a design audit that scores architectural violations by impact and effort, runs adversarial debates on contested findings, and outputs a prioritized remediation roadmap.

Can I run a focused design review on only the changed files in a repository?

Yes, a design audit supports focused checks on changed files or module-scoped reviews, evaluating design health and architectural risks without requiring a full repository scan.

Does the design audit work with any programming language or specific frameworks?

The design audit applies to any repository and programming language, evaluating violations of SOLID, Law of Demeter, and Composition over Inheritance without requiring specific framework dependencies.

How does the audit handle contested architectural findings and code review disagreements?

The audit resolves contested architectural findings by running an adversarial Red/Blue/White debate on top issues, recording concrete refactor proposals or justification comments in the DESIGN_AUDIT.md.

What do I need to run a code design audit on my repository?

Running a code design audit requires access to repository files, with git recommended, to analyze the codebase and produce a prioritized DESIGN_AUDIT.md containing scorecards, debate verdicts, and impact estimates.