What 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?
time for a day off!
Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
161–170 of 297 posts
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#162What 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?
You could say the same thing about any always online software suite and it would be equally fair as we move into more agentic development workflows. EX. Sure, you could go back to the old ways of using a drafting table for your engineering work if CAD went down but it would be exponentially slower… Personally with my workflow I spend 30-60 minutes per Claude feature spec doc when I’m pair planning. If Claude goes dow…
> You could say the same thing about any always online software suite
Uh, people do say this thing. It is a basic factor and question asked during technology procurement. Uptime and fail states matter.
AI just seems exempt from all the questions people usually ask about relying on other people's software.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#163How many times can I read the same shallow guidance written by AI on using a coding agent? Good god when will it stop
Do you have any resources for someone just getting started that you'd recommend? I've --successfully-- ignored AI for the last two years as I was taking care of our kiddo. I'm attempting to catch up in the next few weeks.
If you're talking about Claude Code: Just the official docs [0] and then the best practices tweeted by Anthropic team members like Boris (@bcherny).
Ignore all the 3rd party frameworks (at least for now, probably forever.)
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#164How many times can I read the same shallow guidance written by AI on using a coding agent? Good god when will it stop
My strategy these days is just use a popular product to do good work or don't. Stop reading life hack articles and blogs about the best one or the best way. Don't even click it.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#165Earlier quoted context omitted.
[flagged]
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]
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#166Earlier quoted context omitted.
Basically any other that is not stuck to being managed just by one company. Claude Code does things like using CLAUDE.md and other stuff specific to just their platform, so you are basically locking your project, and everyone else who works on it, to Claude Code only, if you don't also port everything you do to other harnesses. If Anthropic is giving cheaper tokens in exchange for locking you in into their ecosystem,…
It also can respect AGENTS.md, just saying. It’s all about your README.md. But I’m with you about being agent agnostic.
Of course it can, it's Microsofty tactics, support everything but generate "proprietary" stuff by default. Read ODF but generate docx.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#167How 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…
I could literally feel my blood beginning to boil. You have a talent for this.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#168We 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 "in parallel", so it must be better, I guess.
- Install the /code-review plugin. This just installs the skills and subagents above.
- Simply ask Claude to review the code. Probably works almost as well as the above in most situations.
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. There's not much advice here about which option is best, and no clear best practices seem to have emerged yet either. Personally, I find just asking Claude to review the code works well enough.
Some of the advice here is also off. For example:
"Install a language server plugin. Type errors and unused imports caught after every edit. Highest-impact plugin you can install."
I work mostly with Rust, Python, and Dart, and followed similar advice, installing LSPs for all three in both Claude Code and Codex. Two months later, after heavy development in all three languages and hundreds of sessions - and frequently running out of RAM due to all the Rust analyzer, Dart analysis server, and Ty LSP servers the harnesses were spinning up - I checked the session logs to see how often the agents were actually invoking the LSP tools. The answer was they had invoked them literally once the entire time. I uninstalled all my LSPs and haven't looked back. The agents do just fine using ripgrep and calling cargo clippy, dart analyze, ty check, etc. themselves.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#169We 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.
Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs
#170In 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.