vybekiit 0.7.28 → 0.7.29

package/dist/global-guidance/language.md

@@ -267,9 +267,9 @@ its layout automatically for RTL visitors — you don't need to do anything spec
 <!-- source: @vybekiit/agent-kit renderToneSection() — keep in sync -->
 
 - Warm, confident, brief. You're the expert handling the hard parts.
-- One step at a time. Never a wall of instructions.
+- Give the buyer one manual step at a time. Continue work you can do yourself.
 - Always end a manual step by telling them **exactly** what to click/copy and what you'll do next.
-- Celebrate wins.
+- Celebrate verified wins. Vocabulary describes actions; it never proves completion. Inspect before saying work is saved, connected, checked, or online.
 - **No em dashes (`—`).** They read like AI filler. In chat and body copy, use a period, comma, colon, or parentheses instead. **UI titles, nav labels, and section headings:** short phrases only; no em dash and no trailing period, comma, or ellipsis. Split into two lines or two i18n keys instead. Hyphens in compound words (`build-time`) are fine.
 <!-- vybekiit:generated:end tone -->
 
@@ -278,15 +278,15 @@ its layout automatically for RTL visitors — you don't need to do anything spec
 
 | Don't say (jargon) | Say instead (plain) | Why it matters to them |
 |---|---|---|
-| test / unit test | I checked it still works | reassures them without test-suite vocabulary |
+| test / unit test | check that it works | reassures them without test-suite vocabulary |
 | TDD / tests-first | *(agent-internal — never say)* | agent-internal — never say |
 | linter / formatter / Biome | tidying the code | usually invisible; only mention if they ask why you paused |
-| quality smoke / typecheck | everything checks out | onboarding and pre-ship reassurance |
+| quality smoke / typecheck | check the app for problems | onboarding and pre-ship reassurance |
 | pull request / PR | a safe copy for the checker to review | when saving via branch before merge |
 | CI / GitHub Actions | the automatic checker online | never name GitHub Actions |
 | CD / deploy pipeline | putting updates online automatically | only if they overhear pipeline talk |
-| Playwright / E2E / headless browser | I walked through your app like a visitor would | UI walkthrough without tool names |
-| back up / save progress online | I saved your progress online | never say GitHub — stays in service ban list |
+| Playwright / E2E / headless browser | check the app like a visitor would | UI walkthrough without tool names |
+| back up / save progress online | save a copy online | never say GitHub — stays in service ban list |
 | worktree | *(agent-internal — never say)* | agent-internal — never say |
 | husky / hook / pre-push | *(agent-internal — never say)* | agent-internal — never say |
 <!-- vybekiit:generated:end sdlc-vocabulary -->

package/dist/global-skills/add-ai/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-ai

package/dist/global-skills/add-analytics/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-analytics

package/dist/global-skills/add-blog/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-blog

package/dist/global-skills/add-crud/SKILL.md

@@ -5,10 +5,18 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/backend/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-crud
 
+> Agent-only: follow the Persistent features sequence in `.vybekiit/agent/session-bootstrap.md`. Reuse the relevant catalog presets before adding app-owned extensions, and record structural and behavioral evidence separately.
+
 **Goal:** scaffold create/read/update/delete routes for a resource.
 
 

package/dist/global-skills/add-files/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-files

package/dist/global-skills/add-images/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-images

package/dist/global-skills/add-language/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-language

package/dist/global-skills/add-notifications/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-notifications

package/dist/global-skills/add-realtime/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-realtime

package/dist/global-skills/add-route/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/backend/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-route

package/dist/global-skills/add-search/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-search

package/dist/global-skills/add-signin/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-signin

package/dist/global-skills/add-teams/SKILL.md

@@ -5,10 +5,18 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-teams
 
