vybekiit 0.7.29 → 0.7.32

package/dist/global-skills/vybekiitReferences/web/platform-skills/deploy-vercel-vybekiit.md

@@ -10,11 +10,11 @@
 
 ## Kit wiring
 
-1. Set `HOSTING_PROVIDER=vercel` in `.env` (agent decides — builder never picks hosts)
+1. Set `HOSTING_PROVIDER=vercel` in `settings.env` (agent decides — builder never picks hosts)
 2. Call `resolveHosting()` from `@vybekiit/deploy` — returns Vercel adapter
 3. Supply a `VercelRunner` that executes the adapter's vercel action (go-live skill owns the shell)
 4. Secret settings: `VERCEL_TOKEN` in `.env`; optional `VERCEL_ORG_ID`, `VERCEL_PROJECT_ID` after link
-5. CLI auth: token-based (`VERCEL_TOKEN`) or `vercel login` for interactive link — see ADR-0006
+5. CLI auth: token-based (`VERCEL_TOKEN`) or `vercel login` for interactive link
 
 ## Verify-before-advance
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/env-secrets-vybekiit.md

@@ -8,6 +8,7 @@
 2. **Reference keys from `.env.example` only** — say *"the payment key in your secret settings file"* using the plain label from `.env.example` comments, not the raw value.
 3. **If the builder pastes a secret in chat**, warn once: *"Don't paste secrets here — paste it into your secret settings file on your machine instead."* Then guide them to open `.env` locally.
 4. **Doctor must pass** `.cursorignore` listing `.env` — run `vybekiit doctor` if unsure.
+5. **Settings vs secrets.** `settings.env` holds settings that are not secret (which services the app uses, public ids, web addresses) and is saved with the code. A key listed there is set there. Never put a secret in `settings.env`; secrets and private values stay in `.env`.
 
 ## What agents can see
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/extend-capabilities-vybekiit.md

@@ -82,7 +82,7 @@ Ask exactly once:
 | **Codex** | `~/.agents/skills/<name>/SKILL.md` | `--agent codex` |
 | **Fallback** | `~/.agents/skills/<name>/SKILL.md` | omit `--agent` |
 
-Detect tool: Cursor if `.cursor/rules/vybekiit.mdc` exists; else Claude if `CLAUDE.md` session; else Codex via `AGENTS.md`.
+Detect tool: Cursor if `.cursor/rules/vybekiit.mdc` exists; else Claude Code if `.claude/settings.json` exists; else Codex via `AGENTS.md`.
 
 Global install via skills.sh when upstream exists:
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/i18n-vybekiit.md

@@ -1,3 +1,3 @@
 # i18n-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/i18n` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/i18n` — see package README.

package/dist/global-skills/vybekiitReferences/web/platform-skills/jobs-vybekiit.md

@@ -1,3 +1,3 @@
 # jobs-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/jobs` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/jobs` — see package README.

package/dist/global-skills/vybekiitReferences/web/platform-skills/kv-vybekiit.md

@@ -1,3 +1,3 @@
 # kv-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/kv` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/kv` — see package README.

package/dist/global-skills/vybekiitReferences/web/platform-skills/lemon-squeezy-vybekiit.md

@@ -13,7 +13,7 @@
 2. Dashboard provisioning via `@vybekiit/browser-automation` **`ls` target** (codename fresh-squeezy):
    - `vybekiit-automate ls standby` — builder signs in only (`$HOME/.ls-chrome-profile`)
    - `vybekiit-automate ls setup --json --name … --price-cents … --mode test|live --webhook-url …`
-3. Write CLI JSON to `.env`: `LEMONSQUEEZY_API_KEY`, `LEMONSQUEEZY_STORE_ID`, variant ID, webhook secret
+3. Save the CLI JSON: `LEMONSQUEEZY_API_KEY` and webhook secret to `.env`, `LEMONSQUEEZY_STORE_ID` and variant ID to `settings.env`
 4. Webhook route at `app/api/webhook/route.ts`; fulfillment in `src/lib/fulfillment.ts`
 5. Replace `TODO(vybekiit): … — skill: setup-payments` markers
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/mongodb-vybekiit.md

