Skip to content
Back to skills

Complexity Management Skill

ASecurity

KISS/YAGNI/DRY tradeoff heuristics for minimizing accidental complexity. Triggers: complexity, accidental complexity. Not for smell detection (code-smells-skill), over-engineering audit (civiltekk-ponytail-audit-skill), or SOLID reference (solid-principles-skill).

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 20, 2026
code-qualitygoexpress

Security analysis

A100/100

Scanned September 28, 2026

npx -y skills add darellchua2/opencode-config-template --skill complexity-management-skill --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Complexity Management Skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Complexity Management Skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/darellchua2-complexity-management-skill/badge)](https://www.skillsdirectory.com/skills/darellchua2-complexity-management-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: complexity-management-skill
description: "KISS/YAGNI/DRY tradeoff heuristics for minimizing accidental complexity. Triggers: complexity, accidental complexity. Not for smell detection (code-smells-skill), over-engineering audit (civiltekk-ponytail-audit-skill), or SOLID reference (solid-principles-skill)."
license: Apache-2.0
compatibility: opencode
category: Code Quality
---

## What I do

Reduce accidental complexity (self-inflicted: unclear names, leaky abstractions, unnecessary layers) while expressing essential complexity (inherent problem domain) clearly.

## When to use me

- Reviewing whether an abstraction/module/layer earns its cost
- Symptoms present: change amplification (one simple change → many edits), high cognitive load (can't hold the module in your head), unknown unknowns (can't find what to change)

House stance: aggressive deletion of speculative abstraction; KISS/YAGNI are the defaults; add a layer only when the second consumer actually arrives. Working code beats elegant design; invest complexity budget where change is frequent.

> Removed 2026-09: essential-vs-accidental complexity essays, the three symptom deep-dives with code examples, XP values walkthrough, KISS/YAGNI/DRY explanation catalogs, working-effectively-with-legacy notes — Ousterhout-style textbook content the model already carries.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…