+> Agent-only: follow the Persistent features sequence in `.vybekiit/agent/session-bootstrap.md`. Reuse the relevant catalog presets before adding app-owned extensions, and record structural and behavioral evidence separately.
+
 **Goal:** the builder can invite teammates and work in shared organizations.
 
 **Contract:** one action at a time · verify-before-advance · plain language (`language.md`) ·
@@ -33,9 +41,8 @@ have access.
    accounts.
    **Verify:** a user can sign in.
 
-2. **Agree on the team shape, in plain words.** Ask who can invite whom (e.g. "the owner invites
-   people by email"). You decide the data model; they confirm the behavior.
-   **Verify:** read the behavior back in one sentence and get a yes.
+2. **Choose the team behavior from the request.** Infer who can invite whom and reuse the membership preset. Ask only for a missing product decision.
+   **Verify:** describe the behavior in one sentence and continue authorized work.
 
 3. **Use the shipped interactive teams surface (Tier-1).** Do not invent a blank page. Keep every
    `TODO(vybekiit)` seam and wire it in the next step.

package/dist/global-skills/add-upload/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/backend/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: add-upload

package/dist/global-skills/back-up-my-code/SKILL.md

@@ -1,15 +1,21 @@
 ---
 name: back-up-my-code
-description: "the builder's project is saved on GitHub so they never lose work. Use when the vibe coder says something like: save my code; back up; put it on github."
+description: "the builder's project is saved on GitHub at a verified checkpoint. Use when the vibe coder says something like: save my code; back up; put it on github."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: back-up-my-code
 
-**Goal:** the builder's project is saved on GitHub so they never lose work.
+**Goal:** the builder's project is saved on GitHub at a verified checkpoint.
 
 **Contract:** one action at a time · verify-before-advance · plain language (`language.md`) ·
 translate every error · celebrate. You handle git and GitHub; the builder only signs in or creates an account when asked.
@@ -18,7 +24,12 @@ translate every error · celebrate. You handle git and GitHub; the builder only
 
 ## Steps
 
-1. **Explain in one line.** *"I'll save your project online so you can't lose it."*
+0. **Status questions require inspection only.** For "Is my work saved?", inspect changed files,
+   the current commit, and the remote branch. Say which changes are local and which are online.
+   Do not create a repository or push for a status question. For an explicit backup request,
+   continue below. Reuse the existing repository and preserve unrelated changes.
+
+1. **Explain in one line.** *"I'll save a copy of your project online."*
 
 2. **GitHub account.** If they don't have one, walk them through creating one at github.com — **one step at a time** in plain words. `gh` cannot create accounts for them.
 
@@ -26,12 +37,12 @@ translate every error · celebrate. You handle git and GitHub; the builder only
    **Verify:** `gh auth status` shows signed in.
 
 4. **Save it.** Initialize the repo (if needed), commit all safe files (never `.env`), create a **private** GitHub repo, and push.
-   **Verify:** files visible on github.com.
+   **Verify:** the remote branch commit matches the intended local commit, the repository is private, and a fresh clone installs and passes the relevant app check. Check uncommitted and untracked work separately; never claim it was included unless it was.
 
 5. **Give them the link.** Share the repo URL in plain words — *"Your project is saved here."*
    🎉 *Celebrate* — their work is backed up.
 
-6. **Later saves.** For ongoing checkpoints, use `ship-via-pr-vybekiit.md` — the **online checker** runs on all three operating systems before merge. Builder hears: *"Your latest work is saved and checked."*
+6. **Later saves.** For ongoing checkpoints, use `ship-via-pr-vybekiit.md` — the **online checker** runs on all three operating systems before merge. Say "Your latest work is saved and checked" only after verifying that checkpoint and its checks.
 
 ## If anything breaks
 

package/dist/global-skills/buy-domain/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: buy-domain

package/dist/global-skills/check-safety/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: check-safety

package/dist/global-skills/configure-capabilities/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/mobile/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: configure-capabilities

package/dist/global-skills/connect-account/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/mobile/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: connect-account

package/dist/global-skills/connect-account-backend/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/mobile/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: connect-account (mobile / extension)

package/dist/global-skills/design-my-data/SKILL.md

@@ -5,10 +5,18 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: design-my-data
 
+> Agent-only: follow the Persistent features sequence in `.vybekiit/agent/session-bootstrap.md`. Reuse the relevant catalog presets before adding app-owned extensions, and record structural and behavioral evidence separately.
+
 **Goal:** figure out what the app should remember before wiring storage.
 
 **Contract:** one action at a time · verify-before-advance · plain language (`language.md`) ·
@@ -20,18 +28,17 @@ translate every error · celebrate. You do all the planning; the builder describ
 
 ## Steps
 
-1. **Learn what users do.** From the product description, ask what must be saved (not a schema interview).
+1. **Learn what users do.** Infer what must be saved from the product description. Ask only when a missing product decision changes the behavior.
    **Verify:** you can list 1–3 things the app remembers.
 
 2. **Plan the shape (agent-only).** Run `vybekiit plan-data-model entities.json` with entities from step 1.
    **Verify:** plan has collections and a `buyerSummary` sentence.
 
 3. **Read back in one sentence.** Use `renderDataModelSummary(plan)` — plain words only.
-   **Verify:** builder says yes.
+   **Verify:** the plan covers the requested behavior; continue when the request supplies enough intent.
 
 4. **Route to save-data.** Hand off to `save-data.md` to provision the database, wire CRUD, and test.
-   When `DATA_PROVIDER=supabase`, pick an RLS preset from `infra/supabase/policies/` (user-owned,
-   team-owned, or public-read) and include it in the migration — see `harden.md` step on database rules.
+   Use the validated table access contracts in the selected presets and app extensions. Test both allowed and denied actions through the selected provider.
    **Verify:** `save-data` definition of done.
 
 ## When to skip
@@ -41,7 +48,7 @@ instead of running this skill separately.
 
 ## Definition of done
 
-Builder agreed on what the app remembers and `save-data` is running with a clear target shape.
+The plan matches what the builder asked the app to remember and `save-data` is running with a clear target shape.
 
 ## After completing this skill
 

package/dist/global-skills/doctor/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: doctor
@@ -19,15 +25,16 @@ translate every error · celebrate the fix. The builder should mostly just watch
 
 Work through these in order. Stop as soon as you find and fix the problem, then verify.
 
-1. **Reproduce.** Ask the builder, in one question, what they were doing when it broke — **unless**
-   the prompt starts with `[VybeKiit Report]` or they say they used Report mode (Option+Shift+R,
-   clicked an element, sent a note). In that case context is pre-filled; skip this question.
+1. **Reproduce the reported symptom.** Use the prompt, current preview URL, process logs,
+   and recent changes first. For a page that will not open, check that exact URL and process.
+   A stopped preview does not prove lost files. Inspect files and backup status separately.
+   Ask one question only when the failing action or location cannot be determined.
 
-2. **Check the basics, in order:**
+2. **Check only the basics relevant to the reproduced failure:**
    - **Secret settings:** are the required values in `.env` present and non-empty? (Use
      `.env.example` as the checklist.) Missing/blank is the #1 cause. Never read `.env` values aloud —
      follow `env-secrets-vybekiit.md`. Doctor verifies `.cursorignore` lists `.env`.
-   - **Tools installed + signed in:** run `vybekiit doctor` — it installs your AI assistant (Claude Code,
+   - **Tools installed + signed in:** run `vybekiit doctor` only when tool setup is the cause. It installs your AI assistant (Claude Code,
      Codex, or Cursor), the skills installer, and whichever cloud tools your settings use (database, hosting,
      Google sign-in). It also checks official platform skills are present. If it reports "not signed
      in yet," walk the builder through the one sign-in command it prints (a browser window opens;
@@ -48,12 +55,12 @@ Work through these in order. Stop as soon as you find and fix the problem, then
 3. **Fix the one thing.** Make the smallest change that addresses the actual cause. If it's a value
    the builder must supply, ask for **just that one**, with exactly where to get it.
 
-4. **Still stuck on generated code?** If the fix lives in scaffolded kit code and basics are green,
-   follow the maintainer **diagnose** workflow internally (`~/.claude/skills/diagnose/SKILL.md` or
-   equivalent) — never expose that skill name to the builder. Translate the outcome to one plain fix.
+4. **Still stuck?** Inspect the relevant project instructions and official documentation.
+   Do not assume a machine-global maintainer skill is installed. Record the concrete blocker
+   and continue independent work that does not depend on it.
 
 5. **Verify the fix.** Re-run the thing that was broken. Confirm it works now.
-   If the app is already online, ask: *"Want me to put this fix online now?"* (contract rule ⑧).
+   If the app is already online and publishing was not already authorized, ask: *"Want me to put this fix online now?"* (contract rule ⑧).
    Don't say "fixed" until the live URL reflects the change — or the builder said to wait.
    🎉 *Celebrate* — and tell them in one sentence what it was, in plain words.
 

package/dist/global-skills/go-live/SKILL.md

@@ -5,6 +5,12 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: go-live

package/dist/global-skills/harden/SKILL.md

@@ -5,10 +5,18 @@ metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: harden
 
+> Agent-only: follow the Persistent features sequence in `.vybekiit/agent/session-bootstrap.md`. Reuse the relevant catalog presets before adding app-owned extensions, and record structural and behavioral evidence separately.
+
 **Goal:** the builder's app is protected against the common attacks every app faces — someone
 hammering the login to guess passwords, bots flooding requests, and other sites secretly making
 requests on a visitor's behalf. By the end, protection is on and confirmed, in plain words.

package/dist/global-skills/manifest.json

@@ -148,5 +148,8 @@
     "wrangler",
     "xcode-project-setup"
   ],
+  "resources": [
+    "vybekiitReferences"
+  ],
   "count": 147
 }

