fimo 0.12.0-staging.1 → 0.12.0-staging.3

package/assets/skills/fimo/SKILL.md

@@ -2,15 +2,15 @@
 name: fimo
 description: >-
   Working in or with a Fimo project (a content + media + forms + analytics
-  platform for React websites). Load the real, version-locked Fimo skills on
-  demand through the `fimo` CLI before doing Fimo work — writing schema-driven
+  platform for React websites). Load the current Fimo skills on demand through
+  the `fimo` CLI before doing Fimo work — writing schema-driven
   code, running CLI/deploy workflows, using the dashboard, or migrating a site.
 ---
 
 # Fimo
 
-Fimo ships its skills through its CLI so they always match the installed `fimo` version. This file is
-just a pointer — do not rely on cached instructions. Fetch the real skill from the CLI when you need it.
+Fimo ships its skills through its CLI. `fimo-code` resolves from the project's installed `fimo` package;
+workflow skills resolve from the CLI you run. This file is only a pointer — fetch the real skill when needed.
 
 When you are about to do Fimo work:
 
@@ -25,7 +25,9 @@ Pick by task:
 
 - Writing code — schema-driven JSX, schemas/forms JSON, `t()` labels, `fimo/ui` media → `fimo-code`
 - CLI commands and workflows — push, deploy, sync, labels, domains, analytics → `fimo-cli`
-- Project MCP setup — configure `fimo mcp` for a local AI client → `fimo-cli` (`references/mcp.md`)
+- Fimo agents — create, configure, validate, deploy, run, or inspect them → `fimo-cli` (`references/agents.md`)
+- AI agent setup — connect Claude Code, Codex, Cursor, or another agent → `fimo-cli` (`references/agent-setup.md`)
+- Project MCP setup — configure `fimo mcp` for a local agent → `fimo-cli` (`references/mcp.md`)
 - The Fimo Studio dashboard / web app UI → `fimo-studio`
 - Migrating an existing site into Fimo → `fimo-migration`
 

package/assets/skills/fimo-cli/SKILL.md

@@ -1,23 +1,15 @@
 ---
 name: fimo-cli
 description: >-
-  The `fimo` CLI scaffolds and manages Fimo projects from the command line.
-  Load when the user wants to create a new Fimo project, build content
-  (schemas, entries, forms, media, labels/locales), deploy a site, manage
-  custom domains, configure outbound webhooks and event-driven integrations,
-  check site traffic/analytics, inspect or restore project history, invite collaborators, inspect AI credits,
-  connect an AI coding client to a Fimo project through MCP,
-  report a failing or slow Fimo API, rejected documented argument,
-  undocumented workaround, missing capability that blocks work, forces a
-  fragile or heavily manual workaround, or would materially accelerate a
-  recurring workflow, or other Fimo platform problem to support, log in or
-  switch organizations, or set up Fimo for their AI tool. Most "do X with
-  Fimo" tasks go through this skill.
+  Use the `fimo` CLI to create or operate a Fimo project: content, forms,
+  media, labels/locales, deploys, environments, domains, analytics,
+  integrations, Fimo agents, collaboration, accounts, and credits. Also use
+  for AI agent or MCP setup and confirmed Fimo platform blockers.
 ---
 
 # Fimo CLI
 
-The `fimo` CLI is the workflow surface for Fimo. Fimo is a content + media + forms + analytics platform for React websites with a CMS dashboard. The CLI handles project creation, all content / forms / media / labels / locale workflows, deploys, collaboration, account management, AI credit inspection, and AI agent setup.
+The `fimo` CLI is the workflow surface for Fimo. Fimo is a content + media + forms + analytics platform for React websites with a CMS dashboard. The CLI handles project creation, content / forms / media / labels / locale workflows, deploys, collaboration, account management, Fimo agents, and AI agent setup.
 
 This skill describes **what the CLI does and the workflows it drives**. For the package surface used IN code (component props, generated hooks, JSON shapes, code-side rules), load the `fimo-code` skill on demand with `npx fimo@latest skills get fimo-code`.
 