@@ -1,6 +1,6 @@
 # Platform wrapper: MongoDB Atlas (agent/maintainer only)
 
-**Agent-only.** Not invoked by buyer `save-data`. Use when `.env` already has `DATA_PROVIDER=mongodb`.
+**Agent-only.** Not invoked by buyer `save-data`. Use when `settings.env` already has `DATA_PROVIDER=mongodb`.
 
 ## Official upstream
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/notifications-vybekiit.md

@@ -1,3 +1,3 @@
 # notifications-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/notifications` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/notifications` — see package README.

package/dist/global-skills/vybekiitReferences/web/platform-skills/observability-vybekiit.md

@@ -7,7 +7,7 @@
 - Import `log` from `src/lib/logger.ts` (wraps `@vybekiit/core` `createLogger`).
 - **Development:** `debug` and `info` print automatically.
 - **Production:** only `warn` and `error` print — no builder configuration needed.
-- Optional override: `LOG_LEVEL` in `.env` (agent-only; never ask the builder to set it).
+- Optional override: `LOG_LEVEL` in `settings.env` (agent-only; never ask the builder to set it).
 - API routes: `const routeLog = log.child({ requestId })` when correlating a request.
 
 ```ts

package/dist/global-skills/vybekiitReferences/web/platform-skills/paypal-vybekiit.md

@@ -13,7 +13,7 @@
 2. Builder completes PayPal OAuth once when MCP prompts (sandbox endpoint by default)
 3. Agent provisions products/invoices via PayPal MCP write tools as needed
 4. Payments via `@vybekiit/payments` → `resolvePaymentProvider()` when `PAYMENTS_PROVIDER=paypal`
-5. Set `PAYPAL_CLIENT_ID`, `PAYPAL_CLIENT_SECRET`, and webhook id in `.env`
+5. Set `PAYPAL_CLIENT_SECRET` in `.env`, and `PAYPAL_CLIENT_ID` and webhook id in `settings.env`
 6. Webhook route at `app/api/webhook/route.ts`; fulfillment in `src/lib/fulfillment.ts`
 7. Replace `TODO(vybekiit): … — skill: setup-payments` markers
 8. Switch MCP URL to production (`https://mcp.paypal.com/http`) only after sandbox checkout verified

package/dist/global-skills/vybekiitReferences/web/platform-skills/realtime-vybekiit.md

@@ -1,3 +1,3 @@
 # realtime-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/realtime` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/realtime` — see package README.

package/dist/global-skills/vybekiitReferences/web/platform-skills/registrar-vybekiit.md

@@ -33,4 +33,4 @@ On success, write the returned `env` keys to `.env`, then run `vybekiit doctor`
 
 ## Package
 
-`@vybekiit/browser-automation` — ADR-0021.
+`@vybekiit/browser-automation`.

package/dist/global-skills/vybekiitReferences/web/platform-skills/search-vybekiit.md

@@ -1,3 +1,3 @@
 # search-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/search` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/search` — see package README.

package/dist/global-skills/vybekiitReferences/web/platform-skills/sentry-vybekiit.md

@@ -10,7 +10,7 @@
 
 ## Kit wiring
 
-1. Set in `.env`:
+1. Set in `settings.env`:
    - `OBSERVABILITY_PROVIDER="sentry"`
    - `SENTRY_DSN="<from Sentry dashboard>"`
 2. Confirm `instrumentation.ts` exists (calls `resolveObservabilityProvider`).

package/dist/global-skills/vybekiitReferences/web/platform-skills/seo-vybekiit.md

@@ -1,8 +1,6 @@
 # seo-vybekiit
 
-Use `resolveSeoProvider()` from `@vybekiit/seo` — see package README and ADR-0012.
-
-Canonical GEO/SEO patterns: `docs/positioning/seo-geo-plan.md` (maintainer repo).
+Use `resolveSeoProvider()` from `@vybekiit/seo` — see package README.
 
 ## Buyer app wiring
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/supabase-vybekiit.md

