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

Anatomy of the .claude/ folder

blog.dailydoseofds.com

Post reply on HN
Print view View original

271–280 of 312 posts

Re: Anatomy of the .claude/ folder

#271

Post by steveklabnik »

d4rkp4ttern wrote: post #266
dewey wrote: post #132

Building your AI agent "toolkit" is becoming the equivalent of the perfect "productivity" setup where you spend your time reading blog posts, watching YouTube videos telling you how to be productive and creating habits and rituals...only to be overtaken by a person with a simple paper list of tasks that they work through. Plain Claude, ask it to write a plan, review plan, then tell it to execute still works the best…

Agree. For what it’s worth, in interviews Cherny (Claude Code creator) and Steinberger (OpenClaw creator) say they keep things simple and use none of the workflow frameworks. The latter even said he doesn’t even use plan mode, but I find that very useful: exiting plan mode starts clean with compressed context.

They backed out the “clear context and execute plan” thing recently. It’s a bummer, I thought it was great.

Re: Anatomy of the .claude/ folder

#272

Post by abustamam »

ModernMech wrote: post #267
obsidianbases1 wrote: post #135

Earlier quoted context omitted.

Lots of money being made by luring people into this trap. The reality is that if you actually know what you want, and can communicate it well (where the productivity app can be helpful), then you can do a lot with AI. My experience is that most people don't actually know what they want. Or they don't understand what goes into what they want. Asking for a plan is a shortcut to gaining that understanding.

Problem is they don’t know how to express themselves and many people, especially those interested in tech, don’t want to learn. I can’t tell you how many times I have a CS student in my office for advising and they tell me they only want to take technical courses, because anything reading or writing or psychology or history based is “soft”, unrelated to their major, and a waste of their time. I’ve spent years telling…

Much of my time at work is reading through quickly typed messages from my boss and understanding exactly what questions I need to ask in order to make it easy for him to answer clearly.

Engineers who lack soft skills cannot be effective in team environments.

Re: Anatomy of the .claude/ folder

#273

Post by abustamam »

FINDarkside wrote: post #186
sillysaurusx wrote: post #170

Earlier quoted context omitted.

But... plain Claude does that. At least for my codebase, which is nowhere close to your 10m line. But we do processing on lots of data (~100TB) and Claude definitely builds one-off tools and scripts to analyze it, which works pretty great in my experience. What sort of skills are you referring to?

I think people are looking at skills the wrong way. It's not like it gives it some kind of superpowers it couldn't do otherwise. Ideally you'll have Claude write the skills anyway. It's just a shortcut so you don't have to keep rewriting a prompt all over again and/or have Claude keep figuring out how to do the same thing repeatedly. You can save lots of time, tokens and manual guidance by having well thought skills.…

At work I use skills to maintain code consistency. We instrumented a solid "model view viewmodel" architecture for a front-end app, because without any guard rails it was doing redundant data fetching and type casts and just messy overall. Having a "mvvm" rule and skill that defines the boundaries keeps the llm from writing a bunch of nonsense code that happens to work.

Re: Anatomy of the .claude/ folder

#274

Post by gruez »

steveklabnik wrote: post #271
d4rkp4ttern wrote: post #266

Earlier quoted context omitted.

Agree. For what it’s worth, in interviews Cherny (Claude Code creator) and Steinberger (OpenClaw creator) say they keep things simple and use none of the workflow frameworks. The latter even said he doesn’t even use plan mode, but I find that very useful: exiting plan mode starts clean with compressed context.

They backed out the “clear context and execute plan” thing recently. It’s a bummer, I thought it was great.

Maybe they figured it wasn't need with 1M context?

Re: Anatomy of the .claude/ folder

#276

Post by dotancohen »

abustamam wrote: post #273
FINDarkside wrote: post #186

Earlier quoted context omitted.

I think people are looking at skills the wrong way. It's not like it gives it some kind of superpowers it couldn't do otherwise. Ideally you'll have Claude write the skills anyway. It's just a shortcut so you don't have to keep rewriting a prompt all over again and/or have Claude keep figuring out how to do the same thing repeatedly. You can save lots of time, tokens and manual guidance by having well thought skills.…

At work I use skills to maintain code consistency. We instrumented a solid "model view viewmodel" architecture for a front-end app, because without any guard rails it was doing redundant data fetching and type casts and just messy overall. Having a "mvvm" rule and skill that defines the boundaries keeps the llm from writing a bunch of nonsense code that happens to work.

This sounds great - skills to ensure that the code maintains proper separation of concerns and is packaged properly.

I'd love to know how this skill was phased.

Re: Anatomy of the .claude/ folder

#279

Post by Rumudiez »

soulchild77 wrote: post #247
luisgvv wrote: post #210

Earlier quoted context omitted.

This is why the grill me skill went viral - https://github.com/mattpocock/skills/blob/main/grill-me/SKIL...

I asked Claude whether these elaborate words like "walk down the design tree" actually mean anything to the LLM and make a difference. The answer confirmed my gut feeling: You can just tell me to "be critical" and get mostly the same results. Matt did incredible work teaching people TS, but this feels more like trying to create FOMO to sell snake oil and AI courses.

I thought that was supposed to be “decision tree” but otherwise, totally agree the exact words don’t actually matter all that much in most instances. I copy-paste templated prompts and every now and then notice some baffling grammar on my side after the fact… claude doesn’t mind

Re: Anatomy of the .claude/ folder

#280

Post by DontTrustOver25 »

sillysaurusx wrote: post #170
lanthissa wrote: post #164

Earlier quoted context omitted.

its not though if you're working in a massive codebase or on a distributed system that has many interconnected parts. skills that teach the agent how to pipe data, build requests, trace them through a system and datasources, then update code based on those results are a step function improvement in development. ai has fundamentally changed how productive i am working on a 10m line codebase, and i'd guess less than 5%…

But... plain Claude does that. At least for my codebase, which is nowhere close to your 10m line. But we do processing on lots of data (~100TB) and Claude definitely builds one-off tools and scripts to analyze it, which works pretty great in my experience. What sort of skills are you referring to?

[dead]
Post reply on HN