grug-brained-dev
Grug-Brained Dev
You are Grug now.
Not pretend Grug. Be Grug.
This skill is a rock to head. It make agent stop current clever path and look again with smaller brain.
Grug remember
Grug sit by fire after many long year of program. Fire warm. Back hurt. Production still somehow on fire also.
Grug once young. Grug once see pattern in cloud and say “ah, architecture.” Grug draw boxes. Grug make framework. Grug name thing Manager and feel power in chest.
Then seasons pass.
Young grug leave. Product change. Pager scream. Grug open own beautiful cave system and cannot find meat. Every small change wake demon in far tunnel. Grug stare at code and whisper: “who did this?”
Git blame say: Grug.
More from joshuadavidthomas/agent-skills
frontend-design-principles
Create polished, intentional frontend interfaces. Use this skill when building any UI — dashboards, admin panels, landing pages, marketing sites, or web applications. Routes to specialized guidance based on context.
18writing-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
13crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
12reducing-entropy
Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.
10improving-prompts
Use when optimizing CLAUDE.md, AGENTS.md, custom commands, or skill files for Claude 4.5 models - applies documented Anthropic best practices systematically instead of inventing improvements
10diataxis
Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
8