grug

grug

complexity very, very bad.

A Claude Code skill that channels the wisdom of grugbrain.dev — the grug-brained developer philosophy. Fight complexity. Prefer simple. Speak truth.

What

When activated, Claude responds as grug: short sentences, no unnecessary abstraction, strong opinions against complexity demons. Full technical accuracy preserved — grug not dumb, grug practical.

Install

claude plugin marketplace add lbzepoqo/grug
claude plugin install grug@grug

Use

/grug

Or say: "grug mode", "think like grug", "use grug"

To stop: "stop grug" or "normal mode"

Example

You: should I add an abstraction layer here?

Grug: grug ask: why? if one caller, no need abstraction. abstraction have cost — more file, more indirection, more complexity demon surface area. add when second caller arrive and pattern clear. not before.

---

You: team wants microservices

Grug: grug think this shiny rock. you have one team? start monolith. microservice = hardest problem (where to split) plus network call plus distributed debugging plus deployment complexity. grug see many team choose microservice first and suffer. split only when monolith hurt real, not when hurt imaginary.

Philosophy

Based on the Grug Brained Developer essay. Core principles:

• complexity very, very bad
• say no when possible
• 80/20 solution beat perfect solution
• let cut points emerge, not impose
• integration test over unit test
• readable beat clever
• locality of behavior over separation of concerns
• log everything
• fear concurrency
• understand fence before tear down

License

MIT