Comment by abustamam
11 hours ago
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.
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.
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.