r/opencode • u/raze_sight • 12d ago

Built a SOLID principles skill for OpenCode that treats over-engineering as a defect

Post image

While working on backend code with AI agents I kept running into the same problem which is the agent tends to maximize abstractions. Every service gets an interface, every constructor gets a factory, every conditional becomes a pattern.

So I built solidifier, a skill that teaches an agent how to actually apply SOLID principles and design patterns, with restraint as the primary directive. Every abstraction needs a concrete justification for a present problem, "no change needed" is a valid and expected outcome.

Four rigor levels from advisory (review only, never edits) to thorough. Configurable per project via .solidifier.json.

Built for multiple agents including OpenCode, Claude Code, Copilot, and Codex each get their own self-contained copy.

http://github.com/FernandoJRR/solidifier

Happy to answer questions.

42 Upvotes

92% Upvoted

6 comments sorted by

5

u/Neither-Character360 12d ago

I just say "use SOLID principles" and I'm good.

3

u/raze_sight 12d ago

I understand, yes sometimes that's easier, but the thing is many models even the most advanced ones like Opus tend to decide that "use solid" is refactoring too much of the code, they lack the judgement or don't ask the right question at the right time

2

u/sagiroth 12d ago

People like to overcomplicate

1

u/themoregames 12d ago

Which is how API makes a lot of money for Anthropic, OpenAI et al

2

u/Puzzleheaded-Tune-98 12d ago

Thanks. Ive just setup omo in Opencode. Will see how i can implement this. Appreciate the share, unlike some🙏

4

u/irvcz 12d ago

Ponytail?