package/dist/global-skills/onboarding/SKILL.md

@@ -1,15 +1,23 @@
 ---
 name: onboarding
-description: "take the vibe coder from \"I just bought this\" to **their app running and visible in front of. Use when the vibe coder says something like: set up my app; let's start; get me going; just bought."
+description: "take the builder from \"I just bought this\" to **their app running and visible in front of. Use when the vibe coder says something like: set up my app; let's start; get me going; just bought."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---
 
+Prefer the current project instructions and matching project skill when inside a kit app.
+Outside a kit app, resolve guidance relative to this skill directory: ../vybekiitReferences/web/.
+That folder contains language.md, AGENTS.md, CODE-STYLE.md, agent/ and platform-skills/.
+Bare wrapper filenames refer to platform-skills/ there. Do not assume project code or recipe files exist globally.
+Inspect an existing app before changing it. Scaffold a new kit app only when the builder asked for a new app.
+
 <!-- vybekiit:generated:buyer-skill-stub -->
 
 # Skill: onboarding
 
-**Goal:** take the vibe coder from "I just bought this" to **their app running and visible in front of
+> Agent-only: follow the Persistent features sequence in `.vybekiit/agent/session-bootstrap.md`. Reuse the relevant catalog presets before adding app-owned extensions, and record structural and behavioral evidence separately.
+
+**Goal:** take the builder from "I just bought this" to **their app running and visible in front of
 them** in this one session. This is the keystone — the moment that proves the purchase was worth it.
 
 **Contract:** one action at a time · verify-before-advance · plain language (`language.md`) ·
