fimo 2.4.0-staging.1 → 2.4.0-staging.3

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

@@ -100,7 +100,7 @@ Load the matching reference when the user's request fires its trigger. Recipes t
 - "List history / create a restore point / recover content and code / restore a previous version / snapshot usage or retention" → `references/history.md`
 - "Create a Branch / feature Branch / switch Branches / merge Branches / diff two Branches / Branch status / what changed on this Branch / sync from parent / cut a release / tag a version / go to prod" → `references/branches.md`
 - "List my projects / clone an existing project locally / check out a project / delete this project / unpublish / rename the project / manage projects across the org" → `references/projects.md`
-- "Migrate an existing Webflow / Framer / Squarespace / Wix / Carrd site from only a published URL" → load the `fimo-migration` skill and start with `fimo migrate <url> [dir]` to prepare the agent-ready migration draft
+- "Migrate an existing Webflow / Framer / Squarespace / Wix / Carrd site from only a published URL" → load the `fimo-migration` skill, set the target up with `fimo migrate init <dir>`, and read the published site yourself with a browser — the CLI does not crawl it
 - "Migrate from an exported project, source repository, Webflow code export plus CMS CSVs, Framer CMS CSVs, Squarespace XML/CSV, Wix CSVs, Carrd/static export, or downloaded site files" → load the `fimo-migration` skill and use the source repo/export as the migration source of truth
 - "How do AI agents read my site / markdown for agents" → `references/deploy.md`
 - "Modify the URL of the website / change my project's address / connect a custom domain (e.g. blog.example.com) / rename the Fimo-provided `*.fimo.site` subdomain / buy a new domain through Fimo / set up a domain" → `references/domains.md`
@@ -145,7 +145,7 @@ These fire at specific moments in the project lifecycle. **Surface them proactiv
 - **Using `fimo deploy --publish` casually** — `--publish` makes the site live to the public. Plain `fimo deploy` (preview) is the default. Use `--publish` only when the user says "ship it" / "go live" / "publish".
 - **Bare `fimo init` in a non-interactive shell** — will hang. Always pass `[dir]`, `--no-install` (or `--install`), `--no-skills` (or `--skills`), and `--org`/`--agents` as needed explicitly when scripted.
 - **Hardcoding content / strings / images in code** — that's what schemas, `t()`, and the media library are for. See the `fimo-code` skill's anti-patterns.
-- **Adding another deploy tool (Vercel, Netlify, Cloudflare Pages)** — Fimo handles deploys; don't bolt another platform on.
+- **Adding another deploy tool**. Fimo handles deploys; don't bolt another platform on.
 - **Committing secrets** — hidden values use `fimo secrets`; public browser-safe values use `fimo vars`. Local env files are ignored and must not become deploy inputs.
 - **Hardcoding tokens in flags** — use the credentials written by `fimo login` (one file per backend at `~/.config/fimo/credentials/<host>-<hash>.json`).
 - **Treating the daily allowance as extra credits** — the allowance section appears only for legacy Premium organizations, and `fimo credits` already includes its spendable credits in "Available now"; it is accounting context, not an amount to add.

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

@@ -36,7 +36,7 @@ fimo --branch <name> <command>  # peek at another Branch for one command (does n
 | `fimo diff [from] [to]` | `git diff`          | Two-Branch diff across all surfaces. Defaults `from` = current Branch, `to` = `main`. `--surface <name>` limits to one; `--json`; `--no-color`.                              |
 | `fimo status`           | `git status`        | Multi-surface status for the current Branch vs its parent. See below.                                                                                                        |
 | `fimo merge <from>`     | `git merge`         | Merge another Branch into the current one (multi-surface, atomic, interactive conflict resolver). See below.                                                                 |
-| `fimo publish`          | —                   | Publish the synced Production source revision with a stable Fimo publication ID. See "Publishing" below.                                                                     |
+| `fimo publish`          | —                   | Publish the revision already on the Fimo remote (no push) with a stable Fimo publication ID. See "Publishing" below.                                                         |
 
 All of these accept the global `--branch` override. `diff`, `status`, `merge`, and `publish` additionally accept `-C, --cwd <dir>` to point at a project directory.
 
@@ -98,10 +98,10 @@ Syncs the current Branch's data plane from its parent (or `--from <ancestor>`).
 
 Two different "go live" mechanisms — don't confuse them:
 
-- **`fimo publish [--label <text>] [--notes <md>]`** — publishes the synced Production source revision. Fimo assigns the immutable publication ID; the label and notes are optional annotations. `--skip-validate` is an operator override.
-- **`fimo deploy --publish`** — the project-publish path. Pushes the current Production source code and flips the project live in one shot. See `references/deploy.md`.
+- **`fimo publish [--label <text>] [--notes <md>]`** — publishes the revision already on the Fimo remote without pushing. Fimo assigns the immutable publication ID; labels and notes are optional annotations. `--skip-validate` is an operator override.
+- **`fimo deploy --publish`** — pushes the current Production source Branch and flips the project live. See `references/deploy.md`.
 
