Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

arps18.github.io

Post reply on HN
Print view View original

281–290 of 297 posts

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

#281

Post by neobrain »

sshine wrote: post #275
toastal wrote: post #202

Earlier quoted context omitted.

Yikes. That Nix code is a mess without meaningful organization & only usable via experimental flakes.

There are two kinds of organization happening here that you might not see: 1. All .nix files (besides flake.nix) are flake-parts modules: https://flake.parts/ 2. It's not only usable with experimental flakes. Works fine with unflake or trix. The experimental part of flakes is enabling flake support in the `nix` CLI. Flakes are also a design pattern in pure Nix syntax that can be evaluated fine without the experimenta…

(for context, you're replying to the author of an alternative nix input pinning mechanism, which means... they're probably aware of all that and yet they chose their wording like this anyway)

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

#282

Post by sshine »

neobrain wrote: post #281
sshine wrote: post #275

Earlier quoted context omitted.

There are two kinds of organization happening here that you might not see: 1. All .nix files (besides flake.nix) are flake-parts modules: https://flake.parts/ 2. It's not only usable with experimental flakes. Works fine with unflake or trix. The experimental part of flakes is enabling flake support in the `nix` CLI. Flakes are also a design pattern in pure Nix syntax that can be evaluated fine without the experimenta…

(for context, you're replying to the author of an alternative nix input pinning mechanism, which means... they're probably aware of all that and yet they chose their wording like this anyway)

Hahaha, I didn't see.

Hi toastal, I appreciate your work.

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

#283

Post by uberduper »

sshine wrote: post #279
uberduper wrote: post #173

Earlier quoted context omitted.

I do the same. Codex manages a per project flake.nix and uses `nix develop` for all testing. nix-direnv for my own convenience. I generally have it generate dockerfiles or other deployment assets at some point. Codex is way better at nix than I am.

If you generate Dockerfiles using Nix code, how do you build and run those images? Docker? I use NixOS on my self-hosted CI runners, and I generate the OCI image using Nix via pkgs.dockerTools: https://git.shine.town/infra/runners/src/branch/main/nix/nix... It has nothing to do with Docker as such, it's just named that. https://nix.dev/tutorials/nixos/building-and-running-docker-...

Nix isn't involved in my container images. I just take the dependencies and env vars from the flake and generate a dockerfile.

Guess I need to try out dockerTools. That looks really convenient. Thanks!

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

#284

Post by wonkyfruit »

mil22 wrote: post #210
bcherny wrote: post #187

Earlier quoted context omitted.

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…

Hey Boris, thanks for the great product and for listening! I find the mix between slash commands that are programmatic harness configuration and control commands (/config, /model, /feedback, /fork, /usage, etc.) and ones that are little more than prompt template insertion (/code-review, / , etc.) to be a little confusing and unnecessary. A slash command should be one thing, and one thing only: a command for the harne…

What clicked for me recently was treating skills as composable. Having meta-skills that call smaller skills in order. The "skill vs command vs subagent" confusion partly dissolves once you let skills call other skills. The meta-skill holds the workflow state, the smaller ones each do one job well.

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

#285

Post by sfrangulov »

mil22 wrote: 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…

[flagged]

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

#287

Post by yawnxyz »

laylomo2 wrote: post #167
garethsprice wrote: post #158

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…

I could literally feel my blood beginning to boil. You have a talent for this.

saying the quiet part out loud

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

#288

Post by yawnxyz »

pragma_x wrote: post #213
hootz wrote: 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…

self-hosting is fine, but even if you had a $100k god box with opus-level LLMs, you'd still end up grinding it to a halt if you tried running 5-10 parallel inference streams

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

#289

Post by extr »

bcherny wrote: post #205
extr wrote: post #191

Earlier quoted context omitted.

Hey Boris, some feedback. I like the new /code-review skill but was disappointed you guys removed /simplify because I quite liked the focus on finding code reuse/efficiency opportunities. I see now in 2.1.152 you added those focus areas back to /code-review, but still bundled with the correctness finding. It would be great to have more fine grained control over the /code-review angles beyond just effort level. Or may…

Yep, you can add free-form input. Will update /simplify to only check for code quality and not bugs (the way it used to work), that's a good suggestion.

Damn already there in 154. Thank you man.
Post reply on HN