Samuel
@samuel.fm
claude is *really* good at custom eslint rules, it turns out
5 17
fry69
Pre/Post edit hooks that match on specific files/folders/content can spawn separate instances, a very controlled and powerful agent flow.
Aaaaaallan Deutsch
Yes and it’s a fantastic use case for a few reasons: - enforce better code from future LLM usage - linter rules are really easy to write rigorous unit tests for - a bug in one is very unlikely to produce any prod issues
1
embedding-shapes
If no human is reading the code, no human is writing the code, why even have linting rules? They were created for humans to have an easier time reading, writing and reviewing code, so we don't have to nitpick about these things and argue about it But if the machines does it all, why do we have it?
1
Samuel
lint rules are super helpful for machines. helps constrain bad code
1 1
embedding-shapes
I dunno, I kinda feel like if the model produced it, you already lost. Better way is to figure out the way so they don't write bad code in the first place. They get it wrong? Probably your prompt wasn't good enough, iterate on it and restart from beginning
emma 🍞
uh kinda offtopic ig but i thought bluesky used oxlint for some reason
1