fimo 2.8.0-staging.8 → 2.8.0

package/assets/agent-templates/seo-audit/scripts/score.ts

@@ -1,131 +0,0 @@
-/**
- * Tool: score
- *
- * Apply the SEO scoring methodology (see references/scoring-methodology.md)
- * to a list of `(path, SEOSignals)` tuples and produce a per-page report.
- *
- * Inputs (stdin JSON): { signals: Record<path, SEOSignals> }
- * Outputs (stdout JSON): { score: 0..100, pages: PageReport[] }
- */
-
-interface SEOSignals {
-  title: string | null;
-  description: string | null;
-  canonical: string | null;
-  robots: string | null;
-  openGraph: Record<string, string>;
-  schemaOrg: unknown[];
-  headings: { h1: string[]; h2: string[]; h3: string[] };
-}
-
-interface Finding {
-  rule: string;
-  severity: 'ok' | 'warn' | 'fail';
-  message: string;
-}
-
-interface PageReport {
-  path: string;
-  score: number;
-  findings: Finding[];
-}
-
-function audit(signals: SEOSignals): Finding[] {
-  const out: Finding[] = [];
-
-  // Title
-  if (!signals.title) {
-    out.push({ rule: 'title-present', severity: 'fail', message: 'Missing <title>' });
-  } else if (signals.title.length < 30 || signals.title.length > 60) {
-    out.push({
-      rule: 'title-length',
-      severity: 'warn',
-      message: `Title length ${signals.title.length} chars — recommend 30–60`,
-    });
-  } else {
-    out.push({ rule: 'title', severity: 'ok', message: 'Title looks good' });
-  }
-
-  // Description
-  if (!signals.description) {
-    out.push({ rule: 'description-present', severity: 'fail', message: 'Missing meta description' });
-  } else if (signals.description.length < 50 || signals.description.length > 160) {
-    out.push({
-      rule: 'description-length',
-      severity: 'warn',
-      message: `Description length ${signals.description.length} chars — recommend 50–160`,
-    });
-  }
-
-  // OG tags
-  for (const key of ['title', 'description', 'image', 'url']) {
-    if (!signals.openGraph[key]) {
-      out.push({ rule: `og-${key}`, severity: 'warn', message: `Missing og:${key}` });
-    }
-  }
-
-  // Headings
-  if (signals.headings.h1.length === 0) {
-    out.push({ rule: 'h1-present', severity: 'fail', message: 'No <h1> on the page' });
-  } else if (signals.headings.h1.length > 1) {
-    out.push({ rule: 'h1-single', severity: 'warn', message: `Multiple <h1> tags (${signals.headings.h1.length})` });
-  }
-
-  // Canonical
-  if (!signals.canonical) {
-    out.push({ rule: 'canonical', severity: 'warn', message: 'Missing canonical link' });
-  }
-
-  // Robots
-  if (signals.robots && /noindex/i.test(signals.robots)) {
-    out.push({ rule: 'robots-noindex', severity: 'fail', message: 'Page is marked noindex' });
-  }
-
-  // Schema.org
-  if (signals.schemaOrg.length === 0) {
-    out.push({ rule: 'schema-org', severity: 'warn', message: 'No JSON-LD schema.org block' });
-  }
-
-  return out;
-}
-
-function scoreOf(findings: Finding[]): number {
-  // Each fail = -15, each warn = -5. Floor at 0.
-  let pts = 100;
-  for (const f of findings) {
-    if (f.severity === 'fail') {
-      pts -= 15;
-    } else if (f.severity === 'warn') {
-      pts -= 5;
-    }
-  }
-  return Math.max(0, pts);
-}
-
-async function readStdin(): Promise<string> {
-  const chunks: Buffer[] = [];
-  for await (const chunk of process.stdin) {
-    chunks.push(Buffer.from(chunk));
-  }
-  return Buffer.concat(chunks).toString('utf8');
-}
-
-async function main(): Promise<void> {
-  const text = await readStdin();
-  const payload = JSON.parse(text) as { signals: Record<string, SEOSignals> };
-
-  const pages: PageReport[] = [];
-  for (const [path, signals] of Object.entries(payload.signals)) {
-    const findings = audit(signals);
-    pages.push({ path, score: scoreOf(findings), findings });
-  }
-
-  const overall = pages.length === 0 ? 0 : Math.round(pages.reduce((a, p) => a + p.score, 0) / pages.length);
-
-  process.stdout.write(JSON.stringify({ score: overall, pages }, null, 2));
-}
-
-main().catch((err) => {
-  console.error(err);
-  process.exit(1);
-});

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

