mandate-elegance

Evaluate design clarity, economy, and reuse across codebases.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill mandate-elegance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mandate-elegance
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/mandate-elegance
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill mandate-elegance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured critique of design quality, focusing on clarity, economy, and reuse, to help teams reduce duplication and improve maintainability.

Core Features & Use Cases

  • Duplication detection: identifies repeated logic and parallel hierarchies that should be extracted.
  • Abstraction justification: evaluates whether an abstraction used across multiple call sites is warranted.
  • Naming consistency: detects inconsistent naming across subsystems that hinder maintainability.
  • Pattern composition: assesses how well a design pattern integrates with existing patterns and when a new idiom is justified.

Quick Start

Describe a design problem you want evaluated and request an elegance assessment to produce a concise critique.

Frequently Asked Questions about mandate-elegance

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

FAQPage Schema
How do I evaluate design clarity and reuse across my software project?

To evaluate design clarity and reuse, describe a specific design problem to receive a structured critique. This assesses duplication, abstraction justification, naming consistency, and pattern composition to improve maintainability.

What is the best way to detect code duplication and parallel hierarchies during a design review?

Detecting code duplication and parallel hierarchies requires identifying repeated logic that should be extracted. A structured elegance assessment reports these issues alongside criteria for abstraction justification to reduce redundancy.

How do I justify whether an abstraction is warranted across multiple call sites in a codebase?

Justifying an abstraction across multiple call sites requires evaluating whether it genuinely improves economy and reuse. An elegance assessment analyzes abstraction justification criteria to determine if the design choice is warranted.

Can I assess naming consistency across subsystems to improve codebase maintainability?

Yes, you can assess naming consistency across subsystems by requesting an elegance evaluation. It detects inconsistent naming that hinders maintainability and reports findings in structured feedback.

When should I evaluate pattern composition versus introducing a new design idiom?

Evaluating pattern composition is necessary when integrating new logic into existing software designs. It assesses how well a design pattern integrates and determines when introducing a new idiom is justified for clarity.

Does this design evaluation approach work for refactoring assessments in existing codebases?

Yes, this design evaluation approach works for refactoring assessments in existing codebases. It evaluates clarity, economy, and reuse, providing structured feedback on duplication and pattern composition to guide refactoring.