-Use `fimo publish` when the Production source Branch is already synced; use `fimo deploy --publish` when the local revision still needs to be pushed first. Both only run from the configured Production source Branch. Existing projects use `main`.
+Choose `fimo deploy --publish` when local changes need to go live; choose `fimo publish` when the remote revision is the intended release. Both only run from the configured Production source Branch. Existing projects use `main`.
 
 ## Anti-patterns
 

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

@@ -123,12 +123,9 @@ There's nothing special about this — it's the same `fimo deploy` you'd run lat
 
 ## Publishing: `fimo deploy --publish` vs `fimo publish`
 
-Two different "go live" mechanisms — pick deliberately:
+Use `fimo deploy --publish` to push and publish local changes. Use `fimo publish` to publish the revision already on the Fimo remote without pushing. Both target the configured Production source Branch.
 
-- **`fimo deploy --publish`** — push what's on the Production source Branch now and flip the project live in one shot. The simple "ship it" path. Runs from that Branch only.
-- **`fimo publish [--label <text>] [--notes <md>]`** — publish the synced Production source revision without pushing. Fimo assigns the immutable publication ID; a label and notes are optional human annotations. See `references/branches.md`.
-
-When unsure, use `fimo deploy --publish` so the local revision is pushed before it goes live. Use `fimo publish` when the Production source Branch is already synced.
+Check the reported source commit and warnings before reporting completion. If local work is excluded or the built commit cannot be confirmed, follow the CLI's hint.
 
 ## Markdown for AI agents
 

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

@@ -51,8 +51,8 @@ Global flags: `--project <id>` / `-C, --cwd <dir>` for project resolution, `--or
 When a user says "I want to change my website's URL," ask which case fits:
 
 - **"It's fine as-is, just nicer"** → `rename-default` or `suggest-default`. Free, instant, no DNS.
-- **"I own example.com already"** → `add example.com`. Premium. They configure CNAME at their registrar.
-- **"I want to buy a domain"** → `search` → `pricing` → `buy`. Premium + the registered-domains feature flag has to be on (it's not enabled in every environment).
+- **"I own example.com already"** → `add example.com`. Pay as you go or higher. They configure CNAME at their registrar.
+- **"I want to buy a domain"** → `search` → `pricing` → `buy`. The registered-domains feature flag and an eligible plan must be on (the flag is not enabled in every environment).
 
 If they aren't sure, run `fimo domains suggest-default` first — it's free, takes one step, and a good fallback if they don't want to commit to a domain purchase.
 
@@ -60,7 +60,7 @@ If they aren't sure, run `fimo domains suggest-default` first — it's free, tak
 
 After the automatic first-preview deploy on a newly created project, offer a cleaner free `*.fimo.site` URL before the first public publish when there is no custom domain and the current default slug still looks generated or was never explicitly chosen. Choosing it now lets the first public launch use the clean URL. Skip the offer if the user already chose the default slug, attached a custom domain, or declined.
 
-The default URL is free and needs no DNS. A custom domain is the separate Premium workflow above. A default slug can be reserved before publication, but it returns "Project Not Found" until the site is published. Renaming changes the address that will become public, so never silently claim a suggestion:
+The default URL is free and needs no DNS. A custom domain uses the Pay as you go (or higher) workflow above. A default slug can be reserved before publication, but it returns "Project Not Found" until the site is published. Renaming changes the address that will become public, so never silently claim a suggestion:
 
 1. Run `fimo domains suggest-default --base "<brand>" --json` to get candidates.
 2. Show the candidates and ask the user to choose one explicitly.
@@ -72,7 +72,7 @@ Choosing the slug does not publish the site. The first successful `fimo deploy -
 
 The CLI never charges directly. Two distinct money paths:
 
-1. **Premium subscription** — gates `add`, `buy`, `owned`, `refresh`, `remove` for custom domains. The user upgrades through the Fimo web app (Hyperline-hosted checkout). When a free user runs a gated command they get a 403 with the upgrade URL — surface it as-is to the user.
+1. **Pay as you go or higher** — gates custom-domain operations. A valid card activates Pay as you go through the Fimo web app (Hyperline-hosted checkout). When a Free user runs a gated command they get a 403 with the billing URL; surface it as-is to the user.
 2. **Domain registration** — `fimo domains buy` creates a Hyperline invoice with `payment_method_strategy: 'external'` and returns a `checkoutUrl`. The user opens that URL in a browser to pay. **No money moves until they pay the invoice.** That's why `--yes` on `buy` is safe: it queues an invoice; the human still has to consent at checkout.
 
 Domain prices come from name.com via the registrar reseller. They vary by TLD and can change. Pricing is in USD (cents in the API, formatted as dollars in CLI output).
