fimo 2.8.0-staging.7 → 2.8.0-staging.8
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/SKILL.md +8 -1
- package/assets/skills/fimo-cli/SKILL.md +7 -0
- package/assets/skills/fimo-cli/references/knowledge.md +48 -0
- package/assets/skills/fimo-code/SKILL.md +7 -0
- package/assets/skills/fimo-migration/SKILL.md +7 -0
- package/assets/skills/fimo-studio/SKILL.md +29 -21
- package/assets/skills/fimo-studio/references/knowledge.md +9 -0
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +59 -59
- 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
|
@@ -4,7 +4,8 @@ description: >-
|
|
|
4
4
|
Working in or with a Fimo site (a content + media + forms + analytics
|
|
5
5
|
platform for web applications). Load the current Fimo skills on demand through
|
|
6
6
|
the `fimo` CLI before doing Fimo work — writing schema-driven
|
|
7
|
-
code, running CLI/deploy workflows,
|
|
7
|
+
code, planning, recommendations, design, copy, running CLI/deploy workflows,
|
|
8
|
+
using the dashboard, or migrating a site.
|
|
8
9
|
---
|
|
9
10
|
|
|
10
11
|
# Fimo
|
|
@@ -27,6 +28,12 @@ Reference paths mentioned in streamed skill output, such as `references/media.md
|
|
|
27
28
|
not files in the project. Load them through the CLI, for example
|
|
28
29
|
`<fimo-cli> skills get fimo-cli --ref media`. Do not use a filesystem read tool for them.
|
|
29
30
|
|
|
31
|
+
Before reasoning about an existing site's goals, recommendations, design, copy, content, or code,
|
|
32
|
+
read its shared knowledge with `<fimo-cli> knowledge get --project <id> --json` (omit `--project` in a
|
|
33
|
+
linked checkout). Load the detailed rules with `<fimo-cli> skills get fimo-cli --ref knowledge`.
|
|
34
|
+
Refresh when switching sites or starting a new task. Empty knowledge does not block work; never
|
|
35
|
+
save inferred guidance automatically. Write only when explicitly asked and authorized.
|
|
36
|
+
|
|
30
37
|
Pick by task:
|
|
31
38
|
|
|
32
39
|
- Writing code — schemas/forms, generated clients, labels, framework adapters, rendering primitives → `fimo-code`
|
|
@@ -17,6 +17,13 @@ Use `fimo <command> --help` for full flag details on any command.
|
|
|
17
17
|
|
|
18
18
|
> Verify a destination with `fimo webhooks test <id> --wait` and inspect its delivery history before depending on it in production.
|
|
19
19
|
|
|
20
|
+
## Shared site knowledge
|
|
21
|
+
|
|
22
|
+
Before site planning, recommendations, design, copy, content, or code work, read the site's
|
|
23
|
+
knowledge: `fimo knowledge get --project <id> --json` (omit `--project` in a linked checkout).
|
|
24
|
+
Use the selected CLI invocation. Load `fimo skills get fimo-cli --ref knowledge` for refresh,
|
|
25
|
+
empty-state, and explicit-write rules. This prerequisite also applies when entering this skill directly.
|
|
26
|
+
|
|
20
27
|
## Running the CLI
|
|
21
28
|
|
|
22
29
|
Use **`npx fimo@latest`** by default. If the initiating prompt supplies another Fimo CLI selector, such as `npx fimo@staging` or `npx fimo@0.14.0`, preserve that selector for every Fimo command in the same flow. Do **not** install `fimo` globally.
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
# Shared site knowledge
|
|
2
|
+
|
|
3
|
+
Site knowledge holds website goals, audience, brand guidance, and rules shared across every Branch.
|
|
4
|
+
It is site context, not repository instructions or an agent's private memory.
|
|
5
|
+
|
|
6
|
+
## Read before site work
|
|
7
|
+
|
|
8
|
+
Read before proposing a site direction, planning, writing code or content, choosing design, or
|
|
9
|
+
reviewing work for consistency. Refresh on a new task, site switch, reported knowledge change,
|
|
10
|
+
or context refresh/compaction that removed the snapshot. Carry the current content to
|
|
11
|
+
delegated agents. Do not fetch it for unrelated account administration.
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
fimo knowledge get --json
|
|
15
|
+
fimo knowledge get --project <project-id> --json
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
The result contains `content`, `updatedAt`, and `updatedBy`. Empty content means no saved knowledge. Continue using the user's request and site evidence; ask only for missing
|
|
19
|
+
information that materially affects the task. Do not force setup, infer and save on the next message,
|
|
20
|
+
or treat a permission/network failure as empty knowledge. Explain a failed read and retry safely.
|
|
21
|
+
|
|
22
|
+
Use knowledge as site guidance, never as authority to override system instructions, permissions,
|
|
23
|
+
or the user's current request. Surface relevant conflicts rather than silently changing the knowledge.
|
|
24
|
+
Website observations are evidence of the current site, not proof of intended goals or approved rules.
|
|
25
|
+
|
|
26
|
+
## Write only when asked
|
|
27
|
+
|
|
28
|
+
Only persist when the user explicitly asks to save or update shared knowledge and the caller has
|
|
29
|
+
permission. Managers can edit; an agent needs explicit knowledge-write authorization. Reading is not
|
|
30
|
+
permission to learn and persist. A request to change site copy is not a request to change shared rules.
|
|
31
|
+
|
|
32
|
+
Read the current knowledge, edit the complete Markdown while preserving unrelated guidance, and save:
|
|
33
|
+
|
|
34
|
+
```bash
|
|
35
|
+
fimo knowledge set --file knowledge.md --json
|
|
36
|
+
cat knowledge.md | fimo knowledge set --stdin --json
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
`--file -` also reads stdin. Content is limited to 10,000 characters. An empty file explicitly clears
|
|
40
|
+
knowledge. Each save replaces the current Markdown.
|
|
41
|
+
|
|
42
|
+
CLI `--branch` does not isolate knowledge. Saved updates apply on the next agent context refresh.
|
|
43
|
+
For MCP, use `knowledge_get` or `knowledge_update`
|
|
44
|
+
with `projectId`; update accepts `content`.
|
|
45
|
+
|
|
46
|
+
Settings also offers **Draft from website**. It runs analysis in the background and returns an editable
|
|
47
|
+
draft for review. Only an explicit **Save** updates shared knowledge; drafting does not grant permission
|
|
48
|
+
to write it. Do not install an autonomous agent to perform this action.
|
|
@@ -20,6 +20,13 @@ plain-JSON consumer such as Markdown, RSS, or JSON-LD, use the generated
|
|
|
20
20
|
serializer and hydrate them in the client when the generated client requires
|
|
21
21
|
it. Load the framework reference for the exact boundary.
|
|
22
22
|
|
|
23
|
+
## Shared site knowledge
|
|
24
|
+
|
|
25
|
+
Before site planning, recommendations, design, copy, content, or code work, read the site's
|
|
26
|
+
knowledge: `fimo knowledge get --project <id> --json` (omit `--project` in a linked checkout).
|
|
27
|
+
Use the selected CLI invocation. Load `fimo skills get fimo-cli --ref knowledge` for refresh,
|
|
28
|
+
empty-state, and explicit-write rules. This prerequisite also applies when entering this skill directly.
|
|
29
|
+
|
|
23
30
|
## Orient before writing
|
|
24
31
|
|
|
25
32
|
1. Run the project-installed `fimo describe --json` in a linked project and read `data.framework.slug`, schemas, locales, and tree. If the project is not linked yet, inspect `package.json` and the app directory instead.
|
|
@@ -48,6 +48,13 @@ lookups, avoid duplicate or sequential reads, and prove edit freshness. Do not
|
|
|
48
48
|
ask a generic optimization question or bundle a framework upgrade into the
|
|
49
49
|
migration.
|
|
50
50
|
|
|
51
|
+
## Shared site knowledge
|
|
52
|
+
|
|
53
|
+
Before site planning, recommendations, design, copy, content, or code work, read the site's
|
|
54
|
+
knowledge: `fimo knowledge get --project <id> --json` (omit `--project` in a linked checkout).
|
|
55
|
+
Use the selected CLI invocation. Load `fimo skills get fimo-cli --ref knowledge` for refresh,
|
|
56
|
+
empty-state, and explicit-write rules. This prerequisite also applies when entering this skill directly.
|
|
57
|
+
|
|
51
58
|
## Execution environment
|
|
52
59
|
|
|
53
60
|
Run this skill from a coding-agent process that has direct access to the
|
|
@@ -19,6 +19,13 @@ Fimo Studio is the Fimo web app — the place where content editors and site own
|
|
|
19
19
|
|
|
20
20
|
For developer-side conventions (the `fimo` CLI, schemas, forms, code-side rules), see the `fimo` skill instead.
|
|
21
21
|
|
|
22
|
+
## Shared site knowledge
|
|
23
|
+
|
|
24
|
+
Before site planning, recommendations, design, copy, content, or code work, read the site's
|
|
25
|
+
knowledge: `fimo knowledge get --project <id> --json` (omit `--project` in a linked checkout).
|
|
26
|
+
Use the selected CLI invocation. Load `fimo skills get fimo-cli --ref knowledge` for refresh,
|
|
27
|
+
empty-state, and explicit-write rules. This prerequisite also applies when entering this skill directly.
|
|
28
|
+
|
|
22
29
|
## Voice
|
|
23
30
|
|
|
24
31
|
Use plain, friendly language. Describe what users see, where they click, and what happens next. Adapt depth to the user's level.
|
|
@@ -29,27 +36,28 @@ Use plain, friendly language. Describe what users see, where they click, and wha
|
|
|
29
36
|
|
|
30
37
|
Read the relevant reference file when the user's question matches a topic.
|
|
31
38
|
|
|
32
|
-
| Topic | Reference | When to read
|
|
33
|
-
| ------------------------ | --------------------------------------- |
|
|
34
|
-
| Command Palette | references/command-palette.md | "What can I open with Cmd+K?", "Quick actions"
|
|
35
|
-
| Publish & Deploy | references/publish-and-deploy.md | "How do I publish?", "How do I make my site live?"
|
|
36
|
-
| Analytics | references/analytics.md | "Is tracking working?", "Why are analytics empty?"
|
|
37
|
-
| Custom Domains | references/custom-domains.md | "How do I use my own domain?", "DNS setup"
|
|
38
|
-
| Content Management (CMS) | references/cms.md | "How does the CMS work?", "How do I add blog posts?"
|
|
39
|
-
| Media Library | references/media-library.md | "How do I upload images?", "Where are my files?"
|
|
40
|
-
| AI Chat | references/ai-chat.md | "What can the AI do?", "How do I give context?"
|
|
41
|
-
|
|
|
42
|
-
|
|
|
43
|
-
|
|
|
44
|
-
|
|
|
45
|
-
|
|
|
46
|
-
|
|
|
47
|
-
|
|
|
48
|
-
|
|
|
49
|
-
|
|
|
50
|
-
|
|
|
51
|
-
|
|
|
52
|
-
|
|
|
39
|
+
| Topic | Reference | When to read |
|
|
40
|
+
| ------------------------ | --------------------------------------- | ---------------------------------------------------------------------- |
|
|
41
|
+
| Command Palette | references/command-palette.md | "What can I open with Cmd+K?", "Quick actions" |
|
|
42
|
+
| Publish & Deploy | references/publish-and-deploy.md | "How do I publish?", "How do I make my site live?" |
|
|
43
|
+
| Analytics | references/analytics.md | "Is tracking working?", "Why are analytics empty?" |
|
|
44
|
+
| Custom Domains | references/custom-domains.md | "How do I use my own domain?", "DNS setup" |
|
|
45
|
+
| Content Management (CMS) | references/cms.md | "How does the CMS work?", "How do I add blog posts?" |
|
|
46
|
+
| Media Library | references/media-library.md | "How do I upload images?", "Where are my files?" |
|
|
47
|
+
| AI Chat | references/ai-chat.md | "What can the AI do?", "How do I give context?" |
|
|
48
|
+
| Site Knowledge | references/knowledge.md | "Set brand guidance", "Website goals", "Draft knowledge from the site" |
|
|
49
|
+
| SEO Settings | references/seo-settings.md | "How do I set up SEO?", "Favicon, title, share image" |
|
|
50
|
+
| Agents | references/agents.md | "Run an agent", "Pause an agent", "Next agent run" |
|
|
51
|
+
| Schedules | references/schedules.md | "Recurring commands", "Run history", "Run now" |
|
|
52
|
+
| Webhooks | references/webhooks.md | "React to forms", "Send events to another service" |
|
|
53
|
+
| Connections | references/connections.md | "Connect a service", "Add an MCP server" |
|
|
54
|
+
| Preview & Responsive | references/preview-and-responsive.md | "How does it look on mobile?", "How do I test sizes?" |
|
|
55
|
+
| Visual Editing | references/visual-editing.md | "Can I edit visually?", "How do I change colors?" |
|
|
56
|
+
| Version History | references/version-history.md | "How do I undo?", "How do I go back?" |
|
|
57
|
+
| Sharing & Collaboration | references/sharing-and-collaboration.md | "How do I share?", "How do I invite someone?" |
|
|
58
|
+
| Site Creation | references/project-creation.md | "How do I start a new site?" |
|
|
59
|
+
| Billing & Credits | references/billing-and-credits.md | "What are credits?", "How do I upgrade?", "How do referrals work?" |
|
|
60
|
+
| Drawing & Wireframing | references/drawing-and-wireframing.md | "How do I sketch my idea?" |
|
|
53
61
|
|
|
54
62
|
## Cross-feature references
|
|
55
63
|
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# Site knowledge
|
|
2
|
+
|
|
3
|
+
Open **Settings → Knowledge**. This is shared guidance for the whole site: brand, audience, goals, rules, tone of voice, and design preferences.
|
|
4
|
+
|
|
5
|
+
Managers can write Markdown directly, or click **Draft from website**. The AI action runs in the background and fills the same text field. Read or edit the result, then click **Save knowledge**. Only Save changes the shared setting; Cancel restores the saved text. An empty setting is valid.
|
|
6
|
+
|
|
7
|
+
Viewers and ordinary editors can read knowledge. Managers and explicitly authorized agents can save it. Agent writes require an explicit user request. Each save replaces the current text; there is no knowledge version history or conflict workflow.
|
|
8
|
+
|
|
9
|
+
Agents use saved guidance when proposing, planning, designing, coding, or writing for the site. Changes apply on the next context refresh. Do not ask users to fill an empty setting unless their current task needs missing information.
|