@@ -1,298 +0,0 @@
-# Agents workflow (`fimo agents *`)
-
-The `fimo agents` namespace authors and operates **agent bundles** — multi-file definitions under `<project>/.fimo/agents/<name>/` (a `config.yaml`, a `GOAL.md`, optional `capabilities.yaml`, etc.). Legacy projects keep using root `agents/<name>/`.
-
-## Mental model
-
-The namespace splits cleanly in two:
-
-- **Bundle authoring** — `create`, `list-templates`, `list`, `validate`, `secrets add/remove/list`. Local config editing, no API call except the project-level validation path. Operates on the files under `.fimo/agents/<name>/` (or root `agents/<name>/` for legacy projects).
-- **Cloud ops** — `run`, `runs`, `report`. Branch-aware, talk to the server. Default `--branch` is `main`; `--env` is rejected as a Branch selector. `--project` defaults to the linked project in `.fimo/project.json` or legacy `.fimo.settings.json`.
-
-The bundle lives in **git** (`.fimo/agents/<name>/`, or legacy root `agents/<name>/`), not the database. The DB only mirrors what `config.yaml` declares on `main` (which triggers are wired) plus **run sessions**. So the bundle reaches the server through `fimo deploy` — and that push to `main` is also what wires its triggers. There is no activate command: deploying IS the enablement act, and removing a trigger from `config.yaml` tears it down on the next deploy.
-
-Typical flow:
-
-```
-fimo agents create <name>     # scaffold .fimo/agents/<name>/ from a template (local)
-fimo agents secrets add <name> FIRECRAWL_API_KEY  # request a project secret in config.yaml
-fimo secrets add FIRECRAWL_API_KEY --stdin        # store the hidden value in Fimo
-fimo agents validate <name>   # parse + policy + composition + requested secrets
-fimo validate                 # project build and codegen checks
-fimo deploy                   # push to main — this also wires the declared triggers
-fimo agents run <name>        # trigger a manual run → sessionId
-fimo agents runs <name>       # see past sessions
-fimo agents report <name>     # print a run's outcome summary
-```
-
-## Bundle authoring (local)
-
-```bash
-fimo agents list-templates
-fimo agents create <name> [--template <t>] [--description <text>] [--quiet] [-C <dir>]
-fimo agents list [-C <dir>]
-fimo agents validate [name] [--json] [-C <dir>]
-fimo agents secrets list <name> [--json] [-C <dir>]
-fimo agents secrets add <name> <KEY> [-C <dir>]
-fimo agents secrets remove <name> <KEY> [-C <dir>]
-```
-
-- **`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`.
-- **`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.
-- 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.
-- **`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.
-- **`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.
-- **`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`.
-- **`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`.
-
-Agent integration access is configured in `.fimo/agents/<name>/config.yaml` (or legacy root). Enable the integration there; omit `tools` to allow all tools that integration exposes, or add a `tools` map to keep the agent on a smaller set:
-
-```yaml
-integrations:
-  firecrawl:
-    enabled: true
-```
-
-An explicit map is restrictive: only entries set to `true` are available. An omitted or disabled integration cannot be
-used. See `references/integrations.md` for project setup, auth, and provider-specific commands.
-
-Declare a `runtime` block in `config.yaml` to gate where a bundle runs and bound what one run costs:
-
-```yaml
-runtime:
-  cloud: true
-  dev: false
-  max_credits: 5000
-```
-
-- `cloud` / `dev` — declared boolean environment flags for where the bundle may run.
-- `max_credits` — the run's own credit ceiling (integer, credits ≥ 1) and the one limit to tune. The default scaffold
-  template ships `max_credits: 5000` as a visible starter limit; raise, lower, or remove it to fit the agent's work.
-  Unset: the run may spend up to the organization's available credits at admission.
-- `max_steps` — advanced cost-management knob, extremely rare: a cap on model-loop steps for one run (integer ≥ 1).
-  Leave it unset unless the author explicitly wants a step-based bound on top of credits. Do not add it when
-  scaffolding a bundle, and do not reach for it to control spend — tune `max_credits` instead. Unset: no step cap;
-  `max_credits` (or the organization's balance) and the plan's agent-hours bound the run.
-
-All four keys are optional; an absent `runtime` block behaves as if every key were unset. There is no platform step cap
-and no platform per-run cost ceiling — the only stops are these author-owned limits, the organization running out of
-credits (`insufficient_credits`), and the agent-hours allowance. A limit that fires records a truthful terminal reason
-(`max_steps`, `budget_exceeded`, or `insufficient_credits`), readable via `fimo agents report` and the Studio run page.
-
-## How a cloud run ends
-
-Runs perform compute; explicit work sessions hold project changes. Ordinary conversation and research need no session.
-Project operations name their session. Save accumulated work before a risky operation or handoff. A confirmed save
-commits and pushes without merging or publishing; Fimo also attempts a bounded save when compute ends.
-
-Merge ready work explicitly. Resolve clear conflicts through the existing merge tools; ask when the resolution requires
-product intent. Request review with one sessionId; request_review saves current work itself and makes that same session visible and durable. Inspecting or leaving a session open creates no review.
-Discard only unwanted work within the requested scope. Ending a run does none of these operations implicitly.
-
-The autonomous `report` tool records a structured report without ending compute or deciding session fate. The model may
-continue working after reporting. A normal model stop ends compute. Scheduled work has no implicit publication grant.
-
-The run report is a concise outcome summary: what changed, what was verified, and what is still blocked. It is not a
-chronological account, and it should not use decorative emoji.
-
-## Define the agent's decision policy
-
-When authoring or editing an agent, add a short **Decision policy** to its `GOAL.md`. Describe the domain conditions for
-acting, asking, review, and merge; do not copy Fimo's tool protocol. Use this shape and replace the examples with rules
-specific to the agent:
-
-Infer the intended autonomy from the user's request when it is clear. Otherwise ask what the agent may apply itself,
-what needs review, and whether it may publish. Record that policy in `GOAL.md`; do not impose review-first on every
-agent or treat permission to merge as permission to publish. A routine fixer and a proposal writer need different policies.
-
-```md
-## Decision policy
-
-- Proceed without asking when the work is within scope and a safe, reversible choice exists.
-- Ask when a missing human decision changes what the correct result should be.
-- Request review of the saved session when completed work needs a person's approval before merge.
-- Request merge only when the result is complete, verified, and clearly safe for this agent's scope.
-- Discard when the run produced no useful changes or deliberately abandoned them.
-```
-
-`ask_user` requests a blocking decision and ends the current invocation. `request_review` saves and captures one selected session for approval
-without ending compute. Neither operation merges or discards sessions.
-
-Make those rules concrete enough that the agent can decide without guessing. For example:
-
-- **Broken-link sweeper:** fix and request merge for up to ten internal links when each replacement is unambiguous and
-  the link check passes. Ask when two plausible destinations change the page's meaning. Retain useful fixes if complete
-  verification is blocked. Discard when the scan is clean or exploratory edits were reverted.
-- **Launch-copy agent:** draft from an approved brief without asking about routine wording. Ask before choosing pricing,
-  product promises, brand direction, or deletions. Retain every completed draft for human review; never request merge.
-- **Read-only auditor:** inspect and report autonomously. Ask only when the requested scope cannot be inferred.
-- **Missing capability:** ask once for the exact capability and explain which operation it unlocks. Do not retain partial
-  work as a substitute for the blocking permission decision.
-
-A review-first content agent could use this complete policy:
-
-```md
-## Decision policy
-
-- Draft all requested copy without asking when the brief and approved source material answer the content decisions.
-- Ask before inventing a price, product promise, legal claim, brand direction, or deleting existing content.
-- Group every blocking decision and missing capability into one question.
-- Retain every completed draft so a person reviews all changes before merge. Never request merge directly.
-- Discard only when no useful draft was produced or the attempted approach was fully abandoned.
-```
-
-When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. Fimo
-emails project members a link to answer it in Studio, and the current invocation ends. It can reference zero or more
-sessions. An authorized answer starts a continuation in the same thread; the referenced work stays open and the original
-model process does not wait.
-
-Use `ask_user` sparingly, especially from scheduled agents:
-
-- Ask only for a genuinely blocking human decision. Prefer a safe reversible default when one exists.
-- Group every known blocker into one form with 1–4 related steps. Give it a 1–3 sentence description that says where
-  the work stands and why the decision matters or what it unlocks; keep implementation detail in the run.
-- Use choices for compact text options. Use cards only when an option benefits from an image or a richer title and
-  subtitle. Use assets when the image itself is the answer, and tables when options need the same structured comparison.
-- Do not repeat a question or request already waiting in prior run history.
-- Use `request_review` with one sessionId when approval is needed. No pre-save or promotion is required; other sessions stay unchanged and work can continue.
-
-An agent may include one multi-select `capabilities` step in that same form to request public Fimo capabilities it does
-not currently hold. Group related tokens in one request. Selected tokens apply only to the continuation started by that
-answer; unselected tokens are denied, selecting none is valid, and the blocked invocation never gains new authority.
-Internal runtime abilities, integration setup, and OAuth are not capability requests.
-
-At the start of a run, `run_history` provides bounded summaries of earlier outcomes and work still awaiting a person. An agent
-may also maintain `.fimo/agents/<name>/MEMORY.md` as an ordinary reviewed file for durable facts that change future
-behavior. Keep it under 4 KB, record no secrets or run log, and prune stale entries before adding new ones.
-
-When three or more earlier runs still await a question answer, review, conflict resolution, or recovery, the agent
-normally starts no new independent work. Unless the current trigger explicitly asks it to proceed anyway, it makes no
-changes and records a brief report of what is waiting.
-
-## Define reporting preferences when they matter
-
-Fimo's default report needs no setup: a short, scannable brief appears in email, while the full report in Fimo carries
-the organized evidence and depth. Do not add a reporting section merely to restate that default.
-
-When the user names an audience, depth, recurring comparison, required section, or useful visual, preserve the request
-in a short **Reporting** section of `GOAL.md`. Describe the communication outcome in ordinary language. Do not prescribe
-report block arrays or promise that the full report will appear in email.
-
-Examples for different jobs:
-
-```md
-## Reporting
-
-Write the brief for a marketing lead. Lead with the outcome and at most three decisions or risks. Keep implementation
-evidence in the full report.
-```
-
-```md
-## Reporting
-
-Compare this week with the previous four weeks. Use a graph only when the change over time is part of the conclusion,
-and include the complete channel breakdown in the full report.
-```
-
-```md
-## Reporting
-
-Show enough of each created article to judge its voice, then link to the draft. Preserve the complete copy and editorial
-decisions in the full report.
-```
-
-These are preferences, not templates. Keep the default brief short and scannable unless the user asks for a different
-audience or emphasis. Even then, the brief remains the external handoff and the full report holds the supporting depth.
-
-## Capabilities
-
-Capabilities describe the opt-in Fimo actions an agent may take. Managed agents always receive project filesystem
-access, a shell, the ability to commit their task-environment changes, and web and data tools; Fimo owns branch creation
-and publication. If `capabilities.yaml` is absent or empty, the agent keeps baseline project reads such as agent run
-history, but receives no CMS, asset, or other domain-operation scope. Once you add a capabilities file, list every Fimo
-permission the agent needs. `net:fetch` is no longer needed and is ignored.
-Namespace selectors such as `cms:*`, `assets:*`, `i18n:*`, and `forms:*` grant every current and future declarable capability
-in that namespace. Fimo expands selectors to concrete grants when a run starts. Use exact tokens for narrower agents.
-The default template includes those four selectors plus read access to analytics, deployment logs, history, previews,
-webhooks, and schedules; remove entries when an agent should have less access.
-
-| Capability                                  | Allows the agent to                                                       | Risk         |
-| ------------------------------------------- | ------------------------------------------------------------------------- | ------------ |
-| `cms:read`                                  | Read CMS content                                                          | Low          |
-| `cms:write`                                 | Create, update, or delete CMS entries                                     | Medium       |
-| `cms:schema:read`                           | Read CMS schemas                                                          | Low          |
-| `cms:schema:write`                          | Modify CMS schemas                                                        | High         |
-| `assets:read`                               | Read uploaded media                                                       | Low          |
-| `assets:write`                              | Upload, replace, or delete media                                          | Medium       |
-| `i18n:read` / `i18n:write`                  | Read / modify translation catalogs                                        | Low / Medium |
-| `cms:*` / `assets:*` / `i18n:*` / `forms:*` | Every declarable capability in that namespace, including future additions | Mixed        |
-| `forms:read` / `forms:write`                | Read / modify form schemas and submissions                                | Low / Medium |
-| `webhooks:read`                             | Read webhook configs and deliveries                                       | Low          |
-| `webhooks:write`                            | Create, modify, delete, or trigger webhooks                               | High         |
-| `schedules:read`                            | Read schedule configs and run history                                     | Low          |
-| `schedules:write`                           | Create, change, or trigger scheduled runs                                 | Critical     |
-| `fimo:logs:read`                            | Read project deployment logs                                              | Low          |
-| `fimo:analytics:read`                       | Read analytics data                                                       | Low          |
-| `fimo:preview:read`                         | Read a current preview URL                                                | Low          |
-| `fimo:history:read`                         | Read project restore points                                               | Low          |
-| `fimo:deploy`                               | Trigger a production deploy                                               | Critical     |
-| `agent:delegate`                            | Invoke declared sub-agents                                                | Medium       |
-| `runtime:auto_merge`                        | Merge work sessions without per-change review                             | Critical     |
-
-If a public Fimo capability is missing and the work is genuinely blocked, the agent can request it through `ask_user`.
-Fimo grants only the selected subset to the next invocation in that run thread. Unknown capabilities, internal runtime
-abilities, and capabilities the run already holds are refused before the question is stored. For durable access on
-ordinary future runs, add the capability to `capabilities.yaml`, validate, and deploy the bundle.
-
-Managed agents can list project agents and read their run history through baseline site access. This does not
-require `fimo:agents:run`; that capability is only required to dispatch another agent.
-
-Studio chat and project-bound Slack turns receive `fimo:logs:read`. The default autonomous-agent template now declares
-it too; custom templates still need to declare it before using `fimo logs` to diagnose a failed preview.
-
-Example for a content editor that can read and update entries but cannot change schemas:
-
-```yaml
-- cms:read
-- cms:write
-```
-
-## Cloud ops (Branch-aware)
-
-```bash
-fimo agents run <name> [--branch <branch>] [--project <id>] [--skip-drift-check] [-C <dir>]
-fimo agents runs <name> [--limit <n>] [--cursor <cursor>] [--all-pages] [--branch <branch>] [--project <id>] [-C <dir>]
-fimo agents report <name> [--session <id>] [--branch <branch>] [--project <id>] [-C <dir>]
-```
-
-- **`run <name>`** — fire the agent's `manual` trigger on the server; prints a `sessionId` on success. A refusal you must act on exits **1** with a stable code (`--json` puts it in `error.code`, and the raw server reason in `error.details.skipped`):
-
-  | Code                        | Means                                                                           | Fix                                               |
-  | --------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------- |
-  | `AGENT_NOT_DEPLOYED`        | no bundle for this agent on `main`                                              | `fimo deploy`                                     |
-  | `AGENT_CONFIG_INVALID`      | the deployed bundle does not parse, so the sync registered none of its triggers | `fimo agents validate <name>`, fix, `fimo deploy` |
-  | `NO_MANUAL_TRIGGER`         | the deployed `config.yaml` really declares no `manual` trigger                  | add `- type: manual`, `fimo deploy`               |
-  | `MANUAL_TRIGGER_NOT_SYNCED` | `main` declares it, the background sync has not registered it yet               | wait a few seconds, retry                         |
-  | `TRIGGER_NOT_WIRED`         | registered but not live (see the wiring note below)                             | `fimo agents list` for the reason                 |
-  | `INSUFFICIENT_CREDITS`      | the org is under the credit floor a run needs                                   | `fimo credits`                                    |
-
-  A refusal that clears on its own (`agent-paused`, `run-in-progress`, `task-branch-budget`) exits **0** and prints `Dispatch was skipped: <reason>`. **Pre-flight drift check**: if `.fimo/agents/<name>/` (or the legacy root bundle) has uncommitted git changes, the command refuses — the server would dispatch the _deployed_ version, so deploy first. Pass `--skip-drift-check` to dispatch the deployed bundle anyway. Defaults `--branch` to `main`.
-
-- **`runs <name>`** — list past run sessions for the agent in a compact table (id, started, duration, status, trigger, Branch, credits — settled credit consumption, `—` until a run settles). Default `--limit 20`; `--branch` filters to one Branch. The response uses the canonical `branch` field.
-- **`report <name>`** — print a run's structured **report**: its durable outcome summary (for a read-only agent like `seo-audit` this _is_ the audit; for a write agent it's a "what I changed" summary). A run that returns plain text without calling `report` receives a small structured fallback document. With no `--session`, the most recent run for `<name>` is used (combine with `--branch` to scope); `--session <id>` targets a specific run. Output is projected Markdown, so it stays readable in the terminal and pipes cleanly (e.g. `fimo agents report seo-audit | glow`). If the run hasn't finished, or produced no report, it says so (and shows the stop reason when there is one).
-
-## How triggers get wired
-
-Agents are not Branch-scoped: they belong to the project, are read from `main`, and their triggers are global. Studio shows the deployed main agents on every Branch. When the selected Branch contains a new bundle that is not on main yet, Studio also shows it as disabled and explains that it becomes available after merge. Its triggers remain inactive until the bundle reaches main.
-
-Pushing `.fimo/agents/<name>/config.yaml` (or a legacy root bundle) to `main` is the whole enablement act — `fimo deploy` does it. The server reconciles the file into its trigger rows on every push: a `schedule` trigger gets a cron, a `webhook` trigger gets its path, and `manual` becomes runnable. Removing a trigger from the file deletes it (cron torn down, path released) on the next deploy; deleting the agent's directory removes the whole deployment.
-
-Cloud triggers (`schedule` / `webhook`) additionally require `notifications.email_recipients` in `.fimo/config.json` (legacy root `fimo-config.json` and `fimo.config.json` are also accepted). Without it the trigger is recorded but deliberately left **unwired** and will not fire — `fimo agents validate` warns about this before you deploy, and the Studio agents view shows the reason afterwards.
-
-## `-C, --cwd <dir>`
-
-Every `fimo agents` command accepts `-C, --cwd <dir>` to point at a different project directory. For the cloud-ops commands, `--project <id>` overrides the project id otherwise read from `.fimo/project.json` or legacy `.fimo.settings.json`.
-
-## Non-interactive use
-
-No `fimo agents` command prompts — authoring and cloud ops both run unattended.

package/assets/skills/fimo-studio/references/agents.md

@@ -1,33 +0,0 @@
-# Agents
-
-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.
-
-## Open an agent
-
-1. Open the site and choose **Agents**.
-2. Select **Agents** again to see the available bundles.
-3. Choose an agent to open its **Runs** and **Settings** tabs.
-
-On a user Branch, the list also shows new bundles that exist only on that Branch. Their cards are disabled; open one to see that the agent and its triggers become available after the Branch is merged into main.
-
-When the agent has a live schedule, its next run appears first in **Runs**, marked **Scheduled**. The row uses **Next** for its projected ID, a relative date such as **Tomorrow at 11:00 AM**, and **—** for changes and duration until it starts. **Settings** shows the bundle's declared capabilities and trigger wiring; it is read-only because the repository remains the source of truth.
-
-## Run, stop, or resume
-
-Choose **Run** to start an agent whose manual trigger is live.
-
-Choose **Stop** to pause every future trigger and stop planned or running work. Studio asks for confirmation and explains that the bundle, trigger configuration, model, capabilities, and other settings are preserved.
-
-A stopped agent shows **Paused** in the header. **Resume** makes the same triggers live again with their previous settings.
-
-Only site managers see Run, Stop, and Resume. Other site members can still see schedule timing, status, settings, and run history.
-
-## Delete an agent
-
-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.
-
-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.
-
-## Inspect runs
-
-Open **Runs** on an agent to see only that bundle's history. Select a run to read its status, report, captured changes, and any question or review state that needs attention.

package/assets/skills/fimo-studio/references/drawing-and-wireframing.md

@@ -1,61 +0,0 @@
-## Opening the Drawing Tool
-
-Inside an existing site, open the wireframe canvas from the chat attachment dropdown: click the add-attachments (**+**) button next to the chat input, then choose **Draw**. (This option is hidden on mobile.)
-
-Selecting **Draw** opens a large drawing canvas powered by Excalidraw, displayed in a centered dialog.
-
-## Toolbar Basics
-
-Across the top of the canvas you will find these tools:
-
-- **Hand** -- pan around the canvas without selecting anything.
-- **Select** -- select and move elements.
-- **Rectangle** -- draw rectangular shapes.
-- **Diamond** -- draw diamond shapes.
-- **Ellipse** -- draw circles and ovals.
-- **Arrow** -- draw arrows to show flow or connections.
-- **Line** -- draw straight lines.
-- **Draw (freehand)** -- draw anything by hand for quick annotations or custom shapes.
-- **Text** -- click anywhere to add labels like "Header", "Hero Image", or "Sign Up Button".
-- **Image** -- insert an image onto the canvas.
-
-Pick a tool, draw on the canvas, and switch tools as needed. Zoom ranges from 10% to 300%.
-
-## Component Library
-
-The canvas comes with a library panel of **pre-made UI wireframe components**:
-
-- Buttons, input fields, and form elements.
-- Cards, containers, and navigation bars.
-- Common layout blocks you would find on a typical website.
-
-Drag any component from the library onto the canvas to use it. They are meant to be building blocks, so mix and match freely.
-
-## Sketching Tips
-
-You do not need to be an artist. The AI is good at interpreting rough layouts:
-
-- Draw **boxes with text labels** for each section (Header, Hero, Features, Footer).
-- Use **arrows** to show flow or relationships between elements.
-- Indicate approximate **sizing and placement** -- a tall box for a sidebar, a wide box for a hero banner.
-- Rough shapes and simple labels are enough. Pixel-perfect drawings are not necessary.
-
-## Attaching Your Drawing
-
-When you are happy with your sketch:
-
-1. Click **Attach drawing**.
-2. The canvas is exported as an image and added to your message.
-3. The AI uses your wireframe as a visual guide alongside any text you write.
-
-## Clearing the Canvas
-
-Click the **clear canvas** button to start fresh. A confirmation dialog appears before clearing to prevent accidental loss.
-
-Your work is retained while you close and reopen the canvas within the same session, so you can step away and come back to it. It is cleared once you attach the drawing, and it is not persisted across page reloads or navigating away from the site.
-
-## Getting the Best Results
-
-- **Combine a wireframe with a text description.** Tell the AI what each section should contain and how you want it styled. The wireframe handles layout; the text handles details.
-- **Label everything.** A box labeled "Testimonials" tells the AI much more than an unlabeled rectangle.
-- **Keep it simple.** A few well-placed shapes communicate layout faster than a detailed illustration.

package/templates/astro/src/components/ProjectOverview.astro

@@ -1,45 +0,0 @@
----
-import { getLabels } from 'fimo/astro';
-import { Text } from 'fimo/astro/components';
-
-import * as Project from '../schemas/Project';
-import * as SiteSettings from '../schemas/SiteSettings';
-
-interface Props {
-  locale: string;
-  localePrefix?: string;
-  rendering: 'static' | 'server';
-}
-
-const { locale, localePrefix, rendering } = Astro.props;
-const prefix = localePrefix ? `/${localePrefix}` : '';
-const localize = (path: string) => `${prefix}${path}`;
-const [settings, projects, labels] = await Promise.all([
-  SiteSettings.get({ locale }),
-  Project.list({ locale, limit: 12 }),
-  getLabels({ locale }),
-]);
----
-
-<main data-framework="astro" data-rendering={rendering} data-locale={locale} data-fimo-starter="projects">
-  <nav aria-label="Primary">
-    <a href={localize('/')}>Home</a>
-  </nav>
-  <header>
-    <Text as="h1" value={settings.studioName} />
-    <Text as="p" value={settings.intro} />
-    <a href={localize('/projects')}><Text as="span" value={labels.t('navigation.projects')} /></a>
-  </header>
-  <section>
-    <Text as="h2" value={labels.t('projects.heading')} />
-    {
-      projects.items.map((project) => (
-        <article data-project-slug={String(project.slug)}>
-          <Text as="h3" value={project.title} />
-          <Text as="p" value={project.summary} />
-          <a href={localize(`/projects/${String(project.slug)}`)}><Text as="span" value={project.title} /></a>
-        </article>
-      ))
-    }
-  </section>
-</main>

package/templates/astro/src/pages/[locale]/projects/[slug].astro

@@ -1,38 +0,0 @@
----
-import { getLabels } from 'fimo/astro';
-import { Text } from 'fimo/astro/components';
-import { resolveSeoForPath } from 'fimo/seo';
-
-import config from '../../../../.fimo/config.json';
-import Base from '../../../layouts/Base.astro';
-import { prefixedLocales } from '../../../locales';
-import * as Project from '../../../schemas/Project';
-
-export const prerender = false;
-
-const routeLocale = Astro.params.locale;
-const slug = Astro.params.slug ?? '';
-
-if (!routeLocale || !prefixedLocales.has(routeLocale)) {
-  return new Response(null, { status: 404, statusText: 'Not found' });
-}
-
-const locale = Astro.currentLocale ?? routeLocale;
-
-const [project, labels] = await Promise.all([Project.getBySlug(slug, { locale }), getLabels({ locale })]);
-
-if (!project) {
-  return Astro.redirect('/404');
-}
-const seo = resolveSeoForPath(Astro.url.pathname, config, { project });
----
-
-<Base lang={locale} seo={seo} title={seo?.title ?? String(project.title)}>
-  <main data-framework="astro" data-rendering="server" data-project-slug={slug}>
-    <a href={`/${locale}/projects`}><Text as="span" value={labels.t('navigation.projects')} /></a>
-    <article>
-      <Text as="h1" value={project.title} />
-      <Text as="p" value={project.summary} />
-    </article>
-  </main>
-</Base>

package/templates/astro/src/pages/[locale]/projects/index.astro

@@ -1,19 +0,0 @@
----
-import ProjectOverview from '../../../components/ProjectOverview.astro';
-import Base from '../../../layouts/Base.astro';
-import { prefixedLocales } from '../../../locales';
-
-export const prerender = false;
-
-const routeLocale = Astro.params.locale;
-
-if (!routeLocale || !prefixedLocales.has(routeLocale)) {
-  return new Response(null, { status: 404, statusText: 'Not found' });
-}
-
-const locale = Astro.currentLocale ?? routeLocale;
----
-
-<Base lang={locale} title="Projects">
-  <ProjectOverview {locale} localePrefix={locale} rendering="server" />
-</Base>