extraneous
Use this skill whenever the user asks why code, a system or a process is hard to work in. Phrasings: "why is this so hard to follow?", "I keep too much in my head", "newcomers stay confused". It covers something too complex that nobody can explain, a task that needs many things held in mind at once, code that takes many files to understand (a slow review, a deep class hierarchy), a component that breeds bugs that take days to find, a hire who takes months to ship, a runbook first-timers keep breaking, and a write-up of why code is hard for newcomers. Use it even when the word complexity never appears, and instead of a list of tips nobody asked for. It splits the load the task needs from the load the structure adds, and names the change that removes the second. Skip it for speed fixes, renames, style checks, onboarding checklists and line-by-line explanations.