Using your credits efficiently while building

Credits are spent when the AI builds and edits your app. How many it takes depends on your app's complexity — and on whether you get stuck in a loop. Here are the dos and don'ts that stretch your credits the furthest.

Credits are spent when the AI is working — generating code, making changes, and fixing things while you build. Running your finished app doesn't cost credits; building and editing it does. How many credits it takes to finish an app comes down to two things: how complex the app is, and whether you get stuck repeating the same step.

Why two people spend very different amounts

• Complexity. A simple app comes together in a handful of prompts. Something with many pages, lots of data, integrations, and custom logic naturally takes more back-and-forth — that's expected, and it's normal for a bigger app to use more credits.
• Rabbit holes. This is the one that surprises people. If you get stuck re-prompting the same problem over and over, credits can add up fast without much progress to show for it. Getting unstuck early is the single biggest thing you can do to protect your credits.

Do's

• Do plan before you build. Use Plan mode to get the AI's understanding confirmed first. A clear plan means fewer rebuild cycles.
• Do give context up front. Describe the feature, the data, and the design in one prompt instead of discovering it across ten. More context in a single prompt = better output, fewer retries.
• Do build in focused steps. Add one feature or fix one thing at a time, confirm it works, then move on. Small, verified steps beat one giant prompt that's hard to get right.
• Do come up for air when you're stuck. If two or three attempts haven't moved the needle, stop. Ask the community or the OverSkill team — someone can often spot a faster path or a known workaround that saves you a pile of credits.
• Do keep a short brief. Jot down your key decisions and paste them into your prompts so nothing gets lost between sessions.

Don'ts

• Don't keep re-prompting the same broken result. Each attempt is a fresh pass that spends credits. If it's not improving, change your approach — don't repeat it louder.
• Don't pile every feature into one mega-prompt. Huge prompts are harder for the AI to get right on the first try, which leads to more correction cycles.
• Don't fight a confusing bug alone for an hour. That's exactly when to ask. A second set of eyes is cheaper than another ten build attempts.
• Don't guess at vague instructions. Make it better or fix it gives the AI little to work with. Be specific about what's wrong and what you want instead.

When you're stuck, ask — that's the move

The fastest way to save credits isn't a trick, it's a habit: when you hit a wall, pull in help instead of grinding. Share what you're building and where it's catching, and the team or other builders can usually get you unstuck quickly. You don't have to fight it alone.

Editing beats rebuilding

When you want to change something, edit the app you already have — don't rebuild it from scratch. A targeted edit is usually several times cheaper than a full rebuild, and you keep the work you'd already dialed in. See Editing vs. rebuilding — which is more credit-efficient? for when a fresh start actually makes sense.

See exactly where your credits went

Your billing page shows your credit usage broken down, so you can see what's been using them. If anything looks off, reach out to support and we'll help you make sense of it.