@archme/cli 0.29.0 → 0.31.0
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/SKILL.md +12 -2
- package/dist/cli.js +9861 -9548
- package/package.json +1 -1
- package/sandbox-image.json +1 -1
package/SKILL.md
CHANGED
|
@@ -17,8 +17,18 @@ archme stores anchors. You produce and verify them.
|
|
|
17
17
|
Two surfaces:
|
|
18
18
|
|
|
19
19
|
- **archme MCP tools** (`read_architecture`, `update_architecture`,
|
|
20
|
-
`find_components_for_paths`, `get_component`, ...) —
|
|
21
|
-
the architecture. Your only path to archme's data.
|
|
20
|
+
`find_components_for_paths`, `get_component`, `read_deployment`, ...) —
|
|
21
|
+
read and write the architecture. Your only path to archme's data.
|
|
22
|
+
Where components run is written with `update_architecture`'s
|
|
23
|
+
`deploymentUpdates` and read with `read_deployment`: one environment per
|
|
24
|
+
real target, its nodes nested the way the infrastructure nests, each
|
|
25
|
+
running copy an instance `{ id, of }` of the component that deploys as a
|
|
26
|
+
unit, what holds none of our code (a load balancer, a broker) as
|
|
27
|
+
`infrastructure`, and every connection stated as a link `{ from, to, label }`
|
|
28
|
+
between element ids (snake_case). Model only what the infrastructure files show.
|
|
29
|
+
Keep environments current only on a board that already has one
|
|
30
|
+
(`read_deployment` lists them): never write a board's first environment
|
|
31
|
+
unless the user asks for a deployment diagram.
|
|
22
32
|
|
|
23
33
|
- **`@archme/cli`** (the package shipping this skill) — local code
|
|
24
34
|
analysis. Commands:
|