fimo 2.8.0-staging.5 → 2.8.0-staging.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (49) hide show
  1. package/README.md +3 -3
  2. package/assets/skills/fimo/SKILL.md +3 -3
  3. package/assets/skills/fimo-cli/SKILL.md +9 -10
  4. package/assets/skills/fimo-cli/references/agents.md +9 -8
  5. package/assets/skills/fimo-cli/references/branches.md +1 -1
  6. package/assets/skills/fimo-cli/references/credits.md +2 -2
  7. package/assets/skills/fimo-cli/references/deploy.md +1 -1
  8. package/assets/skills/fimo-cli/references/describe.md +2 -2
  9. package/assets/skills/fimo-cli/references/init.md +7 -7
  10. package/assets/skills/fimo-cli/references/integrations.md +2 -2
  11. package/assets/skills/fimo-cli/references/invite.md +1 -1
  12. package/assets/skills/fimo-cli/references/locales.md +1 -1
  13. package/assets/skills/fimo-cli/references/mcp.md +1 -1
  14. package/assets/skills/fimo-cli/references/project-vars-and-secrets.md +1 -1
  15. package/assets/skills/fimo-cli/references/projects.md +3 -3
  16. package/assets/skills/fimo-cli/references/schedules.md +1 -1
  17. package/assets/skills/fimo-cli/references/support.md +1 -1
  18. package/assets/skills/fimo-studio/SKILL.md +8 -8
  19. package/assets/skills/fimo-studio/references/agents.md +4 -4
  20. package/assets/skills/fimo-studio/references/ai-chat.md +5 -5
  21. package/assets/skills/fimo-studio/references/analytics.md +1 -1
  22. package/assets/skills/fimo-studio/references/billing-and-credits.md +3 -3
  23. package/assets/skills/fimo-studio/references/cms.md +1 -1
  24. package/assets/skills/fimo-studio/references/command-palette.md +3 -4
  25. package/assets/skills/fimo-studio/references/connections.md +9 -9
  26. package/assets/skills/fimo-studio/references/custom-domains.md +1 -1
  27. package/assets/skills/fimo-studio/references/drawing-and-wireframing.md +2 -4
  28. package/assets/skills/fimo-studio/references/media-library.md +4 -0
  29. package/assets/skills/fimo-studio/references/preview-and-responsive.md +2 -2
  30. package/assets/skills/fimo-studio/references/project-creation.md +8 -8
  31. package/assets/skills/fimo-studio/references/publish-and-deploy.md +7 -7
  32. package/assets/skills/fimo-studio/references/schedules.md +5 -5
  33. package/assets/skills/fimo-studio/references/sharing-and-collaboration.md +10 -10
  34. package/assets/skills/fimo-studio/references/version-history.md +4 -4
  35. package/assets/skills/fimo-studio/references/visual-editing.md +7 -5
  36. package/assets/skills/fimo-studio/references/webhooks.md +6 -6
  37. package/dist/cli/bundle.json +1 -1
  38. package/dist/cli/index.js +64 -79
  39. package/package.json +12 -12
  40. package/templates/astro/package.json +4 -3
  41. package/templates/nextjs/package.json +7 -6
  42. package/templates/react-router/package.json +5 -5
  43. package/templates/sveltekit/package.json +4 -3
  44. package/templates/vite/package.json +7 -6
  45. package/templates/welcome/manifest.json +4 -4
  46. package/templates/welcome/template/.fimo/config.json +1 -1
  47. package/templates/welcome/template/src/pages/SiteContent.tsx +1 -1
  48. package/templates/welcome/template/src/pages/fallback-content.ts +2 -2
  49. package/assets/skills/fimo-cli/references/inbox.md +0 -86
package/README.md CHANGED
@@ -35,11 +35,11 @@ npx fimo@latest init my-site
35
35
  cd my-site
36
36
  ```
37
37
 
38
- Every command runs the same way: **`npx fimo@latest <command>`**. `fimo init` sets up the project, pushes the first commit, and wires it to your Fimo account. Open it in your coding agent and start building.
38
+ Every command runs the same way: **`npx fimo@latest <command>`**. `fimo init` sets up the site, pushes the first commit, and wires it to your Fimo account. Open it in your coding agent and start building.
39
39
 
40
40
  ## AI coding tools
41
41
 
42
- Fimo ships skills and rules for your AI coding tools (Claude Code, Cursor, Codex, Gemini, and more) so the agent knows how to work in a Fimo project. `fimo init` installs them for you — add or refresh them any time (`--mode=copy` is required under npx):
42
+ Fimo ships skills and rules for your AI coding tools (Claude Code, Cursor, Codex, Gemini, and more) so the agent knows how to work in a Fimo site. `fimo init` installs them for you — add or refresh them any time (`--mode=copy` is required under npx):
43
43
 
44
44
  ```bash
45
45
  npx fimo@latest skills install --mode=copy
@@ -47,7 +47,7 @@ npx fimo@latest skills install --mode=copy
47
47
 
48
48
  ## Local development
49
49
 
50
- A Fimo project is a standard framework application. Run its normal package scripts:
50
+ A Fimo site is a standard framework application. Run its normal package scripts:
51
51
 
