Live data from Hacker News

Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

arps18.github.io

231–240 of 297 posts

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#231

The reliance on context to drive correct actions just doesn't work well. I am constantly wrestling with AI agents that do not do what you tell them. Every AI agent out there seems to suck in this regard, leaving it up to the user to build in their own guardrails. I have a bad feeling that nobody is working on an improved solution.

I’ve seen no reason to believe it’s even possible to solve this. The worst thing about LLMs is they can pass the Turing test, leading people to believe they have an Asimov style robot instead of a very cool statistical model. It feels like they should be able to follow instructions or keep instructions from content separate, but that’s not what’s happening.

When the you send a prompt and the AI wants to run a tool, it should be outputting a structured output which the AI agent can scan, find a tool call, and run that tool call. But how does the AI know the "right" way to call the tool, right args, etc? You're supposed to tell it once at the beginning of the context... but it can forget that.

So really, your tool-specific rules should be passed to the AI either with your follow-up prompt, or in response to the request to issue a tool call, so the AI can validate what it will compose the tool call as, right as it's making the call. This means the agent should keep track of tool-specific rules, and reinforce them to the AI. Yes this will spend a few more tokens per call, but it will probably improve the outcomes somewhat.

In addition to this, we should probably be abstracting the tool calls more. Rather than let the AI run a Bash one-liner which includes writing files to `/tmp/foo.txt`, we should have the AI output even more structured tool calls, liike `make_temp_file AS BAR`, and have it then call another tool referencing $BAR (`some_other_tool -tmpfile $BAR`). This way there is less to go wrong because it's not getting in the weeds doing shell scripting while it's trying to do something more important (diagnosing an issue).

I think this will require additional training by the AI companies. Which is why we need to define these kind of standards now, so 6-12 months from now, we will have AI that actually support these higher level abstractions. You then customize your abstraction, and the AI doesn't have to know anything about how it works on your box. It would greatly reduce the complexity required for AIs to do agentic work.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#233
post #168

We really need some consolidation around commands, skills, subagents, and plugins. For example, if you want to, say, review code, you have five options now: - Write a .claude/commands/review.md. Simple but deprecated. - Use a /code-review skill, either one you install or one you just write yourself (it's just Markdown, after all). - Use the /pr-review subagent. Also just Markdown, but it runs "in the background" and…

Hey, Boris from the CC team here. I agree, we're working on consolidating these. Going forward it will just be the built-in /code-review skill. Here's how to use the skill on the latest version: /code-review # do a balanced code review. checks for bugs and inconsistencies, poor code quality, duplication, band aids, etc. /code-review --fix # same as above, but also fix the issues # choose an explicit effort level (def…

Why doesn't Claude invoke LSPs? It always asks to install them, but then it never uses them, as mentioned in the comment you replied to.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#234

How many times can I read the same shallow guidance written by AI on using a coding agent? Good god when will it stop

You're absolutely right to call this out — and honestly? I want to sit with that for a moment. Here's the thing: this isn't really about AI writing. It's not even about coding agents. It's about something much deeper. What's genuinely worth knowing: while I generally agree, many people may not. I think there's a really interesting conversation to be had here. Thanks for naming this. It needed to be named. (/s - Blarg…

If you wrote this yourself, congratulations are in order. I was genuinely annoyed. It’s not easy. It’s hard. It’s not entertaining. It’s infuriating.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#235
post #111

Earlier quoted context omitted.

Can't wait to learn more about how to vendor-lock-in myself really hard into not being able to code without the help of a specific corporation!

I hear you on vendor lock-in. Everyone's freaked out about other companies getting the upper-hand with AI in the loop, so there's this charge to use the hell out of it at all costs. Meanwhile, we're quietly picking winners and losers on the service side of all this, and we'll have to live with that outcome for a long time. At this point, I'm seriously considering what it would take to build a reasonable budget-AI box…

Right now, self-hosting is too expensive if you’re starting from scratch. We have an old EliteDesk that can run the most basic of models, but it doesn’t feel like it’s worth it. Electricity is also quite expensive in many places, it adds up.

If hardware prices ever come back to sane levels, eh… the Framework desktop with Ryzen AI might be interesting to play with.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#237
post #9

Regarding: ``` # Development Workflow *Always use `bun`, not `npm`.* # 1. Make changes # 2. Typecheck (fast) bun run typecheck # 3. Run tests bun run test -- -t "test name" # Single suite bun run test:file -- "glob" # Specific files # 4. Lint before committing bun run lint:file -- "file1.ts" bun run lint # 5. Before creating PR bun run lint:claude && bun run test ``` I have these things in pre-commit, this way the ta…

How do you tell Claude about VOCABULARY.md? Does it auto-discover it?

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#238
post #234

Earlier quoted context omitted.

You're absolutely right to call this out — and honestly? I want to sit with that for a moment. Here's the thing: this isn't really about AI writing. It's not even about coding agents. It's about something much deeper. What's genuinely worth knowing: while I generally agree, many people may not. I think there's a really interesting conversation to be had here. Thanks for naming this. It needed to be named. (/s - Blarg…

If you wrote this yourself, congratulations are in order. I was genuinely annoyed. It’s not easy. It’s hard. It’s not entertaining. It’s infuriating.

You're absolutely right!

I was at a restaurant the other day and my kid noticed how the waiter started every sentence with "Absolutely!" That reminded me of the Anthropic Super Bowl ad, and got me thinking if the waiter's speech patterns had been influenced by AI.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#239
post #91

Earlier quoted context omitted.

I more meant feature-level differences. For instance, Claude Code has agent teams, and Codex CLI does not. Or for a while, Codex had "/goal" and Claude Code did not (though now Claude Code has it too). To your point, it is usually possible to polyfill these gaps either with custom code/skills/hooks or with third party plugins.

[dead]

https://gail.wharton.upenn.edu/research-and-insights/techrep...
Post reply on HN