@@ -121,7 +121,7 @@ Propagation: typically 15–30 minutes, up to 48 hours rarely.
 ## Common errors
 
 - **"Project Not Found" on a new URL or custom domain.** The route exists but the site was never published — run `fimo deploy --publish`.
-- **"Custom domains require a Premium plan."** — the operation is paid; the message includes the org billing URL. Free users can still run `list`, `rename-default`, `suggest-default`, `search`, and `pricing`.
+- **"Custom domains require Pay as you go or higher."** — add a card at `/app/billing`, then retry. Free users can still run `list`, `rename-default`, `suggest-default`, `search`, and `pricing`.
 - **"Domain purchase is not enabled on this account."** — the registered-domains feature flag is off on this API instance. Contact support.
 - **"This URL is not available."** — slug or hostname collides with another project or is reserved.
 - **"That's a Fimo-owned domain."** — user tried `add <something>.fimo.site`. Use `rename-default` instead.

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

@@ -57,9 +57,9 @@ them are present.
 {
   "redirects": [
     {
-      "source": "/(.*)",
-      "has": [{ "type": "header", "key": "x-vercel-ip-country", "value": "GB" }],
-      "destination": "/uk/:path*"
+      "source": "/offers",
+      "has": [{ "type": "header", "key": "x-promo", "value": "summer" }],
+      "destination": "/summer-sale"
     }
   ],
   "rewrites": [
@@ -74,12 +74,13 @@ them are present.
 
 | `type`   | Matches on                                           |
 | -------- | ---------------------------------------------------- |
-| `header` | a request header, including CDN-injected geo headers |
+| `header` | a request header                                     |
 | `cookie` | a cookie                                             |
 | `query`  | a query parameter                                    |
 | `host`   | the hostname the request arrived on — takes no `key` |
 
 Omit `value` to match on presence alone, as the `consent` cookie above does.
+The redirect example requires the request to include `x-promo: summer`.
 
 **Prefer doing this in the application when it can.** Middleware, a loader, or a
 server component can be run and tested locally; a condition here only takes

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

@@ -24,7 +24,7 @@ JSON output contains only the Branch identity and hosted URL:
     "project_id": "prj_abc",
     "branch": "main",
     "env": "main",
-    "preview_url": "https://fimo-preview-example.vercel.app"
+    "preview_url": "https://preview.example.com"
   }
 }
 ```

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

@@ -43,10 +43,10 @@ fimo rename "<Site Name>"        # local edit: set seo.siteName in the project c
 
 ## Publish commands
 
-| Command                 | Effect                                                                     |
-| ----------------------- | -------------------------------------------------------------------------- |
-| `fimo deploy --publish` | Push the current Production source + flip the project live in one shot.    |
-| `fimo projects publish` | Flip the project live (no git push).                                       |
-| `fimo publish`          | Flip the synced Production source revision live; optional label and notes. |
+| Command                 | Effect                                                                  |
+| ----------------------- | ----------------------------------------------------------------------- |
+| `fimo deploy --publish` | Push the current Production source + flip the project live in one shot. |
+| `fimo projects publish` | Flip the project live (no git push).                                    |
+| `fimo publish`          | Flip the revision already on the Fimo remote live (no git push).        |
 
 See `references/deploy.md` and `references/branches.md` for the full picture.

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

@@ -72,6 +72,7 @@ Each reference defines one package contract. Fetch it when the task reaches that
 - Locale ownership and framework handoff → `references/locales.md`
 - Upgrading a React Router app that imports `fimo/react-router/routes` → `references/migrations/react-router-route-ownership.md`
 - Astro connector and output/adapter contract → `references/frameworks/astro.md`
+- Astro/SvelteKit SEO or a new content route → the framework reference, then `references/frameworks/seo-head.md` for value ownership and edit-and-render acceptance
 - Framework detection, production routing, and hosting adapters → `references/frameworks/hosting.md`
 - Major visual work → `references/design.md`
 

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

@@ -6,7 +6,9 @@ This file covers media fields and the Fimo image components.
 
 ## Media field values
 
-A media field stores a reference to an asset, not a copy of the asset metadata. Write the value returned by upload or generation:
+For single-image and gallery schemas, see `references/content/schema.md`.
+
+Each media object stores a reference to an asset, not a copy of the asset metadata. Use the value returned by upload or generation:
 
 ```json
 {
@@ -31,7 +33,7 @@ const withAsset = await Post.getBySlug('hello', { populate: ['cover'] });
 
 `populate` takes top-level field names. A blocks field populates every media value inside it. One lookup covers all selected media in the response. Media inside a populated reference target stays a reference. Use `fimo assets open <id> --download` to inspect the source file.
 
-Generated reads wrap media in `FimoMedia`. Its `id`, `alt`, `name`, `mime`, `width`, and `height` can be absent. A populated value has the current facts when the asset resolves; missing or external assets stay unchanged. `source` is internal. Pass the whole value to `<Image>` or `<Video>`.
+Generated reads wrap each media object in `FimoMedia`. Its `id`, `alt`, `name`, `mime`, `width`, and `height` can be absent. A populated value has the current facts when the asset resolves; missing or external assets stay unchanged. `source` is internal. Pass one `FimoMedia` value, not the array, to `<Image>` or `<Video>`.
 
 ## Rendering in application code
 

package/assets/skills/fimo-code/references/best-practices/next.md

@@ -38,5 +38,3 @@ Use `instant = true` to find blocking code, then verify with `next build` and `n
 - Avoid duplicate content reads between `generateMetadata` and the page.
 
 Verify valid and missing slugs, canonical and initial HTML, shipped JavaScript, duplicate reads, image sizing, instant shell rendering, streaming, freshness, and bounded prefetching.
-
-Sources: [Instant Navigations](https://nextjs.org/blog/next-16-3-instant-navigations), [`partialPrefetching`](https://github.com/vercel/next.js/blob/canary/docs/01-app/03-api-reference/05-config/01-next-config-js/partialPrefetching.mdx), and [`instant`](https://github.com/vercel/next.js/blob/canary/docs/01-app/03-api-reference/03-file-conventions/02-route-segment-config/instant.mdx).

package/assets/skills/fimo-code/references/content/schema.md

@@ -14,6 +14,7 @@ Write one schema per `src/schemas/<Uid>.json`. The PascalCase filename must matc
     "publishedAt": { "type": "date" },
     "featured": { "type": "boolean" },
     "cover": { "type": "media" },
+    "gallery": { "type": "media", "multiple": true },
     "metadata": { "type": "json" },
     "author": { "type": "reference", "target": "Author" },
     "contributors": { "type": "reference", "target": "Author", "many": true }
@@ -80,11 +81,13 @@ Never declare `id`, `entryId`, `documentId`, `slug`, `locale`, `createdAt`, `upd
 | `boolean`   | boolean                    | flags                                    |
 | `date`      | ISO date string            | calendar days; loose about the form      |
 | `datetime`  | ISO instant with offset    | exact moments (`2026-08-13T09:30:00Z`)   |
-| `media`     | media object or array      | images, video, files                     |
+| `media`     | media object by default    | images, video, files                     |
 | `json`      | JSON                       | structured metadata                      |
 | `reference` | `{ "id": "..." }` or array | links to another schema                  |
 | `blocks`    | ordered object array       | nested/repeatable sections               |
 
+Set `multiple: true` on a media field for an array, even with one image. See `references/assets.md` for the object shape.
+
 A `datetime` value must carry `Z` or `±HH:MM`; a bare day or a naive local time is rejected. Render it with `<DateTime>`, which keeps the whole instant in the `<time datetime>` attribute, and a `date` with `<Date>`. `unique` is not supported on `datetime`.
 
 An enum string uses `options`; its optional `default` must be one of them:

package/assets/skills/fimo-code/references/design.md

@@ -44,10 +44,10 @@ Reference sites to anchor the aesthetic direction. Pull any well-known site, bra
 | Category                 | Example Anchors                                                                                           | Quality Bar                                                                |
 | ------------------------ | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
 | **Creative / Agency**    | Awwwards, FWA, CSS Design Awards, Pentagram, Sagmeister & Walsh, Active Theory, Fantasy Interactive, Resn | Would it win Awwwards SOTD? Would Pentagram put this in their portfolio?   |
-| **SaaS / Product**       | Linear, Vercel, Stripe, Notion, Figma, Raycast, Arc Browser, Supabase, Mercury, Clerk, Loom, Pitch        | Is it Linear-polished? Would a developer tweet "their site is so clean"?   |
+| **SaaS / Product**       | Linear, Stripe, Notion, Figma, Raycast, Arc Browser, Supabase, Mercury, Clerk, Loom, Pitch                | Is it Linear-polished? Would a developer tweet "their site is so clean"?   |
 | **Editorial / Blog**     | Medium, Substack, The Verge, NYT, The Atlantic, Monocle, It's Nice That, Eye on Design, Wired             | Would The Verge's design team respect this? Is it magazine-worthy?         |
 | **E-commerce**           | Apple Store, Shopify Dawn, Gumroad, Everlane, Glossier, SSENSE, Mr Porter, Mejuri, Allbirds               | Does it feel Apple Store premium? Would you trust buying from this?        |
-| **Documentation**        | Stripe Docs, Tailwind Docs, Vercel Docs, Supabase Docs, Prisma Docs, Algolia Docs, Clerk Docs             | Is it Stripe Docs clear? Can a developer find what they need in 3 seconds? |
+| **Documentation**        | Stripe Docs, Tailwind Docs, Supabase Docs, Prisma Docs, Algolia Docs, Clerk Docs                          | Is it Stripe Docs clear? Can a developer find what they need in 3 seconds? |
 | **Personal / Portfolio** | Read.cv, Paco Coursey, Josh Comeau, Rauno Freiberg, Brian Lovin, Lee Robinson, Linus Rogge                | Would Read.cv feature this? Is it memorable and distinctly personal?       |
 | **Corporate**            | Apple, Stripe, Airbnb, Slack, Square, Intercom, Dropbox, Zendesk                                          | Does it feel Airbnb-trustworthy? Premium but not flashy?                   |
 | **Dashboard**            | Linear, Figma, Raycast, Retool, Rows, Height, Airtable, Coda                                              | Is it Linear-efficient? Dense but never cluttered?                         |

package/assets/skills/fimo-code/references/frameworks/astro.md

@@ -1,6 +1,6 @@
 # Astro integration
 
-Use this reference for an existing Astro application. The application keeps its route files, output mode, adapter, locale system, links, `<html lang/dir>`, and SEO. Fimo connects content, labels, native rendering, preview, and hosting.
+Use this reference for an existing Astro application. The application keeps its route files, output mode, adapter, locale system, links, `<html lang/dir>`, and per-page SEO. Fimo connects content, labels, native rendering, preview, hosting, and the site-wide SEO defaults from Studio's Settings → SEO.
 
 ## Setup
 
@@ -90,6 +90,42 @@ browser values before submitting. Do not import the server form module into a
 client island; add a project endpoint if the form is intentionally browser-
 submitted.
 
+## SEO defaults
+
+Resolve the current route, apply page values, then convert to native attributes.
+New projects have this in `src/layouts/Base.astro`. Existing apps should extend
+their current head component, preserving unrelated metadata.
+
+```astro
+---
+import { resolveSeoForPath, toSeoHead } from 'fimo/seo';
+import config from '../../.fimo/config.json';
+
+const { seo = resolveSeoForPath(Astro.url.pathname, config) } = Astro.props;
+const canonicalUrl = seo?.url ? new URL(Astro.url.pathname, seo.url).href : undefined;
+const head = toSeoHead(seo, { canonicalUrl });
+---
+<head>
+  <title>{head.title ?? 'My site'}</title>
+  {head.meta.map((attributes) => <meta {...attributes} />)}
+  {head.links.map((attributes) => <link {...attributes} />)}
+</head>
+```
+
+For a content page, resolve after loading the entry and pass the final values
+to the layout: `const seo = resolveSeoForPath(Astro.url.pathname, config, { article })`,
+then `<Base lang={locale} seo={seo}>`. Route templates can read
+`{{article.title}}`. Apply app-owned overrides before conversion so the title,
+Open Graph and Twitter tags agree.
+
+The example canonical policy fits a root-hosted site. Preserve the app's own
+production domain, base path and trailing-slash policy. Omitting the converter's
+`canonicalUrl` omits canonical and `og:url`; `seo.url` alone is only a site base.
+Imported config changes need sync and rebuild/redeploy. Content freshness
+follows the route's rendering and caching policy.
+
+Full field and composition contract: read `references/frameworks/seo-head.md` when changing SEO.
+
 ## Static and on-demand rendering
 
 Keep the application's per-route rendering choice:

package/assets/skills/fimo-code/references/frameworks/hosting.md

@@ -64,6 +64,28 @@ local environment alias by hand.
 projects. Do not add it to new code, env files, setup instructions, or migration
 plans.
 
+## `hosting`: how the deployed site is served
+
+Declare hosting rules only in `.fimo/config.json#hosting`, not provider
+deployment files. Run `fimo validate` to catch unsupported keys and malformed rules.
+
+| Key             | Shape                                                            |
+| --------------- | ---------------------------------------------------------------- |
+| `rewrites`      | `{ source, destination }`, URL unchanged                         |
+| `redirects`     | `{ source, destination, permanent?, statusCode? }`               |
+| `headers`       | `{ source, headers: [{ key, value }] }`, response headers        |
+| `cleanUrls`     | Serve `/about` for `/about.html` and redirect the extension away |
+| `trailingSlash` | `true` requires a trailing slash, `false` forbids one            |
+
+Rewrites, redirects, and header rules accept `has` / `missing` conditions:
+`header`, `cookie`, and `query` require `key`; `host` requires only `value`.
+
+Redirects default to temporary. Use `permanent: true` only for lasting moves;
+browsers cache it. `statusCode`, one of 301, 302, 307, 308, overrides `permanent`.
+
+Verify rules on a hosted Preview or published site, not a local dev server.
+Legacy static hosting ignores them; contact support if deployed rules have no effect.
+
 ## React Router framework mode
 
 For the supported client-rendered setup, keep `ssr: false` and add Fimo's
@@ -111,5 +133,4 @@ Astro has a dedicated connector — load `references/frameworks/astro.md` before
 editing an Astro config.
 
 `.fimo/config.json#routes` is the Studio page catalog, not deployment routing.
-Never generate hosting rewrites from it. If a project already has a
-provider-specific deployment file, preserve it; that file remains authoritative.
+Never generate hosting rewrites from it.

package/assets/skills/fimo-code/references/frameworks/next/app-router.md

@@ -109,24 +109,10 @@ Do not add `'use client'` to a page solely because Fimo is present. Keep promise
 
 ## Metadata
 
-Fimo owns the site-wide defaults; the application owns per-page overrides. Keep (or add) the starter wiring in the root layout — it maps `.fimo/config.json#seo` (Studio's Settings → SEO: title, description, favicon, share image, robots, theme color, canonical) onto Next `Metadata`/`Viewport`:
-
-```ts
-import { buildFimoMetadata, buildFimoViewport } from 'fimo-next';
-
-export const generateMetadata = () => buildFimoMetadata();
-export const generateViewport = () => buildFimoViewport();
-```
-
-If the root layout lacks this wiring, add it (updating the fimo packages if `fimo-next` does not export the helpers); without it, Settings → SEO never reaches the rendered head.
-
-Per-page `metadata`/`generateMetadata` exports override the defaults field by field. Resolve labels/content on the server and convert tracked strings only where Next expects primitives:
-
-```ts
-export async function generateMetadata() {
-  const labels = await getLabels();
-  return { title: String(labels.t('seo.home.title')) };
-}
-```
-
-Do not expect `FimoProvider` to inject SEO, routes, language, or direction.
+When creating a site, adding a route, or integrating SEO, load
+`references/frameworks/next/seo.md` (`--ref frameworks/next/seo`). Keep root
+global defaults separate from explicit Home and route SEO. Reuse the app's
+established route integration for new pages; a dynamic route module covers all
+its instances. Next replaces nested metadata objects, not their individual
+fields. Preserve app-owned policies and image routes. `FimoProvider` does not
+inject SEO.

package/assets/skills/fimo-code/references/frameworks/next/seo.md

@@ -0,0 +1,168 @@
+# Next.js SEO
+
+Use the installed package APIs. The app owns routing, metadata policy and
+rendering mode. Fimo supplies editable values, not a router or a merge policy.
+
+## Read, resolve, convert
+
+```ts
+import { getFimoSeo } from 'fimo/seo/server';
+import { toNextMetadata, toNextViewport } from 'fimo-next/seo';
+
+// Root layout: global defaults, never implicitly Home.
+export const generateMetadata = () => toNextMetadata(getFimoSeo());
+export const generateViewport = () => toNextViewport(getFimoSeo());
+```
+
+For a new App Router site, keep this root wiring. Home is an explicit route:
+
+```ts
+// app/page.tsx
+export const generateMetadata = () => toNextMetadata(getFimoSeo({ pathname: '/' }));
+```
+
+For each route module with configured route SEO, resolve its real pathname.
+One dynamic module handles every slug. Reuse the app's content loader and URL
+builder; do not try to infer a full pathname from Next's params in the root.
+
+```ts
+// app/blog/[slug]/page.tsx, using the app's existing loader and URL builder
+export async function generateMetadata({ params }: { params: Promise<{ slug: string }> }) {
+  const { slug } = await params;
+  const article = await getArticle(slug);
+  return toNextMetadata(
+    getFimoSeo({
+      pathname: articlePath(article),
+      routeData: { article },
+    })
+  );
+}
+```
+
+Loaders should retain their normal not-found and caching behavior. Add
+`generateViewport` at a route only when route-specific `themeColor` needs to
+apply; share the existing cached loader if both exports need its data. Other
+routes inherit the root color. When adding a page, follow the established
+pattern and keep its Fimo catalog entry aligned with a URL the app serves.
+
+`getFimoSeo({ pathname?, routeData?, rootDir? })` is synchronous and Node-only.
+No pathname reads global SEO. A pathname applies matching route overrides.
+It reads current or legacy project config using Fimo's config discovery;
+missing config/SEO returns `undefined`, malformed JSON and other I/O errors
+throw. Pass `rootDir` for a monorepo app located away from the process cwd.
+It does not cache, fetch content, infer locales or invalidate Next's caches.
+Config edits reach static output on rebuild and cached output on the app's
+normal revalidation path. Fetched route content can remain cached across
+builds; use the app's data-cache invalidation/revalidation policy and verify
+the rendered value after a content edit. Rebuild success is not freshness proof.
+
+For bundled data or Edge, supply config yourself to the pure resolver instead
+of importing the Node reader:
+
+```ts
+import { resolveSeoForPath } from 'fimo/seo';
+import { toNextMetadata } from 'fimo-next/seo';
+
+const seo = resolveSeoForPath(pathname, publicSeoConfig, { article });
+const metadata = toNextMetadata(seo);
+```
+
+Bundle only public SEO/routes, not credentials or project connection data.
+Every ancestor layout of an Edge page must also avoid the Node reader. Use
+bundled public SEO for shared root defaults, not just for the Edge leaf.
+The converters have no I/O or Next request dependency. Their output is for
+App Router; Pages Router keeps its existing `next/head` or SEO library and
+maps resolved Fimo values there. Do not convert routers for SEO.
+
+## Available fields
+
+Global values live at `seo` and overrides at `routes.<id>.seo` in the project's
+existing Fimo config (normally `.fimo/config.json`). Preserve other config keys.
+`fimo pages set` manages the route catalog but has no `--seo` flag; edit the
+config to author route SEO. For example:
+
+```json
+{
+  "seo": { "title": "Journal", "description": "Notes from the field" },
+  "routes": {
+    "article": {
+      "path": "/blog/:slug",
+      "seo": { "title": "{{article.title}}", "description": "{{article.summary}}" }
+    }
+  }
+}
+```
+
+`FimoSEO` from `fimo/seo` has these optional string fields:
+
+| Fimo field    | Next output                                            |
+| ------------- | ------------------------------------------------------ |
+| `title`       | `title`                                                |
+| `description` | `description`                                          |
+| `siteName`    | `openGraph.siteName`                                   |
+| `url`         | `metadataBase`, relative canonical and `openGraph.url` |
+| `image`       | `openGraph.images`                                     |
+| `favicon`     | `icons.icon` and `icons.apple`                         |
+| `twitterSite` | `twitter.site`                                         |
+| `robots`      | `robots` meta, not robots.txt                          |
+| `themeColor`  | `Viewport.themeColor`, not Metadata                    |
+| `locale`      | `openGraph.locale`, not URL or translation selection   |
+
+Route fields use the same shape. `{{article.title}}` reads caller-supplied
+`routeData.article.title`; `siteName` and route `label` are built-in context.
+A missing, empty or nonscalar token falls back for the entire field to its
+global value, then absence. Tracked Fimo strings are supported. This does not
+invent content when an article is missing.
+
+Converters return `{}` for undefined SEO. They leave social title/description
+and Twitter images unset so Next derives them from final page metadata/OG.
+They default OG type to `website` and Twitter card to `summary_large_image`.
+`url` is a site base; relative canonical/OG URLs follow the active route.
+App-specific canonical policies, hreflang, JSON-LD, sitemaps, robots.txt,
+verification tags and generated social images remain app-owned.
+
+## Existing app: adopt only chosen fields
+
+Inspect existing root/section/page exports and file-based icons/social images
+first. Do not spread every resolved global value into a leaf: that can replace
+a section's `noindex` policy or image. Keep the app's established metadata
+builder and choose the fields Fimo should supply. For example, an app choosing
+Fimo's editable description while retaining its title and policy:
+
+```ts
+export async function generateMetadata(context: Props) {
+  const application = await getApplicationMetadata(context);
+  const seo = getFimoSeo({ pathname: await getApplicationPathname(context) });
+  return {
+    ...application,
+    ...(seo?.description ? { description: seo.description } : {}),
+  };
+}
+```
+
+The loader/path helpers above belong to the app, not Fimo. For nested fields,
+explicitly retain the siblings the app intends to keep. Next replaces
+`openGraph`, `twitter`, `icons` and `alternates` objects across segments; there
+is no generic deep-merge or null-based suppression guarantee. Never spread
+parent `ResolvedMetadata` wholesale. File-based images can mask config values;
+preserve them unless the user chooses to replace that behavior.
+
+Use one title-suffix owner. If a Fimo template already produces a complete
+title, return `title: { absolute: seo.title }` to bypass an ancestor
+`title.template`, or remove the duplicated suffix from the Fimo template.
+Next's layout `title.template` does not apply to a page in that same segment;
+give Home its complete app-owned title when it needs the suffix too.
+Preserve deliberate Twitter-specific images; otherwise allow Next's OG fallback.
+
+The existing `buildFimoMetadata(rootDir?)` and `buildFimoViewport(rootDir?)` from `fimo-next`
+remain global-only helpers. Their string argument is a directory, not a route.
+
+## Prove the rendered result
+
+Build and request representative Home, static and dynamic routes. Check the
+actual title, description, canonical, OG/Twitter images, icons, robots and
+theme color against configured values. Include missing template data and an
+existing section policy. Confirm social titles follow the final page title,
+suffixes occur once, and no Home values leak to other routes. A helper import
+or a successful build alone does not prove SEO. Check supported runtime and
+revalidation behavior when those are part of the task.

package/assets/skills/fimo-code/references/frameworks/next.md

@@ -2,7 +2,7 @@
 
 Use this reference when `fimo describe --json` reports `framework.slug: "nextjs"`, or the project uses an App Router (`app/` or `src/app/`) or Pages Router (`pages/` or `src/pages/`) tree.
 
-Fimo supports schema-first content in both routers across static generation, ISR, request-time rendering, and Client Components. The application owns routes, locale resolution, links, `<html lang/dir>`, and per-page SEO overrides. Fimo receives the resolved locale and supplies content, labels, source metadata, client editing context, and the site-wide SEO defaults (App Router: `buildFimoMetadata`/`buildFimoViewport` in the root layout — see the router reference's Metadata section).
+Fimo supports schema-first content in both routers across static generation, ISR, request-time rendering, and Client Components. The application owns routes, locale resolution, links, `<html lang/dir>`, and SEO policy. Fimo supplies content, labels, editing context and optional resolved SEO values. For site creation, new routes or SEO changes, load `references/frameworks/next/seo.md`.
 
 ## Choose the router reference
 

package/assets/skills/fimo-code/references/frameworks/seo-head.md

@@ -0,0 +1,78 @@
+# Astro and SvelteKit SEO
+
+Resolve route data, apply the app's policy, then convert. Both imports are pure
+and bundle-safe. Neither reads files, fetches content, discovers a route, nor
+sets framework caching. Use the installed package's exports.
+
+```ts
+import { resolveSeoForPath, toSeoHead, type FimoSEO } from 'fimo/seo';
+import config from '../../.fimo/config.json'; // adjust to the actual file
+
+const resolved = resolveSeoForPath(pathname, config, { article });
+const seo: FimoSEO = { ...resolved, title: String(article.title) };
+const head = toSeoHead(seo, { canonicalUrl });
+```
+
+`resolveSeoForPath` combines global defaults and the matching catalog route's
+`seo`. Supply the actual pathname, including the app's locale/base path, and
+the already-loaded data named by templates such as `{{article.title}}`.
+Unresolved tokens fall back for the entire field. The route catalog is not a
+router. For domain/custom locale routing, the app selects locale-specific
+values explicitly. No global defaults are required to use route SEO.
+
+All `FimoSEO` fields are optional strings:
+
+| Fields                 | Output                                                                            |
+| ---------------------- | --------------------------------------------------------------------------------- |
+| `title`, `description` | Native title/description and matching Open Graph/Twitter values                   |
+| `image`                | Open Graph and Twitter share image                                                |
+| `favicon`              | Icon and apple-touch-icon links                                                   |
+| `siteName`, `locale`   | Open Graph site name and locale                                                   |
+| `twitterSite`          | Twitter site account                                                              |
+| `robots`, `themeColor` | Native meta tags                                                                  |
+| `url`                  | Site base only. The app computes `canonicalUrl`; it emits canonical and `og:url`. |
+
+`toSeoHead` returns `{ title?, meta, links }`. No configured values produces
+empty arrays. Absent/empty fields emit no corresponding tags. The default
+social type/card are `website`/`summary_large_image`; use the existing head
+component for article tags, alternate languages, JSON-LD, and other app-owned
+metadata. Filter a converter attribute before replacing that same tag.
+
+Preserve editor-owned settings through resolution; do not copy their initial
+values into app constants that overwrite config. Derive content-owned title
+and description from the same loaded entry or singleton as the visible page,
+including Home/About. Pass that data to resolution or compose its current
+values before conversion. A correct first render does not prove editability.
+
+App values win only where intentionally required. Keep overrides together and
+record their reason in the existing code or handoff, not a new ownership
+registry. Set `image: undefined` to remove a
+global image, or `robots: 'noindex'` for an editorial page before conversion. An
+explicit `undefined` in a spread removes a field; use conditional spreads to
+retain defaults for missing optional overrides. Resolve once, then compose;
+do not resolve again after applying policy.
+
+Pass a final absolute canonical URL from the app's production URL policy.
+`new URL(pathname, seo.url).href` fits a root-hosted starter; preserve existing
+base paths, domains, trailing slashes and query policy in other apps. Never use
+the preview/request origin as a production canonical. Omit `canonicalUrl` to
+emit neither canonical nor `og:url`.
+
+For existing apps, inventory the current head owner and extend it in place.
+Do not add duplicate tags or overwrite unrelated metadata. Framework-escape
+attributes; never render a raw HTML string. Each new route must use the app's
+SEO path, with route data where needed. Verify title, description, canonical,
+robots and social values in built HTML, not only the browser tab title.
+
+Imported JSON is a build snapshot. Studio config changes need sync and
+rebuild/redeploy. Content freshness follows the app's SSR/prerender/cache
+policy; changing a helper does not change that policy.
+
+For SEO integration acceptance, use an authorized isolated project to change
+one inherited setting and one content-owned value after the initial render.
+Follow the app's sync/build/cache policy, then compare built HTML and the
+hydrated head; verify intentional overrides remain unchanged. Restore the
+test values. Include client navigation and Back where supported. Never mutate
+customer production data for this check. If edits or rendering are unavailable,
+report freshness unproven. `fimo validate` checks declared contracts, not rendered
+head propagation; a green result or helper import is not this acceptance proof.