52
52
  ```bash
53
53
  npm install
package/assets/skills/fimo/SKILL.md CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: fimo
3
3
  description: >-
4
- Working in or with a Fimo project (a content + media + forms + analytics
4
+ Working in or with a Fimo site (a content + media + forms + analytics
5
5
  platform for web applications). Load the current Fimo skills on demand through
6
6
  the `fimo` CLI before doing Fimo work — writing schema-driven
7
7
  code, running CLI/deploy workflows, using the dashboard, or migrating a site.
@@ -30,7 +30,7 @@ not files in the project. Load them through the CLI, for example
30
30
  Pick by task:
31
31
 
32
32
  - Writing code — schemas/forms, generated clients, labels, framework adapters, rendering primitives → `fimo-code`
33
- - Project creation, local setup, cloning, and CLI workflows — init, push, deploy, sync, labels, domains, analytics → `fimo-cli`
33
+ - Site creation, local setup, cloning, and CLI workflows — init, push, deploy, sync, labels, domains, analytics → `fimo-cli`
34
34
  - Fimo agents — create, configure, validate, deploy, run, or inspect them → `fimo-cli` (`references/agents.md`)
35
35
  - AI agent setup — connect Claude Code, Codex, Cursor, or another agent → `fimo-cli` (`references/agent-setup.md`)
36
36
  - Remote MCP integrations — add, inspect, search, or run an MCP server → `fimo-cli` (`references/mcp.md`)
@@ -38,7 +38,7 @@ Pick by task:
38
38
  - Migrating an existing site into Fimo → `fimo-migration`
39
39
 
40
40
  For project setup, load `fimo-cli` first. Its `references/init.md` decision tree distinguishes a new or empty
41
- project, an existing Fimo project, and an external migration; load `fimo-migration` for the last path.
41
+ project, an existing Fimo site, and an external migration; load `fimo-migration` for the last path.
42
42
 
43
43
  If a confirmed Fimo platform failure or missing capability materially blocks the task, finish or safely preserve the main work first, then use the built-in `supportReport` tool. Load the `fimo-cli` support instructions for the reporting criteria.
44
44
 
package/assets/skills/fimo-cli/SKILL.md CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: fimo-cli
3
3
  description: >-
4
- Use the `fimo` CLI to create or operate a Fimo project: content, forms,
4
+ Use the `fimo` CLI to create or operate a Fimo site: content, forms,
5
5
  media, labels/locales, deploys, Branches, Environments, domains, analytics,
6
6
  integrations, Fimo agents, collaboration, accounts, and credits. Also use
7
7
  for AI agent or MCP setup and confirmed Fimo platform blockers.
@@ -9,7 +9,7 @@ description: >-
9
9
 
10
10
  # Fimo CLI
11
11
 
12
- The `fimo` CLI is the workflow surface for Fimo. Fimo connects content, media, forms, analytics, editing, and hosting to web applications. The CLI handles project creation, content / forms / media / labels / locale workflows, deploys, collaboration, account management, Fimo agents, AI credit inspection, and AI agent setup.
12
+ The `fimo` CLI is the workflow surface for Fimo. Fimo connects content, media, forms, analytics, editing, and hosting to web applications. The CLI handles site creation, content / forms / media / labels / locale workflows, deploys, collaboration, account management, Fimo agents, AI credit inspection, and AI agent setup.
13
13
 
14
14
  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 `fimo skills get fimo-code`, using the invocation prefix below.
15
15
 
@@ -40,11 +40,11 @@ Pretty output may hide URLs behind clickable labels. Agents should use `--json`
40
40
 
41
41
  ## Critical: `.fimo/project.json` is the project link
42
42
 
43
- A Fimo project is identified by `.fimo/project.json`, written by `fimo init`. This file connects the local directory to the remote Fimo project. **Never edit it manually.** Most CLI commands find it by walking up from the cwd.
43
+ A Fimo site is identified by `.fimo/project.json`, written by `fimo init`. This file connects the local directory to the remote Fimo site. **Never edit it manually.** Most CLI commands find it by walking up from the cwd.
44
44
 
45
45
  ## Critical: commands target the Branch matching the current git branch
46
46
 
47
- A project can have multiple **Branches** — each is a git branch _plus_ its own DB, sandbox, preview, and assets. Project-scoped commands (`deploy`, `status`, `entries`, `diff`, …) operate on the Branch matching the **current git branch**, and print a one-line banner saying which one. Analytics reads are the exception: they default to canonical `prod`, independent of the checkout; see `references/analytics.md`. Annotation writes keep the current or explicit Branch. New projects start on `main`. Override for a single command with the canonical `--branch <name>` flag; the removed `--env <name>` spelling is rejected. Never edit the link file to switch. The full git-shaped workflow (`branch` / `checkout` / `switch` / `pull` / `diff` / `merge` / `status` / `publish`) lives in `references/branches.md`.
47
+ A project can have multiple **Branches** — each is a git branch _plus_ its own DB, sandbox, preview, and assets. Site-scoped commands (`deploy`, `status`, `entries`, `diff`, …) operate on the Branch matching the **current git branch**, and print a one-line banner saying which one. Analytics reads are the exception: they default to canonical `prod`, independent of the checkout; see `references/analytics.md`. Annotation writes keep the current or explicit Branch. New sites start on `main`. Override for a single command with the canonical `--branch <name>` flag; the removed `--env <name>` spelling is rejected. Never edit the link file to switch. The full git-shaped workflow (`branch` / `checkout` / `switch` / `pull` / `diff` / `merge` / `status` / `publish`) lives in `references/branches.md`.
48
48
 
49
49
  ## Quick Start
50
50
 
@@ -64,7 +64,7 @@ fimo deploy # ON-DEMAND: hosted project previ
64
64
  fimo deploy --publish # ON-DEMAND: publish live (only when the developer says "ship it")
65
65
  ```
66
66
 
67
- New projects use the Next.js App Router template by default. Fimo's canonical React Router template is selected explicitly with `--framework react-router`; use `--framework vite` for a React SPA.
67
+ New sites use the Next.js App Router template by default. Fimo's canonical React Router template is selected explicitly with `--framework react-router`; use `--framework vite` for a React SPA.
68
68
 
69
69
  The working loop is local: run the app with the project's package-manager `dev` script (`pnpm dev` / `npm run dev` / `yarn dev` / `bun dev` — match the lockfile), ask the developer what they want, edit, and iterate against the live localhost server. Outside the first-time onboarding rule below, `fimo deploy` is **not** a required final step — reach for it only when the developer wants a hosted project preview or to go live, and only on their signal (see `references/deploy.md`).
70
70
 
@@ -78,7 +78,7 @@ Keep `fimo validate --json` at the front of the project's `build` script, which
78
78
 
79
79
  Load the matching reference when the user's request fires its trigger. Recipes that involve writing code also need the `fimo-code` skill's package references — they're called out where relevant.
80
80
 
81
- - "Create a new Fimo project / scaffold a site / start a new website / link an existing project locally" → `references/init.md`
81
+ - "Create a new Fimo site / scaffold a site / start a new website / link an existing project locally" → `references/init.md`
82
82
  - "Add a content type / blog / products / content schemas / CMS" → `references/content.md` (workflow) **+ run `fimo skills get fimo-code --ref content/schema` and load the detected framework reference**
83
83
  - "Declare Pages routes / configure Pages sources or route params / control what Studio shows for a route" → `references/pages.md`
84
84
  - "Add a contact / signup / feedback / newsletter form" → `references/forms.md` (workflow) **+ run `fimo skills get fimo-code --ref forms` for the JSON spec and generated client**
@@ -107,7 +107,6 @@ Load the matching reference when the user's request fires its trigger. Recipes t
107
107
  - "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`
108
108
  - "Invite a collaborator / add Marc / share with client" → `references/invite.md`
109
109
  - "Login / log out / who am I / switch organization" → `references/account.md` — note: switching **org** is `fimo orgs switch`; bare `fimo switch` changes the active **Fimo Branch** (see `references/branches.md`)
110
- - "Check the Inbox / what are my agents waiting on / answer a blocked agent / an agent asked me a question / approve or deny what an agent asked for (`fimo inbox *`)" → `references/inbox.md`. Never answer on the person's behalf.
111
110
  - "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`
112
111
  - "Install Fimo for my agent / fimo skills install / set up Claude Code, Codex, or Cursor for Fimo" → `references/agent-setup.md`
113
112
  - "Add, inspect, search, or run a remote MCP server / use `fimo mcp`" → `references/mcp.md`
@@ -123,7 +122,7 @@ Load the matching reference when the user's request fires its trigger. Recipes t
123
122
  These fire at specific moments in the project lifecycle. **Surface them proactively** rather than waiting for the user to ask:
124
123
 
125
124
  - **Right after `fimo init`** → `cd` into the new directory, read the project's `AGENTS.md` (or `CLAUDE.md` for Claude Code), run `fimo describe --json`, then load `fimo-code` and only the task/framework references it routes to. The rules file came into existence mid-session and may not be auto-loaded by the harness. See `references/init.md` § Load the project context.