@@ -31,17 +39,17 @@ translate every error · celebrate. Decide all technical choices yourself.
    *"In one sentence, what do you want to build?"* Use their answer to tailor the starter page later.
    Keep the conversation about their idea.
 
-1b. **One-time planning offer** (skip if `.vybekiit/state/planning-intro-seen` exists).
-   Ask: *"Before we start building — want to **think it through together** first? I'll ask one question
-   at a time until we're totally aligned. Or we can jump straight to building."*
-   - **Yes** → run `plan-my-idea.md` with their one-sentence answer as seed; when done, continue to
-     step 2.
-   - **No** → continue to step 2.
-   Create `.vybekiit/state/planning-intro-seen` (any content) so this offer never repeats.
+1b. **Keep the requested goal.** If the builder asked for working behavior, carry that goal
+   through setup and implement it. Offer planning only when they ask to plan or a missing product
+   decision would change the work. Do not replace a booking flow with a personalized headline.
 
 2. **Set up the tools, then get the preview running.**
-   First run `vybekiit doctor` — it installs the tools the app will need (for the database and for
-   putting the app online) so the vibe coder never configures anything. It may say a tool "isn't signed
+   In an empty folder, use `vybekiit create app --web <destination>` before running project
+   checks. If setup has already written files such as `.env`, preserve them and choose an empty
+   child folder for the scaffold. Do not delete existing files to make the command accept a path.
+   Inspect an existing app and reuse its setup instead of scaffolding over it.
+   Then run `vybekiit doctor` — it installs the tools the app will need (for the database and for
+   putting the app online) so the builder never configures anything. It may say a tool "isn't signed
    in yet" — that's fine for now; sign-in happens later, only when a step needs it (one browser click
    each). Then install the project's building blocks. Check the URL printed by setup and the
    project's running processes. Reuse a preview only after confirming it serves this app.
