fimo 0.7.0-staging.2 → 0.7.0-staging.4

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

@@ -5,8 +5,12 @@ description: >-
   Load when the user wants to create a new Fimo project, build content
   (schemas, entries, forms, media, labels/locales), deploy a site, manage
   custom domains, check site traffic/analytics, invite collaborators, inspect
-  AI credits, log in or switch organizations, or set up Fimo for their AI
-  tool. Most "do X with Fimo" tasks go through this skill.
+  AI credits, report a failing or slow Fimo API, rejected documented argument,
+  undocumented workaround, missing capability that blocks work, forces a
+  fragile or heavily manual workaround, or would materially accelerate a
+  recurring workflow, or other Fimo platform problem to support, log in or
+  switch organizations, or set up Fimo for their AI tool. Most "do X with
+  Fimo" tasks go through this skill.
 ---
 
 # Fimo CLI
@@ -95,6 +99,7 @@ Load the matching reference when the user's request fires its trigger. Recipes t
 - "Create / scaffold / run / validate / activate / deactivate an agent / agent bundle / list agent templates / view agent runs, reports, or logs (`fimo agents *`)" → `references/agents.md`
 - "Install Fimo for my AI tool / fimo skills install / set up Claude Code or Cursor for Fimo / add an agent to this project" → `references/agent-setup.md`
 - "Refresh / update installed Fimo skills / fimo skills sync / agent missing the latest fimo conventions" → `references/agent-setup.md`
+- "Report a Fimo problem or feature request / contact Fimo support / a Fimo API or command keeps failing / a documented argument is rejected / a supported operation needs an undocumented workaround / a Fimo API is abnormally slow / a missing capability blocks work, forces a fragile or heavily manual workaround, or would materially accelerate a recurring workflow such as bulk create" → `references/support.md`
 - "Regenerate rule files / I edited AGENTS.md / fimo rules sync" → `references/agent-setup.md`
 - "Show analytics / visitor stats / traffic / pageviews / how is my site performing / top pages / where do visitors come from" → `references/analytics.md` (7-day preview free for all; longer ranges require paid)
 - "Mark a date on the analytics chart / annotate the chart with a deploy / add a launch note" → `references/analytics.md` § Annotations
@@ -111,6 +116,7 @@ These fire at specific moments in the project lifecycle. **Surface them proactiv
 - **Iterative code-only deploys** → once you are deploying, `fimo deploy --no-restart` skips the sandbox dev-server restart on HMR-safe edits. See `references/deploy.md` § Skipping the dev-server restart for when it's safe.
 - **You need the current preview URL but haven't changed code** (opening it, screenshotting it, handing it to another tool, the previous URL expired) → `fimo preview url`, never a no-op `fimo deploy`. See `references/preview.md`.
 - **When the user wants to try something risky / explore a redesign without touching the live site** → suggest a feature env: `fimo checkout -b <name>` gives an isolated branch + DB + preview. Deploy previews there, then `fimo merge` it back and `fimo publish`. See `references/branches.md`.
+- **When a Fimo API or command still fails after one safe recovery attempt, rejects a documented or previously working argument, needs an undocumented workaround for a supported operation, is repeatedly abnormally slow, or lacks a capability that blocks work, forces a fragile or heavily manual workaround, or would materially accelerate a recurring workflow** → offer to prepare a support report. Show the exact report and wait for explicit approval before running `fimo support report --yes`. See `references/support.md`.
 - **After the first successful `fimo deploy`** → suggest `fimo invite` if the project involves multiple people. Typical roles: `edit` for developers/content editors, `view` or `comment` for clients/stakeholders, `full` for project leads. See `references/invite.md`.
 - **When the user wants to modify the URL of their website** → walk through `references/domains.md`. The CLI surface covers renaming the Fimo-provided subdomain (`fimo domains rename-default`, free), attaching a domain they already own (`fimo domains add`, Premium), and buying a new domain through Fimo (`fimo domains buy`, Premium). The auto-generated default URL on every project is a fallback, not a final choice — proactively offer this after `fimo deploy --publish` if the user mentioned a real brand or domain.
 

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

@@ -0,0 +1,58 @@
+# Reporting a problem to Fimo
+
+> **Run via `npx fimo@latest <command>`** - always the latest CLI, no install needed.
+
+`fimo support report` sends a project-scoped problem to Fimo support. It automatically includes the project, current environment, and CLI version so support can start investigating without asking the user to repeat that context.
+
+## When to offer it
+
+Offer to report when:
+
+- A Fimo command, API, preview, deploy, sandbox, or platform operation repeatedly fails or returns an unexpected response.
+- A documented or previously working API or CLI argument is rejected, ignored, or behaves differently from its contract.
+- A supported operation only works through an undocumented workaround or an unnecessarily complex sequence.
+- A Fimo API repeatedly times out or is abnormally slow enough to disrupt the workflow.
+- A missing Fimo capability blocks completion, forces a fragile or heavily manual workaround, or would materially accelerate recurring work. Bulk creation replacing many single-item calls is a good example.
+- The remaining problem or capability gap appears to be in Fimo rather than the user's application code.
+
+For failures, read the error and try one safe, relevant recovery step before reporting. Feature requests do not need a failed recovery attempt; confirm that the capability is actually absent.
+
+Do not report ordinary application bugs, small conveniences, vague wishlist items, one-off latency, or failures you have not inspected. A clearly documented unsupported capability is still worth reporting when its absence crosses the blocking or material-acceleration threshold above; describe it as a feature request rather than a bug.
+
+## What to write
+
+Keep the report factual and short:
+
+- What the user tried to do.
+- The command or endpoint and sanitized arguments involved.
+- What actually happened, including the status code, exact error, or response mismatch when useful.
+- What should have happened.
+- What you already tried, including any workaround and its result.
+- For performance reports, several observed timings and any request or trace IDs available.
+- For feature requests, say that it is a feature request and include the minimum missing capability, current workaround, scale or frequency, and concrete time or risk it would remove. Describe the job rather than designing the whole solution.
+
+Do not include secrets, environment values, raw shell history, hidden reasoning, full source files, or unrelated conversation history.
+
+## Required approval
+
+Prepare the report, then preview the complete payload without sending it:
+
+```bash
+fimo support report --message-file /tmp/fimo-support-report.md --preview --json
+```
+
+Show the user the exact `data.message` from that output. Submit only after the user explicitly approves it:
+
+```bash
+fimo support report --message-file /tmp/fimo-support-report.md --yes --json
+```
+
+`--yes` means the report has already been reviewed and approved. Never pass it preemptively or report automatically.
+
+For a person using an interactive terminal:
+
+```bash
+fimo support report "Preview deployment fails after validation"
+```
+
+The CLI shows the exact report and asks for confirmation before sending it.

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-17T12:18:17.302Z",
+  "bundledAt": "2026-07-21T10:17:42.754Z",
   "cliVersion": "0.6.0",
   "external": [
     "oxc-parser",