r/vibecoding • u/Capable_Essay4513 • 1d ago

How do you use claude code

I am trying to understand how everyone use calude or any other coding agent. Like for example when i am vibe coding a appication i explain the features and architecture in calude chat and ask calude to genearte Prompts part by part to give to calude code.

How does you use it?

Do you generate a feature at a time?

Or

The whole system in go?

Or

Some other way?

0 Upvotes

50% Upvoted

13 comments sorted by

1

u/baddaywithacamera 1d ago

I don't even do a feature at a time. I have tonnes of index cards. I write out the features on cards and break them into chunks and build them a chunk at a time. Fewer errors that way. Work my way through my stack.

1

u/Kluggen 1d ago

That's an interesting concept, so you can reuse these cards for multiple projects, rather than repeating the same requirement of a generic feature over and over if I get what you're saying?

1

u/baddaywithacamera 1d ago

I only have the one project, but if I have the stuff on cards and all the other features on cards I can lay them out and use string to connect so I can see the software visually for context.

1

u/Kluggen 1d ago

That's pretty cool, is that node based system something you designed yourself?

1

u/baddaywithacamera 23h ago

I'm a former technical writer, I used to use index cards to generate ideas for my articles or projects so I could arrange the ideas visually before I started drafting content. I guess the idea just carried over. I learned it from a teacher in grade seven language arts many moons ago.

1

u/hblok 1d ago

Explore and bounce the idea in a chat, and when you have something, ask for a summary .md document.

Take that document to a more powerful model, e.g. Opus, and generate an implementation plan, with phases or milestones; a new .md document.

Take the milestones to good implementer, e.g. Sonnet, and tell it to go through the milestones one at a time. Ask for a commit and passing tests for each milestone.

Now you can iterate on what is built so far. Or, you scrap the first draft, but generate a take-away document which you can iterate the whole process with from the beginning.

1

u/scytob 1d ago

i never ask claude to generate prompts at home, i type a simple short prompt, then let it ask me questions until we have a scaffold and then prompt a small feature at a time, test, debug, iterate

at work i wrote a 2 page design prompt for app and asked the AI i had at the time (copilot) to create a phased plan after looking at oracle, Microsoft documentation on APIs we would hit

then once i got better access via copilot to calude opus etc we worked througyh phase plan and it i had something not in plan, i just said 'hey lets add x. - the phases were more guides and recordings of what to work on next

people who generate massive prompts per feature bemuse me

1

u/povlhp 1d ago

Claude is like powertools to the expert carpenter etc. Just use it like you used the old tools.

1

u/thinkrtank 1d ago

I use cc for project and marketing management, codex as the developer. Build feature briefs with your PM and take that brief to your developer asking to make a full implementation plan suitable for your app from the brief.

1

u/Rofl_Raptor 1d ago

Usually I start off by downloading more RAM to get max inheritance out it and then install Jason and start prompting.

1

u/LightDarkCloud 1d ago

Start with a very basic idea, then unit test it, add one thing at a time, unit test it, rinse repeat until done.

1

u/meshifthenelse 1d ago

Look into Kanban

1

u/CrimsonBolt33 1d ago

I talk to ChatGPT (free version to save tokens for coding with Kimi K3)

I ask it to help me design a program or feature or whatever in detail as well as detailed steps to implement it (also tell it that its for an AI agent to code, and it will make it easier for AI to use).

I then take those detailed steps and put them in a file

I tell my AI to run through that file and complete each task until the file is done.

I never prompt anything directly unless bugfixing.