source/skills/reconfigure/SKILL.md
Re-ask the voice and beneficiary questions and update .bodega.md. Useful when the user's preference changes or the store is being handed off to someone new.
npx skillsauth add mitcheman/bodega reconfigureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Change the voice or beneficiary settings on an existing project. Non-destructive — only touches preferences, never the store itself.
Read .bodega.md. If absent, say:
This project doesn't have Bodega set up yet. Run
{{command_prefix}}bodega:setupfirst.
In the currently-configured voice:
Current config:
mode: developer
handoff: true
merchant: [email protected]
operator: [email protected]
Your current settings:
How I talk to you: developer-mode (tech terms) Who's running the store: your partner ([email protected])
What do you want to change?
a. how I talk to you (voice) b. who's running the store (beneficiary) c. both d. actually nothing — cancel
Re-ask the voice question:
How should I talk?
- developer — tech terms, full logs, concise
- simple — plain English, tell me what to click
Update .bodega.md:
mode: simple # or developer
Who's running the store day-to-day?
- me — I'm the business owner
- someone else — I'm setting this up for them
If "someone else":
What's their email?
Validate format.
Update .bodega.md:
handoff: true
merchant:
email: [email protected]
If the beneficiary changed, offer to send them a fresh magic link:
Send a welcome email + login link to the new person now?
If yes, invoke {{command_prefix}}bodega:admin (it handles the handoff
package + email).
✓ Updated. New config:
mode: simple
handoff: true
merchant: [email protected]
✓ Got it. I'll talk to you in simple voice from now on.
Want anything else? Or we're done?
.bodega.md at invocation.development
Roll back a Bodega-provisioned project. Walks the user through removing the Vercel project, blob store, GitHub repo, Stripe webhook, and (optionally) `.bodega.md` itself. The merchant's Stripe account stays — that's their data.
business
Reports the current state of the store — what's set up, what's pending, what the URLs are, and what to do next.
testing
First-time Bodega setup. Detects whether the folder has an existing project (adapt) or is empty (greenfield), asks about voice and beneficiary, writes .bodega.md, and orchestrates the full flow through hosting, payments, deploy, and admin.
development
Walks the merchant through Stripe onboarding, captures their API keys, and writes them to Vercel env vars. Handles the common case where KYC takes days by supporting a preview-mode deploy path.