fimo 0.2.3-experimental.1782118113229 → 0.2.3-staging.10

package/assets/skills/fimo/references/setup-plain-vite.md

@@ -36,7 +36,6 @@ pnpm add -D vite @vitejs/plugin-react @types/react @types/react-dom typescript
   "type": "module",
   "scripts": {
     "dev": "vite --host 0.0.0.0 --port 5173",
-    "prebuild": "fimo validate",
     "build": "vite build",
     "preview": "vite preview --host 0.0.0.0 --port 4173",
     "typecheck": "tsc --noEmit"
@@ -44,6 +43,10 @@ pnpm add -D vite @vitejs/plugin-react @types/react @types/react-dom typescript
 }
 ```
 
+Validate runs automatically during `fimo deploy` and API-side sandbox builds.
+For a purely local build, run `fimo validate` manually first when you need to
+sync schemas/forms/translations before `pnpm build`.
+
 ## File: `vite.config.ts`
 
 ```ts

package/assets/skills/fimo/references/setup-react-router.md

@@ -27,7 +27,6 @@ pnpm add -D @react-router/dev @react-router/node @tailwindcss/vite tailwindcss v
   "type": "module",
   "scripts": {
     "dev": "react-router dev --port 5173",
-    "prebuild": "fimo validate",
     "build": "react-router build && fimo export-static",
     "preview": "vite preview --host 0.0.0.0 --port 4173",
     "typecheck": "tsc --noEmit"
@@ -35,7 +34,9 @@ pnpm add -D @react-router/dev @react-router/node @tailwindcss/vite tailwindcss v
 }
 ```
 
-(Dependencies installed via the command above; this is the scripts shape.)
+Validate runs automatically during `fimo deploy` and API-side sandbox builds.
+For a purely local build, run `fimo validate` manually first when you need to
+sync schemas/forms/translations before `pnpm build`.
 
 ## File: `vite.config.ts`
 

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/agent-setup.md

@@ -60,7 +60,7 @@ The command prints exactly which files were written, so the context-aware behavi
 You rarely have to invoke it by hand:
 
 - **Global skills auto-refresh** after a CLI version change via a marker at `~/.config/fimo/last-version`.
-- **The project skill auto-refreshes on `pnpm install`** when the `fimo` package version bumps — the package's postinstall hook re-syncs the skill from `node_modules/fimo/assets/skills/fimo/` (which is version-locked to the installed package). The scaffolded template approves the `fimo` and `esbuild` build scripts for pnpm (`pnpm-workspace.yaml` `allowBuilds` for pnpm 11+, plus `package.json` `pnpm.onlyBuiltDependencies` for pnpm 10-era installs). npm / yarn run lifecycle scripts by default and need no extra config.
+- **The project skill auto-refreshes during Fimo-controlled installs** when the `fimo` package version bumps — the package's postinstall hook re-syncs the skill from `node_modules/fimo/assets/skills/fimo/` (which is version-locked to the installed package). For pnpm, `fimo create --install`, sandbox `fimopm install`, and E2E helper installs pass a scoped allow-all-builds flag so the hook can run without persisting build-script approvals in the template. npm / yarn run lifecycle scripts by default and need no extra config.
 
 Invoke `fimo skills sync` explicitly when iterating on skill content locally, when you bumped the package via something other than a fresh install, or any time you want to force a refresh.
 

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

@@ -1,5 +1,7 @@
 # Envs & branches (git-shaped workflow)
 
+> **Beta:** Branch environments are still in beta. The CLI surface is available for early workflows, but not every command or cross-surface merge path is guaranteed to work reliably yet.
+
 A Fimo **env** is a multi-surface clone of the project: a git branch **plus** its own Neon DB branch, sandbox, preview URL, and R2 asset prefix. The CLI mirrors `git` command shapes so the workflow transfers directly — same verbs, multi-surface semantics.
 
 Every project starts with one env: `main`. You create more for feature work, deploy previews per-env, then merge back and publish.

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/assets/skills/fimo-studio/references/code-editor.md

@@ -1,6 +1,6 @@
 ## Browsing Your Files
 
-The Code tab requires **Developer Mode** to be enabled. Go to **Account Settings → Preferences** and turn on the **Developer Mode** toggle. Once enabled, click the **Code** tab (the code icon) in the workspace navigation, or press **Option+4** (Mac) / **Alt+4** (Windows/Linux). A file tree appears showing all your project files and folders.
+Click the **Code** tab (the code icon) in the workspace navigation, or press **Option+4** (Mac) / **Alt+4** (Windows/Linux). A file tree appears showing all your project files and folders.
 
 Inside the Code workspace, the left sidebar shows the **Files** tree. If you ever switch the sidebar to another view, press **Cmd+Shift+E** (Mac) / **Ctrl+Shift+E** (Windows/Linux) to bring the Files explorer back.
 

package/dist/cli/bundle.json

@@ -1,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-06-22T08:48:42.757Z",
-  "cliVersion": "0.2.3-experimental.1782118113229",
+  "bundledAt": "2026-06-23T15:06:33.888Z",
+  "cliVersion": "0.2.3-staging.10",
   "external": [
     "oxc-parser",
     "fsevents"