vybekiit 0.7.29 → 0.7.33

package/dist/global-skills/neon-postgres/references/vector-search.md

@@ -5,7 +5,7 @@ Use `lakebase_vector` for approximate nearest-neighbor retrieval over embeddings
 ## Contents
 
 - [Create the extension](#create-the-extension) — enable `lakebase_vector` and its `pgvector` dependency
-- [Prepare embeddings](#prepare-embeddings) — define the vector column and keep embedding dimensions consistent
+- [Prepare embeddings](#prepare-embeddings) — generate vectors with the AI Gateway and match the column dimension
 - [Build the index](#build-the-index) — match the distance metric, operator class, and query operator
 - [Tune the index](#tune-the-index) — configure index-build options and concurrent index management
 - [Query](#query) — rank by vector distance or filter by a similarity radius
@@ -24,28 +24,111 @@ CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
 
 ## Prepare Embeddings
 
-Use any embedding provider whose vector dimensions and distance metric match the schema and index:
+Neon's [AI Gateway embeddings endpoint](https://neon.com/docs/ai-gateway/embeddings) is an OpenAI-compatible way to generate vectors for Lakebase Search. This table uses 1024 dimensions as an example; set the column dimension to the output of the model and any `dimensions` parameter you choose:
 
 ```sql
 CREATE TABLE documents (
   id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
   title text NOT NULL,
   body text NOT NULL,
-  embedding vector(1536)
+  embedding vector(1024)
 );
 ```
 
-Replace `1536` with the embedding model's dimension. Generate stored-document and query embeddings with the same model and preprocessing. Keep embedding generation outside SQL unless the architecture already provides an in-database embedding function.
+Enable the AI Gateway on the branch and get `NEON_AI_GATEWAY_TOKEN` and the bare-host `NEON_AI_GATEWAY_BASE_URL`:
+
+- With `neon.ts`, declare `aiGateway: true`, run `neon deploy`, then run `neon env pull --file .env`.
+- Without `neon.ts`, run `neon env pull --service ai-gateway --file .env` from a directory linked to the intended project and branch. This requests the gateway variables explicitly and skips other services.
+- Alternatively, get both values from the Neon Console. Neon Functions receive them automatically.
+
+### AI SDK (Recommended)
+
+For TypeScript apps, use Neon's `@neon/ai-sdk-provider` 1.0.0+ with the [Vercel AI SDK](https://ai-sdk.dev) (`ai`, 6+) (`npm install @neon/ai-sdk-provider ai dotenv`). The provider reads `NEON_AI_GATEWAY_TOKEN` and `NEON_AI_GATEWAY_BASE_URL` directly and sends embedding requests to `/v1/embeddings`. Load `.env` in a standalone app; Neon Functions inject the variables automatically.
+
+```typescript
+import "dotenv/config";
+import { neon } from "@neon/ai-sdk-provider";
+import { embed, embedMany } from "ai";
+
+const embeddingModel = neon.embeddingModel("qwen3-embedding-0-6b");
+const providerOptions = { neon: { dimensions: 1024 } };
+// Qwen3 query prompt adapted for Neon documentation search; documents stay unprefixed.
+const queryPrompt =
+  "Instruct: Given a question about Neon, retrieve documentation passages that answer the question\nQuery: ";
+
+const { embeddings: documentEmbeddings } = await embedMany({
+  model: embeddingModel,
+  values: documentBodies, // non-empty document batch; store vectors by input index
+  providerOptions,
+  maxParallelCalls: 1,
+});
+const { embedding: queryEmbedding } = await embed({
+  model: embeddingModel,
+  value: `${queryPrompt}${queryText}`,
+  providerOptions,
+}); // bind to $1 below
+```
+
+Skip empty imports before calling `embedMany`. It returns vectors in input order and splits requests according to the provider's item limit. For large imports, also split document text within the endpoint's token limits and keep database writes bounded.
+
+For Neon documentation search, the example adapts the task instruction in Qwen3's stored `query` prompt from [config_sentence_transformers.json](https://huggingface.co/Qwen/Qwen3-Embedding-0.6B/blob/main/config_sentence_transformers.json). Its `document` prompt is empty, so document text stays unprefixed. Neither SDK applies SentenceTransformers prompts automatically. Keep the original `queryText` for BM25, and use the selected model's own prompt conventions if you switch models.
+
+### OpenAI SDK Alternative
+
+For an existing OpenAI SDK integration, install `openai` and `dotenv` (`npm install openai dotenv`) and configure the client explicitly:
+
+```typescript
+import "dotenv/config";
+import OpenAI from "openai";
+
+const apiKey = process.env.NEON_AI_GATEWAY_TOKEN;
+const gatewayBaseUrl = process.env.NEON_AI_GATEWAY_BASE_URL;
+if (!apiKey || !gatewayBaseUrl) {
+  throw new Error("Missing Neon AI Gateway credentials");
+}
+
+const client = new OpenAI({
+  apiKey,
+  baseURL: `${gatewayBaseUrl}/v1`,
+});
+
+async function embedBatch(inputs: string[]): Promise<number[][]> {
+  if (inputs.length === 0) return [];
+  const response = await client.embeddings.create({
+    model: "qwen3-embedding-0-6b",
+    input: inputs,
+    dimensions: 1024,
+    encoding_format: "float",
+  });
+  const vectors: number[][] = [];
+  for (const item of response.data) vectors[item.index] = item.embedding;
+  return inputs.map((_, index) => {
+    const embedding = vectors[index];
+    if (!embedding) throw new Error(`Missing embedding for input ${index}`);
+    return embedding;
+  });
+}
+
+const documentEmbeddings = await embedBatch(documentBodies);
+const [queryEmbedding] = await embedBatch([`${queryPrompt}${queryText}`]);
+if (!queryEmbedding) throw new Error("Missing query embedding");
+```
+
+Use the same `queryPrompt` defined above, only for query inputs. Keep each batch within the endpoint's input and rate limits, and pair each vector with its source row using the response `index`. The [OpenAI JavaScript SDK v6](https://github.com/openai/openai-node/blob/v6.0.0/src/resources/embeddings.ts) defaults to requesting base64 and decodes the response as base64. If a compatible endpoint returns float arrays instead, that decoder can silently turn them into zeros. Pass `encoding_format: "float"` explicitly for the AI Gateway; the SDK then returns the float arrays directly. Base64 can reduce response size when an endpoint actually returns base64, but do not assume that format for this gateway.
+
+Use the same model and output dimensions for stored documents and queries. Follow the model's input conventions: some models recommend a query instruction while document text remains unprefixed. If the model supports shorter vectors, compare retrieval quality, storage, and latency before changing dimensions; set the column and both embedding requests to the chosen size. Switching models requires re-embedding the corpus; changing dimensions also requires migrating the vector column and index. Generate embeddings in the application, outside SQL, unless the architecture already provides an in-database embedding function. Other embedding providers are also valid when their output matches the schema and index.
 
 ## Build the Index
 
 Choose the operator class and query operator as a matched pair:
 
-| Metric | Common use | Operator class | Distance operator |
-| --- | --- | --- | --- |
-| Cosine | Most text embeddings | `vector_cosine_ops` | `<=>` |
-| L2 / Euclidean | Absolute distance matters; vectors do not need normalization | `vector_l2_ops` | `<->` |
-| Inner product | Unit-normalized vectors; matches cosine for unit vectors | `vector_ip_ops` | `<#>` |
+| Metric         | Common use                                                   | Operator class      | Distance operator |
+| -------------- | ------------------------------------------------------------ | ------------------- | ----------------- |
+| Cosine         | Most text embeddings                                         | `vector_cosine_ops` | `<=>`             |
+| L2 / Euclidean | Absolute distance matters; vectors do not need normalization | `vector_l2_ops`     | `<->`             |
+| Inner product  | Unit-normalized vectors; matches cosine for unit vectors     | `vector_ip_ops`     | `<#>`             |
+
+Choose the metric recommended for the selected model, and keep its index operator class and query operator aligned. The [Qwen3 Embedding model card](https://huggingface.co/Qwen/Qwen3-Embedding-0.6B) demonstrates cosine similarity and normalized dot product for retrieval. For unit-normalized vectors, cosine, inner product, and L2 have the same exact ranking; approximate indexes can still differ in recall and latency, so benchmark on your corpus.
 
 ```sql
 CREATE INDEX documents_embedding_ann ON documents
@@ -79,7 +162,7 @@ For a large table, use `CREATE INDEX CONCURRENTLY` to avoid locking out writes w
 
 ## Query
 
-Generate the query embedding with the same model and preprocessing used for stored documents, then bind it as a parameter:
+Generate the query embedding with the same model and dimensions used for stored documents, following the model's query-input conventions (using the Qwen3 query prompt shown above), then bind it as a parameter:
 
 ```sql
 SELECT id, title, embedding <=> $1::vector AS distance

package/dist/global-skills/neon-postgres-branches/SKILL.md

@@ -12,6 +12,7 @@ description: >-
 metadata:
   parent: neon
   source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres-branches
+disable-model-invocation: true
 ---
 
 **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more.

package/dist/global-skills/neon-postgres-egress-optimizer/SKILL.md

@@ -12,6 +12,7 @@ description: >-
 metadata:
   parent: neon
   source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres-egress-optimizer
+disable-model-invocation: true
 ---
 
 **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more.

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

@@ -1,6 +1,6 @@
 ---
 name: onboarding
-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."
+description: "take the builder from \"I just bought this\" to their app running and visible in front of them in this one session. Use when the vibe coder says something like: set up my app; let's start; get me going; just bought; hi; help."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---
@@ -26,16 +26,17 @@ translate every error · celebrate. Decide all technical choices yourself.
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install the end-user onboarding recipe when the vibe coder wants a first-run wizard (catalog SSOT — Option C).**
-   Copy `apps/componentLibrary/src/pageRecipes/OnboardingPage.tsx` export `OnboardingPage` into the buyer app at route `/onboarding`.
-   Recipe id: `onboarding`. Presets: none.
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Skip this step if the vibe coder only needs *their* kit setup (steps 1–5 below) and not a product wizard for their users.
-   Also reference `packages/agentKit` `getPageRecipeInstall('onboarding')` / page-recipe-manifest.json.
-   **Verify:** if installed, `/onboarding` builds with practice UI.
-
-1. **Welcome + ask the one thing that matters.**
-   Greet warmly. If the vibe coder already described their app, use that description. Otherwise ask:
+0. **Add the first-run wizard page when the vibe coder wants one for their users.** Run
+   `vybekiit add page-recipe onboarding`. It adds the page at `/onboarding`. Keep every `TODO:` in the
+   page and fill each one in. Skip this step when the vibe coder only needs their own kit setup
+   (steps 1-5 below).
+   **Verify:** if added, `/onboarding` opens and shows practice content.
+
+1. **Welcome, say what VybeKiit is, then ask the one thing that matters.**
+   Greet warmly in plain text with no emojis, then tell them in a few short sentences what they have, in plain words:
+   *"VybeKiit is a ready-made web app with the hard parts already working. It comes with sign-in, payments, a database that remembers your customers' information, emails your app sends, file uploads, visitor stats, alerts when something breaks, more languages, and putting your app online. While we build, you can turn on Report mode and point at anything on screen that looks wrong, and I fix it. You own all of it, and I do the technical work."*
+   Then stop talking about the kit and move on to their idea.
+   If the vibe coder already described their app, use that description. Otherwise ask:
    *"In one sentence, what do you want to build?"* Use their answer to tailor the starter page later.
    Keep the conversation about their idea.
 
@@ -64,7 +65,7 @@ translate every error · celebrate. Decide all technical choices yourself.
    **Verify:** the dev server is up with no errors. If it fails → run `doctor`.
 
    > (Agent-only) **Database MCP tier:** Supabase, Neon, and Firebase use login-once MCP configs
-   > (`mcp-supabase.json`, `mcp-neon.json`, `mcp-firebase.json`) — merge via `agent/mcp-setup.md`
+   > (`mcp-supabase.json`, `mcp-neon.json`, `mcp-firebase.json`) — merge via `.vybekiit/agent/mcp-setup.md`
    > (Cursor, Claude Desktop, Codex). MongoDB and AWS are advanced only.
    >
    > **Payment MCP tier:** Stripe and PayPal use `mcp-stripe.json` / `mcp-paypal.json` when
@@ -73,7 +74,7 @@ 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:** 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.
+   *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."*
 

package/dist/global-skills/plan-my-idea/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plan-my-idea
-description: "help the builder figure out exactly what they want **before** you build — so the first. Use when the vibe coder says something like: help me plan; figure out my idea; think it through; marketplace; like airbnb."
+description: "help the builder figure out exactly what they want before you build — so the first version matches their idea instead of your guess. Use when the vibe coder says something like: help me plan; figure out my idea; think it through; marketplace; like airbnb."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---

package/dist/global-skills/publish-app/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: publish-app
-description: "the builder's app is **in the App Store and Google Play** for anyone to download. This is. Use when the vibe coder says something like: put it online; publish; make it live; ship it; deploy; publish app."
+description: "the builder's app is in the App Store and Google Play for anyone to download. Use when the vibe coder says something like: put it online; publish; make it live; ship it; deploy; publish app."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---

package/dist/global-skills/publish-extension/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: publish-extension
-description: "the builder's extension is **listed in the Chrome Web Store** for anyone to install. Use when the vibe coder says something like: put it online; publish; make it live; ship it; deploy; chrome store."
+description: "the builder's extension is listed in the Chrome Web Store for anyone to install. Use when the vibe coder says something like: put it online; publish; make it live; ship it; deploy; chrome store."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---

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

@@ -4,7 +4,7 @@ description: Use when working with the Resend email API — sending transactiona
 license: MIT
 metadata:
     author: resend
-    version: "3.12.0"
+    version: "3.14.0"
     homepage: https://resend.com/agent-skills
     source: https://github.com/resend/resend-skills
     openclaw:
@@ -47,6 +47,7 @@ references:
     - usage.md
     - installation.md
     - fetch-all-templates.mjs
+disable-model-invocation: true
 ---
 
 # Resend
@@ -177,22 +178,11 @@ export async function POST(req: Request) {
 
 ## SDK Version Requirements
 
-Always install the latest SDK version. These are the minimum versions for full functionality (sending, receiving, webhook verification):
+Always install the latest SDK version. Older SDKs may be missing `webhooks.verify()`, `emails.receiving.get()`, or `domains.claims.*`.
 
-| Language | Package | Min Version | Install |
-|----------|---------|-------------|---------|
-| Node.js | `resend` | >= 6.14.0 | `npm install resend` |
-| Python | `resend` | >= 2.34.0 | `pip install resend` |
-| Go | `resend-go/v3` | >= 3.11.0 | `go get github.com/resend/resend-go/v3` |
-| Ruby | `resend` | >= 1.6.0 | `gem install resend` |
-| PHP | `resend/resend-php` | >= 1.1.0 | `composer require resend/resend-php` |
-| Rust | `resend-rs` | >= 0.26.1 | `cargo add resend-rs` |
-| Java | `resend-java` | >= 4.16.0 | See [installation.md](references/installation.md) |
-| .NET | `Resend` | >= 0.2.1 | `dotnet add package Resend` |
+> **If the project already has a Resend SDK installed**, check its version against the minimum versions in [installation.md](references/installation.md) and upgrade if it's below.
 
-> **If the project already has a Resend SDK installed**, check the version and upgrade if it's below the minimum. Older SDKs may be missing `webhooks.verify()`, `emails.receiving.get()`, or `domains.claims.*`.
-
-See [installation.md](references/installation.md) for full installation commands, language detection, and cURL fallback.
+See [installation.md](references/installation.md) for the minimum version per language, full installation commands, language detection, and cURL fallback.
 
 ## Common Setup
 

package/dist/global-skills/resend/references/domains.md

@@ -108,7 +108,7 @@ Claiming takes over a domain **another Resend account has already verified**. Th
 Claim → Add TXT proof to DNS → Verify claim → (completed) → Update DKIM in DNS → Verify domain → Send
 ```
 
-Claim methods are available in the **Node.js** (`resend >= 6.14.0`), **Python** (`resend >= 2.34.0`), **Ruby** (`resend >= 1.6.0`), **Go** (`resend-go/v3 >= 3.11.0`), **Rust** (`resend-rs >= 0.26.1`), and **Java** (`resend-java >= 4.16.0`) SDKs, plus the **CLI** (`resend domains claim`) and REST API. Not yet in the PHP or .NET SDKs.
+Claim methods are available in the **Node.js** (`resend >= 6.14.0`), **Python** (`resend >= 2.34.0`), **Ruby** (`resend >= 1.6.0`), **Go** (`resend-go/v4 >= 4.0.0`), **Rust** (`resend-rs >= 0.26.1`), and **Java** (`resend-java >= 4.16.0`) SDKs, plus the **CLI** (`resend domains claim`) and REST API. Not yet in the PHP or .NET SDKs.
 
 | Operation | Method | Notes |
 |-----------|--------|-------|

package/dist/global-skills/resend/references/installation.md

@@ -10,7 +10,7 @@ These are the minimum versions required for full functionality (sending, receivi
 |----------|---------|-------------|---------|
 | Node.js | `resend` | >= 6.14.0 | `npm install resend` |
 | Python | `resend` | >= 2.34.0 | `pip install resend` |
-| Go | `resend-go/v3` | >= 3.11.0 | `go get github.com/resend/resend-go/v3` |
+| Go | `resend-go/v4` | >= 4.0.0 | `go get github.com/resend/resend-go/v4` |
 | Ruby | `resend` | >= 1.6.0 | `gem install resend` |
 | PHP | `resend/resend-php` | >= 1.1.0 | `composer require resend/resend-php` |
 | Rust | `resend-rs` | >= 0.26.1 | `cargo add resend-rs` |
@@ -27,7 +27,7 @@ Check for these files to determine the project's language/framework:
 |------|----------|-----|
 | `package.json` | Node.js/TypeScript | resend |
 | `requirements.txt` or `pyproject.toml` | Python | resend |
-| `go.mod` | Go | resend-go/v3 |
+| `go.mod` | Go | resend-go/v4 |
 | `Gemfile` | Ruby | resend |
 | `composer.json` | PHP | resend/resend-php |
 | `Cargo.toml` | Rust | resend-rs |
@@ -59,7 +59,7 @@ pip install resend
 ### Go
 
 ```bash
-go get github.com/resend/resend-go/v3
+go get github.com/resend/resend-go/v4
 ```
 
 ### Ruby

package/dist/global-skills/resend/references/sending/best-practices.md

@@ -86,7 +86,7 @@ result = resend.Batch.send(emails, idempotency_key=f"batch-orders/{batch_id}")
 Other SDKs use the `Idempotency-Key` header:
 
 ```go
-import "github.com/resend/resend-go/v3"
+import "github.com/resend/resend-go/v4"
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
 
@@ -223,7 +223,7 @@ except resend.exceptions.ResendError as e:
 ```go
 import (
     "fmt"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
@@ -359,7 +359,7 @@ result = send_email_with_retry(
 import (
     "fmt"
     "time"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 func sendEmailWithRetry(client *resend.Client, params *resend.SendEmailRequest, maxRetries int) (*resend.SendEmailResponse, error) {

package/dist/global-skills/resend/references/sending/single-email-examples.md

@@ -58,7 +58,7 @@ email = resend.Emails.send({
 Other SDKs use the `Idempotency-Key` header:
 
 ```go
-import "github.com/resend/resend-go/v3"
+import "github.com/resend/resend-go/v4"
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
 
@@ -172,7 +172,7 @@ except resend.exceptions.ResendError as e:
 ```go
 import (
     "fmt"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
@@ -293,7 +293,7 @@ result = send_email_with_retry(
 import (
     "fmt"
     "time"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 func sendEmailWithRetry(client *resend.Client, params *resend.SendEmailRequest, maxRetries int) (*resend.SendEmailResponse, error) {

package/dist/global-skills/resend/references/webhooks.md

@@ -65,7 +65,9 @@ The `email.received` payload contains metadata only (sender, recipient, subject,
 |-------|---------|
 | `domain.created` / `updated` / `deleted` | Domain configuration changes |
 | `contact.created` / `updated` / `deleted` | Contact list changes (not from CSV imports) |
+| `contact.topics.updated` | Contact's topic subscriptions change |
 | `suppression.added` / `removed` | Email address added to or removed from the suppression list |
+| `topic.created` / `updated` / `deleted` | Topic created, updated, or deleted |
 
 ## Setup
 

package/dist/global-skills/reset-password/SKILL.md

@@ -26,12 +26,10 @@ translate every error · celebrate.
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install the page recipe first (catalog SSOT — Option C).**
-   Copy `apps/componentLibrary/src/pageRecipes/AccountSecurityPage.tsx` export `AccountSecurityPage` into the buyer app at route `/settings/security`.
-   Recipe id: `account-security`. Preset: auth-bridge.
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Also reference `packages/agentKit` `getPageRecipeInstall('reset-password')` / page-recipe-manifest.json.
-   **Verify:** route builds with practice security UI before provider wiring.
+0. **Add the ready-made page first.** Run `vybekiit add page-recipe account-security`. It adds the page
+   at `/settings/security` and lists any data setup to run next. Keep every `TODO:` in the page and fill
+   each one in as you connect the real service.
+   **Verify:** `/settings/security` opens and shows practice content.
 
 1. **Confirm sign-in is wired.** Run `add-signin` first if accounts are not set up yet.
    **Verify:** existing sign-in works.

package/dist/global-skills/save-data/SKILL.md

@@ -51,6 +51,9 @@ For other requests, select matching presets from the catalog before authoring an
    Inspect the selected service's existing CLI or MCP login and exact project before requesting
    access. Reuse authorized connections and preserve existing projects. Never delete a project to
    free capacity. Request one manual action only when an actual access blocker remains.
+   Supabase keys: after `supabase login`, run `vybekiit-automate db setup --json --project-ref=<ref>`.
+   It saves `SUPABASE_URL` and `SUPABASE_ANON_KEY` to `settings.env`, `SUPABASE_SERVICE_ROLE_KEY` to `.env`, and prints
+   only their names.
    **Verify:** the database is reachable (`@vybekiit/db`'s `pingDatabase`).
 
 2. **Decide what to remember from the request.** Reuse existing data shapes and ownership rules.

package/dist/global-skills/sentry-sdk-setup/SKILL.md

@@ -3,6 +3,7 @@ name: sentry-sdk-setup
 description: Set up Sentry in any language or framework. Detects the user's platform and loads the right SDK skill. Use when asked to add Sentry, install an SDK, or set up error monitoring in a project.
 license: Apache-2.0
 role: router
+disable-model-invocation: true
 ---
 
 > [All Skills](../../SKILL_TREE.md)

package/dist/global-skills/sentry-workflow/SKILL.md

@@ -3,6 +3,7 @@ name: sentry-workflow
 description: Keep Sentry SDKs up to date. Use when asked to upgrade the Sentry SDK across major versions, migrate SDK versions, or fix deprecated APIs.
 license: Apache-2.0
 role: router
+disable-model-invocation: true
 ---
 
 > [All Skills](../../SKILL_TREE.md)

package/dist/global-skills/setup-email/SKILL.md

@@ -31,17 +31,16 @@ when asked.
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install the page recipe first (catalog SSOT — Option C).**
-   Copy `apps/componentLibrary/src/pageRecipes/EmailNotificationsPage.tsx` export `EmailNotificationsPage` into the buyer app at route `/dashboard/email`.
-   Recipe id: `email-notifications`. Presets: notifications_log.
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Also reference `packages/agentKit` `getPageRecipeInstall('setup-email')` / page-recipe-manifest.json.
-   **Verify:** route builds and shows practice UI before provider wiring.
-
+0. **Add the ready-made page first.** Run `vybekiit add page-recipe email-notifications`. It adds the page
+   at `/settings/notifications` and lists any data setup to run next. Keep every `TODO:` in the page and fill
+   each one in as you connect the real service.
+   **Verify:** `/settings/notifications` opens and shows practice content.
 
 1. **Confirm the one sending detail.** Ask for (or guide them to set up) a verified sender address —
    the "from" address their app's emails come from. Tell them exactly where to confirm it, then save
-   it to the secret settings file.
+   it to the secret settings file. For the sending key (Resend by default), ask the builder to run
+   `vybekiit-automate resend setup` in their own terminal. It asks for the key with hidden typing,
+   checks it, and saves `RESEND_API_KEY` to `.env`. Never ask for the key in chat.
    **Verify:** the sender address is set and confirmed.
 
 2. **Wire sending.** Connect the app's email sending to `resolveEmailProvider()` (see wrapper for

package/dist/global-skills/setup-payments/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: setup-payments
-description: "the requested purchase flow works in practice. A test purchase succeeds end-to-end; accepting real money requires separately verified live setup. Use when the vibe coder says something like: add payments; take money; sell something; charge people."
+description: "the requested purchase flow works in practice. Use when the vibe coder says something like: add payments; take money; sell something; charge people."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---
@@ -32,14 +32,11 @@ translate every error · celebrate. You wire all the code; the builder only sign
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install the page recipe first (catalog SSOT — Option C).**
-   Copy `apps/componentLibrary/src/pageRecipes/PricingPage.tsx` export `PricingPage` into the buyer app at route `/pricing`.
-   Recipe id: `pricing`. Presets: orders + webhook_events (apply after provider secrets exist).
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Selling physical/digital goods (not only subscriptions)? Also install catalog ids
-   `commerce-products`, `commerce-cart`, `commerce-checkout` via `getPageRecipeInstall`.
-   Also reference `packages/agentKit` `getPageRecipeInstall('setup-payments')` / page-recipe-manifest.json.
-   **Verify:** `/pricing` builds and shows practice plans before provider wiring.
+0. **Add the ready-made pricing page first.** Run `vybekiit add page-recipe pricing`. It adds the page
+   at `/pricing` and lists any data setup to run next (run that after the payment keys are saved).
+   Selling products, not only plans? Also run `vybekiit add page-recipe product-grid`, then `cart` and
+   `checkout` the same way. Keep every `TODO:` in the pages and fill each one in as you connect payments.
+   **Verify:** `/pricing` opens and shows practice plans.
 
 1. **Explain the plan in one line.** *"I'll connect a payment service so you can charge people. I'll do
    the setup — you'll sign in once when I ask."* (Never name Lemon Squeezy, Stripe, or PayPal.)
@@ -48,15 +45,16 @@ translate every error · celebrate. You wire all the code; the builder only sign
    - Run `vybekiit-automate ls setup --json …` (or wizard mode without `--json`).
    - If Lemon Squeezy shows a sign-in screen, the automation **waits** until the builder completes login in the browser, then continues — no separate standby step required.
    - Optional pre-check: `vybekiit-automate ls standby` opens the dashboard and waits the same way.
-   - Write JSON output to `.env` (`LEMONSQUEEZY_STORE_ID`, variant ID, API key, webhook secret).
-   **Verify:** values saved; product exists in test mode.
+   - The command saves the store, product and key settings straight into the app's `.env` and prints only
+     their names. Never copy key values into the chat.
+   **Verify:** the command lists the saved names; product exists in test mode.
 
 3. **Stripe (opt-in).** Merge `mcp-stripe.json` via `agent/mcp-setup.md`; builder OAuth once.
    Agent creates product/price via Stripe MCP; write restricted API key to `.env`.
    **Verify:** test mode product visible in Stripe dashboard.
 
 4. **PayPal (opt-in).** Merge `mcp-paypal.json` via `agent/mcp-setup.md`; builder OAuth once (sandbox).
-   Agent provisions via PayPal MCP; write client id/secret and webhook id to `.env`.
+   Agent provisions via PayPal MCP; write the client secret to `.env`, the client id and webhook id to `settings.env`.
    **Verify:** sandbox checkout completes.
 
 5. **Connect the automatic payment message (webhook).** Webhook URL is `/api/webhook` on the deployed app

package/dist/global-skills/setup-sms/SKILL.md

@@ -27,7 +27,7 @@ Inspect an existing app before changing it. Scaffold a new kit app only when the
 1. **Collect Twilio secret settings** through doctor (never ask the builder to type SIDs by hand):
    `TWILIO_ACCOUNT_SID`, `TWILIO_AUTH_TOKEN`, `TWILIO_FROM_NUMBER`. Optional:
    `TWILIO_VERIFY_SERVICE_SID`, `TWILIO_WHATSAPP_FROM`.
-   **Verify:** values saved to `.env`.
+   **Verify:** values saved to `settings.env` and `.env`.
 
 2. **Set `NOTIFICATIONS_PROVIDER=twilio`.**
    **Verify:** `resolveNotificationsProvider()` does not throw.

package/dist/global-skills/sign-in-with-email-link/SKILL.md

@@ -24,12 +24,10 @@ Inspect an existing app before changing it. Scaffold a new kit app only when the
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install / extend the auth page recipe first (catalog SSOT — Option C).**
-   Copy or extend `apps/componentLibrary/src/pageRecipes/AuthPage.tsx` export `AuthPage` at route `/login`
-   with a "Email me a link" path. Recipe id: `auth`. Preset: auth-bridge.
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Also reference `packages/agentKit` `getPageRecipeInstall('sign-in-with-email-link')` / page-recipe-manifest.json.
-   **Verify:** `/login` shows a practice magic-link entry before provider wiring.
+0. **Add the ready-made sign-in page first.** Run `vybekiit add page-recipe auth`. It adds the page
+   at `/login` (if the app already has a sign-in page, it is kept). Then add an "Email me a link" option to it.
+   Keep every `TODO:` in the page and fill each one in as you connect the real service.
+   **Verify:** `/login` opens and shows an "Email me a link" option with practice content.
 
 1. **Confirm sign-in + email are wired** (`add-signin`, `setup-email` when going live).
    **Verify:** email OTP or password sign-in already works.

package/dist/global-skills/sign-in-with-google/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sign-in-with-google
-description: "people can tap **Continue with Google** — one button that signs them in **or** creates. Use when the vibe coder says something like: sign in with google; continue with google."
+description: "people can tap Continue with Google — one button that signs them in or creates their account. Use when the vibe coder says something like: sign in with google; continue with google."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---
@@ -28,14 +28,12 @@ needs it.
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install / extend the auth page recipe first (catalog SSOT — Option C).**
-   Copy or extend `apps/componentLibrary/src/pageRecipes/AuthPage.tsx` export `AuthPage` at route `/login`
-   with a **Continue with Google** button. Recipe id: `auth`. Preset: auth-bridge.
-   Legal pages when needed: `TermsOfServicePage` → `/terms`, `PrivacyPolicyPage` → `/privacy`
-   from the page-recipe manifest (group `legal`).
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Also reference `packages/agentKit` `getPageRecipeInstall('sign-in-with-google')` / page-recipe-manifest.json.
-   **Verify:** `/login` shows practice Google button before provider wiring.
+0. **Add the ready-made sign-in page first.** Run `vybekiit add page-recipe auth`. It adds the page
+   at `/login` (if the app already has a sign-in page, it is kept). Then add a "Continue with Google" button to it.
+   Keep every `TODO:` in the page and fill each one in as you connect the real service.
+   Need terms and privacy pages for Google? Run `vybekiit add page-recipe terms-of-service` and
+   `vybekiit add page-recipe privacy-policy` (they add `/terms` and `/privacy`).
+   **Verify:** `/login` opens and shows a practice "Continue with Google" button.
 
 1. **Make sure the basics exist.** Database (`save-data`) and base sign-in (`add-signin`) must work
    first — Google builds on top.
@@ -45,10 +43,13 @@ needs it.
    If it says "not signed in yet," walk the builder through the one command it prints.
    **Verify:** doctor reports gcloud ready.
 
-3. **Create the Google login for your app.** Use `gcloud` to create a **Web application** OAuth client.
-   Write `GOOGLE_OAUTH_CLIENT_ID`, `GOOGLE_OAUTH_CLIENT_SECRET`, and `GOOGLE_OAUTH_REDIRECT_URI`
-   to `.env`. Never ask the builder to open the Google Cloud console.
-   **Verify:** all three values are non-empty in `.env`.
+3. **Create the Google login for your app.** Run `vybekiit-automate google oauth --json` with
+   `--project=<gcloud-project-id>`, `--app-name=<app-name>`, `--support-email=<builder-email>`,
+   `--app-url=<app-url>` and `--redirect=<app-url>/api/auth/callback/google`. It creates (or fixes) the
+   Web login client and saves `GOOGLE_OAUTH_CLIENT_ID` to `settings.env` and
+   `GOOGLE_OAUTH_CLIENT_SECRET` to `.env`, printing only their names. If Google asks to sign in, the builder signs in once in the
+   browser it opens. Never ask the builder to open the Google Cloud console.
+   **Verify:** both names are listed as saved and are non-empty.
 
 4. **Enable Google on the sign-in handler.** Follow `platform-skills/better-auth-vybekiit.md` — add
    the Google social provider to the auth route. One flow handles sign-in and sign-up.

package/dist/global-skills/sign-in-with-phone/SKILL.md

@@ -25,15 +25,13 @@ Inspect an existing app before changing it. Scaffold a new kit app only when the
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install / extend the auth page recipe first (catalog SSOT — Option C).**
-   Copy or extend `apps/componentLibrary/src/pageRecipes/AuthPage.tsx` export `AuthPage` at route `/login`
-   with phone + code UI. Recipe id: `auth`. Preset: auth-bridge.
-   Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Also reference `packages/agentKit` `getPageRecipeInstall('sign-in-with-phone')` / page-recipe-manifest.json.
-   **Verify:** `/login` shows practice phone sign-in UI before provider wiring.
+0. **Add the ready-made sign-in page first.** Run `vybekiit add page-recipe auth`. It adds the page
+   at `/login` (if the app already has a sign-in page, it is kept). Then add a phone number and code form to it.
+   Keep every `TODO:` in the page and fill each one in as you connect the real service.
+   **Verify:** `/login` opens and shows a phone number and code form with practice content.
 
 1. **Run `setup-sms` first** if Twilio secret settings are not filled in.
-   **Verify:** `NOTIFICATIONS_PROVIDER=twilio` and Twilio keys in `.env`.
+   **Verify:** `NOTIFICATIONS_PROVIDER=twilio` in `settings.env` and `TWILIO_AUTH_TOKEN` in `.env`.
 
 2. **Add phone + code UI** on login → send code, then verify.
    **Verify:** practice mode accepts code `000000` with empty Twilio settings.