@seeed-studio/sensecraft-cli 0.4.0 → 0.4.2
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/package.json +1 -1
- package/skills/README.md +5 -1
- package/skills/sensecraft-cli/SKILL.md +13 -10
- package/skills/sensecraft-cli/create-app/SKILL.md +90 -83
- package/skills/sensecraft-cli/create-app/assets/manifest-template.json +5 -18
- package/skills/sensecraft-cli/create-app/assets/validate_manifest.py +221 -54
- package/skills/sensecraft-cli/create-app/references/content-review.md +55 -0
- package/skills/sensecraft-cli/create-app/references/manifest.md +112 -53
- package/skills/sensecraft-cli/create-app/references/project-discovery.md +56 -0
- package/skills/sensecraft-cli/references/app-commands.md +6 -2
- package/skills/sensecraft-cli/references/app-fields.md +36 -0
- package/skills/sensecraft-cli/references/apps.md +4 -2
- package/skills/sensecraft-cli/references/data-commands.md +35 -13
- package/skills/sensecraft-cli/references/data.md +2 -4
- package/skills/sensecraft-cli/references/model-commands.md +1 -2
- package/skills/sensecraft-cli/references/models.md +1 -1
- package/skills/sensecraft-cli/references/recamera-commands.md +3 -1
- package/skills/sensecraft-cli/references/recamera.md +1 -1
- package/skills/sensecraft-cli/references/tool-blocks.md +7 -1
|
@@ -2,6 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
Help the Agent choose the right block and fill `config` safely. Execution on hardware is **L3** unless noted.
|
|
4
4
|
|
|
5
|
+
## Plan before writing blocks
|
|
6
|
+
|
|
7
|
+
Read this entire reference before drafting a deployment plan or tool config. Inspect `sensecraft-cli app blocks` as the static catalog, then map the real project journey to supported actions. For each action identify prerequisites, the suitable tool, actual artifact/config sources, and the observable result. Select only tools the project needs, and place each immediately after its instructions in the flat array.
|
|
8
|
+
|
|
9
|
+
Check the exact hardware variant, artifact target/architecture, deployment inputs, and device rules below. A local file awaiting upload is a planned upload; a missing artifact or unknown target is an unresolved deployment gap. Preserve a needed tool in the local draft while resolving its inputs. Do not substitute a prose-only instruction that makes an unsupported action appear executable. Report such gaps and agree on a supported path or an explicitly incomplete draft. A format-valid block is not evidence that deployment will work.
|
|
10
|
+
|
|
5
11
|
## Content format
|
|
6
12
|
|
|
7
13
|
The editor does **not** render Markdown on read. Preview wraps each block by `type` and treats `content` as HTML or plain text. Raw `**bold**`, `# heading`, or `- item` inside `content` shows up as those characters.
|
|
@@ -56,7 +62,7 @@ Write these as **flat fields** on the block. The editor wraps them into `config`
|
|
|
56
62
|
|
|
57
63
|
| Field | How to write |
|
|
58
64
|
|-------|----------------|
|
|
59
|
-
| `device_id` | Material SKU string, e.g. `"100017057"`. Not a production type
|
|
65
|
+
| `device_id` | Material SKU string, e.g. `"100017057"`, matching the BOM row's SKU in `id`. Not a production type (`"29"`) or an internal catalog product id |
|
|
60
66
|
| `device_type` | `uniform_type` string. Use `""` when the board has none (Wio / Grove may) |
|
|
61
67
|
| `flash_mode` | `"bin"` when a firmware URL is set. `"zip"` for a project zip |
|
|
62
68
|
| `firmware_url` / `firmware_name` / `firmware_size` | Bin mode. `firmware_size` is a string, not a number. Empty `firmware_name` is filled from the URL by the editor |
|