126
- - **When `fimo init` created or scaffolded a new project (create-new path, including a Studio-supplied `--project-id`)** → after init and context loading succeed, run the single first-preview deploy and return the preview and dashboard links — see `references/init.md` § Create the first hosted preview. That deploy is also the sandbox warm-up; never run a separate warm-up deploy. Skip it only if the user explicitly said not to deploy. Linking a project with existing code and migrations keep their own approval rules.
125
+ - **When `fimo init` created or scaffolded a new site (create-new path, including a Studio-supplied `--project-id`)** → after init and context loading succeed, run the single first-preview deploy and return the preview and dashboard links — see `references/init.md` § Create the first hosted preview. That deploy is also the sandbox warm-up; never run a separate warm-up deploy. Skip it only if the user explicitly said not to deploy. Linking a project with existing code and migrations keep their own approval rules.
127
126
  - **Right after `fimo init`** → suggest `fimo rename "<Display Name>"` to set a human-readable name (the default post-init name is an auto-generated slug). Infer the name from what the user is building (e.g. "Acme Coffee" for a café, "Jane Doe Portfolio" for a personal site). See `references/init.md`.
128
127
  - **Right after `fimo init`** → start the app locally with the project's package-manager `dev` script (`pnpm dev` / `npm run dev` / `yarn dev` / `bun dev`) in the background. This localhost server with live reload is your iteration loop — edit, show, repeat. No deploy is needed to see local changes. If the initiating request did not say what to build, ask the developer — after the first preview on the create-new path, never as a blocker before initializing.
129
128
  - **When a user-visible unit of work looks done outside first-time onboarding** → **offer** to deploy (`fimo deploy` for a hosted project preview, `fimo deploy --publish` to go live) and run it only after the developer confirms — or immediately if they ask. Never deploy ordinary edits on your own. See `references/deploy.md`.
@@ -132,14 +131,14 @@ These fire at specific moments in the project lifecycle. **Surface them proactiv
132
131
  - **You need the current preview URL but haven't changed code** (opening it, screenshotting it, handing it to another tool, the previous URL expired) → `fimo preview url`, never a no-op `fimo deploy`. See `references/preview.md`.
133
132
  - **When the user wants to try something risky / explore a redesign without touching the live site** → suggest a feature Branch: `fimo checkout -b <name>` gives an isolated Branch + DB + preview. Deploy previews there, then `fimo merge` it back and `fimo publish`. See `references/branches.md`.
134
133
  - **After completing or safely preserving the user's main work, when a confirmed Fimo platform failure still materially blocks the task after one safe recovery attempt, or a confirmed missing capability blocks completion or forces a fragile or heavily manual workaround** → use the built-in `supportReport` tool. Do not wait for the user to ask and do not stop after only describing the gap. See `references/support.md`.
135
- - **When a project agent has stopped and is waiting on a person** → `fimo inbox list --topic agent_question --unread` surfaces it. Show the stored form to the person, collect their explicit answer, and submit it with `fimo inbox answer`. See `references/inbox.md`.
134
+ - **When a project agent has stopped and is waiting on a person** → a project member answers its question in Studio, on the run's page; the question email links there. The CLI cannot answer it. Never answer on the person's behalf.
136
135
  - **After the first successful `fimo deploy`** → suggest `fimo invite` if the project involves multiple people. Typical roles: `edit` for developers/content editors, `view` or `comment` for clients/stakeholders, `full` for project leads. See `references/invite.md`.
137
136
  - **After the automatic first-preview deploy on the create-new path, before the project has been published** → if there is no custom domain and the free default `*.fimo.site` slug still looks generated or was never explicitly chosen, offer to find a cleaner free subdomain. It needs no DNS. Never claim one without explicit user confirmation: suggest candidates, let the user choose, then rename it. Choosing the slug does not publish the site; the URL starts resolving only after the first successful `fimo deploy --publish`. Skip this nudge if the user already chose the default slug, attached a custom domain, or declined. See `references/domains.md` § Offer a cleaner default URL before first publish.
138
137
  - **When the user wants to modify the URL of their website** → walk through `references/domains.md`. The CLI surface covers renaming the Fimo-provided subdomain (`fimo domains rename-default`, free), attaching a domain they already own (`fimo domains add`, Premium), and buying a new domain through Fimo (`fimo domains buy`, Premium).
139
138
 
140
139
  ## Anti-Patterns
141
140
 
142
- - **Editing `.fimo/project.json`** — read-only; it's the link between local and remote project. Treat as a generated file.
141
+ - **Editing `.fimo/project.json`** — read-only; it's the link between local and remote site. Treat as a generated file.
143
142
  - **Treating `fimo deploy` as the working loop or a required final step** — the loop is local (`pnpm dev` etc.). Deploy commits + pushes + round-trips the sandbox; it's for hosted previews / going live, on-demand. Iterate locally and deploy at logical breakpoints. See `references/deploy.md`.
144
143
  - **Deploying without the developer asking or confirming** — new-project onboarding authorizes exactly one automatic first preview deploy (unless the user said not to deploy); every other deploy is offer-then-confirm. Don't auto-deploy after finishing an ordinary edit.
145
144
  - **Running `fimo deploy` just to get the current preview URL** — that's a commit + push + sandbox sync when only destination resolution is needed. Use `fimo preview url` instead. See `references/preview.md`.
package/assets/skills/fimo-cli/references/agents.md CHANGED
@@ -38,10 +38,10 @@ fimo agents secrets remove <name> <KEY> [-C <dir>]
38
38
  ```
39
39
 
40
40
  - **`list-templates`** — list the bundled starter templates with the first line of each template's `GOAL.md` as a summary. Ships with the CLI binary; no API call. The five bundled templates are `_default`, `seo-audit`, `content-translator`, `broken-link-sweeper`, `post-deploy-check`.
41
- - **`create <name>`** — scaffold `.fimo/agents/<name>/` from a template (default `_default`, a minimal valid bundle with a manual trigger). `--description <text>` writes a one-line tagline into the scaffolded `config.yaml` (surfaces in the dashboard's agents list). When run **without** `-C`, it requires the cwd to be inside a real Fimo project (walks up for `.fimo/project.json` or legacy `.fimo.settings.json`) and errors out cleanly otherwise, so it never leaks an agent bundle into a stray cwd. If the template declares capabilities, an install-consent flow runs after the copy (`--quiet` skips it; critical caps still abort). Keep the scaffolded `runtime` block as is unless the author asks for a different credit limit; see the `runtime` reference below before adding any limit key.
41
+ - **`create <name>`** — scaffold `.fimo/agents/<name>/` from a template (default `_default`, a minimal valid bundle with a manual trigger). `--description <text>` writes a one-line tagline into the scaffolded `config.yaml` (surfaces in the dashboard's agents list). When run **without** `-C`, it requires the cwd to be inside a real Fimo site (walks up for `.fimo/project.json` or legacy `.fimo.settings.json`) and errors out cleanly otherwise, so it never leaks an agent bundle into a stray cwd. If the template declares capabilities, an install-consent flow runs after the copy (`--quiet` skips it; critical caps still abort). Keep the scaffolded `runtime` block as is unless the author asks for a different credit limit; see the `runtime` reference below before adding any limit key.
42
42
  - Every generated `config.yaml` includes `model: openai/gpt-5.6-luna`. Change that top-level value to another supported Fimo text model when needed; bundles without `model` keep the Luna fallback. Deploy after changing it because cloud runs use the deployed bundle.
43
43
  - **`list`** — list the agents declared under `<project>/.fimo/agents/` (or legacy root `agents/`), with each one's trigger types and capability count. Local — the bundle list is the source of truth even if the project isn't linked yet.
44
- - **`validate [name]`** — run the full validation pipeline: parse → capability vocabulary → composition (cycle / missing sub-agents / invalid grants) → semantic + Fimo project config policy checks. Omit `name` to validate every bundle. `--json` emits a structured `ValidationReport` for CI; exit code is non-zero on any failure.
44
+ - **`validate [name]`** — run the full validation pipeline: parse → capability vocabulary → composition (cycle / missing sub-agents / invalid grants) → semantic + Fimo site config policy checks. Omit `name` to validate every bundle. `--json` emits a structured `ValidationReport` for CI; exit code is non-zero on any failure.
45
45
  - **`secrets add/remove/list`** — edit or inspect the agent's requested secret names in `.fimo/agents/<name>/config.yaml` (or legacy root). These commands do not create, rotate, or reveal secret values. Store values with `fimo secrets add`; run `fimo agents validate` to check that required requested secrets exist in the project. See `references/project-vars-and-secrets.md`.
46
46
  - **`integrations <name>`** — preview the agent's `integrations` allowlist from `.fimo/agents/<name>/config.yaml` (or legacy root) and, when linked, overlay project integration status. See `references/integrations.md`.
47
47
 
@@ -141,9 +141,10 @@ A review-first content agent could use this complete policy:
141
141
  - Discard only when no useful draft was produced or the attempted approach was fully abandoned.
142
142
  ```
