skills.rest
allexcd
allexcdCOMMUNITY
Explore all skills by this author →
GitHub

demand-elegance

Evaluate non-trivial software changes for elegance versus pragmatism.

Updated Apr 23, 2026
Search Tags:#workflow#quality#refactor#code-review#pragmatism#elegance
One-click install
npx skills add https://github.com/allexcd/claude-workspace-kit --skill demand-elegance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: demand-elegance
Source: https://github.com/allexcd/claude-workspace-kit/tree/main/.claude/skills/demand-elegance
Command: npx skills add https://github.com/allexcd/claude-workspace-kit --skill demand-elegance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a mental model and process to prioritize elegant, maintainable solutions over quick hacks when addressing non-trivial changes, reducing future tech debt.

Core Features & Use Cases

  • Structured prompts for evaluating elegance vs pragmatism
  • Guided trade-off analysis and kick-off for refactor vs quick fix
  • Use Case: before presenting a major change to stakeholders, run an elegance check to ensure quality.

Quick Start

Ask the AI to review a proposed non-trivial change and balance elegance with pragmatism.

Frequently Asked Questions about demand-elegance

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

FAQPage Schema
How do I balance code elegance with pragmatism for a non-trivial software change?▼

To balance elegance with pragmatism, apply structured evaluation prompts that enforce guardrails and guide trade-off analysis before presenting work. This process ensures maintainable outcomes for non-trivial implementations.

When should I run an elegance check during a code review?▼

Run an elegance check before presenting major changes to stakeholders or implementing non-trivial fixes. It evaluates your proposed workflow to prioritize maintainable solutions over quick hacks, reducing future tech debt.

What is the best way to decide between a major refactor and a quick fix?▼

The best way to decide between a refactor and a quick fix is using guided trade-off analysis and kick-off evaluation prompts. This structured approach enforces guardrails, ensuring you prioritize maintainable code without sacrificing necessary pragmatism.

How do I reduce future tech debt when implementing new features?▼

Reduce future tech debt by applying a mental model that prioritizes elegant solutions over quick hacks. Use structured evaluation prompts to assess non-trivial changes and enforce quality guardrails before finalizing the implementation.

Can I use this elegance evaluation process for trivial bug fixes?▼

No, this elegance evaluation process applies only to non-trivial fixes or implementations. Trivial changes do not require the structured trade-off analysis and guardrails needed to ensure maintainable outcomes for complex software projects.

Related Skills

Explore More Product & Management Skills→
lciaccilciacci

adr-gate

Enforce architectural decision linkage for non-trivial code changes before review.

Community
Advanced
erhankaraarslanerhankaraarslan

refactoring-patterns

Apply refactoring patterns to JavaScript/TypeScript codebases with test scaffolding.

Community
Intermediate
viktorbezdekviktorbezdek
10

moai-workflow-testing

Automate end-to-end development workflows integrating testing, debugging, profiling, and code review.

Community
Advanced
hainamchunghainamchung
54

agent-assistant-code-fast

Execute coding tasks immediately by bypassing the planning phase.

Community
Intermediate