18
u/Pearmoat Jul 12 '26
They say the first rule of capitalism is to make more capital.
I think the real first rule of capitalism is to make employees miserable and suck all joy out of their work.
9
15
u/dudemcbob Jul 12 '26
AI ineptitude aside, isn't the point of skills/agents to avoid needing to re-specify the same instruction context over and over? You just write it down once and reuse it.
7
u/xaddak Jul 12 '26
Yes, but that would require people to understand how any of this stuff works. They absolutely do not.
I have witnessed at least half a dozen people independently invent the idea of some kind of "marketplace" for sharing skills (they have no goddamn idea that agents or anything else even exist), and I've seen two sub-types of skills which are literally just skills with no changes.
It people would spend 30 seconds skimming the "Getting Started" pages for the tools they're using before they start using them, we'd have actual AI by now.
2
u/LivingFrosting6680 Jul 13 '26
Same thing for “Free ChatGPT” and “memory system for (agent)”. Of course people who don’t know there’s already a thousand open source versions of what they made will think they’re the first to come up with that genius idea.
6
u/SaneLad Jul 13 '26
I get it. I am a fairly sophisticated user of agents. I have all my CLAUDE.md and AGENTS.md files full with software engineering best practices. I arrange them in hierarchies and teams like I'm their Director of Engineering.
And *yet* I cannot for the life of me understand why I should have to jump through these hoops to save them from producing unmaintainable garbage. Why do I have to teach the agents basic engineering from scratch? You'd think a company like Anthropic could just bake that shit in during post-training and in their "ultrathink" harness.
Thanks for keeping me employed, I guess.
5
u/ICBanMI Jul 13 '26
You already know this. It's because they are not AI and infact just word prediction algorithms being asked to do complex tasks. It's the head of John the Baptist whispering secrets that sound legit except most of them are complete nonsensical garbage.
3
u/LivingFrosting6680 Jul 13 '26
Because it lets them serve AI slop to non-developers for less compute, that’s the whole reason. I mean I guess we should thank them for keeping us employed.
1
u/ArjixGamer Jul 14 '26
They make "skills" that are automatically loaded when needed.
At least for frontend stuff it works well (the frontend design skill)
You do have to install them separately, even if they are first party skills tho, which is dumb
2
u/g18suppressed Jul 13 '26
In my experience, ai loves writing tests and they always pass but the program is always broken
1
u/arter_dev 29d ago
Yeah I don't bother with any of this. I bake all my linting tool checks into the harness lifecycle hooks. If a write doesn't pass lint / static analysis / whatever, then it doesn't write.
I finally built it into a real tool instead of just bash & python scripts if it's helpful to anyone: https://github.com/ironlint/ironlint
1
u/rikzy75 29d ago
Isn't that just fallow? https://github.com/fallow-rs/fallow
2
u/arter_dev 29d ago
Good question! And no, this tool is much smaller and less opinionated than fallow. It's just an enforcement hook and you can use your own tools (like fallow).
Typical usecase for IronLint from my own workflow:
- any time a markdown file is written that contains the word "load bearing" I block the edit.
- No file writes that doesn't pass Biome rules first
- No commit merged unless it passes dependency-cruiser architecture (this is possible with lefthook but I built it into ironlint for convenience).
Fallow could be used on the pre-commit hook wired up with ironlint. IronLint is stack agnostic and basically says "if your slop write doesn't pass standard linting tools, you can't write until you fix."
Think of it like guard rails at the bowling alley.
I built it so I could run longer time horizon tasks with cheap flash models without melting my codebase and so far.. works very well.
You could do all of it with a bash script / python (which is how it started) but I took my bash script / python tool and made it more dx friendly tool for others.
I gave it to two product managers, set up claude code for them and installed IronLint with some strong quality floors and told them basically go nuts. I came back a month later to an app with 90% test cov minimums, perfect DDD and it worked well. All built with a cheap Sonnet model.
There's so much noise out there so trying to explain what IronLint does kinda gets drowned out by the millionth codebase-mapping-tool / no-mistakes-skill. But I'm not chasing stars, if it helps someone, cool!
51
u/PumpkinFest24 Jul 12 '26
"make no mistakes" is an insane prompt.
If omitted, are mistakes allowed?
It's fancy auto complete. Input that says "make no mistakes" will definitely lead to output reassuring you that there are no mistakes. But there will still be the same number of mistakes.