fimo 0.2.3-staging.5 → 0.2.3-staging.7

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

@@ -44,6 +44,7 @@ npm i -g fimo                              # install the CLI globally
 fimo login                                 # authenticate via browser
 fimo skills install                        # install Fimo skills for your AI tools
 fimo create my-site --org <id>             # scaffold (writes .fimo.settings.json + AGENTS.md + project skill). Use the org **id** from `fimo orgs list`, NOT the slug.
+fimo clone                                 # interactively choose an existing project to clone locally
 cd my-site                                 # the `fimo` project skill auto-loads from here
 fimo credits                               # inspect the owning org's AI credit balance (read-only)
 fimo validate                              # run all checks + sync schemas/forms/translations to DB
@@ -72,7 +73,7 @@ Load the matching reference when the user's request fires its trigger. Recipes t
 - "Firecrawl / scrape a public website / competitor research / agent web research" → `references/integrations.md` **+ load `references/integrations/firecrawl.md`**
 - "Check credits / credit balance / can I keep using AI / billing credits / running low / how many credits are left" → `references/credits.md`
 - "Create a branch / feature environment / new env / switch envs / merge envs / diff two envs / env status / what changed on this branch / sync from parent / cut a release / tag a version / go to prod" → `references/branches.md`
-- "List my projects / delete this project / unpublish / rename the project / manage projects across the org" → `references/projects.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 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`

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

@@ -8,6 +8,8 @@
 | **Custom domain**     | A hostname the user owns (e.g. `blog.example.com`), attached via DNS | Premium                | Many        | `project_domains` table    |
 | **Registered domain** | A new domain bought _through_ Fimo via the registrar reseller        | Premium + feature flag | Many        | `registered_domains` table |
 
+> **A renamed URL or custom domain only resolves once the site is published** (`fimo deploy --publish`); before that it returns "Project Not Found".
+
 ## Commands
 
 ```bash
@@ -106,6 +108,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`.
 - **"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.

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

@@ -1,12 +1,13 @@
 # Managing projects
 
-Commands for listing projects across an org and for managing the lifecycle of a single project (delete, publish, unpublish, rename). Most operate on the **current project** (read from `.fimo.settings.json` in the cwd) by default; for `delete`, `publish`, and `unpublish` you can pass an explicit `[projectId]` to target another. (`rename` is local-only — it never targets a different project; see below.)
+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.settings.json` in the cwd) by default; for `delete`, `publish`, and `unpublish` you can pass an explicit `[projectId]` to target another. (`rename` is local-only — it never targets a different project; see below.)
 
 ## The `fimo projects` namespace
 
 ```bash
 fimo projects list [--org <id>]                 # list projects in an org (defaults to active org)
 fimo projects create [dir] [--org <id>] [--install|--no-install]   # alias of `fimo create`
+fimo projects clone [projectId] [dir] [--env <name>] # clone an existing project locally
 fimo projects delete [projectId] [-C <dir>] [-y] # delete (defaults to current project)
 fimo projects publish [projectId] [-C <dir>]     # make the project live (publish from main)
 fimo projects unpublish [projectId] [-C <dir>]   # take the project offline
@@ -15,10 +16,19 @@ fimo projects rename <name> [projectId] [-C <dir>]   # local-only: set seo.siteN
 
 - **`list`** — projects you can see in the org. Live projects are marked.
 - **`create`** — identical to `fimo create`; see `references/create.md`.
+- **`clone`** — clone a remote Fimo project's git repo to your machine and write the local `.fimo.settings.json`/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 `--env <name>` to clone a specific env. The target directory defaults to the project display name/name, or pass `[dir]` explicitly.
 - **`delete`** — destructive; prompts unless `-y`. Removes the remote project.
 - **`publish` / `unpublish`** — toggle the project's public visibility. `publish` flips the current `main` state live (the same "go live" as `fimo deploy --publish`, minus the git push). This is **not** the versioned release path — for that, see `fimo publish` in `references/branches.md`.
 - **`rename`** — **local-only**, unlike the others. It does not touch the remote project record. It requires `.fimo.settings.json` 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). It writes `seo.siteName` into the local `fimo-config.json`; you must commit and run `fimo deploy` to apply the change.
 
+## Top-level clone shortcut
+
+```bash
+fimo clone [projectId] [dir] [--env <name>] # same as `fimo projects clone`
+```
+
+Use the top-level shortcut for the common "get this project onto my machine" workflow. After clone succeeds, `cd` into the printed directory and load the newly written project context (`AGENTS.md` plus the installed project skill) before generating code.
+
 ## Top-level shortcuts (current project)
 
 These target the project linked in the cwd's `.fimo.settings.json` — handy from inside a project directory:

package/dist/cli/bundle.json

@@ -1,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-06-19T14:20:28.710Z",
-  "cliVersion": "0.2.3-staging.5",
+  "bundledAt": "2026-06-23T08:08:32.546Z",
+  "cliVersion": "0.2.3-staging.7",
   "external": [
     "oxc-parser",
     "fsevents"