How does the escalation system work?

The skill adjusts its tone based on risk severity: ◇ Alternative (suggests common patterns), ◆ Caution (highlights moderate maintenance risks), and ◆◆ Hazard (warns against high-risk violations of simplicity principles).

How does this skill help with 'Build vs Buy' decisions?

It prompts developers to evaluate proven libraries or managed cloud services (like Auth0 or AWS Secrets Manager) before committing to building and maintaining custom internal solutions.

When should I avoid using this skill?

This skill is not intended for trivial tasks, situations with clear requirements that necessitate high complexity, or when following regulatory and compliance-mandated implementation patterns.

What is a complexity smell?

A complexity smell is an indicator that a solution may be more complicated than necessary, such as building a custom plugin system for a single use case or using a heavy framework for a static site.

Complexity Analysis

Name: Complexity Analysis
Author: outfitter-dev

byoutfitter-dev

•

開発者ツール

Systematically challenges over-engineering and promotes architectural simplicity through structured evaluation and pushback.

概要

Complexity Analysis is a specialized Claude Code skill designed to act as a senior architectural partner, identifying and challenging over-engineered solutions. It helps developers avoid common pitfalls like premature abstraction, performance theater, and unnecessary framework overkill by facilitating a 'justified simplicity' workflow. The skill scans proposals for 'complexity smells,' provides concrete simpler alternatives, and ensures that any necessary complexity is thoroughly documented with architectural decision records (ADRs). It is particularly useful during feature planning, framework selection, and code reviews where 'YAGNI' (You Ain't Gonna Need It) principles are paramount.

主な機能

Tiered escalation system (Alternative, Caution, Hazard) for architectural pushback
Structured 'Build vs. Buy' evaluation for auth, state management, and infrastructure
Pattern-based guidance for transforming complex abstractions into direct implementations
Automated workflow for documenting architectural decisions and trade-offs
Identification of complexity smells like premature abstraction and performance theater
16 GitHub stars

ユースケース

Deciding whether to build a custom internal tool or utilize existing cloud provider services
Reviewing new feature proposals to ensure they don't introduce unnecessary architectural bloat
Refactoring legacy code by replacing complex custom patterns with standard library features

概要

主な機能

Tiered escalation system (Alternative, Caution, Hazard) for architectural pushback
Structured 'Build vs. Buy' evaluation for auth, state management, and infrastructure
Pattern-based guidance for transforming complex abstractions into direct implementations
Automated workflow for documenting architectural decisions and trade-offs
Identification of complexity smells like premature abstraction and performance theater
16 GitHub stars

ユースケース

Deciding whether to build a custom internal tool or utilize existing cloud provider services
Reviewing new feature proposals to ensure they don't introduce unnecessary architectural bloat
Refactoring legacy code by replacing complex custom patterns with standard library features