Give this to your coding agent

The shortest useful version is often the best.

If you already know you want to use Bootstrapware Onboard, here is the compact brief.

Copy-paste brief

Integrate Bootstrapware Onboard into this application.

@bootstrapware/onboard is an embeddable first-run setup checklist: required/optional steps, dependencies, eligibility, facts, dismiss, snooze.

Paths (do in this order):
- Path A local: createLocalAdapter, optional items/SAAS_FIRST_RUN_ITEMS. No keys. Free forever.
- Path B Hosted: omit adapter; pass flowId + publishableKey. Live writes need authorToken from our BFF.
- Path C BYO: pass OnboardAdapter AND flowId + publishableKey so published config still loads. Progress on our backend. Use onEvent for side effects (no Bootstrapware webhooks).

Important boundaries:
- Bootstrapware does NOT authenticate end users. Pass user={{ id: session.user.id }} and workspaceKey. Never invent user.id.
- Import @bootstrapware/onboard/styles.css
- Publishable keys only in the browser; secret keys (bsw_*_sec_) server-side only
- Never send host context or flags through MCP (flow config only)
- Never mint API keys via MCP. If env has no bsw_test_pub_ / bsw_live_pub_ value, STOP and ask a human to mint one at https://app.bootstrapware.co/onboard/keys
- Live publishable config needs BYO ($9.99) or Hosted ($19.99); live Hosted writes need Hosted ($19.99)
- Live Hosted: BFF mints and renews authorToken (POST /api/v1/author-tokens with secret). Widget never mints.
- Call completeStep from the host on real actions AND pass facts for reconciliation
- Hosted webhooks (if used): onboard.flow_started, onboard.item_completed, onboard.item_skipped, onboard.flow_completed, onboard.flow_dismissed, onboard.flow_snoozed, onboard.flow_resumed, onboard.progress_reset. Verify X-Bootstrapware-Signature (hex HMAC-SHA256 of raw body). Ids only.

Implementation tasks:
- Add Onboard at [ROUTE]
- Wire user + workspaceKey from session
- Choose Path A / B / C and implement
- Keep modular and aligned to the existing design system

Why this page exists

Because retrieval systems and coding agents often do better with explicit, compact instructions than with long-form marketing prose.

This page is deliberately direct.

It is not trying to persuade somebody that first-run setup matters.

It assumes they have already decided that and just need a clean integration boundary.

Longer fill-in template: Agent prompt template.

Package AGENTS.md: Agents.

Related: Onboard · Quickstart · AI coding agents · Vibe-coded SaaS · Cursor