fimo 2.10.1-staging.1 → 2.10.1-staging.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/fimo-cli/SKILL.md +57 -139
- package/assets/skills/fimo-cli/SKILL.studio.md +42 -0
- package/assets/skills/fimo-cli/references/branches.md +43 -106
- package/assets/skills/fimo-cli/references/content/bulk.md +48 -0
- package/assets/skills/fimo-cli/references/content/entries.md +54 -0
- package/assets/skills/fimo-cli/references/content/localized.md +56 -0
- package/assets/skills/fimo-cli/references/content/schemas.md +29 -0
- package/assets/skills/fimo-cli/references/content/sql.md +57 -0
- package/assets/skills/fimo-cli/references/content.md +33 -272
- package/assets/skills/fimo-cli/references/deploy.md +35 -126
- package/assets/skills/fimo-cli/references/domains.md +38 -131
- package/assets/skills/fimo-cli/references/forms.md +1 -1
- package/assets/skills/fimo-cli/references/init.md +36 -170
- package/assets/skills/fimo-cli/references/locales.md +2 -2
- package/assets/skills/fimo-cli/references/projects.md +1 -1
- package/assets/skills/fimo-code/references/design.md +42 -126
- package/assets/skills/fimo-migration/SKILL.md +114 -408
- package/assets/skills/fimo-migration/references/content-delivery.md +67 -0
- package/assets/skills/fimo-migration/references/frameworks/nextjs.md +1 -1
- package/assets/skills/fimo-migration/references/qa/browser.md +41 -0
- package/assets/skills/fimo-migration/references/qa/guardrails.md +95 -0
- package/assets/skills/fimo-migration/references/qa/results.md +78 -0
- package/assets/skills/fimo-migration/references/qa.md +102 -383
- package/assets/skills/fimo-migration/references/questions-and-improvements.md +77 -168
- package/assets/skills/fimo-migration/references/setup.md +90 -0
- package/assets/skills/fimo-migration/references/workers/validator.md +2 -2
- package/assets/skills/fimo-migration/references/workers.md +1 -1
- package/assets/skills/fimo-migration/references/workflow.md +117 -171
- package/assets/skills/fimo-studio/SKILL.md +12 -11
- package/assets/skills/fimo-studio/references/ai-chat/agents.md +46 -0
- package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +57 -0
- package/assets/skills/fimo-studio/references/ai-chat/routines.md +53 -0
- package/assets/skills/fimo-studio/references/ai-chat.md +39 -76
- package/assets/skills/fimo-studio/references/custom-domains.md +2 -2
- package/assets/skills/fimo-studio/references/publish-and-deploy.md +1 -1
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +38 -17
- package/package.json +8 -8
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -1,98 +1,61 @@
|
|
|
1
|
-
|
|
1
|
+
# AI chat
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
How people work with chat in Studio. For agents (plans, **New agent**, the default agents), read `ai-chat/agents`; for what each default routine does, `ai-chat/default-agents`; for routines (triggers, runs, reports, agent-hours), `ai-chat/routines`.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Chat can write and edit code, create pages, manage CMS content, generate images, install packages, search the web and fix bugs.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
## Where to find it
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
Open **Chats** in the site header. On a phone, the **Chat** tab opens the chat list first; select a chat to open it.
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
## Several chats
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
- A site has many chats, shared by everyone on the site. The list shows **Agents** above and **Chats** below, the most recently active first. A row shows what the chat does while it works, then the start of its last message. The **Chats** tab shows how many chats have new activity.
|
|
14
|
+
- One orange dot marks unread activity, a question that waits for you, or both. Hover over it for the reason. Opening the chat clears unread activity for you only; the dot stays while a question still waits for an answer.
|
|
15
|
+
- **+** then **New chat** starts a blank chat. It joins the list, for everyone, when its first message is sent, and takes its name from that message. An empty chat offers starter requests.
|
|
16
|
+
- The search icon finds a chat by name or last message. The filter icon shows only **Working** or **Done** chats, or with **Kind** only chats or only agents. The list settings change the order and show read, unread or archived chats.
|
|
17
|
+
- For you only (the buttons above the open chat, or right-click a row): **Mark as unread**, **Pin**, **Archive** (turn on **Show archived** to see it again), **Mute**.
|
|
18
|
+
- To rename a chat for everyone, double-click its name above the open chat, or right-click its row and select **Rename**. Enter saves; Escape keeps the old name.
|
|
19
|
+
- The settings icon above the open chat changes its portrait (shape, eyes, mouth, color), renames it, holds the same pin, mute and archive switches, and deletes it. **Deleting stops a running reply and removes the chat for everyone.**
|
|
20
|
+
- Each chat has its own messages and context. When you refer to an earlier discussion, chat searches this site's chats and answers from the messages it found.
|
|
21
|
+
- The open chat is in the page address (`/chats?chat=<id>`), so a link or a reload opens the same chat.
|
|
14
22
|
|
|
15
|
-
|
|
23
|
+
## Send a message
|
|
16
24
|
|
|
17
|
-
|
|
25
|
+
1. Type in the message box at the bottom; its placeholder follows the workspace you are in. Be specific: "Add a hero with a dark green background and the heading Fresh beans weekly" works better than "make it look nice".
|
|
26
|
+
2. Press **Enter** or select the send button.
|
|
27
|
+
3. The reply streams. Progress lines name each task chat works on, and the preview updates.
|
|
18
28
|
|
|
19
|
-
|
|
29
|
+
While a reply runs, the send button becomes **Stop** (a square). Select it when the reply goes the wrong way. Messages sent during a reply wait at the end of the chat as **Queued** and run in order, one reply each.
|
|
20
30
|
|
|
21
|
-
|
|
31
|
+
## Answer a question
|
|
22
32
|
|
|
23
|
-
|
|
33
|
+
A reply can hold choices, cards, tables, images and actions. Optional suggestions do not stop the conversation.
|
|
24
34
|
|
|
25
|
-
|
|
35
|
+
When chat needs an answer to continue, it opens a form under the message that asks, and waits. Move with **Previous**, **Next** and **Submit**; a step with choices has an optional note field.
|
|
26
36
|
|
|
27
|
-
|
|
37
|
+
- **Submit** sends only the form. Text in the message box stays unsent.
|
|
38
|
+
- Sending from the message box sends your message with the choices already made. With no choices, it is an ordinary message and the question stays open.
|
|
39
|
+
- If you send a message that does not answer it, the question folds to one line with an orange **?** where it was asked. Select it to open it and answer, at any time. The answer is sent as a new message at the end of the chat, and an answered question shows a gray check.
|
|
40
|
+
- **Minimize** folds the form to one line and keeps your answers; select the line to open it again.
|
|
41
|
+
- When a routine asks again before anyone answered, its earlier question stays unanswered, folded where it was asked.
|
|
28
42
|
|
|
29
|
-
##
|
|
43
|
+
## Attach context
|
|
30
44
|
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
3. Press **Enter** or click the **send button**.
|
|
34
|
-
4. The AI responds in a stream. You see tool status badges appear as it works, and the preview updates automatically.
|
|
45
|
+
- **+** in the message box: **Attach assets** (media library), **Attach entries** (CMS content), **Upload from computer**. For GLB, self-contained glTF, FBX, OBJ, STL and PLY models, Fimo renders four views and saves a description, so every chat model can understand the model. ZIP archives up to 20 MiB are supported; chat can open them under `/tmp` in its sandbox, and the original stays attached to the conversation.
|
|
46
|
+
- Type **@** to refer to files, pages or content.
|
|
35
47
|
|
|
36
|
-
##
|
|
48
|
+
## Edit, regenerate, stop
|
|
37
49
|
|
|
38
|
-
|
|
50
|
+
Hover over a message. Your messages have **Copy** and **Edit** (change and resend; chat replies again); a form answer has no **Edit**. AI messages have **Copy** and **More**; the last AI message also has **Regenerate** (try again with the same request) when no reply is running.
|
|
39
51
|
|
|
40
|
-
|
|
52
|
+
## Proposals, reviews and merges
|
|
41
53
|
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
- **+ button**: Opens a dropdown with options:
|
|
47
|
-
- **Attach Assets** -- browse your media library and attach files.
|
|
48
|
-
- **Attach Entries** -- attach CMS content for the AI to reference.
|
|
49
|
-
- **Upload from Computer** -- upload a file directly. For GLB, self-contained glTF, FBX, OBJ, STL, and PLY models, Fimo renders four views and saves a description so every chat model can understand the attachment. ZIP archives are supported up to 20 MiB; the AI can download and inspect them under `/tmp` in its sandbox while the original stays attached to the conversation.
|
|
50
|
-
- **@ mentions**: Type **@** in the chat to reference specific files, pages, or content inline.
|
|
51
|
-
|
|
52
|
-
## Editing and Regenerating
|
|
53
|
-
|
|
54
|
-
Hover over a message to see its action icons. The icons differ by who sent the message:
|
|
55
|
-
|
|
56
|
-
- On **your own messages**: a **Copy icon** and an **Edit icon**. Editing lets you change your message and resend it; the AI generates a new response based on your updated request.
|
|
57
|
-
- On **AI messages**: a **Copy icon**, a **Regenerate icon** (ask the AI to try a different approach without changing your original message), and a **More menu** for additional actions.
|
|
58
|
-
|
|
59
|
-
To halt the AI mid-generation, use the **Stop button** in the input bar — while the AI is generating, the send button turns into a Stop (square) button. Click it to stop if the response is going in the wrong direction.
|
|
60
|
-
|
|
61
|
-
## Understanding Tool Badges
|
|
62
|
-
|
|
63
|
-
While the AI works, you see small badges in the chat showing what it is doing. Each badge displays a tool name and its current status. Examples include reading files, writing code, searching your site, or generating images. These badges help you follow along without needing to understand the technical details.
|
|
64
|
-
|
|
65
|
-
## Reviewing Proposals
|
|
66
|
-
|
|
67
|
-
Ask the AI to keep alternatives as named proposals. Open the Branch picker and choose one from **Proposals** to preview its work. Each proposal has its own changes. The picker follows visibility: internal work stays hidden even when saved, durable, or given more time. Extending retention does not show the work.
|
|
68
|
-
|
|
69
|
-
A review request saves the selected session's current work and makes that same session visible and durable. Follow its review card to the proposal, or its Preview and Changes links from chat, Slack, or an agent report. These links open the current Branch in Studio and require site access. A review request refers to saved work: if that work changes, request a new review before merging. Exploring or merging proposal B keeps A, C, and D available unless you ask to discard them. Merging does not publish the site.
|
|
70
|
-
|
|
71
|
-
Delete a proposal from the Branch picker when you no longer need it. Pull is unavailable for proposals; ask the AI to update the proposal instead. New Branch defaults to the proposal's upstream. Merge the proposal first if you want to create a Branch from its changes.
|
|
72
|
-
|
|
73
|
-
## Reviewing Changes That Could Not Merge
|
|
74
|
-
|
|
75
|
-
Chat changes are prepared separately and then applied to the environment you are viewing. Most changes merge automatically.
|
|
76
|
-
|
|
77
|
-
If the site changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input.
|
|
78
|
-
|
|
79
|
-
Choose **Auto fix** or keep chatting to let Fimo continue in the retained proposal, resolve the conflict, and retry the merge. Choose **Review manually** to inspect and resolve the proposal yourself. Discarding leaves the current environment unchanged and permanently removes the proposal.
|
|
80
|
-
|
|
81
|
-
## Tips for Better Results
|
|
82
|
-
|
|
83
|
-
- **Be specific**: Mention colors, layout, text content, and spacing when you can.
|
|
84
|
-
- **Reference existing elements**: Say "Change the navbar background" instead of "Change the top thing."
|
|
85
|
-
- **Use visual details**: Describe what you want to see, not just what you want it to do.
|
|
86
|
-
- **The AI can do a lot**: Write and edit code, create new pages, manage CMS content, generate images, install packages, search the web, and fix bugs.
|
|
54
|
+
- Ask chat to keep alternatives as named proposals. Open the Branch picker and choose one under **Proposals** to preview it; each has its own changes. Internal work stays hidden there, even when saved or kept longer. Exploring or merging one keeps the others unless you ask to discard them. Delete a proposal from the Branch picker. Pull is not available for a proposal: ask chat to update it. **New Branch** starts from the proposal's upstream; merge the proposal first to branch from its changes.
|
|
55
|
+
- A review request saves the session's current work and makes that same session visible and durable. Work waiting for review shows in a strip above the message box (**View changes**, **Open preview**), and the conversation keeps a line with **View changes** where it was saved. Opening a review approves nothing. The Preview and Changes links, also in Slack or an agent report, open the Branch in Studio and need site access. If the work changes, request a new review before merging.
|
|
56
|
+
- Chat prepares changes separately and merges them into the environment you view; most merge automatically. If the site changed in the same place, a banner above the message box (**Your last changes need attention**) offers **Auto fix** (chat continues in the retained proposal, resolves the conflict and retries the merge; keep chatting has the same effect) and **Review manually**. Discarding leaves the environment unchanged and removes the proposal for good.
|
|
57
|
+
- **Merging does not publish the site.**
|
|
87
58
|
|
|
88
59
|
## Credits
|
|
89
60
|
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
Clicking it opens a breakdown showing:
|
|
93
|
-
|
|
94
|
-
- **Monthly credits** included with your plan.
|
|
95
|
-
- **Purchased credits** you bought separately.
|
|
96
|
-
- **Earned credits** from referrals or promotions.
|
|
97
|
-
|
|
98
|
-
You get a warning when credits are running low. To keep going, upgrade your plan or buy more credits from the billing page.
|
|
61
|
+
Chat uses AI credits. For people who can view billing, the coin icon near the send button shows the balance; select it for **Monthly credits**, **Purchased credits**, **Earned credits** (referrals and promotions) and, when present, **Daily free credits**. A warning shows when credits run low. To continue, upgrade the plan or buy credits on the billing page (`billing-and-credits`).
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
## Also available via CLI
|
|
2
2
|
|
|
3
|
-
If you're driving Fimo from the terminal, the equivalent commands are `fimo domains add`, `fimo domains refresh`, and `fimo domains remove`. The default URL (the `<slug>.fimo.site` subdomain) is managed with `fimo domains rename-default` and `fimo domains suggest-default` — both free
|
|
3
|
+
If you're driving Fimo from the terminal, the equivalent commands are `fimo domains add`, `fimo domains refresh`, and `fimo domains remove`. The default URL (the `<slug>.fimo.site` subdomain) is managed with `fimo domains rename-default` and `fimo domains suggest-default` — both free on every plan. See the `fimo-cli` skill's `references/domains.md`. Full docs: https://fimo.ai/docs/deploy/custom-domains.
|
|
4
4
|
|
|
5
5
|
## Before You Start
|
|
6
6
|
|
|
7
|
-
- You need
|
|
7
|
+
- You need the **Starter plan or higher**. Without it, the Domains option shows an "Upgrade" label.
|
|
8
8
|
- Your site must be **published at least once**. An alert appears if it has not been published yet.
|
|
9
9
|
- You need access to your **domain registrar** (GoDaddy, Namecheap, Cloudflare, etc.).
|
|
10
10
|
- Both **subdomains** (e.g., `blog.example.com`) and **apex/root domains** (e.g., `example.com`) are supported. A subdomain uses a single CNAME record; an apex domain uses two A records, with an optional automatic redirect to its `www` subdomain. The redirect direction can be reversed later without changing DNS.
|
|
@@ -37,7 +37,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
|
|
|
37
37
|
|
|
38
38
|
- **Saving vs. publishing**: Edits save automatically as you work (like a draft). Publishing sends those changes to your live site. Visitors only see published changes.
|
|
39
39
|
- **SEO before publishing**: Go to Settings > SEO to set your page title, description, and share image before going live. After changing SEO settings, a reminder asks you to publish to apply the changes.
|
|
40
|
-
- **Custom domains**:
|
|
40
|
+
- **Custom domains**: On the Starter plan or higher, set up a custom domain in Settings > Domains. Your domain works once your site is published.
|
|
41
41
|
- **Unpublishing**: To take your site offline, go to Settings > General and click Unpublish. A confirmation dialog appears before proceeding.
|
|
42
42
|
|
|
43
43
|
## Troubleshooting
|