Re:Anatomy of the .claude/ Folder
by abustamam on Saturday March 28, 2026 @10:07AM
(#47554762)
At work I use skills to maintain code consistency. We instrumented a solid "model view viewmodel" architecture for a front-end app, because without any guard rails it was doing redundant data fetching and type casts and just messy overall. Having a "mvvm" rule and skill that defines the boundaries keeps the llm from writing a bunch of nonsense code that happens to work.
[ Parent
| on HN ]
Re:Anatomy of the .claude/ Folder
by dotancohen on Saturday March 28, 2026 @10:42AM
(#47555046)
This sounds great - skills to ensure that the code maintains proper separation of concerns and is packaged properly.
I'd love to know how this skill was phased.
Honestly I started with Obra superpowers and worked with my boss to brainstorm the best way to keep separation of concerns, and we just stepped on rakes as we developed and had Obra superpowers suggest updates to our rules/skills.
It's certainly an iterative process but it gets better every iteration.
Re:Anatomy of the .claude/ Folder
by dotancohen on Monday March 30, 2026 @05:51PM
(#47580164)
Thank you. I've never heard of Obra Superpowers, I'm looking at it now.
A deterministic layer linter would be better for this.
Possibly, and we do use linters, but linters don't stop LLMs from going off the rails. It does end up fixing itself because of the linter, but then the results are only as good as the linter itself.