How many times can I read the same shallow guidance written by AI on using a coding agent? Good god when will it stop
Reachmaxxxing wannabe influencers who were too far gone to looksmaxxx have to do something to grift a living and NFTs are dead.
Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
181–190 of 297 posts
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#182In my CLAUDE.md I have: - corporal threats of harm directly against Claude - threats of prison for the entire board of directors of Anthropic - explanation how every time it goes off the rails / makes mistakes, it gives more evidence to a class action lawsuit against Anthropic Especially the latter two seem to have improved its "behaviour" to be more "careful" and "deliberate"
I am nothing but polite with my agents. I always ask, say "please" and "thank you", and never swear at it or call it names. I'm hoping that when the robot apocalypse happens, they'll let me stay in the breeding harem, or worst case let me live a few extra minutes.
I am, too, and it got me thinking... why? And I realized that I've tried to be polite in all my interactions my whole life and I'm not going to practice being terse and commanding for a few pennies worth of tokens.
Apocalyptic safety is just a bonus.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#183This is just so much fluff. All the focus on "orchestrating" is ultimately accidental complexity.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#184100% AI generated according to Pangram.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#185We 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…
> They are all just variations of "insert a canned prompt", varying only along the dimensions of (a) how and where the prompt is installed and from where it is sourced, and (b) which context or contexts the prompt runs in.
Yes, yes, thank you, sometimes I feel like I'm taking crazy pills.
The industry and overall developer ecosystem has become absolutely mesmerized by the act of creating and popularizing little bits of protocol and machinery to dress up the act of inserting text into the machine. Yes, they're useful and provide some consistency, but I'm convinced that the main reason people like them so much is because they put a thin "I'm still a programmer wielding complicated tools that laypeople don't understand" coating over the fact that we're all just asking the AI nicely to do a thing.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#186We 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…
I just consider this temp phase because models are dumb and harnesses are not yet there. When I need code review I should just say “review it”. Model should figure out what plugins, skills, etc. to use.
Why does it need plugins/skills for a code review? Claude will just "review it" if you ask it to, and if you have particular preferences, they can go in CLAUDE.md
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#187We 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 (defaults to your current effort level). all of these also accept --fix:
/code-review low
/code-review medium
/code-review high
/code-review xhigh
/code-review max
# do an expensive and extremely thorough review (reliably catches >99% of bugs, costs $3-20 per review depending on complexity):
/code-review ultra
Open to feedback if anyone has feedback or ideas for how to make these even nicer to use.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#188Earlier 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…
I could literally feel my blood beginning to boil. You have a talent for this.
And honestly? That’s rare.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#189What happens when you have a codebase made with claude using this setup and claude is down for let's say 8 hours? Are you able to efficiently, smoothly and productively take over the codebase?
I assume it will be similar to when a person is out sick or on vacation. Another person on the team likely could take over the work for a day, but realistically it just sits until they're is back.
Not really, realistically speaking it's now possible to use an agent to read code and make sensible summaries of a codebase faster than ever before, and it's exactly the thing you'd use to onboard yourself or someone else on the team.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#190Earlier quoted context omitted.
I just consider this temp phase because models are dumb and harnesses are not yet there. When I need code review I should just say “review it”. Model should figure out what plugins, skills, etc. to use.
Why does it need plugins/skills for a code review? Claude will just "review it" if you ask it to, and if you have particular preferences, they can go in CLAUDE.md
Skills are effectively the same thing as asking it, just with more depth. So the skill is just a framework for a very precisely asked question. It often includes how you want Claude to respond, etc.
I’m not aware of anything fundamentally unique about skills or commands, they’re just more tokens to shape the llm