Why Installing More AI Skills Makes Your Model Dumber—and the One-Sentence Skill That Fixes It
As AI coding agents become standard tools, the bottleneck shifts from model capability to instruction design. A skill that permanently occupies context window space degrades performance on everything else; a well-designed skill with a one-line interface and deferred complexity keeps the model sharp. The deletion test for skills—if removing an instruction doesn't change behavior, it was noise—gives teams a concrete way to audit their own agent configurations.
The once-dominant Superpowers framework for Claude Code is being abandoned as models improve and rigid workflows become a bottleneck. Matt Pocock's open-source skills repository offers a lightweight alternative: small, composable instructions that install only what you need. The standout is /grill-me, a one-line skill that forces an AI agent to relentlessly interview you before writing any code, eliminating the most common failure mode—misalignment between what you want and what gets built.
The system extends into a full composable workflow: /to-spec distills conversations into specifications, /to-tickets breaks them into dependency-ordered tasks, /implement runs a TDD red-green-refactor loop, and /code-review performs dual-axis quality checks. For large, ambiguous projects, /wayfinder uses a fog-of-war metaphor to create a decision map of research tickets that progressively reveal the path forward, accepting that you cannot make every decision on day one.
Underneath all of this sits /writing-great-skills, a meta-skill that applies software design principles—deep modules, progressive disclosure, and the deletion test—to the problem of writing AI instructions. It explains why every extra skill description permanently occupies the model's limited Smart Zone of roughly 120k tokens, and why the solution is not fewer skills but better-designed ones that keep interfaces tiny and complexity hidden.
The uninstall-Superpowers movement signals a maturation in how developers think about AI tooling: the value is shifting from comprehensive process enforcement to lightweight, composable primitives that respect the model's attention budget.
Applying software design principles like deep modules and progressive disclosure to AI instructions is an underexplored idea with immediate practical payoff. Most teams treat prompts as prose; treating them as API surfaces with interface and implementation layers changes what gets built.
The fog-of-war metaphor for project planning is a genuinely different paradigm from spec-first development. It accepts that complex projects have irreducible uncertainty and builds a process around discovering decisions rather than pretending to make them all upfront.
The observation that LLMs have a Smart Zone of roughly 120k tokens is a concrete, falsifiable claim with direct engineering consequences. If true, it means context-window benchmarks are misleading and skill designers should treat token budget as a hard resource constraint.