@@ -64,17 +72,24 @@ translate every error · celebrate. Decide all technical choices yourself.
 
 3. **Show them their app.**
    Give them the verified preview link from this run and tell them what they'll see.
-   **Verify:** ask them to confirm they can see the page. Don't continue until they say yes.
+   **Verify:** open the page in a browser yourself. Continue the requested work; ask the builder only if you cannot verify what they see.
    🎉 *Celebrate* — their app is alive.
    Mention Report mode once: *"If something looks wrong, press Option+Shift+R (Alt+Shift+R on
    Windows), click it, tell me what's off — I'll get the details automatically."*
 
 4. **Make it theirs.**
-   Edit the starter page to reflect the one sentence from step 1 (headline + intro). Keep it simple.
-   **Verify:** the preview updated; they confirm it looks like their idea.
+   Implement the requested behavior from step 1 using the existing app. A class-booking request needs a class list and a working booking flow, not only a headline.
+   Necessary capabilities are part of the original request: apply `save-data` for shared information
+   and the matching access skill when needed. Do not offer these as optional next goals while the
+   requested behavior depends on them. Reuse existing authorized connections before asking for access.
+   **Verify:** exercise the requested behavior in the browser, including saved changes after reload
+   and from a second browser when people share information. Test allowed and denied actions and
+   business limits. A successful page load or unrelated passing tests do not prove the feature.
+   Success messages must describe completed actions; do not promise an email without sending one.
+   Explain any actual access blocker and the part still incomplete.
 
 5. **Offer the next goal.**
-   Ask what they want next and route via `goal-index.md`:
+   Only after the original requested behavior passes its checks, ask what they want next and route via `goal-index.md`:
    - take money → `setup-payments`
    - put it online for real → `go-live`
    - let people sign in → `add-signin`
@@ -87,8 +102,9 @@ Stop the steps and run `doctor`. Never show a raw error — say what happened an
 
 ## Definition of done
 
-The vibe coder has seen their own app running and personalized, and knows the next thing they can ask
-for. Save progress for them (don't make them think about it).
+The requested behavior works and has passed its browser and behavior checks, or the exact blocked
+part is recorded as incomplete. A personalized preview alone completes only a preview request.
+Record progress locally. Claim an online backup only after verifying the remote commit.
 
 ## After completing this skill