You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/cross-platform/deploy-ml-model-to-npu-with-topo/build-the-template.md
+41Lines changed: 41 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,47 @@ The project has three implementation areas:
18
18
19
19
When bootstrapping this Template from scratch, first make the project work as a normal Compose build. Then add the `x-topo` metadata that lets Topo deploy it consistently to an Arm64 target.
20
20
21
+
## Install the Topo Template authoring skills
22
+
23
+
The [Topo Template Format](https://github.com/arm/Topo-Template-Format) repository includes public authoring skills for agents that support skill installation:
24
+
25
+
-`topo-template-context`: provides Topo and Topo Template reference context for `x-topo` metadata, schema, docs, and CLI Template behavior.
26
+
-`topo-template-bootstrap`: converts a Compose repository into a Topo Template by adding or improving `compose.yaml` and `x-topo` metadata.
27
+
-`topo-template-lint`: reviews a Topo Template for schema correctness, metadata consistency, deployment success messages, and build argument wiring.
28
+
29
+
Install the skills with `npx skills`:
30
+
31
+
```bash
32
+
npx skills add arm/topo-template-format
33
+
```
34
+
35
+
If your agent does not use `npx skills`, clone the Template Format repository and manually copy or symlink the directories under `skills/` into your agent's skills directory:
Restart your agent after installing or updating the skills.
42
+
43
+
You can then use the skills as part of the Template authoring flow. From the root of any Compose project, ask your agent to use `topo-template-bootstrap`:
44
+
45
+
```output
46
+
Use topo-template-bootstrap on this repository.
47
+
Treat the root compose.yaml as the Template root.
48
+
Preserve plain docker compose behavior.
49
+
Add x-topo metadata only where it reflects the actual services, hardware requirements, and build arguments.
50
+
```
51
+
52
+
After bootstrap, ask the agent to use `topo-template-lint`:
53
+
54
+
```output
55
+
Use topo-template-lint on topo-imx93-npu-deployment.
56
+
Validate compose.yaml against the Topo Template Format schema.
57
+
Check README alignment, deployment_success_message, Remoteproc Runtime metadata, and x-topo.args wiring.
58
+
```
59
+
60
+
The lint pass should confirm that the Template has a root-level `x-topo.name`, that non-remoteproc services use `platform: linux/arm64`, that `cm33-runner` uses the Remoteproc Runtime annotation, and that every `x-topo.args` entry is carried into Compose or Docker build arguments where appropriate.
61
+
21
62
## Create the runner build pipeline
22
63
23
64
The `executorch-runner/Dockerfile` is a multi-stage Dockerfile. It builds two artifacts from one build context:
0 commit comments