菜单
Scaffold a new NucleoOS web app correctly — manifest, www assets, registry entry, ANIMA launch aliases, i18n, icon — so it shows up, launches by name, and passes validation. Use when adding a new app to the OS, creating an app folder, or wiring an existing app folder into the registry.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build and ship NucleoOS to BOTH Cardputer units — the original and the ADV — in one pass. Use when the user wants to release/build/OTA/flash for both boards, the ADV and non-ADV Cardputers, or two devices at once. Encodes the key fact that it's ONE universal binary (runtime board auto-detect), so you build once and fan out the shipping to each unit, then verify per board.
Build, gate, and ship NucleoOS to the Cardputer — firmware via OTA and the web/SD payload via the device file API. Use when the user asks to release, deploy, flash, OTA, sync the SD, or push a web app to the device. Covers the one-command release, firmware-only and SD-only paths, and the gotchas (PIN, .gz shadowing, never /MIR).
Debug and develop NucleoOS firmware/ANIMA logic on the PC without flashing — the host harness compiles the real C and runs it locally. Use when working on ANIMA (the offline NL assistant), retrieval cascade, NLU, knowledge graph, or any firmware logic, and when deciding how to verify a change. Lists the gate suites to run before claiming a fix.
Scaffold and implement a NucleoOS native firmware app (C++) correctly — anti-flicker, poll handler, RAM discipline, input routing, registration. Use when creating or fixing a native app in firmware/components/nucleo_app/.
How to verify a NucleoOS change actually works before claiming done or releasing — the full preflight matrix (registry/manifest validation, i18n, gzip parity, API spec drift, ANIMA gate, app tests) plus running the device simulator for web changes. Use when finishing a change, before a release, or when asked to verify/test that something works.
| name | nucleo-new-app |
| description | Scaffold a new NucleoOS web app correctly — manifest, www assets, registry entry, ANIMA launch aliases, i18n, icon — so it shows up, launches by name, and passes validation. Use when adding a new app to the OS, creating an app folder, or wiring an existing app folder into the registry. |
An app is apps/<id>/ with a manifest.json + a www/ folder. To actually appear and be
launchable it must also be registered and aliased. Miss a step and it's invisible or unfindable.
apps/<id>/manifest.json (validated against schemas/manifest.schema.json — see an existing one like
apps/radio/manifest.json and docs/app-manifest.md):
{ "id": "<id>", "name": "<Name>", "version": "1.0.0", "description": "...",
"category": "media|tools|system|games|...", "runtime": "web",
"entry_service": "none", "web_route": "/apps/<id>/", "icon": "/apps/<id>/icon.svg",
"permissions": ["storage.shared"], "handles": { "role": "none", "extensions": [] },
"intents": [], "subscribes": [], "publishes": [],
"power": { "budget_class": "low", "wants_wakeup": [] }, "mesh": { "exposes": [], "consumes": [] } }
www/ holds at least index.html, icon.svg, and (if it has UI text) i18n.en.json +
i18n.it.json. The icon is served only from www/ (/apps/<id>/icon.svg); an app's icon
source is its manifest. To import code from another app use /apps/<otherid>/<file> —
without /www/ (webfs + sim both map there; adding /www/ 404s).
registry/apps.jsonAdd to installed[]: { "id":"<id>", "version":"1.0.0", "path":"/apps/<id>", "enabled":true, "autostart":false, "permissions":[...] } (permissions mirror the manifest). If it owns a file
type, add to registry/file-associations.json.
registry/app-aliases.jsonAdd "<id>": ["italian", "and", "english", "aliases"] (lowercase, accents folded). This is the
single source for the "apri X" intent, shared by firmware + simulator. After editing, run the
generator so the firmware copy stays in lock-step:
python tools/anima/gen_aliases.py
It errors on exact alias collisions, warns on prefixes. Order = first-match priority.
Per-app strings go in apps/<id>/www/i18n.{en,it}.json; the shell/core catalogs live in
web/shell/i18n/. Both must stay in parity (npm run i18n:gate). See docs/i18n.md.
npm run validate # registry + manifest schema + cross-refs
npm run i18n:gate
node tools/serve-shell.mjs # http://localhost:5599 — open /apps/<id>/ and exercise it
npm run gz:check # the device serves <file>.gz first — keep it in sync
Use the nucleo-verify skill for the full matrix and nucleo-release to ship.
Don't deploy/flash on your own initiative.