fimo 2.10.4 → 2.11.0-staging.1
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.
- package/assets/skills/fimo-cli/SKILL.md +1 -1
- package/assets/skills/fimo-cli/references/account.md +1 -1
- package/assets/skills/fimo-cli/references/domains.md +2 -0
- package/assets/skills/fimo-cli/references/hosting.md +1 -1
- package/assets/skills/fimo-cli/references/init.md +1 -1
- package/assets/skills/fimo-cli/references/knowledge.md +10 -3
- package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +1 -1
- package/assets/skills/fimo-studio/references/custom-domains.md +3 -2
- package/dist/cli/bundle.json +2 -2
- package/dist/cli/index.js +32 -31
- package/package.json +18 -10
- package/release.json +2 -2
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -45,7 +45,7 @@ This skill covers CLI workflows. For code (schema JSON, generated clients, primi
|
|
|
45
45
|
Load a reference with `fimo skills get fimo-cli --ref <name>`. "+ fimo-code `<ref>`" means: also load that `fimo-code` reference and the reference for the detected framework.
|
|
46
46
|
|
|
47
47
|
- Create a site, link a project, `fimo init`, and the steps right after init → `init`
|
|
48
|
-
- No account or no browser: `fimo new <dir> --yes --json` (a person claims the site in 72 hours; `fimo claim --json` shows the link; `fimo new --instructions` prints the guide) → `account`
|
|
48
|
+
- No account or no browser: `fimo new <dir> --yes --json`, or `fimo link --json` for an app that already exists (a person claims the site in 72 hours; `fimo claim --json` shows the link; `fimo new --instructions` prints the guide) → `account`
|
|
49
49
|
- Sign in, who am I, switch organization (`fimo orgs switch`; `fimo switch` changes the Branch) → `account`
|
|
50
50
|
- List, clone, rename, delete, or unpublish projects → `projects`
|
|
51
51
|
- Project snapshot: framework, schemas, routes, locales, tree (`fimo describe --json`) → `describe`
|
|
@@ -10,7 +10,7 @@ fimo login # opens your browser; the CLI captures the token automatically
|
|
|
10
10
|
|
|
11
11
|
`fimo login` starts a local loopback server, opens your browser to authorize, and the browser redirects the token back to the CLI — **there's nothing to copy or paste**. After login, the CLI saves the session token and auto-selects an active organization (your session's current org, otherwise the first one) — it never prompts. If you belong to more than one org, change the active one later with `fimo orgs switch` (see below).
|
|
12
12
|
|
|
13
|
-
`fimo login` needs a browser on this machine, not a terminal: a coding agent can run it and the user finishes sign-in in the browser that opens. Where no browser can open (a sandbox, CI), it stops at once with `LOGIN_REQUIRES_BROWSER`; create the site without an account instead with `fimo new <dir> --yes --json` (`fimo new --instructions` prints the guide).
|
|
13
|
+
`fimo login` needs a browser on this machine, not a terminal: a coding agent can run it and the user finishes sign-in in the browser that opens. Where no browser can open (a sandbox, CI), it stops at once with `LOGIN_REQUIRES_BROWSER`; create the site without an account instead with `fimo new <dir> --yes --json` (`fimo new --instructions` prints the guide), or run `fimo link --json` in an app that already exists.
|
|
14
14
|
|
|
15
15
|
```bash
|
|
16
16
|
fimo whoami # show the currently signed-in user + active organization
|
|
@@ -37,12 +37,14 @@ Choosing the slug does not publish the site. The URL resolves after the first su
|
|
|
37
37
|
```bash
|
|
38
38
|
fimo domains add <hostname> [--redirect-www] [--wait [10m]] --json # --redirect-www: the apex redirects to www; bare --wait = 5 min (Ns or Nm)
|
|
39
39
|
fimo domains refresh <hostname> # check DNS and SSL again; it polls by default
|
|
40
|
+
fimo domains primary <hostname> --json # the address search engines see; list marks it (primary)
|
|
40
41
|
fimo domains remove <hostname> --yes
|
|
41
42
|
```
|
|
42
43
|
|
|
43
44
|
- `add` returns the DNS records (usually a CNAME and a TXT) that the user sets at their registrar; with `--json` they are in the domain record. Give them to the user exactly.
|
|
44
45
|
- After the user sets DNS, run `refresh` once; it polls until SSL is active or the wait ends (`--no-wait` prints one status). Read the returned status: the end of a wait does not prove the domain works. Do not run `refresh` in a loop. DNS can take from minutes to 48 hours.
|
|
45
46
|
- In an interactive setup, omit `--wait` on `add` so the user gets the records at once. In CI, `--wait` polls until the domain is verified or the wait ends.
|
|
47
|
+
- The primary domain is the canonical host of the published site. Fimo picks the oldest serving domain until the user chooses one with `primary`; the domain must be active with its certificate issued, else `DOMAIN_NOT_SERVING`. The canonical links change only on the next publish, so tell the user to publish again.
|
|
46
48
|
- A Free plan gets a `PAYWALL` 403 with the billing URL: give that URL to the user.
|
|
47
49
|
- `remove` and `buy` ask for confirmation: pass `--yes` in a run without prompts, after the user agreed.
|
|
48
50
|
|
|
@@ -114,7 +114,7 @@ header on a static asset.
|
|
|
114
114
|
serves `/about` and `/about/` as separate URLs, which search engines index as
|
|
115
115
|
duplicates.
|
|
116
116
|
- **An empty `hosting: {}` means no platform routing**, which is different from
|
|
117
|
-
omitting `hosting` entirely — that leaves legacy SPA
|
|
117
|
+
omitting `hosting` entirely — that leaves legacy SPA behavior untouched.
|
|
118
118
|
- **Not supported:** cron jobs (use `fimo schedules`), image optimization (use
|
|
119
119
|
Fimo media), per-function runtime settings, deployment regions.
|
|
120
120
|
|
|
@@ -13,7 +13,7 @@ fimo link <projectId> [--relink] # link the app in t
|
|
|
13
13
|
- **New site:** `fimo init <dir>`. Without a TTY, or with `--json` or `-y`, it needs `<dir>`. It also needs `--org <id>` when you are in more than one organization and none is active. Use the `ID` column of `fimo orgs list`, not the slug.
|
|
14
14
|
- **Site from Studio, or another existing site:** add `--project-id <id>`. A site with no code yet (for example one just created in Studio) gets a new scaffold and the first push. A site with code is cloned into `<dir>`. `--branch` selects the Branch to check out (default: the site's default Branch).
|
|
15
15
|
- **App that already exists in this folder:** `fimo link <projectId>` keeps the code and the Git history. Run it again to repair missing Fimo files, dependencies, or the `fimo` remote. If the folder is linked to another site, the command stops. Add `--relink` only when the user wants to replace that link. The linked app keeps its text in code, so Studio shows "Nothing to edit". When people will edit the site, load the `fimo-migration` skill and follow its source-backed, same-framework path: it moves the text to labels and the CMS, and its `editable-text` guardrail proves it.
|
|
16
|
-
- **No account, or no browser:** `fimo new <dir> --yes --json` (`--ref account`). With `--json` and no session, `init` fails with `NOT_AUTHENTICATED`.
|
|
16
|
+
- **No account, or no browser:** for a new site, `fimo new <dir> --yes --json` (`--ref account`). For an app that already exists in this folder, `fimo link --json` with no id: without a session it creates an unclaimed site, links the folder, saves the token in `.fimo/credentials.local.json` and returns the claim link. If it fails after creating the site, the error's `details` carry `claim` and `retry_command`: give the claim link to the user and run the retry. `fimo link <projectId>` for another site still needs a session. With `--json` and no session, `init` fails with `NOT_AUTHENTICATED`.
|
|
17
17
|
|
|
18
18
|
## Defaults
|
|
19
19
|
|
|
@@ -32,16 +32,23 @@ permission to learn and persist. A request to change site copy is not a request
|
|
|
32
32
|
Read the current knowledge, edit the complete Markdown while preserving unrelated guidance, and save:
|
|
33
33
|
|
|
34
34
|
```bash
|
|
35
|
-
fimo knowledge set --file knowledge.md --json
|
|
36
|
-
cat knowledge.md | fimo knowledge set --stdin --json
|
|
35
|
+
fimo knowledge set --file knowledge.md --expected-updated-at '<updatedAt from get>' --json
|
|
36
|
+
cat knowledge.md | fimo knowledge set --stdin --expected-updated-at '<updatedAt from get>' --json
|
|
37
37
|
```
|
|
38
38
|
|
|
39
39
|
`--file -` also reads stdin. Content is limited to 10,000 characters. An empty file explicitly clears
|
|
40
40
|
knowledge. Each save replaces the current Markdown.
|
|
41
41
|
|
|
42
|
+
Use `none` for a read whose `updatedAt` is null. On `KNOWLEDGE_CONFLICT`, read again and merge
|
|
43
|
+
your changes while preserving the newer sections; save with the revision from that read.
|
|
44
|
+
Never fetch a newer timestamp just to submit the old content or retry without the condition.
|
|
45
|
+
Fimo's structured `fimo` tool tracks the revision itself: use `knowledge get` successfully
|
|
46
|
+
before `knowledge set` in the same run and omit the flag from tool arguments.
|
|
47
|
+
|
|
42
48
|
CLI `--branch` does not isolate knowledge. Saved updates apply on the next agent context refresh.
|
|
43
49
|
For MCP, use `knowledge_get` or `knowledge_update`
|
|
44
|
-
with `projectId`; update accepts `content
|
|
50
|
+
with `projectId`; update accepts `content` and optional `expectedUpdatedAt`, the timestamp read
|
|
51
|
+
or null for an absent document. Standalone CLI and MCP calls that omit it still replace unconditionally.
|
|
45
52
|
|
|
46
53
|
Settings also offers **Draft from website**. It runs analysis in the background and returns an editable
|
|
47
54
|
draft for review. Only an explicit **Save** updates shared knowledge; drafting does not grant permission
|
|
@@ -44,7 +44,7 @@ It also measures accessibility in each page, and opens one or two pages of each
|
|
|
44
44
|
- **Mobile optimization:** a missing viewport or one that blocks zoom, sideways scrolling, images, tables and forms wider than the screen, tap targets under 24 × 24 px, text mostly under 12 px.
|
|
45
45
|
- **Page speed** (3rd of each month): Lighthouse on a phone for the home page and one page of each template.
|
|
46
46
|
|
|
47
|
-
Alone, it names a control or labels a field from words the page shows, fixes heading levels, tabindex and a removed focus outline, lets visitors zoom again, keeps media inside the screen by its own width, gives small tap targets 24 × 24 px, and moves a failing
|
|
47
|
+
Alone, it names a control or labels a field from words the page shows, fixes heading levels, tabindex and a removed focus outline, lets visitors zoom again, keeps media inside the screen by its own width, gives small tap targets 24 × 24 px, and moves a failing color to a passing shade the site's palette already has. Any other color, size or layout change is asked as a decision. Image alt text stays with SEO.
|
|
48
48
|
|
|
49
49
|
## Compliance (3 routines)
|
|
50
50
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
## Also available via CLI
|
|
2
2
|
|
|
3
|
-
If you're driving Fimo from the terminal, the equivalent commands are `fimo domains add`, `fimo domains refresh`, and `fimo domains remove`. The default URL (the `<slug>.fimo.site` subdomain) is managed with `fimo domains rename-default` and `fimo domains suggest-default` — both free on every plan. See the `fimo-cli` skill's `references/domains.md`. Full docs: https://fimo.ai/docs/deploy/custom-domains.
|
|
3
|
+
If you're driving Fimo from the terminal, the equivalent commands are `fimo domains add`, `fimo domains refresh`, `fimo domains primary`, and `fimo domains remove`. The default URL (the `<slug>.fimo.site` subdomain) is managed with `fimo domains rename-default` and `fimo domains suggest-default` — both free on every plan. See the `fimo-cli` skill's `references/domains.md`. Full docs: https://fimo.ai/docs/deploy/custom-domains.
|
|
4
4
|
|
|
5
5
|
## Before You Start
|
|
6
6
|
|
|
@@ -41,7 +41,8 @@ Each domain shows a small status icon with a tooltip on hover (there is no inlin
|
|
|
41
41
|
## Managing Domains
|
|
42
42
|
|
|
43
43
|
- **Open your domain**: Click the three-dot menu on a domain and select "Open URL" to visit it in a new tab.
|
|
44
|
-
- **
|
|
44
|
+
- **See the primary domain**: The domain search engines see carries a **Primary** badge. Until you choose one, it is the first domain you added that is active with its certificate issued.
|
|
45
|
+
- **Change the primary domain**: Click the three-dot menu on another domain and select **Make primary**. On the redirecting half of an apex and `www` pair, confirm the new direction: Fimo keeps both domains connected and permanently redirects the other hostname while preserving its path and query string. On any other domain, confirm the choice: your other domains keep serving the site. The hostname must be active with its certificate issued first; otherwise the action is disabled or Studio asks you to retry once the certificate is ready. Publish again so canonical links use the new primary domain.
|
|
45
46
|
- **Remove a domain**: Click the three-dot menu and select "Remove". A confirmation dialog appears before deleting.
|
|
46
47
|
- **Refresh status**: Click the refresh button (circular arrow) to re-check DNS propagation.
|
|
47
48
|
|
package/dist/cli/bundle.json
CHANGED