fimo 0.15.0-staging.1 → 0.15.0-staging.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fimo",
-  "version": "0.15.0-staging.1",
+  "version": "0.15.0-staging.2",
   "description": "Fimo CLI - create, deploy, and manage Fimo projects",
   "bin": {
     "fimo": "dist/cli/index.js"
@@ -122,6 +122,7 @@
     "postinstall": "node scripts/postinstall.mjs",
     "test": "vitest run",
     "test:integration:astro": "vitest run --config vitest.integration.config.ts test/integration/astro-runtime.test.ts",
+    "test:integration:astro-compat": "vitest run --config vitest.integration.config.ts test/integration/astro-compat.test.ts",
     "test:integration:frameworks": "vitest run --config vitest.integration.config.ts",
     "test:integration:next": "vitest run --config vitest.integration.config.ts test/integration/next-runtime.test.ts",
     "test:integration:sveltekit": "vitest run --config vitest.integration.config.ts test/integration/sveltekit-runtime.test.ts",

package/templates/nextjs/AGENTS.md

@@ -4,14 +4,18 @@ This is a Fimo project. Fimo connects content, media, forms, analytics, editing,
 
 ## Load the Fimo skills before doing Fimo work
 
-Load only the skill relevant to the task:
+Before writing schema-driven code, running CLI/deploy workflows, or migrating content, load only the
+skill relevant to the task. During onboarding, preserve the exact CLI invocation prefix from the
+initiating prompt for every operational command; otherwise default to `npx fimo@latest`:
 
 ```bash
-pnpm exec fimo skills get fimo-code   # code and framework APIs from this project runtime
-npx fimo@latest skills get fimo-cli   # operational workflows: push, deploy, labels, domains
+pnpm exec fimo skills get fimo-code   # match the lockfile; code + framework APIs come from this project runtime
+npx fimo@latest skills get fimo-cli   # default prefix; keep the onboarding prefix when one was supplied
 ```
 
-Use the command that matches the project lockfile. Add `--ref <doc>` for one reference at a time. For Next.js code, start with `fimo-code --ref frameworks/next`, then load the App Router, Pages Router, or locale reference only when needed.
+Use `npm exec fimo`, `yarn fimo`, or `bunx --no-install fimo` instead of `pnpm exec fimo` when that
+matches the project lockfile. Add `--ref <doc>` for one reference at a time. Do not load `fimo-cli` for
+a code-only task, or use `npx fimo@latest` for project-local code generation and validation.
 
 ## Never hardcode editable values
 
@@ -26,10 +30,11 @@ The scaffolded homepage is disposable. Replace it on the first real generation.
 
 1. Start the application with the project package manager (`pnpm dev`, `npm run dev`, `yarn dev`, or `bun dev`).
 2. Build and verify against the local server.
-3. Offer `fimo deploy` for a hosted preview or `fimo deploy --publish` to go live. Deploy only after the developer confirms.
+3. When a unit of work is done, **offer** to deploy: `fimo deploy` for a hosted preview / shareable link, or `fimo deploy --publish` to go live. Deploy on the developer's request or confirmation. The one exception: new-project onboarding creates a single first hosted preview automatically unless the developer said not to deploy. Never publish without an explicit request.
 
 ## Project rules
 
+- **Deploy is on-demand**, not a save step. Batch related edits into one deploy.
 - The application owns routes, locale resolution, links, HTML language/direction, and SEO. Fimo connects to those decisions.
 - Do not add a second deployment platform.
 - Never edit `.fimo/project.json`; it links this directory to the remote project.

package/templates/react-router/AGENTS.md

@@ -9,11 +9,12 @@ When asked to create or manage an agent in this project, use Fimo's agent workfl
 ## Load the Fimo skills before doing Fimo work
 
 Before writing schema-driven code, running CLI/deploy workflows, or migrating content, load only the
-skill relevant to the task:
+skill relevant to the task. During onboarding, preserve the exact CLI invocation prefix from the
+initiating prompt for every operational command; otherwise default to `npx fimo@latest`:
 
 ```bash
 pnpm exec fimo skills get fimo-code   # match the lockfile; code + framework APIs come from this project runtime
-npx fimo@latest skills get fimo-cli   # operational workflows: push, deploy, labels, domains
+npx fimo@latest skills get fimo-cli   # default prefix; keep the onboarding prefix when one was supplied
 ```
 
 Use `npm exec fimo`, `yarn fimo`, or `bunx --no-install fimo` instead of `pnpm exec fimo` when that
@@ -34,7 +35,7 @@ breaks that. Load `fimo-code` for the exact primitives, but the rule is:
 
 1. Start the dev server with the project's package manager (`pnpm dev`, `npm run dev`, …) — live reload on localhost.
 2. Make edits; the running server shows them instantly. No deploy needed to see local changes.
-3. When a unit of work is done, **offer** to deploy: `fimo deploy` for a hosted preview / shareable link, or `fimo deploy --publish` to go live. Only after the developer confirms — never deploy on your own.
+3. When a unit of work is done, **offer** to deploy: `fimo deploy` for a hosted preview / shareable link, or `fimo deploy --publish` to go live. Deploy on the developer's request or confirmation. The one exception: new-project onboarding creates a single first hosted preview automatically unless the developer said not to deploy. Never publish without an explicit request.
 
 ## Project rules
 

package/templates/react-router/package.json

@@ -21,7 +21,7 @@
     "cmdk": "^1.1.1",
     "date-fns": "^4.1.0",
     "embla-carousel-react": "^8.6.0",
-    "fimo": "0.15.0-staging.1",
+    "fimo": "0.15.0-staging.2",
     "input-otp": "^1.4.2",
     "isbot": "^5",
     "lucide-react": "^0.577.0",

package/templates/sveltekit/AGENTS.md

@@ -2,15 +2,35 @@
 
 This SvelteKit application is connected to Fimo for content, editing, environments, and hosting.
 
-## Load Fimo guidance before changing Fimo code
+## Load the Fimo skills before doing Fimo work
+
+Before writing schema-driven code, running CLI/deploy workflows, or migrating content, load only the
+skill relevant to the task. During onboarding, preserve the exact CLI invocation prefix from the
+initiating prompt for every operational command; otherwise default to `npx fimo@latest`:
 
 ```bash
 pnpm exec fimo skills get fimo-code
 pnpm exec fimo skills get fimo-code --ref frameworks/sveltekit
+npx fimo@latest skills get fimo-cli
 ```
 
-Load only the additional task reference you need. The SvelteKit reference owns the framework API and setup rules.
+Use `npm exec fimo`, `yarn fimo`, or `bunx --no-install fimo` instead of `pnpm exec fimo` when that
+matches the project lockfile. Add `--ref <doc>` for one reference at a time. Do not load `fimo-cli` for
+a code-only task, or use `npx fimo@latest` for project-local code generation and validation.
+
+## Development loop
+
+1. Start the application with the project package manager (`pnpm dev`, `npm run dev`, `yarn dev`, or `bun dev`).
+2. Build and verify against the local server.
+3. When a unit of work is done, **offer** to deploy: `fimo deploy` for a hosted preview / shareable link, or `fimo deploy --publish` to go live. Deploy on the developer's request or confirmation. The one exception: new-project onboarding creates a single first hosted preview automatically unless the developer said not to deploy. Never publish without an explicit request.
+
+## Project rules
 
-The scaffolded homepage is disposable. Replace it when building the requested site. The application owns routes, locale resolution, links, HTML language and direction, and SEO.
+- **Deploy is on-demand**, not a save step. Batch related edits into one deploy.
+- The application owns routes, locale resolution, links, HTML language/direction, and SEO. Fimo connects to those decisions.
+- Do not add a second deployment platform.
+- Never edit `.fimo/project.json`; it links this directory to the remote project.
+- Keep secrets in the Fimo dashboard, not committed environment files.
+- Pass flags to interactive Fimo commands when scripting them.
 
-Never edit `.fimo/project.json`; it links this directory to its Fimo project. Keep secrets in Fimo, not committed environment files. Offer `fimo deploy` only when the developer wants a hosted preview or publication.
+The scaffolded homepage is disposable. Replace it when building the requested site.