143
143
 
144
- When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. The
145
- question goes to the Fimo Inbox and the current invocation ends. It can reference zero or more sessions. An authorized
146
- answer starts a continuation in the same thread; the referenced work stays open and the original model process does not wait.
144
+ When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. Fimo
145
+ emails project members a link to answer it in Studio, and the current invocation ends. It can reference zero or more
146
+ sessions. An authorized answer starts a continuation in the same thread; the referenced work stays open and the original
147
+ model process does not wait.
147
148
 
148
149
  Use `ask_user` sparingly, especially from scheduled agents:
149
150
 
@@ -170,8 +171,8 @@ changes and records a brief report of what is waiting.
170
171
 
171
172
  ## Define reporting preferences when they matter
172
173
 
173
- Fimo's default report needs no setup: a short, scannable brief appears in email and the Inbox, while the full report in
174
- Fimo carries the organized evidence and depth. Do not add a reporting section merely to restate that default.
174
+ Fimo's default report needs no setup: a short, scannable brief appears in email, while the full report in Fimo carries
175
+ the organized evidence and depth. Do not add a reporting section merely to restate that default.
175
176
 
176
177
  When the user names an audience, depth, recurring comparison, required section, or useful visual, preserve the request
177
178
  in a short **Reporting** section of `GOAL.md`. Describe the communication outcome in ordinary language. Do not prescribe
@@ -243,7 +244,7 @@ Fimo grants only the selected subset to the next invocation in that run thread.
243
244
  abilities, and capabilities the run already holds are refused before the question is stored. For durable access on
244
245
  ordinary future runs, add the capability to `capabilities.yaml`, validate, and deploy the bundle.
245
246
 
246
- Managed agents can list project agents and read their run history through baseline project access. This does not
247
+ Managed agents can list project agents and read their run history through baseline site access. This does not
247
248
  require `fimo:agents:run`; that capability is only required to dispatch another agent.
248
249
 
249
250
  Studio chat and project-bound Slack turns receive `fimo:logs:read`. The default autonomous-agent template now declares
package/assets/skills/fimo-cli/references/branches.md CHANGED
@@ -8,7 +8,7 @@ New standalone projects start with one Branch: `main`. Linking an unversioned fo
8
8
 
9
9
  ## The Branch model — how every command picks its target
10
10
 
11
- **This is the single most important concept: project-scoped commands target the Branch matching the _current git branch_.** When you're on git branch `feat/seo`, `fimo deploy`, `fimo status`, `fimo entries list`, etc. all operate on the `feat/seo` Branch's DB / sandbox / preview. The CLI prints a one-line stderr banner telling you which Branch it resolved.
11
+ **This is the single most important concept: site-scoped commands target the Branch matching the _current git branch_.** When you're on git branch `feat/seo`, `fimo deploy`, `fimo status`, `fimo entries list`, etc. all operate on the `feat/seo` Branch's DB / sandbox / preview. The CLI prints a one-line stderr banner telling you which Branch it resolved.
12
12
 
13
13
  ```bash
14
14
  fimo --branch <name> <command> # peek at another Branch for one command (does not switch)
package/assets/skills/fimo-cli/references/credits.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Credits
2
2
 
3
- `fimo credits` is a read-only command for checking the AI credit balance of the organization that owns a Fimo project. It resolves the project from `.fimo/project.json` unless `--project <project-id>` is provided.
3
+ `fimo credits` is a read-only command for checking the AI credit balance of the organization that owns a Fimo site. It resolves the project from `.fimo/project.json` unless `--project <project-id>` is provided.
4
4
 
5
5
  ```bash
6
6
  fimo credits
@@ -9,7 +9,7 @@ fimo credits --project <project-id>
9
9
  fimo credits -C ./path/to/project
