Claude recently gave users near-unlimited access as part of a launch promotion. That kind of access unlocks a different way of working.

Write a strong prompt. Generate a complete working solution, frontend and backend, as fast as possible. Not a feature, not a component. The whole thing. Then start sculpting.

What follows is hundreds of prompt iterations, each one focused on something specific to remove or simplify. Tighten this function. Eliminate this abstraction. Consolidate these modules. Improve test coverage here. Profile this. The session gets long. The codebase gets smaller. Somewhere in that process, it gets genuinely good. This is functionally identical to how a sculptor works. You are not adding. You are revealing.

The reason this feels different from normal AI-assisted coding is the direction of control. Typically you stay in the driver’s seat. Prompt for something specific, review it, integrate it. This workflow inverts that. You let go first. Generate the full solution on purpose, then take back control gradually, refactor by refactor, decision by decision.

That is where the craft lives. Not in the generation. Anyone can generate. The craft is in the taste required to recognize good architecture when you are approaching it. Knowing which refactor matters. Knowing when something is actually done versus just smaller. That judgment does not come from the model. It comes from you.

Vibe-coding gets criticized for producing unmaintainable messes. That is true if you stop at the vibe. The mess is the raw material, not the output. The output is what you sculpt it into. The tools changed. The taste does not.