https://platform.claude.com/cookbook/coding-prompting-for-fr... Before: bland After: bland with gradients
Yes, and a couple of them look better before, I would say only the Blog one is truly better.
Claude Cookbook
31–40 of 182 posts
Re: Claude Cookbook
#32Does anybody here have a frontend development workflow that works well with coding agents? In my experience coding agents ship buggy, broken, incomplete, or awkward frontend features at a way higher frequency than they do for backend features. The reason seems obviously to
be the difference in verifiability between the two. Basic test suites dont seem to help much. I assume something like Garry Tan’s gstack is the right direction but I dont know if that particular tool is mature enough to adopt yet. I was surprised too see here on HN recently that gemini 3.5 flash may outperform Opus/gpt-5.5 on frontend tasks (maybe because of Gemini’s supposed edge w.r.t. multimodality? or maybe it understands Chrome more deeply?), can anyone here second that take?
Re: Claude Cookbook
#33After all this effort of not opening the models, then trying to forbid people to use open models and all the rubbish their CEO keeps talking about common people I am done with Anthropic. I can't use it on good faith Same goes for grok, chat gpt and others all involved in killing people and monopolising the market.
The open models will also be used to kill people, unfortunately.
Aren't closed models used to kill people by the US and Israel?
Re: Claude Cookbook
#34Gotta be honest, almost every "how to use AI" resource seems pointless to me. I'm either going to ask the AI how to do it, or if it's about using the AI then we can just bake it into the harness or wait for Anthropic/OpenAI to do it for me because they're always trivial. All of these resources on agentic workflows, managing agent memory, harness engineering, etc. appear to just be theatre to me.
I think the main thing of interest in the linked site is the dates. You can quickly get a view of what was possible and when.
Re: Claude Cookbook
#35Gotta be honest, almost every "how to use AI" resource seems pointless to me. I'm either going to ask the AI how to do it, or if it's about using the AI then we can just bake it into the harness or wait for Anthropic/OpenAI to do it for me because they're always trivial. All of these resources on agentic workflows, managing agent memory, harness engineering, etc. appear to just be theatre to me.
>I'm either going to ask the AI how to do it LLMs seem terrible at using LLMs in harnesses. Have you seen how they rot their context with the stuff they put in .md files if you let them? You'd have to have the LLMs search, and thus these resources could be for them more than you
Yes, but I have had moderate luck with creating an "agent-instructor" skill that has strict instructions around keeping language strong, unambiguous, concise, and always presenting me with exact diffs to review before writing anything.
Another thing in it is a strict line count. Any increase in line count requires my approval. That last one is important because it plays well with two biases: models don't tend to create long lines so they won't try to cheat that way, and they're strongly inclined to keep churning out lines so I take that away from them.
Re: Claude Cookbook
#36Re: Claude Cookbook
#37Gotta be honest, almost every "how to use AI" resource seems pointless to me. I'm either going to ask the AI how to do it, or if it's about using the AI then we can just bake it into the harness or wait for Anthropic/OpenAI to do it for me because they're always trivial. All of these resources on agentic workflows, managing agent memory, harness engineering, etc. appear to just be theatre to me.
Remember in 2023 when people thought "prompt engineering" would be the new software engineering and invested tons of time into learning CoT, ReAct, thread-of-thoughts, etc? Those were mostly obviated by reasoning models and harness updates by 2024. It seems pointless to invest energy into the latest/greatest AI technique or framework when they're going to either be absorbed or replaced on a 3 month cycle.
Isn't it clear that some people are better at working with/prompting LLMs than other people? Or is the idea that what you write to them and how you use them doesn't matter, it's all up to the model/harness? To me this seems clear, so then clearly this is a skill, which typically is called "prompt engineering". Specifically CoT or the other things you mention wasn't referred to as "prompt engineering" as far as I know, that skill is more about how you communicate with the LLMs and how you use them, rather than what specific processes/workflows/technologies you use.
Re: Claude Cookbook
#38Does anybody here have a frontend development workflow that works well with coding agents? In my experience coding agents ship buggy, broken, incomplete, or awkward frontend features at a way higher frequency than they do for backend features. The reason seems obviously to be the difference in verifiability between the two. Basic test suites dont seem to help much. I assume something like Garry Tan’s gstack is the ri…
Agents aren't great at complex async state updates, mostly because it's hard to represent what's happening in their context. They're fine at creating complex components in isolation and implementing decoupled stuff like animations.
Re: Claude Cookbook
#39Gotta be honest, almost every "how to use AI" resource seems pointless to me. I'm either going to ask the AI how to do it, or if it's about using the AI then we can just bake it into the harness or wait for Anthropic/OpenAI to do it for me because they're always trivial. All of these resources on agentic workflows, managing agent memory, harness engineering, etc. appear to just be theatre to me.
Ok, thanks, because I looked at one example and was like, “I am supposed to take someone’s OpenAPI doc and translate it back to English for the model?” And if they’re implying I should have an AI do that, why don’t they just build that step into the models rather than having someone prompt an AI to write these half-ass docs?
Re: Claude Cookbook
#40I've been using Matt Pocock's skills at home, and they seem pretty great. He makes a great case for them vs other skills in his videos. I don't remember the exact arguments, but basically they're designed to be called by the user instead of called automatically, and that makes them take less context merely because they exist.
I've also found that they tend to coerce the programmer into thinking about the end result, rather than try to push them out of that role. His grill skills are about making sure the actual requirements are known, and his prototype skill can help explore things that need to be experienced to make a hard decision on.