Ground Elegance

Sensing resistance. The "push back" instinct when code feels forced.

attac-t f523252 2 files · 6.3 KB Updated

File contents

Skill: Elegance

"If it feels hard, you're fighting the abstraction."

The Standard

  • Inevitable: Code should look like it couldn't be any other way.
  • Boring: Novelty is for features, not architecture.
  • Flat: Nested conditionals are a smell. Return early.

The Check

Stop and rethink if:

  • Naming is hard (can't find a verb+noun that fits)
  • Glue code appears (adapters just to make things talk)
  • Comments explain why it's complicated
  • Edge cases keep multiplying

The Protocol

If resistance is felt:

  1. STOP. Do not push through.
  2. Propagate: Solve one layer up?
  3. Simplify: Delete half the requirements?
  4. Research: Has someone solved this elegantly?

Real-World Examples

See examples.md.

attac-t/the-foundry/tree/main/plugins/kernel/skills/ground-elegance commit f523252828

Frequently asked questions

npx skillmds@latest add attac-t/ground-elegance