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

281–290 of 312 posts

Re: Anatomy of the .claude/ folder

#281

Post by dinkumthinkum »

JohnMakin wrote: post #180
imiric wrote: post #178

Earlier quoted context omitted.

Modern "skills" and Markdown formats of the day are no different than "save the kittens". All of these practices are promoted by influencers and adopted based on wishful thinking and anecdata.

Uh, this couldn't be more false. I've implemented these from scratch at my company and rolled them out org-wide and I've yet to watch a youtube video and don't consume any influencers. Mostly by just using the tools and reading documentation - as any other technical tool. Perhaps your blanket statement could be wrong, and I would encourage you to let your mind be a bit more open. The landscape here is not what it was…

To be fair, if you have never watched a YouTube video in your life then how can you say the OP was wrong about what influencers are peddling? Side note, have you ever seen that Onion article on the man that can't stop telling people he doesn't own a TV?

https://theonion.com/area-man-constantly-mentioning-he-doesn...

Re: Anatomy of the .claude/ folder

#282

Post by dinkumthinkum »

brandnewideas wrote: post #270
dataviz1000 wrote: post #87

Claude Fast has very good alternate documentation for this. [0] I don't understand the hate for defining .claude/ . It is quite easy to have the main agent write the files. Then rather doing one shot coding, instead iterate quickly updating .claude/ I'm at the point where .claude/ makes copies of itself, performs the task, evaluates, and updates itself. I'm not coding code, I'm coding .claude/ which does everything e…

I'm in absolute disbelief at the existence of this website. Idiocracy is at an all-time high.

Yes. I think people that think like us are in a major minority, ironically. It's a sinking ship.

Re: Anatomy of the .claude/ folder

#283

Post by dinkumthinkum »

TheRoque wrote: post #5

So that's what "software engineering" has become nowadays ? Some cargo cult basically. Seriously all of this gives red flag. No statements here are provable. It's just like langhchain that was praised and then everyone realized it's absolute dog water. Just like MCP too. The job in 2026 is really sad.

I would say, yes its pretty sad. The hypers are kind of gassing themselves up because they, unironically, think they are using LLMs in some special way and they are going to win. I think the industry is ramping up to speed-run into some Tai Lopez type situation.,

Re: Anatomy of the .claude/ folder

#284

Post by dinkumthinkum »

fogzen wrote: post #91
63stack wrote: post #30

The article starts off really weak: >Claude Code users typically treat the .claude folder like a black box. They know it exists. They’ve seen it appear in their project root. But they’ve never opened it, let alone understood what every file inside it does. I know we are living in a post-engineering world now, but you can't tell me that people don't look at PRs anymore, or their own diffs, at least until/if they decid…

I don't. I have Claude do all my PR reviews, running in a daily loop in the morning. The truth is an LLM is better at code review than the average programmer. I'm a senior engineer who has been shipping code since before GitHub and PR reviews was a thing. Thankfully LLMs have freed me from being asked to read other people's shit code for hours every day.

It "freed" you. :) That's an interesting way to put it.

Re: Anatomy of the .claude/ folder

#286

Post by theshrike79 »

abustamam wrote: post #272
ModernMech wrote: post #267

Earlier quoted context omitted.

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.

Being able (and willing) to write shit down is a superpower among 10x programmers who think "code is self-documenting" and don't even add comments.

Re: Anatomy of the .claude/ folder

#287

Post by pydry »

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.

A deterministic layer linter would be better for this.

Re: Anatomy of the .claude/ folder

#288

Post by abustamam »

theshrike79 wrote: post #286
abustamam wrote: post #272

Earlier quoted context omitted.

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.

Being able (and willing) to write shit down is a superpower among 10x programmers who think "code is self-documenting" and don't even add comments.

Haha. I always say that I'm only a good IC not because of my technical skills but because of my communication skills and my willingness to, as Steven Covey says, seek first to understand.

Re: Anatomy of the .claude/ folder

#289

Post by theshrike79 »

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…

I consider it more like people installing oh-my-zsh or whatever that brings a TON of features they'll never use, just because some cool tech influencer said it's cool to use it.

The proper way to do this is find a personal pain point, figure out how to fix it, fix it, and then continue.

That's how I built my own system, zero skills, just a git submodule with shared guides how to do stuff the way _I_ like it. I can just refer any agent to read that directory and they'll usually get it on the first go.

Re: Anatomy of the .claude/ folder

#290

Post by theshrike79 »

gruez wrote: post #274
steveklabnik wrote: post #271

Earlier quoted context omitted.

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?

Anecdotal evidence says that the 1M context one still gets stupid around 200-300k tokens.

Context still matters and I'll never stop implementing things in small slices instead of trying to one-shot.

Post reply on HN