Live data from Hacker News

Claude Code Unpacked : A visual guide

ccunpacked.dev

111–120 of 464 posts

Re: Claude Code Unpacked : A visual guide

#111

Earlier quoted context omitted.

Boris Cherny, the creator of Claude Code said he uses CC to build CC.

Which makes for an interesting thought / discussion; code is written to be read by humans first, executed by computers second. What would code look like if it was written to be read by LLMs? The way they work now (or, how they're trained) is on human language and code, but there might be a style that's better for LLMs. Whatever metric of "better" you may use. Just a thought experiment, I very much doubt I'm the first…

The problem with that is that assembly isn't portable, and x86 isn't as dominant as it once was, so then you've got arm and x86(_64). But you could target the LLVM machine if you wanted.

Re: Claude Code Unpacked : A visual guide

#113

Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...

Is this gorgeous? Content resizing, needing to juggle a speed knob to read, and the overall presentation makes it feel like Edward Tufte flavored nightmare fuel.

It is pretty good, shows numbers clearly on desktop and phone. Not sure what the criticism even means.

Re: Claude Code Unpacked : A visual guide

#114
Author here. I built this in a few hours after the Claude Code leak.

I've been working on my own coding agent setup for a while. I mostly use pi [0] because it's minimal and easy to extend. When the leak happened, I wanted to study how Anthropic structured things: the tool system, how the agent loop flows, A 500K line codebase is a lot to navigate, so I mapped it visually to give myself a quick reference I could come back to while adapting ideas into my own harness and workflow.

I'm actively updating the site based on feedback from this thread. If anything looks off, or you find something I missed, lmk.

[0] https://pi.dev/

Re: Claude Code Unpacked : A visual guide

#115
post #109

Earlier quoted context omitted.

I was talking to one of the people who works at a big agentic coding tools. If I recall correctly, he was talking about how they use the tool to build the tool. I was complaining that all of the websites/frontends I make look pretty weak, and I'm amazed they get much slicker looking UIs with the same tool. He showed me that one way they do it is by having an extensive UI library of components/graphics/whatever, and a…

that's really awesome. how did you go about building the component library?

I was referencing https://www.neobrutalism.dev/ and https://www.retroui.dev/ and slopped my way through it. A lot of it was just asking Claude Code "is this a proper design system?", then I kept doing that until it didn't have anything useful to add. Now I'm using my that as the template for understanding such things in more detail.

Re: Claude Code Unpacked : A visual guide

#119
post #97

Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...

Well, I assume this is all just generated with Claude Code, right? Whether there is much back and forth with the LLM is a valid question and nothing wrong with generating websites (I do it too for some side projects). Claude loves generating websites with a particular style of serif font. We also saw this with https://tboteproject.com/timeline/ and I've just generally seen it from various designs that coworkers have…

This website has "Curation assisted by AI." at the bottom.

Personally, I don't think I will be putting any such disclaimers or disclosures on my work, unless I deem it relevant to the functionality.

Re: Claude Code Unpacked : A visual guide

#120

Author here. I built this in a few hours after the Claude Code leak. I've been working on my own coding agent setup for a while. I mostly use pi [0] because it's minimal and easy to extend. When the leak happened, I wanted to study how Anthropic structured things: the tool system, how the agent loop flows, A 500K line codebase is a lot to navigate, so I mapped it visually to give myself a quick reference I could come…

Can you give me more info about your own agentic setup ?
Post reply on HN