@@ -107,9 +99,9 @@ Load the matching reference when the user's request fires its trigger. Recipes t
 - "Invite a collaborator / add Marc / share with client" → `references/invite.md`
 - "Login / log out / who am I / switch organization" → `references/account.md` — note: switching **org** is `fimo orgs switch`; bare `fimo switch` switches **env** (see `references/branches.md`)
 - "Create / scaffold / run / validate an agent / agent bundle / wire or enable its triggers / list agent templates / view agent runs, reports, or logs (`fimo agents *`)" → `references/agents.md`
-- "Install Fimo for my AI tool / fimo skills install / set up Claude Code or Cursor for Fimo / add an agent to this project" → `references/agent-setup.md`
-- "Connect an AI coding client to a Fimo project through MCP / configure `fimo mcp` / expose Fimo tools to a local MCP client" → `references/mcp.md`
-- "Refresh / update installed Fimo skills / fimo skills sync / agent missing the latest fimo conventions" → `references/agent-setup.md`
+- "Install Fimo for my agent / fimo skills install / set up Claude Code, Codex, or Cursor for Fimo" → `references/agent-setup.md`
+- "Connect an agent to a Fimo project through MCP / configure `fimo mcp` / expose Fimo tools to a local MCP client" → `references/mcp.md`
+- "Refresh / update installed Fimo skills / fimo skills sync / agent missing the latest Fimo conventions" → `references/agent-setup.md`
 - "Report a Fimo problem or blocking feature request / contact Fimo support / a Fimo API or command keeps failing / a documented argument is rejected / a supported operation needs an undocumented workaround / a Fimo API is abnormally slow / a confirmed missing capability blocks completion or forces a fragile or heavily manual workaround" → `references/support.md`
 - "Regenerate rule files / I edited AGENTS.md / fimo rules sync" → `references/agent-setup.md`
 - "Show analytics / visitor stats / traffic / pageviews / how is my site performing / top pages / where do visitors come from" → `references/analytics.md` (7-day preview free for all; longer ranges require paid)

package/assets/skills/fimo-cli/references/agent-setup.md

@@ -2,12 +2,12 @@
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
-Fimo wires up to AI coding tools in two layers:
+Fimo connects agents in two layers:
 