@@ -17,7 +17,7 @@
 2. Builder completes Supabase OAuth once when MCP prompts on first use
 3. Data access via `@vybekiit/db` → `resolveDataProvider()` — never direct Supabase client in UI
 4. After `supabase login`, agent runs programmatic project create (see `doctor` / onboarding)
-5. Write `SUPABASE_URL`, `SUPABASE_ANON_KEY`, service role to `.env`
+5. Write `SUPABASE_URL` and `SUPABASE_ANON_KEY` to `settings.env`, the service role key to `.env`
 6. Migrations under `infra/`; RLS reviewed; service role server-side only
 7. For auth: also set `DATABASE_URL` (Postgres connection) for better-auth — see `better-auth-vybekiit.md`
 

package/dist/global-skills/vybekiitReferences/web/platform-skills/tenancy-vybekiit.md

@@ -1,3 +1,3 @@
 # tenancy-vybekiit
 
-Use `resolve*Provider()` from `@vybekiit/tenancy` — see package README and ADR-0012.
+Use `resolve*Provider()` from `@vybekiit/tenancy` — see package README.

package/dist/global-skills/web-to-native/SKILL.md

@@ -3,6 +3,7 @@ name: web-to-native
 description: Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, window) map to native. This is the end-to-end migration guide; use the `use-dom` skill for the DOM-component mechanism itself.
 version: 1.0.0
 license: MIT
+disable-model-invocation: true
 ---
 
 # Web to Native

package/dist/global-skills/workers-best-practices/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: workers-best-practices
 description: Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
+disable-model-invocation: true
 ---
 
 Your knowledge of Cloudflare Workers APIs, types, and configuration may be outdated. **Prefer retrieval over pre-training** when writing or reviewing Workers code.
@@ -17,7 +18,7 @@ Read the sections relevant to the task:
 | [Runtime patterns](references/runtime-patterns.md) | Streaming, promise lifetime, request state, service calls, security, and runtime tests |
 | [Platform API checks](references/platform-apis.md) | Handler signatures, platform classes, binding access, and serialization |
 
