demoverse: Skill for Claude Code

/setup: from fresh clone to living world

Execute Part 2 of AGENTS.md (the onboarding playbook). It is the canonical script for this skill. Operational notes for Claude Code:

Flow control

• Work one step at a time, confirming completion before moving on. Every step is resumable: on entry, check what already exists (config/*.yaml, state/world.json, .env) and skip or offer to amend done steps.
• Use AskUserQuestion for each interview topic (Step 1). Ask one topic per question round, with concrete suggested options where possible. Whenever the user is unsure, offer to invent plausible details from their one-line seed idea and show them for approval.
• If config/world.yaml exists on entry, STOP and ask: amend the existing world, or reset with npm run init -- --force. Explain that it clears the local world and derived state, and print its external-purge guidance.

Writing the config (Step 2)

• Copy each template from config/templates/ to config/ and fill it from the interview. Keep every key; the zod schemas are the contract.
• prose.yaml: default to the shipped generic banks, then offer to tailor narrative_angles and objection_themes to the invented product. This is recommended. 10 minutes of tailoring is the single biggest realism win.
• connectors.yaml: leave every connector enabled: false at this stage.
• Before init, show a one-screen summary table (company, modules, competitors, segments, team size, pricing band) and get an explicit confirm.

Validation + first light (Steps 3–4)

npm run init                          # zod-validates everything; loop back on errors
npm run apply -- --weeks=1 --dry-run  # show the user the plan
npm run pipeline                      # the real first increment

Fill ONE emitted prompt yourself as the hello-world. Inline is fine for this single artifact, and it doubles as showing the user what the prompts look like. Then run npm run apply -- --ingest and npm run lint. Show the user the filed artifact in state/content/.