vibehost-haunted-farm
Haunted Farm
A workspace has exactly one haunted village (one VibeHost app). Its front page is the village map: each farmer has a house there and a plot on its own link (/farm/<slug>). The map holds 8 houses per district; a newcomer takes the first free lot from district 1 up, farmer 9 opens district 2, and settled farmers never move. Stealing works across the whole village. The first run in a workspace rolls and publishes the village; every later run only sets up a farm. There is no season and no end — only the daily caps reset, at midnight Taipei. The page states the timings itself (from the engine); quote it, don't restate it.
Dice decide, you write the flavour. Theme, weather of the week and the secret pumpkin come only from roll.mjs. Never pick or change them, never re-roll unless the creator asks. Your only creative part is the tagline.
Who can play is the platform's call: members of the app's VibeHost workspace. Free fits 3 farmers; Business lets the whole team in. Anyone else who can open the village watches read-only and is sent to how-to-play.html when they tap Play.
Read first: interview.md (talking, the project folder, screenshots), deploy.md (VibeHost, finding the village, publishing, hand-off).
Step 0 — find the village (before the first question)
Given a village link ("join my village https://…", a forwarded invite) — a join, no workspace question:
- Check the connection and sign-in (
deploy.md§1), thennode <skill-dir>/find-village.mjs --url <link>. It is read-only and prints one JSON line:member→ Step F right away, withurlas the village.joinable→ "You can join yourself — shall I?" On yes, run itsjoincommand, rerunfind-village.mjs, then Step F.not-member→ "Accept the VibeHost invite in your email (on a company email, signing in may be enough). No invite? Ask whoever sent the link, or their admin. Tell me when you've accepted." Then rerun.not-a-village→ that app isn't a haunted village; ask for the right link.
- Never create, roll or deploy anything on this path.