Wasting money credits

Im already on the second day to create a leaderboard for a game. simple table to record the game scores and show in the webapp…

32$ and nothing

Sometimes I think the errors its only for the user to spend more credits.

If I ask not to put placeholders in the leaderboard with fake scores why the agent is putting fake scores there.
The app is not working, and the agent says its all good.

What are the errors? How have you tried to fix them?

I delete database, and when i create again, come always with the same error.
Unexpected error happened 😕

7a90b693df374203b25c97f09eff6cae

We’re already looking into it! Feel free to reach out to our support team, make sure to copy error ID

Nothing in the console log?

Can you describe in detail what you’re trying to do? Perhaps we can help you with the prompting.

Well I create an game hub app, with 6 games, I want the leaderboards for each game in the database…simple right!!

I moved the project to claude code and now is working well, but I dont have database yet…

So my question for you guys…

Now that my app is working, each leaderboard is showing the scores for the respective game…I’ll push to github, from github, Ill pull to replit…and then what should I prompt to have a database that record all score from all users, and the users data.

(I still need to implement stripe)

Since database is a built in native integration you can ask Replit Agent to add a database. More details here: Replit Docs

You will need user auth as well. There are some built in integrations you can try too.

More details on auth here: Replit Docs

1 Like

It can be hard getting started. I know that using the high powered Agent options burns through a lot of $$ very quickly, so have a look if that is turned on. For relatively straightforward issues you likely don’t need it.

Also make sure you are using Agent for thinking tasks and to the Assistant. A bit confusing having 2 things to use but they have different capabilities and costs.

Also having good prompts really does help. Here is an example prompting system that was suggested to me that seems to help. Step 1, using this prompt to try and fix prblems:

I am trying to find a fix for the following issue:
<ISSUE>
I want you to do the following:
Research deeply across my codebase. Research only, do not make any changes.
Find what files and functions are related to the problems and goals I outlined above.
Assess reasons for why the feature might not be working or why it might not work. If I am asking for something impossible or a task you do not have the tools to accomplish, let me know.
Develop a plan to fix it. Do not make any changes until I have given explicit instructions to do so.
If there is any aspect of the problem that is unclear ask clarifying questions before progressing further.
If there are different ways to implement the changes and some of them have implications for future code changes then ask which options are preferable.
If the plan involves changes to the database also review the database reset and sample data load scripts and the sample data to ensure that they are still valid after the proposed changes and include plans to update these files as well.
Write this entire plan and report into a file called “Instructions.md” in my project, overwriting any existing file.
Do not make any changes to the code without explicit confirmation to do so.

Then have a look in the Instructions.md file and review it. then use this prompt once you are happy with what it is planning:

I want you to fix and implement (s-h-o-r-t description about goal or bug you have). Before you begin, please carefully read and adhere to the plan and insights found in the “Instructions.md” file and follow those instructions. If there is something in those Instructions that might stop you, let me know and guide me on how to unblock you.

See if that approach helps.

2 Likes

Be the boss of your agent: this is the biggest lesson I feel needs passing on to vibe coders. So your approach is great @CraigRT.

One small thing though: as far as I know, instructions.md is not an official file that Replit Agent is trained to look for. You should use replit.md for that.

2 Likes

I take is that the Replit.md file is an ongoing document about the project whereas I am using Instructions.md for one specific issue and fix and it will be overwritten/deleted after.

2 Likes

Ah got you. yes as long as you explicitly tell it to look at your md file than that’s a good plan.

Whereas agent will automatically look at replit.md - so better for instructions that are persistent over the longer term.

2 Likes