When should you use it?
- You need a small internal or hobby data app
- The data source is known and you can parse it
- You want to judge an app-building agent on a real task
Not for: Projects where every UI tweak would burn paid credits; Messy undocumented APIs you expect the agent to untangle alone
What do you need, and what do you get?
You need
- The data endpoint and a sample of its JSON
- A one-line description of the app
- A budget for agent credits
You get
- A hosted map app with search
- A clear split of what the agent did well and what you should own
How does it work, step by step?
- Give the data up frontShare the endpoint and an example response in the first prompt so it does not hunt for a public API.
- Let it scaffoldAccept the agent's package setup, components and default layout.
- Take over data debugging earlyIf it loops on the API, parse the response yourself and hand it clean data.
- Batch small tweaksMake tiny UI edits yourself where each agent request would cost time and credits.
- Publish with the agentUse the built-in hosting, and retry if the first deploy fails.
The prompt
Our own prompt, inspired by Makena Kong and written to work in Custom agent. Values in lime are placeholders.
Build a web app that shows [entities] on an interactive map with a search box. Data comes from [endpoint]; here is a sample response: [JSON]. Use an open-source map library. Show name, total raised and investor count in a popup. Do not look for other data sources. Before each change, tell me roughly how long it will take. Avoid full reloads for small edits.
Inspired by Makena Kong: Building an interactive map with Replit Agent: A software engineer tests vibe-coding efficiency. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Each small prompt took minutes and cost money; one icon fix took eight minutes.
- Full reloads after tiny changes burned credits faster than expected.
Our take
Makena Kong's useful contribution is an honest division of labor. Agents are fast at scaffolding, wiring libraries and getting something hosted, and slow and expensive when the data is unclear or the API is poorly documented. Knowing that before you start lets you plan the handoffs: give the agent clean data and the broad strokes of the interface, and keep the fiddly parsing yourself. Her experience of the agent chasing wrong fixes on a private API is common; once two or three attempts fail, take that part over rather than burning more credits. Watch spend per prompt, because it adds up quietly during debugging loops. Batch small UI tweaks into one request instead of many tiny ones. Compare the result with what you would have built alone, as she did, so you learn which jobs are actually worth delegating next time. Publish with the agent if hosting is part of the brief, then verify the live site yourself, including search and filters on real data.
Where the time goes back: Boilerplate and hosting vanish, provided you step in before the agent burns time on problems you can solve quickly.
FAQ
Was it worth it?
What would she change?
Source and credit
Inspired by Makena Kong. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Building an interactive map with Replit Agent: A software engineer tests vibe-coding efficiency
- Creator
- Makena Kong
- Published on
- DEV Community (dev.to)
- Original date
- Nov 17, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.