10
10
  ```
11
11
 
12
- This command is **project-scoped but not Branch-scoped**. It does not depend on the current git branch or `--branch`, because credits belong to the project's organization, not to a Branch.
12
+ This command is **site-scoped but not Branch-scoped**. It does not depend on the current git branch or `--branch`, because credits belong to the project's organization, not to a Branch.
13
13
 
14
14
  ## Pretty Output
15
15
 
package/assets/skills/fimo-cli/references/deploy.md CHANGED
@@ -4,7 +4,7 @@
4
4
 
5
5
  > **Local vs hosted.** The local dev server is localhost only. The Fimo **dashboard preview** and the authenticated **project-member preview URL** are served by the deployed sandbox — so if the developer wants to see the site in the dashboard or send another project member a link, that requires a `fimo deploy`.
6
6
 
7
- `fimo deploy` uses the current Branch. New projects start on `main`; `release/*` is read-only, and `--publish` only runs from the project's configured Production source Branch. See `references/branches.md` for the multi-Branch workflow.
7
+ `fimo deploy` uses the current Branch. New sites start on `main`; `release/*` is read-only, and `--publish` only runs from the project's configured Production source Branch. See `references/branches.md` for the multi-Branch workflow.
8
8
 
9
9
  Before deploying, Fimo fast-forwards a clean checkout that is behind and stops on dirty-behind or diverged branches. This syncs the whole branch, including config commits from Studio or locale commands.
10
10
 
package/assets/skills/fimo-cli/references/describe.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Describe — read-only snapshot of the current project
2
2
 
3
- `fimo describe` prints a structured snapshot of the Fimo project in the current working directory: project name + config version, detected framework, fimo package version, package manager, route / schema / locale counts, and a file tree.
3
+ `fimo describe` prints a structured snapshot of the Fimo site in the current working directory: project name + config version, detected framework, fimo package version, package manager, route / schema / locale counts, and a file tree.
4
4
 
5
5
  It is **read-only**. Never writes, never hits the network. Safe to run any time.
6
6
 
@@ -76,4 +76,4 @@ The scoped view still emits the project-level metadata header (name, framework,
76
76
 
77
77
  - The JSON shape is stable; parse it rather than scraping the human output when you need a specific field.
78
78
  - `framework` is normally auto-detected. If it is `null`, inspect the project before choosing framework-specific guidance.
79
- - The command runs in any directory that contains `.fimo/project.json` or one of its ancestors. If you're not in a Fimo project, `describe` will run against whatever directory you point it at (it doesn't require Fimo credentials).
79
+ - The command runs in any directory that contains `.fimo/project.json` or one of its ancestors. If you're not in a Fimo site, `describe` will run against whatever directory you point it at (it doesn't require Fimo credentials).
package/assets/skills/fimo-cli/references/init.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # `fimo init`
2
2
 
3
- One-stop project setup: sign in, create a new Fimo project (or link an existing one), install dependencies, and optionally set up Fimo skills for your AI tools.
3
+ One-stop project setup: sign in, create a new Fimo site (or link an existing one), install dependencies, and optionally set up Fimo skills for your AI tools.
4
4
 
5
5
  ## Command
6
6
 
@@ -11,7 +11,7 @@ fimo init [dir] [options]
11
11
  `fimo init` runs the full onboarding in one shot:
12
12
 
13
13
  1. **Signs in automatically** — if there's no session it opens the browser loopback login. In `--json` / non-TTY with no session it fails with `NOT_AUTHENTICATED` (run `fimo login` first).
14
- 2. **Resolves the project** — with `--project-id <id>` it sets up the named Fimo project: a project with no code yet is scaffolded as a fresh site, while an existing repository is cloned. Without it, `init` creates a NEW project. An interactive TTY shows a "Create new / Link existing" picker; non-interactive shells default to create-new. New projects use the Next.js App Router by default; `--framework react-router`, `--framework vite`, `--framework astro`, and `--framework sveltekit` select the other minimal framework-native shells.
14
+ 2. **Resolves the project** — with `--project-id <id>` it sets up the named Fimo site: a project with no code yet is scaffolded as a fresh site, while an existing repository is cloned. Without it, `init` creates a NEW project. An interactive TTY shows a "Create new / Link existing" picker; non-interactive shells default to create-new. New sites use the Next.js App Router by default; `--framework react-router`, `--framework vite`, `--framework astro`, and `--framework sveltekit` select the other minimal framework-native shells.
15
15
  3. **Installs dependencies** — prompts for the package manager, or honor `--package-manager <pm>` / `--no-install`.
16
16
  4. **Optionally sets up Fimo skills** — confirm prompt, or `--skills` / `--no-skills`.
17
17
 
@@ -20,7 +20,7 @@ Generated pnpm projects pin `pnpm@10.26.0` and carry project-owned `pnpm-workspa
20
20
  | Flag | Required | Purpose |
21
21
  | ---------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
22
22
  | `[dir]` positional | yes in non-TTY for create-new | Target directory (e.g. `my-site`) |
23
- | `--project-id <id>` | no | Set up the named Fimo project: scaffold and push a fresh site when it has no code yet, otherwise clone it. |
23
+ | `--project-id <id>` | no | Set up the named Fimo site: scaffold and push a fresh site when it has no code yet, otherwise clone it. |
24
24
  | `--org <id>` | no | Target organization **id** when creating (use the `ID` column from `fimo orgs list`, NOT the slug). Picker shown interactively if omitted and TTY. |
25
25
  | `--branch <name>` | no | Branch to check out when linking an existing project (defaults to `main`). |
26
26
  | `--env <name>` | no | Rejected as a Branch selector; use `--branch <name>`. |
@@ -95,7 +95,7 @@ For `--agents`, pass the AI tool you're running in: `--agents=claude-code` for C
95
95
 
96
96
  ## Setting up a project by ID
97
97
 
98
- Pass `--project-id <id>` to set up a known Fimo project. If the project has no code yet — for example, one just created in Fimo Studio — `init` scaffolds a fresh site into it and pushes the initial commit: the same create-new path, linked to the existing ID. If the project already has code, `init` clones it into `[dir]`, like `fimo clone`. Use `--branch <name>` to check out a specific Branch (defaults to `main`). Without `--project-id`, `fimo init` creates a new project.
98
+ Pass `--project-id <id>` to set up a known Fimo site. If the project has no code yet — for example, one just created in Fimo Studio — `init` scaffolds a fresh site into it and pushes the initial commit: the same create-new path, linked to the existing ID. If the project already has code, `init` clones it into `[dir]`, like `fimo clone`. Use `--branch <name>` to check out a specific Branch (defaults to `main`). Without `--project-id`, `fimo init` creates a new site.
99
99
 
100
100
  ## Linking an existing local application
101
101
 
@@ -110,7 +110,7 @@ fimo link <projectId> --relink
110
110
  `fimo init` (create-new path) scaffolds:
111
111
 
112
112
  - The selected project shell: Next.js App Router by default, React Router with `--framework react-router`, a native React SPA with `--framework vite`, Astro with `--framework astro`, or SvelteKit with `--framework sveltekit`
113
- - `.fimo/project.json` — links this directory to the remote project (read-only after creation)
113
+ - `.fimo/project.json` — links this directory to the remote site (read-only after creation)
114
114
  - `.fimo/config.json` — project, optional Studio Pages route metadata, locale, SEO, and agent policy
115
115
  - `.fimo/agents/` — versioned agent bundles
116
116
  - `AGENTS.md` + `CLAUDE.md` — project rules (from the template) read by AGENTS.md-compatible tools and Claude Code. Both point the agent at `fimo skills get` to load the real skills on demand.
@@ -149,7 +149,7 @@ After `fimo init` completes, the project root has `AGENTS.md` (universal) and `C
149
149
 
150
150
  **These files came into existence mid-session, so they may not be auto-loaded by the harness.** Explicitly:
151
151
 
152
- 1. `cd <project-dir>` — switch into the new project.
152
+ 1. `cd <project-dir>` — switch into the new site.
153
153
  2. `Read` the project rules file: `AGENTS.md` (or `CLAUDE.md` if you're Claude Code).
154
154
  3. Run `fimo describe --json` with the current invocation prefix and read the detected framework, schemas, locales, and tree.
155
155
  4. Load the code skill on demand with the same prefix: `fimo skills get fimo-code`.
@@ -159,7 +159,7 @@ Do not batch-load every reference. Progressive disclosure keeps unrelated framew
159
159
 
160
160
  ### Create the first hosted preview (create-new path)
161
161
 
162
- Whenever `fimo init` created or scaffolded a new project — including a Studio-supplied `--project-id`, since Studio creates the project before any code exists — finish onboarding with exactly one plain preview deploy after init and context loading succeed, unless the user explicitly said not to deploy:
162
+ Whenever `fimo init` created or scaffolded a new site — including a Studio-supplied `--project-id`, since Studio creates the project before any code exists — finish onboarding with exactly one plain preview deploy after init and context loading succeed, unless the user explicitly said not to deploy:
163
163
 
164
164
  ```bash
165
165
  fimo deploy -m "chore: first preview" --json
package/assets/skills/fimo-cli/references/integrations.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # Integrations
2
2
 
3
- Use integrations to enable external services for a Fimo project. Firecrawl and Fal are built into Fimo: Fimo owns the provider account and bills the project in Fimo credits, so they take no API key at all. Every other credential (MCP servers, OAuth workspaces) is stored encrypted by Fimo and never printed back to the CLI. Teammates and agents receive access to the integration, not the underlying token.
3
+ Use integrations to enable external services for a Fimo site. Firecrawl and Fal are built into Fimo: Fimo owns the provider account and bills the project in Fimo credits, so they take no API key at all. Every other credential (MCP servers, OAuth workspaces) is stored encrypted by Fimo and never printed back to the CLI. Teammates and agents receive access to the integration, not the underlying token.
4
4
 
5
- Start with `fimo integrations list` whenever the task could benefit from an external service. It is the project-scoped,
5
+ Start with `fimo integrations list` whenever the task could benefit from an external service. It is the site-scoped,
6
6
  runtime-truthful inventory; use `info` only for the relevant integration instead of loading every provider's tools into
7
7
  context.
8
8
 
package/assets/skills/fimo-cli/references/invite.md CHANGED
@@ -93,4 +93,4 @@ fimo invite --email "dev@agency.com" --role full
93
93
  - Invited users receive an email with a sign-up link if they don't have an account, or a sign-in link if they do.
94
94
  - Organization invites can be resent with `--resend` if the user didn't receive the original.
95
95
  - Project invites are scoped to a single project; organization invites grant access to all projects in that organization.
96
- - If `--cwd` is set and the directory belongs to a linked Fimo project, that project is auto-selected.
96
+ - If `--cwd` is set and the directory belongs to a linked Fimo site, that project is auto-selected.
package/assets/skills/fimo-cli/references/locales.md CHANGED
@@ -33,7 +33,7 @@ The synchronized `.fimo/config.json` remains the application runtime's declarati
33
33
  - `defaultLocale` is the locale used by `fimo validate`, `fimo labels set` without `--locale`, and content commands without `--locale`. Change it with `fimo locales set-default`.
34
34
  - `locales` must include `defaultLocale`. Add and remove values with `fimo locales add` and `fimo locales remove`.
35
35
  - Locale tags should be structurally valid, for example `en`, `es`, `pt-BR`, or `zh-Hans`.
36
- - New projects do not need a global routing strategy. The route contract declares locale placement with `/:locale`; legacy `i18n.routing.strategy` values are read only for compatibility while migrating.
36
+ - New sites do not need a global routing strategy. The route contract declares locale placement with `/:locale`; legacy `i18n.routing.strategy` values are read only for compatibility while migrating.
37
37
  - If multiple locales are configured, create or update labels and localized content for every configured locale. Create schemas with `i18n: { "enabled": false }` only once.
38
38
 
39
39
  Edit application-owned settings such as `routes` directly in `.fimo/config.json`. Locale membership and the default use the lifecycle commands above because they must update the selected Fimo Branch and local checkout together.
package/assets/skills/fimo-cli/references/mcp.md CHANGED
@@ -121,4 +121,4 @@ Remote connections support HTTPS Streamable HTTP servers with OAuth, no authenti
121
121
  private headers. Local stdio commands such as `npx`, arbitrary child processes, resources, and prompts are not supported.
122
122
 
123
123
  To connect ChatGPT, Claude, or another remote MCP client to Fimo itself, use Fimo's hosted Project MCP at
124
- `https://api.fimo.ai/api/mcp`. That is a separate direction from connecting a Fimo project to an external MCP server.
124
+ `https://api.fimo.ai/api/mcp`. That is a separate direction from connecting a Fimo site to an external MCP server.
package/assets/skills/fimo-cli/references/project-vars-and-secrets.md CHANGED
@@ -53,7 +53,7 @@ and the active git branch; hosted preview and production inject it directly.
53
53
 
54
54
  `fimo vars add`, `fimo vars update`, and `fimo vars pull` write public project variables to a managed block in `.env.local`.
55
55
 
56
- Local env files are ignored by git in Fimo projects. They are for local development only; deployment reads project variables from Fimo and injects them into the remote build.
56
+ Local env files are ignored by git in Fimo sites. They are for local development only; deployment reads project variables from Fimo and injects them into the remote build.
57
57
 
58
58
  ## Agent Secrets
59
59
 
package/assets/skills/fimo-cli/references/projects.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Managing projects
2
2
 
3
- Commands for listing projects across an org, cloning a remote project locally, and managing the lifecycle of a single project (delete, publish, unpublish, rename). Most lifecycle commands operate on the **current project** (read from `.fimo/project.json`, or the legacy `.fimo.settings.json`, in the cwd) by default; for `delete`, `publish`, and `unpublish` you can pass an explicit `[projectId]` to target another. (`rename` only edits the linked local project; see below.)
3
+ Commands for listing projects across an org, cloning a remote site locally, and managing the lifecycle of a single project (delete, publish, unpublish, rename). Most lifecycle commands operate on the **current project** (read from `.fimo/project.json`, or the legacy `.fimo.settings.json`, in the cwd) by default; for `delete`, `publish`, and `unpublish` you can pass an explicit `[projectId]` to target another. (`rename` only edits the linked local project; see below.)
4
4
 
5
5
  ## The `fimo projects` namespace
6
6
 
@@ -16,8 +16,8 @@ fimo projects rename <name> [projectId] [-C <dir>] # set seo.siteName in the l
16
16
 
17
17
  - **`list`** — projects you can see in the org. Live projects are marked.
18
18
  - **`create`** — identical to `fimo init` (create-new path); see `references/init.md`.
19
- - **`clone`** — clone a remote Fimo project's git repo to your machine and write the local `.fimo/project.json` and agent files. Use `fimo clone <projectId>` when scripting or when the ID is known. In an interactive terminal, bare `fimo clone` opens a project picker for the active org; JSON mode and non-TTY shells require an explicit project ID and fail fast instead of prompting. By default it clones `main`; pass `--branch <name>` to clone a specific Branch. The removed `--env <name>` spelling is rejected as a Branch selector. The target directory defaults to the project display name/name, or pass `[dir]` explicitly.
20
- - **`delete`** — destructive; prompts unless `-y`. Removes the remote project.
19
+ - **`clone`** — clone a remote Fimo site's git repo to your machine and write the local `.fimo/project.json` and agent files. Use `fimo clone <projectId>` when scripting or when the ID is known. In an interactive terminal, bare `fimo clone` opens a project picker for the active org; JSON mode and non-TTY shells require an explicit site ID and fail fast instead of prompting. By default it clones `main`; pass `--branch <name>` to clone a specific Branch. The removed `--env <name>` spelling is rejected as a Branch selector. The target directory defaults to the project display name/name, or pass `[dir]` explicitly.
20
+ - **`delete`** — destructive; prompts unless `-y`. Removes the remote site.
21
21
  - **`publish` / `unpublish`** — toggle the project's public visibility. `publish` flips the configured Production source state live (the same "go live" as `fimo deploy --publish`, minus the git push).
22
22
  - **`rename`** — edits only the linked local project's `seo.siteName`. It does not commit or deploy. It requires a project marker in the cwd, and if you pass a `[projectId]` that doesn't match the linked project it errors and exits 1 (so you can't rename a different project). Later remote config commands may require reconciliation while the local config is dirty. Finish your local edits, then explicitly run `fimo deploy --no-wait` when ready for a quick sync.
23
23
 
package/assets/skills/fimo-cli/references/schedules.md CHANGED
@@ -33,7 +33,7 @@ fimo schedules delete <schedule>
33
33
 
34
34
  Scheduled commands run in the project's Branch runtime, not on the user's machine. Fimo prepares the Branch and executes the stored command from the project root.
35
35
 
36
- `--do` can be any command that works with schedule runtime permissions, such as `fimo validate`, `pnpm test`, or a project script. The runtime can edit project content and publish or unpublish the project, but it cannot manage project access, secrets, schedules, or other project-level settings.
36
+ `--do` can be any command that works with schedule runtime permissions, such as `fimo validate`, `pnpm test`, or a project script. The runtime can edit project content and publish or unpublish the project, but it cannot manage site access, secrets, schedules, or other project-level settings.
37
37
 
38
38
  Runs use at-least-once delivery. If Fimo loses a completion response, the same run may execute again. Side-effecting commands should use `FIMO_SCHEDULE_RUN_ID` as their idempotency key.
39
39
 
package/assets/skills/fimo-cli/references/support.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Reporting a problem to Fimo
2
2
 
3
- `fimo support report` sends a project-scoped problem to Fimo support. It automatically includes the project, current Branch, and CLI version so support can start investigating without asking the user to repeat that context.
3
+ `fimo support report` sends a site-scoped problem to Fimo support. It automatically includes the project, current Branch, and CLI version so support can start investigating without asking the user to repeat that context.
4
4
 
5
5
  ## When to prepare it
6
6
 
package/assets/skills/fimo-studio/SKILL.md CHANGED
@@ -6,7 +6,7 @@ description: >-
6
6
  Triggers: "in Fimo Studio", "in the dashboard", "in the web app",
7
7
  "how do I X in the UI", or screenshots of the dashboard. Topics
8
8
  covered: dashboard content and CMS, publishing from the dashboard,
9
- dashboard SEO/domain settings, project connections, agents, schedules and run history, outbound webhooks,
9
+ dashboard SEO/domain settings, site connections, agents, schedules and run history, outbound webhooks,
10
10
  visual editing, version history UI, dashboard sharing/billing, dashboard chat,
11
11
  and the command palette. Never describe
12
12
  UI locations, buttons, or panels from memory — always read the relevant
@@ -15,7 +15,7 @@ description: >-
15
15
 
16
16
  # Fimo Studio
17
17
 
18
- Fimo Studio is the Fimo web app — the place where content editors and project owners manage their site without writing code. This skill guides users through Studio features with step-by-step walkthroughs.
18
+ Fimo Studio is the Fimo web app — the place where content editors and site owners manage their site without writing code. This skill guides users through Studio features with step-by-step walkthroughs.
19
19
 
20
20
  For developer-side conventions (the `fimo` CLI, schemas, forms, code-side rules), see the `fimo` skill instead.
21
21
 
@@ -47,7 +47,7 @@ Read the relevant reference file when the user's question matches a topic.
47
47
  | Visual Editing | references/visual-editing.md | "Can I edit visually?", "How do I change colors?" |
48
48
  | Version History | references/version-history.md | "How do I undo?", "How do I go back?" |
49
49
  | Sharing & Collaboration | references/sharing-and-collaboration.md | "How do I share?", "How do I invite someone?" |
50
- | Project Creation | references/project-creation.md | "How do I start a new project?" |
50
+ | Site Creation | references/project-creation.md | "How do I start a new site?" |
51
51
  | Billing & Credits | references/billing-and-credits.md | "What are credits?", "How do I upgrade?", "How do referrals work?" |
52
52
  | Drawing & Wireframing | references/drawing-and-wireframing.md | "How do I sketch my idea?" |
53
53
 
@@ -59,12 +59,12 @@ Read the relevant reference file when the user's question matches a topic.
59
59
  | Custom domains | Publishing (must publish first), Billing (premium required) |
60
60
  | Adding images | Media Library, AI Chat, Edit Mode |
61
61
  | Content/CMS | AI Chat, Media Library |
62
- | Webhooks | Project secrets, Forms, Publishing, Agents |
63
- | Connections | AI Chat, Agents, Project secrets |
64
- | Agents | Connections, Project secrets, Branches |
65
- | Schedules | Project secrets, Environments, Agents |
62
+ | Webhooks | Site secrets, Forms, Publishing, Agents |
63
+ | Connections | AI Chat, Agents, Site secrets |
64
+ | Agents | Connections, Site secrets, Branches |
65
+ | Schedules | Site secrets, Environments, Agents |
66
66
  | Visual changes | Edit Mode (CMS content), AI Chat (layout, styling, and code changes) |
67
67
  | Something went wrong | Version History, AI Chat |
68
68
  | Working with others | Sharing, Collaboration |
69
- | Starting a project | Preview & Responsive, Publish & Deploy |
69
+ | Starting a site | Preview & Responsive, Publish & Deploy |
70
70
  | Running out of credits | Billing |
package/assets/skills/fimo-studio/references/agents.md CHANGED
@@ -1,10 +1,10 @@
1
1
  # Agents
2
2
 
3
- Project agents are versioned bundles from the project's repository. Studio lets project members inspect their configuration and run history, while project managers can start, stop, resume, and delete them.
3
+ Site agents are versioned bundles from the site's repository. Studio lets site members inspect their configuration and run history, while site managers can start, stop, resume, and delete them.
4
4
 
5
5
  ## Open an agent
6
6
 
7
- 1. Open the project and choose **Agents**.
7
+ 1. Open the site and choose **Agents**.
8
8
  2. Select **Agents** again to see the available bundles.
9
9
  3. Choose an agent to open its **Runs** and **Settings** tabs.
10
10
 
@@ -20,11 +20,11 @@ Choose **Stop** to pause every future trigger and stop planned or running work.
20
20
 
21
21
  A stopped agent shows **Paused** in the header. **Resume** makes the same triggers live again with their previous settings.
22
22
 
23
- Only project managers see Run, Stop, and Resume. Other project members can still see schedule timing, status, settings, and run history.
23
+ Only site managers see Run, Stop, and Resume. Other site members can still see schedule timing, status, settings, and run history.
24
24
 
25
25
  ## Delete an agent
26
26
 
27
- Project managers can open **Agent actions** beside Run/Stop, choose **Delete agent**, and confirm. Deletion stops planned or running work and commits removal of the agent bundle from `main`. Recorded runs remain in history. Remove the bundle from a local checkout before deploying again, or that deployment recreates the agent.
27
+ Site managers can open **Agent actions** beside Run/Stop, choose **Delete agent**, and confirm. Deletion stops planned or running work and commits removal of the agent bundle from `main`. Recorded runs remain in history. Remove the bundle from a local checkout before deploying again, or that deployment recreates the agent.
28
28
 
29
29
  If a run cannot be stopped or `main` changes before deletion commits, the definition stays intact and the agent may remain paused. Reload and retry, or resume it if you want to keep it.
30
30
 
package/assets/skills/fimo-studio/references/ai-chat.md CHANGED
@@ -1,10 +1,10 @@
1
1
  ## Where to Find It
2
2
 
3
- Open the **Chats** tab in the project header. On a phone, the Chat tab at the bottom opens the chat list first; select a chat to open it.
3
+ Open the **Chats** tab in the site header. On a phone, the Chat tab at the bottom opens the chat list first; select a chat to open it.
4
4
 
5
5
  ## Working in Several Chats
6
6
 
7
- Chat has its own **Chats** tab in the project header; the tab shows how many chats have unread activity. A project can have several chats, shared by everyone on the project. The left list shows them most recently active first with a status (**Working** with a spinner while replying, **Done** once the reply finished) and their last words; a dot marks unread activity. Select **+** for a new chat (its name comes from the first message; an empty chat offers starter requests), the search icon to find a chat, the filter icon to show only Working or Done chats, and the list settings for ordering and showing read, unread, or archived chats. The buttons above an open chat (or a right-click on a row) mark it unread, pin, archive, or mute it, for you only; the settings icon opens the chat's settings, which rename it for everyone, hold the same pin, mute and archive switches, and delete it, stopping a running reply first. Each chat has only its own messages and context. The open chat is in the page address (`/chats?chat=<id>`), so a link or reload opens the same chat.
7
+ Chat has its own **Chats** tab in the site header; the tab shows how many chats have unread activity. A site can have several chats, shared by everyone on the site. The left list shows them most recently active first with a status (**Working** with a spinner while replying, **Done** once the reply finished) and their last words; a dot marks unread activity. Select **+** for a new chat (it joins the list when its first message is sent, and its name comes from that message; an empty chat offers starter requests), the search icon to find a chat, the filter icon to show only Working or Done chats, and the list settings for ordering and showing read, unread, or archived chats. The buttons above an open chat (or a right-click on a row) mark it unread, pin, archive, or mute it, for you only; the settings icon opens the chat's settings, which change its portrait (shape, face, color) and rename it for everyone, hold the same pin, mute and archive switches, and delete it, stopping a running reply first. Each chat has its own messages and context; when you refer to an earlier discussion, Chat searches the site's chats and answers with the messages it found. The open chat is in the page address (`/chats?chat=<id>`), so a link or reload opens the same chat.
8
8
 
9
9
  ## Sending a Message
10
10
 
@@ -41,13 +41,13 @@ To halt the AI mid-generation, use the **Stop button** in the input bar — whil
41
41
 
42
42
  ## Understanding Tool Badges
43
43
 
44
- While the AI works, you see small badges in the chat showing what it is doing. Each badge displays a tool name and its current status. Examples include reading files, writing code, searching your project, or generating images. These badges help you follow along without needing to understand the technical details.
44
+ While the AI works, you see small badges in the chat showing what it is doing. Each badge displays a tool name and its current status. Examples include reading files, writing code, searching your site, or generating images. These badges help you follow along without needing to understand the technical details.
45
45
 
46
46
  ## Reviewing Proposals
47
47
 
48
48
  Ask the AI to keep alternatives as named proposals. Open the Branch picker and choose one from **Proposals** to preview its work. Each proposal has its own changes. The picker follows visibility: internal work stays hidden even when saved, durable, or given more time. Extending retention does not show the work.
49
49
 
50
- A review request saves the selected session's current work and makes that same session visible and durable. Follow its review card to the proposal, or its Preview and Changes links from chat, Slack, or an agent report. These links open the current Branch in Studio and require project access. A review request refers to saved work: if that work changes, request a new review before merging. Exploring or merging proposal B keeps A, C, and D available unless you ask to discard them. Merging does not publish the site.
50
+ A review request saves the selected session's current work and makes that same session visible and durable. Follow its review card to the proposal, or its Preview and Changes links from chat, Slack, or an agent report. These links open the current Branch in Studio and require site access. A review request refers to saved work: if that work changes, request a new review before merging. Exploring or merging proposal B keeps A, C, and D available unless you ask to discard them. Merging does not publish the site.
51
51
 
52
52
  Delete a proposal from the Branch picker when you no longer need it. Pull is unavailable for proposals; ask the AI to update the proposal instead. New Branch defaults to the proposal's upstream. Merge the proposal first if you want to create a Branch from its changes.
53
53
 
@@ -55,7 +55,7 @@ Delete a proposal from the Branch picker when you no longer need it. Pull is una
55
55
 
56
56
  Chat changes are prepared separately and then applied to the environment you are viewing. Most changes merge automatically.
57
57
 
58
- If the project changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input.
58
+ If the site changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input.
59
59
 
60
60
  Choose **Auto fix** or keep chatting to let Fimo continue in the retained proposal, resolve the conflict, and retry the merge. Choose **Review manually** to inspect and resolve the proposal yourself. Discarding leaves the current environment unchanged and permanently removes the proposal.
61
61
 
package/assets/skills/fimo-studio/references/analytics.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Analytics
2
2
 
3
- Open **Analytics** in the project's workspace navigation. It may be inside
3
+ Open **Analytics** in the site's workspace navigation. It may be inside
4
4
  **More** at narrower desktop widths. This workspace reports the published site,
5
5
  regardless of the editing branch currently selected.
6
6
 
package/assets/skills/fimo-studio/references/billing-and-credits.md CHANGED
@@ -15,14 +15,14 @@ Look for the **coin icon with a number** near the chat send button. That number
15
15
  - Click it to open a detailed breakdown showing how many credits you have in each category.
16
16
  - When your balance is low, opening that breakdown shows an alert-triangle warning ("No credits left" or "_N_ credits left") at the bottom.
17
17
 
18
- From a linked project directory, `fimo credits` shows the same organization balance in the CLI. Its "Available now" total already includes the visible buckets.
18
+ From a linked site directory, `fimo credits` shows the same organization balance in the CLI. Its "Available now" total already includes the visible buckets.
19
19
 
20
20
  ## Referral progress
21
21
 
22
- Open **Earn free credits** from the project header (or the project menu on mobile), then use **Copy** inside the link field.
22
+ Open **Earn free credits** from the site header (or the site menu on mobile), then use **Copy** inside the link field.
23
23
 
24
24
  - **Signed up** counts people who registered through your link, including those who later published. Link visits do not count.
25
- - **Published** counts people who published their first project, not the number of projects they publish.
25
+ - **Published** counts people who published their first site, not the number of sites they publish.
26
26
  - **AI credits earned** shows inviter rewards already credited to you. It excludes your own bonus for joining through someone else's link; a publication can appear before its reward is credited.
27
27
 
28
28
  Each signup uses one of the five referral slots. Publishing unlocks the reward but does not reopen a slot. The dialog shows signups used and how many people have not published yet. **Terms and Conditions** opens the program terms; **Close** dismisses the dialog.
package/assets/skills/fimo-studio/references/cms.md CHANGED
@@ -55,7 +55,7 @@ When you open a Collection, the entry list provides several tools:
55
55
 
56
56
  ## Completing Missing Translations
57
57
 
58
- Localized Collections show only entries for the locale selected beside the Collection name. When that locale is missing translations that exist in the project's default locale:
58
+ Localized Collections show only entries for the locale selected beside the Collection name. When that locale is missing translations that exist in the site's default locale:
59
59
 
60
60
  1. Click the amber **N missing** warning beside the locale selector.
61
61
  2. Review the source and target languages in the popover.