Tiny Vibe Studio
Status: Failed.
Your muse
Make a vibe coding studio for one owner: I type an idea for a small app, it builds and publishes that app for me, and each app it makes has a working chatbot inside it. Show my spending today, each app's status and its link. Keep this studio small: one screen to start an app and one to list them. Made-up example: an app for a pretend tide-pool club.
Done. Milestone 1 is built. Tiny Vibe Studio turns a typed idea into a live mini app with a working chatbot: Start screen with idea box and build progress, Apps screen with spending and statuses, and each published app served at its own `/app/[i…
Checks found problems
Smoke test, caps, Requirements
Done. Milestone 2 is done. R5–R8 all work end to end with their own passing tests:
Checks found problems, try 2
caps
Done. Milestone 3 is done. R9–R12 all work end to end with their own passing tests:
Checks found problems, try 3
caps
Done. Milestone 4 is done. R13–R15 all work end to end with their own passing tests:
Checks found problems, try 4
Smoke test, caps, Requirements
Done. Fix round done. The judge found a real product bug: a long model-written starter prompt rendered as a
nowrapchip ran 32px past the phone viewport. Fixed in the product two ways —starterPromptscapped at 48 characters in the plan sche…Checks found problems, try 5
caps
Done. Fix round 2 complete. Investigation first, per the guidance to fix the first failure first:
Checks found problems, try 6
caps
Done. Fix round 3 complete. The verify failure is unchanged and unactionable:
platform, checker: scripts/caps/platform.mjs is missing.Checks found problems, try 7
caps
The plan: Tiny Vibe Studio
Type an idea and get a live mini app with chatbot.
- Open the Start screen
- Type an idea for a small app in the text box
- Press Build and publish
- Watch the build move from queued to building to live
See the full plan
Who it's for
A solo owner who wants quick tiny apps for fun ideas
How it works
- Open the Start screen
- Type an idea for a small app in the text box
- Press Build and publish
- Watch the build move from queued to building to live
- Open the Apps screen to see status and live link
- Click the live link to open the new app
- Try the working chatbot inside the new app
- Check spending today at the top of the Apps screen
Screens
- Start. Type an app idea and press Build and publish, then see build progress.
- Apps. See spending today plus every app with its status, live link and chatbot check.
What goes in
- Text: Short idea for a small app, one or two paragraphs, for example the pretend tide-pool club.
What comes out
- Text: Live link URL for each published mini app.
- Text: Status per app such as queued, building, live or failed plus chatbot check.
- Text: Spending today total and remaining daily budget for the owner.
Models
Model Used for Why Muse Wonder Turn the typed idea into a small build plan for the sandbox builder It reads the free text idea like the pretend tide-pool club and returns structured title, features and chatbot behavior so the build is consistent. Limits
- For the owner only. There are no visitor accounts and no public app creation.
- Each product has a hard daily spending limit. Builds stop when the limit is reached.
- Apps made by the studio cannot themselves build or publish other apps.
- Builds run in sandboxes and can take several minutes. Status shows queued, building, live or failed.
- Child apps get their own metered token for their chatbot. Heavy chatbot use counts toward platform spend.
- No outside services. No payments, SMS, email, maps or social posting. The web version only links to the live app.
From your inspo
The person gave text only with no references. They want a small owner-only vibe coding studio that builds and publishes mini apps with chatbots and shows spending and status.
Takes
- The job of turning a typed idea into a live mini app
- The small two step flow from start to list
- The example domain of a pretend tide-pool club for the sample fixture
Cost per run: about $0.03 (est.). One Wonder planning call uses about 800 input tokens at $4 per M ($0.0032) and about 1500 output tokens at $20 per M ($0.03) for a total of about $0.0332, rounded to $0.033. Child app builds and chatbot chats bill to platform meters separately.
What you asked for 0 of 15 checked and working
- R1: Owner can type an idea for a small app in a text box on the Start screen. Not checked yet Its test passed. The judge hasn't looked yet.
- R2: Studio builds the requested small app in an owner sandbox. Not checked yet Its test passed. The judge hasn't looked yet.
- R3: Studio publishes the built app and gives the owner a live link. Not checked yet Its test passed. The judge hasn't looked yet.
- R4: Each app the studio makes includes a working chatbot inside it. Not checked yet Its test passed. The judge hasn't looked yet.
- R5: Studio shows the owner spending today with total used and limit left. Not checked yet Its test passed. The judge hasn't looked yet.
- R6: Apps list shows each app status such as queued, building, live or failed. Not checked yet Its test passed. The judge hasn't looked yet.
- R7: Apps list shows each app live link that opens the published app. Not checked yet Its test passed. The judge hasn't looked yet.
- R8: Studio has one Start screen to start an app. Not checked yet Its test passed. The judge hasn't looked yet.
- R9: Studio has one Apps screen to list apps. Not checked yet Its test passed. The judge hasn't looked yet.
- R10: Owner can move between Start and Apps screens from a simple header. Not checked yet Its test passed. The judge hasn't looked yet.
- R11: Apps list with names, ideas, status, links and creation time is still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
- R12: Before any app exists the Apps screen shows an empty state with an example prompt for the pretend tide-pool club. Not checked yet Its test passed. The judge hasn't looked yet.
- R13: Failed builds show an error state with reason and a retry button. Not checked yet Its test passed. The judge hasn't looked yet.
- R14: Owner can edit the saved display name for an app in the list and the new name is still there after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
- R15: Owner can delete a saved app entry from the list and the list stays without that entry after a reload. Not checked yet Its test passed. The judge hasn't looked yet.
This build didn't ship.
The product did not pass its checks after 3 fix rounds, so it was not deployed.
A broken product is never shown as working. Muse Code's notes are in its steps.