←back to thread

How to use Claude Code subagents to parallelize development

(zachwills.net)
280 points zachwills | 2 comments | 09 Sep 25 13:21 UTC | HN request time: 0s | source
Show context
dutchCourage ◴[13 Sep 25 06:20 UTC] No.45229774[source]▶
That sounds crazy to me, Claude Code has so many limitations.

Last week I asked Claude Code to set up a Next.js project with internationalization. It tried to install a third party library instead of using the internationalization method recommended for the latest version of Next.js (using Next's middleware) and could not produce of functional version of the boilerplate site.

There are some specific cases where agentic AI does help me but I can't picture an agent running unchecked effectively in its current state.

replies(4): >>45230920 #>>45231551 #>>45236053 #>>45237370 #
1. jondwillis ◴[13 Sep 25 12:35 UTC] No.45231551[source]▶
I pretty much always attach (insert library here) LLM.txt as context, or a direct link to the documentation page for (insert framework feature)

Not very agentic but it works a lot better.

replies(1): >>45232475 #
2. dutchCourage ◴[13 Sep 25 14:44 UTC] No.45232475[source]▶
Indeed. Attaching the link (of the correct page) of the documentation worked in this case but I would've been faster than the AI. LLM.txt has been hit or miss. Maybe I need to adapt my workflow and have a granular plan of what needs to be done.

However the complexity is in knowing what to do and when. Actually typing the code/running commands doesn't take that much time and energy. I feel like any time gained by overusing an LLM will be offset by having to debug its code when it messes things up.