-1. **One global bootstrap skill** — a tiny, generic `fimo` skill installed once per user, machine-wide (symlinked into each agent's global skills dir). It doesn't contain workflow content itself; it tells the agent to load the real, version-locked skills on demand from the CLI. It never goes stale because it just points at `fimo skills get`.
-2. **Per-project rule files** — `AGENTS.md` (universal) and `CLAUDE.md` ship in the project template. `fimo rules sync` regenerates the other agents' variants (`.cursor/rules/fimo.mdc`, `.windsurfrules`, `GEMINI.md`) from `AGENTS.md`.
+1. **One global bootstrap skill** — a tiny, generic `fimo` skill installed once per user, machine-wide (symlinked into each agent's global skills directory). It contains no workflow content; it routes the agent to skills fetched through `fimo skills get`.
+2. **Per-project rule files** — `AGENTS.md` (universal) and `CLAUDE.md` ship in the project template. `fimo rules sync` generates other agents' variants (`.cursor/rules/fimo.mdc`, `.windsurfrules`, `GEMINI.md`) from `AGENTS.md`.
 
-The rich skills (`fimo-code`, `fimo-cli`, `fimo-studio`, `fimo-migration`) are **never installed as files**. They're served on demand straight from the CLI, so they always match the installed version and never land in the project:
+The rich skills (`fimo-code`, `fimo-cli`, `fimo-studio`, `fimo-migration`) are **never installed as files**. They are served on demand and never land in the project. `fimo-code` resolves from the project's installed package; the others resolve from the CLI being run:
 
 ```bash
 npx fimo@latest skills list            # what's available
@@ -40,15 +40,15 @@ fimo skills sync                               # re-ensure the bootstrap + clean
 fimo skills uninstall                          # remove the global bootstrap
 ```
 
-`fimo skills install` installs the single global `fimo` bootstrap skill for the selected agents (symlinked into each agent's global skills dir; it transparently falls back to a copy when a symlink can't be created, e.g. under `npx`). It writes **nothing** into your project — the working tree stays clean.
+`fimo skills install` installs the single global `fimo` bootstrap skill for the selected agents (symlinked into each agent's global skills directory; it transparently falls back to a copy when a symlink can't be created, e.g. under `npx`). It writes **nothing** into your project — the working tree stays clean.
 
-Once installed, the agent discovers everything else through the bootstrap: it runs `fimo skills get <name>` to load the real skill for the task at hand.
+Once installed, the agent discovers everything else through the bootstrap: it runs `fimo skills get <name>` to load the skill for the task at hand.
 
-**`fimo skills sync`** re-ensures the global bootstrap for whichever agents already have it, and cleans up stale global skills that older CLI versions used to copy in (`fimo-cli`, `fimo-studio`, `fimo-migration`, and legacy migration skills). You rarely need it: the bootstrap is a symlink, so it always tracks the running CLI, and the real skills are fetched fresh via `fimo skills get`. Run it after upgrading from an old CLI to clear leftovers.
+**`fimo skills sync`** re-ensures the global bootstrap for whichever agents already have it, and cleans up stale global skills that older CLI versions used to copy in (`fimo-cli`, `fimo-studio`, `fimo-migration`, and legacy migration skills). You rarely need it: the bootstrap is a symlink, so it tracks the running CLI, and the real skills are fetched fresh via `fimo skills get`. Run it after upgrading from an old CLI to clear leftovers.
 
 **`fimo skills uninstall`** removes the global bootstrap for the selected agents.
 
-## `fimo rules sync` — rule files only
+## `fimo rules sync` — agent rule files only
 
 `fimo init` scaffolds `AGENTS.md` (the universal-spec file) and `CLAUDE.md` from the template. Other agents' variants are generated on demand:
 
@@ -60,7 +60,7 @@ Once installed, the agent discovers everything else through the bootstrap: it ru
 | gemini-cli                        | `GEMINI.md`                           |
 | codex / opencode / aider / others | none — they read `AGENTS.md` natively |
 
-`fimo rules sync` regenerates these variants from the current `AGENTS.md`. Use it when:
+`fimo rules sync` generates these variants from the current `AGENTS.md`. Use it when:
 
 - You edited `AGENTS.md` and want variants refreshed (delete the variant first — see below).
 - You added an agent that needs its own rule file generated.
@@ -81,15 +81,15 @@ Every command that takes agents accepts the same selection inputs:
 - `--agents=claude-code,cursor` — comma-separated list (headless)
 - `-a claude-code -a cursor` — repeatable short form
 - No flag → interactive multi-select. The picker has two sections:
-  - **Universal** — agents that read `AGENTS.md` natively (codex, opencode, aider, …). Always covered, not toggleable.
+  - **Universal** — agents that read `AGENTS.md` natively (Codex, OpenCode, Aider, …). Always covered, not toggleable.
   - **Additional** — agents that get the global bootstrap skill installed. The 6 popular ones (`claude-code`, `cursor`, `codex`, `opencode`, `windsurf`, `gemini-cli`) appear at the top of an 8-item scrollable viewport; the full list of 50+ supported agents is below the fold. Agents already set up on the machine are pre-checked.
 - `--agents=none` (only `fimo init`) — skip the global skill entirely.
 
-In headless contexts (CI, AI-tool-spawned commands), pass the flag explicitly. Env-var detection (only Claude Code's `CLAUDECODE` / `CLAUDE_CODE_ENTRYPOINT`) silently targets `claude-code` if the flag is omitted; every other agent must be named explicitly with `--agents` in a headless shell, or the command exits with "No agents detected and no --agents flag passed."
+In headless contexts (CI, agent-spawned commands), pass the flag explicitly. Env-var detection (only Claude Code's `CLAUDECODE` / `CLAUDE_CODE_ENTRYPOINT`) silently targets `claude-code` if the flag is omitted; every other agent must be named explicitly with `--agents` in a headless shell, or the command exits with "No agents detected and no --agents flag passed."
 
 ## Always current, never stale
 
-Because the only installed artifact is a generic pointer, and the real skills are fetched with `fimo skills get`, the content an agent reads always matches the running CLI. There's no version stamp to check and no cached copy to refresh — re-run `fimo skills get <name>` any time to get the current instructions.
+Because the only installed artifact is a generic pointer, the agent fetches current instructions with `fimo skills get`. `fimo-code` resolves from the project's installed package; the workflow skills resolve from the CLI being run. Re-run `fimo skills get <name>` any time to refresh them.
 
 ## When to use which
 
@@ -98,4 +98,4 @@ Because the only installed artifact is a generic pointer, and the real skills ar
 - "Clean up skills left by an old CLI version" → `fimo skills sync`
 - "I edited `AGENTS.md` and want variants regenerated" → delete the stale variant + `fimo rules sync`
 - "I'm done with Fimo on this machine" → `fimo skills uninstall`
-- For a fresh project, `fimo init` installs the global skill for the AI tools you select at scaffold time.
+- For a fresh project, `fimo init` installs the global skill for the agents you select at scaffold time.

package/assets/skills/fimo-cli/references/assets.md

@@ -2,7 +2,7 @@
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
-> For how to plug returned media into UI components (`FimoMedia` shape, `<Image>` integration), see **`fimo/references/assets.md`** and **`fimo/references/ui.md`**.
+> Package contract: run `npx fimo@latest skills get fimo-code --ref assets` for `FimoMedia`, and `--ref ui` for component integration.
 > For **generating** new images / videos with AI, see **`references/media.md`** for the task commands and recipes.
 
 This file covers the **CLI workflow** for media that already exists: uploading files, browsing the library, opening an asset to inspect it, moving / deleting items.
@@ -129,4 +129,4 @@ fimo assets delete <asset-id>
 
 1. Upload with `fimo assets upload` or generate with a task command such as `fimo image generate`.
 2. Keep the returned `url` (for direct use) or `id` (to attach to a `media` content-type field).
-3. To use in JSX, see `fimo/references/ui.md` — schema media → `<Image>` / `<Video>`, hardcoded URLs → `<StaticImage>`. **Never** use raw `<img src={asset.url}>`.
+3. To use in JSX, load the `fimo-code` UI reference — schema media → `<Image>` / `<Video>`, hardcoded URLs → `<StaticImage>`. **Never** use raw `<img src={asset.url}>`.

package/assets/skills/fimo-cli/references/content.md

@@ -2,15 +2,15 @@
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
-> For the JSON shape, field types, Tiptap node spec, slug rules, and generated React Query hooks — these are package surface (version-locked to the project's `fimo`). See **`fimo/references/content.md`**.
+> Package contract: run `npx fimo@latest skills get fimo-code --ref content` for the JSON shape, field types, Tiptap nodes, slug rules, and generated React Query hooks.
 
 This file covers the **CLI workflow** for content. Use it when the user wants to add a content type (blog, products, pages) or manage Singles and entries.
 
 ## Flow
 
-1. Write `src/schemas/{Uid}.json` — PascalCase filename (e.g. `BlogPost.json`). For the JSON shape and field types, load `fimo/references/content.md`.
+1. Write `src/schemas/{Uid}.json` — PascalCase filename (e.g. `BlogPost.json`). For the JSON shape and field types, load the `fimo-code` content reference.
 2. Run `fimo schemas push {Uid}`. It generates `src/schemas/{Uid}.types.ts` and `src/schemas/{Uid}.ts`, then registers the schema with Fimo. It does not run whole-project validation.
-3. App code imports the generated client from `@/schemas/{Uid}`, not from `.types.ts` directly. See `fimo/references/content.md` for the hook API.
+3. App code imports the generated client from `@/schemas/{Uid}`, not from `.types.ts` directly. See the `fimo-code` content reference for the hook API.
 4. Seed collections via `fimo entries create`, or update one-off content via `fimo singles update`. Generate cover images first with `fimo image generate` if needed (see `media.md` / `assets.md`).
 5. Write React pages that import from `@/schemas/{Uid}` and render with `fimo/ui` components.
 
@@ -34,7 +34,7 @@ The command is `fimo schemas` (plural). There is no singular `fimo schema` alias
 
 All commands accept `-C, --cwd <dir>` to point at a different project directory.
 
-Blocks schemas support at most 7 nested `blocks` levels, 40 variants in one `schema.oneOf`, and `min` or `max` values up to 200 items per blocks field. Load `fimo/references/content.md` for the complete blocks JSON shape.
+Blocks schemas support at most 7 nested `blocks` levels, 40 variants in one `schema.oneOf`, and `min` or `max` values up to 200 items per blocks field. Load the `fimo-code` content reference for the complete blocks JSON shape.
 
 Schema transitions are automatic. Adding optional fields and changing labels preserve content. A new required field backfills its `default` only where existing values need it; the push fails safely when no default can satisfy existing content. Removing a nested field or block variant removes only those values. `string` and `text` preserve values in both directions. Other primitive changes convert safe values and reject unsafe ones without changing the schema or entries. Lowering block `max` trims from the end; raising `min` fills from the blocks `default` templates. A reference target change clears its connections. Use repeatable `--rename old.path=new.path` arguments when a field moved by name so the one-time migration preserves its values; the operation is not stored in schema JSON. Collection-to-Single removes that type's entries and cleans inbound references; Single-to-collection preserves its entry. Run `fimo validate` after pushing.
 
@@ -76,7 +76,7 @@ fimo entries bulk-update <TypeName> (--file <path> | --stdin)
 fimo entries bulk-delete <TypeName> (--ids <id1>,<id2> | --where '<json>') [--locale es]
 ```
 
-`--body` is a **required** option on `create` and `update`. Its JSON shape (where `slug` goes, how `media` fields look, Tiptap richtext format) lives in `fimo/references/content.md`. **Always read that first before constructing an entry payload — slug must be inside `data`, media has a specific shape, richtext must be Tiptap JSONContent.**
+`--body` is a **required** option on `create` and `update`. Its JSON shape (where `slug` goes, how `media` fields look, Tiptap richtext format) lives in the `fimo-code` content reference. **Always read that first before constructing an entry payload — slug must be inside `data`, media has a specific shape, richtext must be Tiptap JSONContent.**
 
 `entries list` accepts the same read query surface as generated hooks:
 
@@ -100,7 +100,7 @@ Reference filters take the target `id` string (`{"author":"750e..."}`). On a to-
 
 Polymorphic references declare `targets: ["Post", "Product"]` instead of `target` (never both) and their values carry both parts: `{ "contentType": "Post", "id": "..." }`. Populate returns mixed full entries, and generated hooks expose `$type` on each populated value to branch on. `--where` on polymorphic fields is not supported yet and fails with a clear error.
 
-In generated React code, the equivalent is `populate: ['author', 'contributors'] as const` in the schema hook/query params. Let hooks infer the result when possible; if a named TypeScript shape is needed, use the generated `BlogPostResult<TFields, TPopulate>` type documented in `fimo/references/content.md`. Writes use the separate generated `BlogPostInput` type.
+In generated React code, the equivalent is `populate: ['author', 'contributors'] as const` in the schema hook/query params. Let hooks infer the result when possible; if a named TypeScript shape is needed, use the generated `BlogPostResult<TFields, TPopulate>` type documented in the `fimo-code` content reference. Writes use the separate generated `BlogPostInput` type.
 
 ### Read-only SQL
 
@@ -191,7 +191,7 @@ fimo entries bulk-delete BlogPost --where '{"archived":true}'
 
 Each bulk request handles at most 1,000 entries. Missing requested IDs do not fail valid work: the CLI prints a warning, and `--json` includes both a top-level `warnings` array and the exact IDs in `data.meta.missing`. Bulk writes use the same validation, locale, reference, and content-change paths as singular entry writes. They apply entries one at a time. Recoverable create and update errors report how many earlier entries were already changed.
 
-For reference schema JSON and entry value shape, load `fimo/references/content.md` § Reference fields. The short version:
+For reference schema JSON and entry value shape, load the `fimo-code` content reference § Reference fields. The short version:
 
 ```json
 {
@@ -257,13 +257,13 @@ Use `"isSingleton": true` for a Single with exactly one set of content. Generate
 
 ## "Add a blog" recipe
 
-1. Load `fimo/references/content.md` for the JSON shape and field types.
+1. Load the `fimo-code` content reference for the JSON shape and field types.
 2. Write `src/schemas/BlogPost.json` with fields `title`, `body` (richtext), `coverImage` (media), etc. Do NOT declare a `slug` field — `slug` (and `id`, `entryId`, `documentId`, `locale`, `createdAt`, `updatedAt`, `__fimo`) is reserved entry metadata and will be rejected; every entry gets a `slug` for free.
 3. Run `fimo schemas push BlogPost`.
 4. Generate cover images: `fimo image generate --prompt "..." --aspect-ratio 16:9` (see `media.md`).
 5. Seed entries: `fimo entries create BlogPost --body '{"data": {"slug": "first-post", "title": "...", "coverImage": {...}}}'`.
-6. Load `fimo/references/ui.md` for the `<Text>`, `<Image>`, `<RichText>` components.
-7. Load `fimo/references/labels.md` for wrapping labels in `t()`.
+6. Load the `fimo-code` UI reference for the `<Text>`, `<Image>`, `<RichText>` components.
+7. Load the `fimo-code` labels reference for wrapping labels in `t()`.
 8. Write the React page using the generated `useGet()` hook from `@/schemas/BlogPost`.
 
 ## When to run sync manually

package/assets/skills/fimo-cli/references/forms.md

@@ -2,15 +2,15 @@
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
-> For the JSON spec, generated Zod schema, submit helper signature, and React usage patterns — these are package surface (version-locked to the project's `fimo`). See **`fimo/references/forms.md`**.
+> Package contract: run `npx fimo@latest skills get fimo-code --ref forms` for the JSON spec, generated Zod schema, submit helper, and React usage.
 
 This file covers the **CLI workflow** for forms. Use it when the user wants to add a contact form, signup, feedback form, etc.
 
 ## Flow
 
-1. Write `src/forms/{name}.json` — kebab-case filename (e.g. `contact-us.json`). For the JSON spec and field types, load `fimo/references/forms.md`.
+1. Write `src/forms/{name}.json` — kebab-case filename (e.g. `contact-us.json`). For the JSON spec and field types, load the `fimo-code` forms reference.
 2. Register with `fimo forms push {name}` — creates the form, obtains its `id`, patches it back into the JSON file.
-3. Pre-build generates `src/forms/{name}.ts` (Zod schema + `submitX` helper). See `fimo/references/forms.md` for the generated API.
+3. Pre-build generates `src/forms/{name}.ts` (Zod schema + `submitX` helper). See the `fimo-code` forms reference for the generated API.
 4. Write a React component that imports from `@/forms/{name}`.
 
 Steps 1, 3, and 4 reference the `fimo-code` skill (`npx fimo@latest skills get fimo-code`). Step 2 is the CLI command.
@@ -45,11 +45,11 @@ Use this when the user asks "who filled out the contact form?", "how many signup
 
 ## "Add a contact form" recipe
 
-1. Load `fimo/references/forms.md` for the JSON spec.
+1. Load the `fimo-code` forms reference for the JSON spec.
 2. Write `src/forms/contact-us.json` with the required fields.
 3. Run `fimo forms push contact-us` — the `id` is patched back into the JSON automatically.
-4. Load `fimo/references/forms.md` for the generated `submitContactUs` + `ContactUsSchema` API.
-5. Load `fimo/references/labels.md` for wrapping form labels in `t()`.
+4. Load the `fimo-code` forms reference for the generated `submitContactUs` + `ContactUsSchema` API.
+5. Load the `fimo-code` labels reference for wrapping form labels in `t()`.
 6. Write the React form component that imports from `@/forms/contact-us`.
 
 **Register BEFORE writing app code that depends on the form** — otherwise the generated `.ts` doesn't exist and the runtime fetch 404s.

package/assets/skills/fimo-cli/references/init.md

@@ -120,7 +120,7 @@ After `fimo init` completes, the project root has `AGENTS.md` (universal) and `C
 1. `cd <project-dir>` — switch into the new project.
 2. `Read` the project rules file: `AGENTS.md` (or `CLAUDE.md` if you're Claude Code).
 3. Load the code skill on demand: `npx fimo@latest skills get fimo-code`.
-4. From the `fimo-code` skill's "load these references up front" section, batch-read the referenced docs (`npx fimo@latest skills get fimo-code --ref content`, `--ref forms`, `--ref assets`, `--ref labels`, `--ref locales`, `--ref ui`) before generating any significant code.
+4. Load only the `fimo-code` references needed for the first task, using `npx fimo@latest skills get fimo-code --ref <doc>`.
 
 Once those are in context, generation respects the project's conventions (schemas, `t()`, `fimo/ui` components, asset handling).
 

package/assets/skills/fimo-cli/references/labels.md

@@ -2,7 +2,7 @@
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
-> For the `t()` helper signature, `useLabels()` hook, key naming rules, and the "wrap every user-facing string" rule, see **`fimo/references/labels.md`**.
+> Package contract: run `npx fimo@latest skills get fimo-code --ref labels` for `t()`, `useLabels()`, key naming, and wrapping rules.
 > For locale configuration and route-prefix validation, see **`references/locales.md`**.
 
 This file covers the **CLI workflow** for labels: static UI copy such as nav items, buttons, headings, placeholders, alt text, and SEO strings.
@@ -61,9 +61,9 @@ Prefer `fimo validate` — this primitive is for narrow debugging/test use.
 
 ## Workflow
 
-1. Write JSX with `t('key')` calls. Load `fimo/references/labels.md` for the rules.
+1. Write JSX with `t('key')` calls. Load the `fimo-code` labels reference for the rules.
 2. Run `fimo validate`.
 3. Add missing values with `fimo labels set` or `fimo labels set-many`.
 4. Editors can now change copy in the Fimo admin without code changes.
 
-For the helper signatures, hooks, and code patterns, **always** load `fimo/references/labels.md` before writing code that uses `t()`.
+For the helper signatures, hooks, and code patterns, **always** load the `fimo-code` labels reference before writing code that uses `t()`.

package/assets/skills/fimo-cli/references/locales.md

@@ -2,7 +2,7 @@
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
-This file covers CLI-side locale configuration and validation. For code helpers such as `fimoRoutes()` and `FimoLink`, load `fimo/references/locales.md`.
+This file covers CLI-side locale configuration and validation. For code helpers such as `fimoRoutes()` and `FimoLink`, run `npx fimo@latest skills get fimo-code --ref locales`.
 
 ## Configure Locales
 

package/assets/skills/fimo-code/SKILL.md

@@ -27,9 +27,9 @@ This is the load-bearing rule for every code change. **Fimo's whole point is tha
 
 If you find yourself about to hardcode anything user-facing, **stop and use the appropriate Fimo primitive instead.** For pushing the schema/form/asset to the backend, that's CLI territory — see the `fimo-cli` skill.
 
-## When starting code work, load these references up front
+## Load only the references the task needs
 
-These define the package surface for the load-bearing primitives. **Read all six before generating significant code:**
+Each reference defines one package contract. Fetch it when the task reaches that surface; do not batch-load unrelated references:
 
 - `references/content.md` — schema JSON shape, field types, Tiptap nodes, generated React Query hooks
 - `references/forms.md` — form JSON spec, generated Zod + `submitX` helper

package/assets/skills/fimo-studio/SKILL.md

@@ -7,7 +7,8 @@ description: >-
   "how do I X in the UI", or screenshots of the dashboard. Topics
   covered: dashboard content and CMS, publishing from the dashboard,
   dashboard SEO/domain settings, schedules and run history, outbound webhooks,
-  visual editing, version history UI, dashboard sharing/billing, and dashboard chat. Never describe
+  visual editing, version history UI, dashboard sharing/billing, dashboard chat,
+  and the command palette. Never describe
   UI locations, buttons, or panels from memory — always read the relevant
   reference file first.
 ---
@@ -30,6 +31,7 @@ Read the relevant reference file when the user's question matches a topic.
 
 | Topic                    | Reference                               | When to read                                          |
 | ------------------------ | --------------------------------------- | ----------------------------------------------------- |
+| Command Palette          | references/command-palette.md           | "What can I open with Cmd+K?", "Quick actions"        |
 | Publish & Deploy         | references/publish-and-deploy.md        | "How do I publish?", "How do I make my site live?"    |
 | Custom Domains           | references/custom-domains.md            | "How do I use my own domain?", "DNS setup"            |
 | Content Management (CMS) | references/cms.md                       | "How does the CMS work?", "How do I add blog posts?"  |

package/assets/skills/fimo-studio/references/ai-chat.md

@@ -1,6 +1,6 @@
 ## Where to Find It
 
-The AI chat opens as a floating panel by default. You can dock it to the left or right edge from the project menu's **Chat position** submenu (Floating / Left / Right). Toggle the chat open or closed by clicking the **chat (speech-bubble) icon** in the header, or press **Cmd+Shift+H** (Mac) / **Ctrl+Shift+H** (Windows/Linux).
+On desktop, the AI chat opens docked on the left by default. You can make it floating or dock it on either side from the project menu's **Chat position** submenu (Floating / Left / Right). Toggle the chat open or closed by clicking the **chat (speech-bubble) icon** in the header, or press **Cmd+Shift+H** (Mac) / **Ctrl+Shift+H** (Windows/Linux).
 
 ## Sending a Message
 

package/assets/skills/fimo-studio/references/command-palette.md

@@ -0,0 +1,31 @@
+# Command Palette
+
+Press **Cmd+K** on macOS or **Ctrl+K** on Windows and Linux to open the command palette from any authenticated Studio screen. Start typing to filter the available commands.
+
+## What You Can Open
+
+The palette includes the destinations you are allowed to use:
+
+- Organizations, projects, and the main Studio workspaces
+- Preview pages
+- CMS Collections, Singles, Forms, Labels, and content types
+- Agent runs, definitions, and individual agents
+- Project settings sections
+- Asset folders and code files
+
+You can also open documentation, feedback, account actions, project history, invitations, and the Publish review flow. Use **Escape** to return from a searchable subpage to the main command list, then press it again to close the palette.
+
+## Actions for the Current Page
+
+Studio adds commands that are relevant to the page you are viewing. Depending on the page and your permissions, these can include:
+
+- Refreshing Preview or opening it in a new tab
+- Creating a CMS entry or changing the content locale
+- Uploading an asset, creating a folder, or generating an image
+- Opening a code file or toggling the code sidebar
+- Running an agent, opening its Preview result, or resolving proposed changes
+- Adding a language, secret, schedule, or webhook
+
+## Permissions and Confirmations
+
+The palette follows the same permissions, plan availability, and feature flags as Studio's visible navigation and buttons. Publishing and other reviewed flows open their normal dialog instead of acting immediately. If a command is unavailable on the page or for your role, it is not shown.

package/dist/build/vite/plugins/content-sync.js

@@ -29,7 +29,7 @@ export default function contentSyncPlugin() {
                     return;
                 }
                 if (file.startsWith(schemasGlob)) {
-                    syncSchemas({ cwd: rootDir, verbose: false });
+                    syncSchemas({ cwd: rootDir, framework: 'vite', verbose: false });
                     return;
                 }
                 if (file.startsWith(formsGlob)) {

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-09T19:42:51.429Z",
+  "bundledAt": "2026-08-11T07:27:30.271Z",
   "cliVersion": "0.11.0",
   "external": [
     "oxc-parser",