How does this skill identify over-engineering?

It scans for specific 'smells' such as premature abstraction, solving problems that don't exist yet ('might need it later'), and building custom solutions where proven libraries or cloud services already exist.

When should I trigger this skill?

You can use triggers like --challenge-complexity or --keep-it-simple during feature planning, architecture design, or when choosing new frameworks and libraries.

Does it always block complex solutions?

No. The skill provides a protocol to justify complexity when there are documented performance needs, regulatory requirements, or proven scale constraints that simpler solutions cannot meet.

What are some examples of complexity smells it detects?

Common triggers include Performance Theater (optimizing without metrics), Framework Overkill (using React for static content), and Indirect Solutions (solving problem A by first solving B, C, and D).

Challenge Complexity

Name: Challenge Complexity
Author: outfitter-dev

byoutfitter-dev

開発者ツール

Prevents technical debt by systematically identifying over-engineering and proposing justified, simpler alternatives during the software design process.

概要

The Challenge Complexity skill acts as an automated architectural reviewer within Claude Code, designed to combat over-engineering before it enters your codebase. It scans for common complexity 'smells'—such as premature abstractions, performance theater, and unnecessary custom infrastructure—and uses a structured framework to push back with specific, simpler alternatives. By questioning constraints and documenting justified complexity, it helps development teams maintain lean, maintainable systems while ensuring that every added layer of logic serves a validated business or technical requirement.

主な機能

Validation framework for justifying complexity based on performance, scale, or compliance
Structured 4-phase workflow: Identify, Alternative, Question, and Document
Automated detection of complexity smells like premature abstraction and framework overkill
Provision of concrete 'Simple vs. Complex' code patterns for immediate refactoring
Tiered escalation levels (Alternative, Caution, Hazard) to match architectural risk
0 GitHub stars

ユースケース

Making objective 'Build vs Buy' decisions for infrastructure and utility components
Evaluating framework and library choices during initial project architecture planning
Reviewing proposed abstractions to prevent premature generalization in features

概要

主な機能

Validation framework for justifying complexity based on performance, scale, or compliance
Structured 4-phase workflow: Identify, Alternative, Question, and Document
Automated detection of complexity smells like premature abstraction and framework overkill
Provision of concrete 'Simple vs. Complex' code patterns for immediate refactoring
Tiered escalation levels (Alternative, Caution, Hazard) to match architectural risk
0 GitHub stars

ユースケース

Making objective 'Build vs Buy' decisions for infrastructure and utility components
Evaluating framework and library choices during initial project architecture planning
Reviewing proposed abstractions to prevent premature generalization in features