-For missing evidence, consult [Workers best practices](https://developers.cloudflare.com/workers/best-practices/workers-best-practices/) or find the affected product in the [Cloudflare docs directory](https://developers.cloudflare.com/directory/). Use the installed Wrangler schema for config fields. A newer type package does not supersede the project's configured target.
+For missing evidence, consult [Workers best practices](https://developers.cloudflare.com/workers/best-practices/workers-best-practices/index.md) or find the affected product in the [Cloudflare docs directory](https://developers.cloudflare.com/directory/index.md). Use the installed Wrangler schema for config fields. A newer type package does not supersede the project's configured target.
 
 ## Keep Compatibility Dates Current
 
@@ -25,7 +26,7 @@ Use today's date for new Workers. Encourage periodic updates for existing Worker
 
 ## Enable Observability
 
-Enable [Workers Logs](https://developers.cloudflare.com/workers/observability/logs/workers-logs/) and [Traces](https://developers.cloudflare.com/workers/observability/traces/) when creating or preparing a Worker for production. Set `observability.enabled` and `observability.traces.enabled` to `true`; the top-level setting alone does not enable traces. Use structured JSON logging and configure sampling for the workload. During reviews, flag missing logs or traces. See the [configuration example](references/configuration.md#enable-workers-logs-and-traces).
+Enable [Workers Logs](https://developers.cloudflare.com/workers/observability/logs/workers-logs/index.md) and [Traces](https://developers.cloudflare.com/workers/observability/traces/index.md) when creating or preparing a Worker for production. Set `observability.enabled` and `observability.traces.enabled` to `true`; the top-level setting alone does not enable traces. Use structured JSON logging and configure sampling for the workload. During reviews, flag missing logs or traces. See the [configuration example](references/configuration.md#enable-workers-logs-and-traces).
 
 ## Anti-Patterns to Flag
 
@@ -56,5 +57,5 @@ Use the project's existing checks for affected Workers behavior: type-check bind
 This skill covers Workers-specific best practices and code review. For related topics:
 
 - **Durable Objects**: load the `durable-objects` skill
-- **Workflows**: see [Rules of Workflows](https://developers.cloudflare.com/workflows/build/rules-of-workflows/)
+- **Workflows**: see [Rules of Workflows](https://developers.cloudflare.com/workflows/build/rules-of-workflows/index.md)
 - **Wrangler CLI commands**: load the `wrangler` skill

package/dist/global-skills/workers-best-practices/references/configuration.md

@@ -136,4 +136,4 @@ Anti-pattern:
 console.log("Got a request to " + url.pathname);
 ```
 
-**Retrieve**: [Workers Logs](https://developers.cloudflare.com/workers/observability/logs/workers-logs/) and [Traces](https://developers.cloudflare.com/workers/observability/traces/) for current config options.
+**Retrieve**: [Workers Logs](https://developers.cloudflare.com/workers/observability/logs/workers-logs/index.md) and [Traces](https://developers.cloudflare.com/workers/observability/traces/index.md) for current config options.

package/dist/global-skills/workers-best-practices/references/platform-apis.md

@@ -44,8 +44,8 @@ Check the API and encoding at each boundary. Structured clone support does not i
 
 | Boundary | What to check |
 |----------|---------------|
-| [Queue messages](https://developers.cloudflare.com/queues/configuration/javascript-apis/#queuescontenttype) | Match the body to `contentType`: `json` requires JSON-compatible data, `text` a string, `bytes` an `ArrayBuffer`, and `v8` supports structured-clone values such as `Map` and `Date`. Check the configured compatibility date when relying on the default encoding. |
-| [Workflow step results](https://developers.cloudflare.com/workflows/build/workers-api/) | Verify the step result against the documented serialization contract and the project's Workflow types before flagging a value. |
-| [Durable Object KV storage](https://developers.cloudflare.com/durable-objects/api/sqlite-storage-api/#put-1) | `storage.put()` supports structured-clone values; do not apply a blanket ban on `Map` or `Set`. |
-| [Durable Object SQL](https://developers.cloudflare.com/durable-objects/api/sqlite-storage-api/#exec) | Check bound parameters against the SQL API's supported types. Encode objects explicitly for the intended column representation. |
-| [WebSocket messages](https://developers.cloudflare.com/workers/runtime-apis/websockets/#send) | Use `send()` with a string, `ArrayBuffer`, or `ArrayBufferView`; encode objects, for example with `JSON.stringify()`. |
+| [Queue messages](https://developers.cloudflare.com/queues/configuration/javascript-apis/index.md#queuescontenttype) | Match the body to `contentType`: `json` requires JSON-compatible data, `text` a string, `bytes` an `ArrayBuffer`, and `v8` supports structured-clone values such as `Map` and `Date`. Check the configured compatibility date when relying on the default encoding. |
+| [Workflow step results](https://developers.cloudflare.com/workflows/build/workers-api/index.md) | Verify the step result against the documented serialization contract and the project's Workflow types before flagging a value. |
+| [Durable Object KV storage](https://developers.cloudflare.com/durable-objects/api/sqlite-storage-api/index.md#do-kv-async-put) | `storage.put()` supports structured-clone values; do not apply a blanket ban on `Map` or `Set`. |
+| [Durable Object SQL](https://developers.cloudflare.com/durable-objects/api/sqlite-storage-api/index.md#exec) | Check bound parameters against the SQL API's supported types. Encode objects explicitly for the intended column representation. |
+| [WebSocket messages](https://developers.cloudflare.com/workers/runtime-apis/websockets/index.md#send) | Use `send()` with a string, `ArrayBuffer`, or `ArrayBufferView`; encode objects, for example with `JSON.stringify()`. |

package/dist/global-skills/workers-best-practices/references/runtime-patterns.md

@@ -133,7 +133,7 @@ async fetch(request: Request, env: Env): Promise<Response> {
 }
 ```
 
-**Retrieve**: `/queues/` and `/workflows/` for current APIs. For Workflow-specific rules, see [Rules of Workflows](https://developers.cloudflare.com/workflows/build/rules-of-workflows/).
+**Retrieve**: `/queues/` and `/workflows/` for current APIs. For Workflow-specific rules, see [Rules of Workflows](https://developers.cloudflare.com/workflows/build/rules-of-workflows/index.md).
 
 ### Use service bindings for Worker-to-Worker communication
 

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

@@ -1,61 +1,64 @@
 ---
 name: wrangler
 description: Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, Previews, deployment, and Cloudflare resource management.
+disable-model-invocation: true
 ---
 
 # Wrangler CLI
 
+If the project has a `cloudflare.config.ts` file, or the user has asked you to use the `cf` CLI, do not use this skill. Follow the [Cloudflare CLI documentation](https://developers.cloudflare.com/cf/index.md) instead.
+
 Use the project's Wrangler version and retrieve the relevant documentation before writing commands or configuration. CLI flags and configuration fields change; do not rely on memorized examples.
 
 ## Inspect the Project
 
-- Find the package manager, installed Wrangler version, package scripts, framework, and Wrangler config. Run commands through the project's scripts or package manager so they use its local version. Install dependencies using the existing lockfile when needed; do not silently upgrade Wrangler to match current docs. If Wrangler is not a dependency, follow the [installation guide](https://developers.cloudflare.com/workers/wrangler/install-and-update/) to add it locally.
+- Find the package manager, installed Wrangler version, package scripts, framework, and Wrangler config. Run commands through the project's scripts or package manager so they use its local version. Install dependencies using the existing lockfile when needed; do not silently upgrade Wrangler to match current docs. If Wrangler is not a dependency, follow the [installation guide](https://developers.cloudflare.com/workers/wrangler/install-and-update/index.md) to add it locally.
 - Identify the config used by the build or deploy command, including framework-generated config. Edit its source rather than generated output.
 - Establish the target account, Worker, environment, and resource before running commands that change them. For data operations, determine whether the target is local or remote.
 
 ## Retrieve What the Task Needs
 
-Use the Cloudflare MCP `docs` tool if available, or fetch the relevant linked page directly. Follow links to the specific command or product involved; avoid loading the entire reference. If a page moves, rediscover it through the [Wrangler command index](https://developers.cloudflare.com/workers/wrangler/commands/) or Cloudflare docs search.
+Use the Cloudflare MCP `docs` tool if available, or fetch the relevant linked page directly. Follow links to the specific command or product involved; avoid loading the entire reference. If a page moves, rediscover it through the [Wrangler command index](https://developers.cloudflare.com/workers/wrangler/commands/index.md) or Cloudflare docs search.
 
 | Task | Source |
 | --- | --- |
-| Discover commands and flags, including resource management, deployments, rollback, and diagnostics | Project-local `wrangler --help` and `wrangler <command> --help`; [command reference](https://developers.cloudflare.com/workers/wrangler/commands/) |
-| Edit config or add a binding | Installed `wrangler/config-schema.json` (usually under `node_modules`); [configuration reference](https://developers.cloudflare.com/workers/wrangler/configuration/) |
-| Deploy a framework application | [Framework guides](https://developers.cloudflare.com/workers/framework-guides/); follow the guide for the project's existing framework and adapter |
-| Migrate an application to Workers when requested | [Pages to Workers](https://developers.cloudflare.com/workers/static-assets/migration-guides/migrate-from-pages/); [Vercel to Workers](https://developers.cloudflare.com/workers/static-assets/migration-guides/vercel-to-workers/) |
-| Configure staging or production | [Environments](https://developers.cloudflare.com/workers/wrangler/environments/) |
-| Set secrets locally, in CI, or on a deployed Worker | [Secrets](https://developers.cloudflare.com/workers/configuration/secrets/) |
-| Generate binding and runtime types | [TypeScript](https://developers.cloudflare.com/workers/languages/typescript/) |
-| Run locally or choose a testing approach | [Local development](https://developers.cloudflare.com/workers/local-development/); [testing](https://developers.cloudflare.com/workers/testing/) |
-| Choose roles, scopes, or API token permissions for Wrangler | [Roles and permissions](https://developers.cloudflare.com/workers/authorization/); [Workers roles and permissions](https://developers.cloudflare.com/workers/authorization/workers/#wrangler) |
-| Create or manage a branch or pull request environment | [Previews overview](https://developers.cloudflare.com/workers/previews/); [get started](https://developers.cloudflare.com/workers/previews/get-started/); [configuration](https://developers.cloudflare.com/workers/previews/configuration/) |
-| Decide whether Preview resources are isolated or shared | [Resources and isolation](https://developers.cloudflare.com/workers/previews/resources/), including its current limitations |
-| Configure Preview URLs, access, debugging, or CI | [Custom domains](https://developers.cloudflare.com/workers/previews/custom-domains/); [test and debug](https://developers.cloudflare.com/workers/previews/test-and-debug/); [examples](https://developers.cloudflare.com/workers/previews/examples/) |
-| Choose between Previews, Version URLs, and Wrangler environments | [Compare workflows](https://developers.cloudflare.com/workers/previews/compare-workflows/) |
-| Diagnose authentication or select an account | [General commands](https://developers.cloudflare.com/workers/wrangler/commands/general/), including `whoami`; [authentication profiles](https://developers.cloudflare.com/workers/wrangler/profiles/) |
-| Deploy an unauthenticated prototype | [Claim deployments](https://developers.cloudflare.com/workers/platform/claim-deployments/) for eligibility, expiry, and claim URL handling; use a permanent account for production or CI |
+| Discover commands and flags, including resource management, deployments, rollback, and diagnostics | Project-local `wrangler --help` and `wrangler <command> --help`; [command reference](https://developers.cloudflare.com/workers/wrangler/commands/index.md) |
+| Edit config or add a binding | Installed `wrangler/config-schema.json` (usually under `node_modules`); [configuration reference](https://developers.cloudflare.com/workers/wrangler/configuration/index.md) |
+| Deploy a framework application | [Framework guides](https://developers.cloudflare.com/workers/framework-guides/index.md); follow the guide for the project's existing framework and adapter |
+| Migrate an application to Workers when requested | [Pages to Workers](https://developers.cloudflare.com/workers/static-assets/migration-guides/migrate-from-pages/index.md); [Vercel to Workers](https://developers.cloudflare.com/workers/static-assets/migration-guides/vercel-to-workers/index.md) |
+| Configure staging or production | [Environments](https://developers.cloudflare.com/workers/wrangler/environments/index.md) |
+| Set secrets locally, in CI, or on a deployed Worker | [Secrets](https://developers.cloudflare.com/workers/configuration/secrets/index.md) |
+| Generate binding and runtime types | [TypeScript](https://developers.cloudflare.com/workers/languages/typescript/index.md) |
+| Run locally or choose a testing approach | [Local development](https://developers.cloudflare.com/workers/local-development/index.md); [testing](https://developers.cloudflare.com/workers/testing/index.md) |
+| Choose roles, scopes, or API token permissions for Wrangler | [Roles and permissions](https://developers.cloudflare.com/workers/authorization/index.md); [Workers roles and permissions](https://developers.cloudflare.com/workers/authorization/workers/index.md#wrangler) |
+| Create or manage a branch or pull request environment | [Previews overview](https://developers.cloudflare.com/workers/previews/index.md); [get started](https://developers.cloudflare.com/workers/previews/get-started/index.md); [configuration](https://developers.cloudflare.com/workers/previews/configuration/index.md) |
+| Decide whether Preview resources are isolated or shared | [Resources and isolation](https://developers.cloudflare.com/workers/previews/resources/index.md), including its current limitations |
+| Configure Preview URLs, access, debugging, or CI | [Custom domains](https://developers.cloudflare.com/workers/previews/custom-domains/index.md); [test and debug](https://developers.cloudflare.com/workers/previews/test-and-debug/index.md); [examples](https://developers.cloudflare.com/workers/previews/examples/index.md) |
+| Choose between Previews, Version URLs, and Wrangler environments | [Compare workflows](https://developers.cloudflare.com/workers/previews/compare-workflows/index.md) |
+| Diagnose authentication or select an account | [General commands](https://developers.cloudflare.com/workers/wrangler/commands/general/index.md), including `whoami`; [authentication profiles](https://developers.cloudflare.com/workers/wrangler/profiles/index.md) |
+| Deploy an unauthenticated prototype | [Claim deployments](https://developers.cloudflare.com/workers/platform/claim-deployments/index.md) for eligibility, expiry, and claim URL handling; use a permanent account for production or CI |
 
 Use installed help and schema to check whether documented features exist in the project's version. If a required feature needs an upgrade, make that dependency explicit. If retrieval is unavailable, state the gap and use available local evidence rather than inventing syntax.
 
 ## Apply the Change
 
-- Prefer `wrangler.jsonc` for new config. Set a new project's [compatibility date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to today; review runtime changes and test when advancing an existing project's date. Preserve existing project conventions and avoid incidental format migrations.
+- Prefer `wrangler.jsonc` for new config. Set a new project's [compatibility date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/index.md) to today; review runtime changes and test when advancing an existing project's date. Preserve existing project conventions and avoid incidental format migrations.
 - Check environment inheritance before adding bindings or variables. Some fields must be specified separately for each environment; a working default config does not establish that staging is configured.
-- With the Cloudflare Vite plugin, select the environment via `CLOUDFLARE_ENV` at dev or build time. Deploy the resulting build; setting an environment at deploy time does not retarget its flattened config. See [Vite environments](https://developers.cloudflare.com/workers/vite-plugin/reference/cloudflare-environments/).
-- Reconcile dashboard changes with the config before deploying: Wrangler can overwrite dashboard variables and routes. When binding existing resources, verify their identifiers; omitted identifiers can trigger [automatic provisioning](https://developers.cloudflare.com/workers/wrangler/configuration/#automatic-provisioning).
+- With the Cloudflare Vite plugin, select the environment via `CLOUDFLARE_ENV` at dev or build time. Deploy the resulting build; setting an environment at deploy time does not retarget its flattened config. See [Vite environments](https://developers.cloudflare.com/workers/vite-plugin/reference/cloudflare-environments/index.md).
+- Reconcile dashboard changes with the config before deploying: Wrangler can overwrite dashboard variables and routes. When binding existing resources, verify their identifiers; omitted identifiers can trigger [automatic provisioning](https://developers.cloudflare.com/workers/wrangler/configuration/index.md#automatic-provisioning).
 - Distinguish local simulation from remote bindings during development. A locally running Worker can still access real resources; check the selected bindings before testing writes.
 - Before a remote command, identify the authenticated member or API token and retrieve the current role and scope required for the exact operation. Prefer the narrowest scope that satisfies the user's intent. The `wrangler login` OAuth flow does not support granular authorization; use an account-owned API token when granular access is required, and never ask the user to paste its value into chat.
 - Keep secret values out of command arguments, source code, and logs. Use the documented interactive input or protected file/stdin mechanism for the command. Local secret files must be ignored by version control and are not automatically uploaded as deployed secrets. For missing local secrets, check file precedence and any `secrets.required` declaration in the secrets docs.
 - Treat `wrangler secret put` and `secret delete` as deployments: they create a version and deploy it immediately. Use the documented `wrangler versions secret` workflow when the change must be staged.
-- Before a rollback, check [rollback limitations](https://developers.cloudflare.com/workers/versions-and-deployments/rollbacks/): connected resources and their data are not rolled back with Worker code.
+- Before a rollback, check [rollback limitations](https://developers.cloudflare.com/workers/versions-and-deployments/rollbacks/index.md): connected resources and their data are not rolled back with Worker code.
 
 ## Work with Workers Previews
 
 - Workers Previews requires project-local Wrangler 4.135.0 or later; project commands do not use a newer global installation. Check the project's pinned version and make any required dependency upgrade explicit.
-- Use Previews for branch and pull request environments under the same Worker. Use Version URLs to inspect a specific uploaded version with production resources, and Wrangler environments for persistent, separately deployed Workers. Follow [Compare workflows](https://developers.cloudflare.com/workers/previews/compare-workflows/) rather than adapting an older aliased Version URL workflow.
+- Use Previews for branch and pull request environments under the same Worker. Use Version URLs to inspect a specific uploaded version with production resources, and Wrangler environments for persistent, separately deployed Workers. Follow [Compare workflows](https://developers.cloudflare.com/workers/previews/compare-workflows/index.md) rather than adapting an older aliased Version URL workflow.
 - First inspect how the user manages production configuration and deployments. Configure Preview domains through the same configuration system as production, such as Wrangler, the dashboard, or Terraform. Run Preview deployments through the user's existing path, such as the local CLI, Workers Builds, or external CI, unless the user requests a different workflow. Mirror the management approach, not production resource bindings or data.
-- Before deploying, follow the current [configuration placement table](https://developers.cloudflare.com/workers/previews/configuration/#what-goes-in-the-previews-block) and [resource matrix and limitations](https://developers.cloudflare.com/workers/previews/resources/). Do not infer isolation from the Preview name or allow writes to production resources unless the user explicitly intends to share them.
-- Tell the user that Preview URLs are public unless access controls are configured, then let them decide whether to protect the URLs. Follow the [custom domain and access guidance](https://developers.cloudflare.com/workers/previews/custom-domains/) for the chosen setup.
+- Before deploying, follow the current [configuration placement table](https://developers.cloudflare.com/workers/previews/configuration/index.md#what-goes-in-the-previews-block) and [resource matrix and limitations](https://developers.cloudflare.com/workers/previews/resources/index.md). Do not infer isolation from the Preview name or allow writes to production resources unless the user explicitly intends to share them.
+- Tell the user that Preview URLs are public unless access controls are configured, then let them decide whether to protect the URLs. Follow the [custom domain and access guidance](https://developers.cloudflare.com/workers/previews/custom-domains/index.md) for the chosen setup.
 - Confirm which Worker or Wrangler environment the user intends to target. When targeting a Wrangler environment, pass the same `--env` value to every Preview command; omitting it targets the top-level Worker.
 
 ## Validate

package/dist/global-skills/xcode-project-setup/SKILL.md

@@ -4,6 +4,7 @@ description: Safely modifies Xcode projects (.pbxproj) to add Swift Packages and
 compatibility: Requires Swift to be installed locally and macOS environment.
 metadata:
   category: ApplicationDevelopment
+disable-model-invocation: true
 ---
 
 # Xcode Project Setup

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vybekiit",
-  "version": "0.7.29",
+  "version": "0.7.32",
   "description": "Choose your services, sign in, create a VybeKiit app, and open its verified local welcome page.",
   "license": "MIT",
   "publishConfig": {
@@ -21,6 +21,7 @@
     "@clack/prompts": "1.7.0",
     "@neondatabase/serverless": "^0.10.4",
     "@supabase/supabase-js": "^2.47.10",
+    "cross-spawn": "7.0.6",
     "effect": "3.21.4",
     "firebase-admin": "^13.0.2",
     "mongodb": "^7.4.0",
@@ -29,18 +30,19 @@
     "pg": "8.22.0"
   },
   "devDependencies": {
+    "@types/cross-spawn": "6.0.6",
     "@types/node": "22.20.0",
     "tsup": "8.5.1",
     "typescript": "5.7.2",
     "vitest": "3.2.6",
     "@effect/vitest": "0.29.0",
-    "@vybekiit/agent-kit": "0.7.29",
-    "@vybekiit/agent-mcp": "0.7.29",
-    "@vybekiit/core": "0.7.29",
-    "@vybekiit/db": "0.7.29",
-    "@vybekiit/deploy": "0.7.29",
-    "@vybekiit/payments": "0.7.29",
-    "@vybekiit/report-mode": "0.7.29"
+    "@vybekiit/agent-kit": "0.7.32",
+    "@vybekiit/agent-mcp": "0.7.32",
+    "@vybekiit/payments": "0.7.32",
+    "@vybekiit/core": "0.7.32",
+    "@vybekiit/db": "0.7.32",
+    "@vybekiit/report-mode": "0.7.32",
+    "@vybekiit/deploy": "0.7.32"
   },
   "scripts": {
     "build": "tsup && node scripts/bundleGlobalSkills.mjs",