@lincyaw/skills 1.0.0-rc.67 → 1.0.0-rc.68
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
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lincyaw/skills",
|
|
3
|
-
"version": "1.0.0-rc.
|
|
3
|
+
"version": "1.0.0-rc.68",
|
|
4
4
|
"description": "Presmium's bundled authoring, animation, presentation and plugin-development skills for coding agents",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
],
|
|
37
37
|
"dependencies": {
|
|
38
38
|
"jiti": "^2.7.0",
|
|
39
|
-
"@lincyaw/kernel": "1.0.0-rc.
|
|
39
|
+
"@lincyaw/kernel": "1.0.0-rc.68"
|
|
40
40
|
},
|
|
41
41
|
"presmium": {
|
|
42
42
|
"skills": [
|
package/skills/index.json
CHANGED
|
@@ -12,8 +12,8 @@
|
|
|
12
12
|
"references/publishing.md",
|
|
13
13
|
"references/writing.md"
|
|
14
14
|
],
|
|
15
|
-
"version": "1.0.0-rc.
|
|
16
|
-
"hash": "
|
|
15
|
+
"version": "1.0.0-rc.68",
|
|
16
|
+
"hash": "7c1484816d0faaae6ebfe5c77ac815b0a6103ed2ec32e61bbe0f01aca5df82db"
|
|
17
17
|
},
|
|
18
18
|
{
|
|
19
19
|
"name": "presmium-animate",
|
|
@@ -545,8 +545,8 @@
|
|
|
545
545
|
"references/team.md",
|
|
546
546
|
"references/timeline.md"
|
|
547
547
|
],
|
|
548
|
-
"version": "1.0.0-rc.
|
|
549
|
-
"hash": "
|
|
548
|
+
"version": "1.0.0-rc.68",
|
|
549
|
+
"hash": "e03f7e914cde64664fc473e7f0a58089283c68f07f213d5be086138089f2e13e"
|
|
550
550
|
},
|
|
551
551
|
{
|
|
552
552
|
"name": "presmium-develop",
|
|
@@ -556,7 +556,7 @@
|
|
|
556
556
|
"references/plugin.md",
|
|
557
557
|
"references/testing.md"
|
|
558
558
|
],
|
|
559
|
-
"version": "1.0.0-rc.
|
|
559
|
+
"version": "1.0.0-rc.68",
|
|
560
560
|
"hash": "af8f48dbe9dbc5bd772fa3d6172ae9c9b96626fec2cd7933b4e08f7c5f154b75"
|
|
561
561
|
}
|
|
562
562
|
]
|
|
@@ -9,7 +9,7 @@ Work top down: each layer decides the next, and its details are in the reference
|
|
|
9
9
|
|
|
10
10
|
## 1. Ground rules
|
|
11
11
|
|
|
12
|
-
- Presmium-owned normalized document IR is the only editable authority; animation implementations are referenced project files. Do not add a MyST directive or Markdown
|
|
12
|
+
- Presmium-owned normalized document IR is the only editable authority; animation implementations are referenced project files. Keep page titles, narration, steps, parameters, timing and comments in `lecture.json`. Do not add per-page content files, a MyST directive or Markdown as a second input, or a generator that reconstructs the saved document from them.
|
|
13
13
|
- A step rests on the final frame of its state, and that frame is at once the still on the web page, the slide and the held shot of the video. So a piece is designed as a strip of rest frames, and motion is what carries one into the next.
|
|
14
14
|
- Every state is reconstructible when selected in any order: the look is a function of the step and the time only. An earlier playback side effect is not state.
|
|
15
15
|
|
|
@@ -69,7 +69,8 @@ There is one `lecture.json`, so writers must not overwrite each other.
|
|
|
69
69
|
|
|
70
70
|
- **One service.** Before dispatching, start `presmium studio` (or `presmium serve`) for the project; `presmium dev` won't do, since it offers neither author actions nor pictures. Every agent connects through the MCP server `presmium mcp`, which relays to that service. Agents never start, stop or restart it and don't run `presmium dev` or builds; the service compiles again when files change, so everyone sees everyone's current pages. Each write may wait for the author's approval in Presmium; whether a run of many agents may write without asking (`presmium serve --allow operate`) is the author's decision, not the agents'.
|
|
71
71
|
- **Author actions are transactions.** A page is created with `plan_page_change` and `apply_page_change`; its blocks, steps, narration and the definition of its scene with `plan_document_change` and `apply_document_change`, which can carry the page's scene file in the same change so that the definition and its code land together. A plan names the source version it was read from. When another agent saved in between, the apply returns 409: read again with `read_document_part`, plan again on the new version and apply that, never the old plan. Changes kept to one page at a time rarely collide.
|
|
72
|
-
- **Without the MCP server**,
|
|
72
|
+
- **Without the MCP server**, the coordinator alone edits `lecture.json`. Each agent changes its own scene files and reports the intended page changes by stable entity ID. Before applying those changes, the coordinator reads the latest saved document and updates only the named entities, preserving all other fields and author edits. Page order, titles, narration, steps, parameters, timing and comments stay in the document. Concurrent Web editing requires the author service and its versioned actions.
|
|
73
|
+
- **One editable source.** Keep page content in `lecture.json`; scene code, data and media remain referenced project files. Do not maintain per-page content mirrors or scripts that reconstruct an existing document from another content source. Checks, builds and publishing consume the saved document without rewriting it.
|
|
73
74
|
|
|
74
75
|
## 4. Each agent's loop
|
|
75
76
|
|
|
@@ -7,6 +7,8 @@ description: "Write, edit, present and produce a Presmium teaching document: the
|
|
|
7
7
|
|
|
8
8
|
A **document** is a folder containing `lecture.json`: the only editable source of a teaching document. Everything readers see is derived from it by the compiler: the **reading version** (the web page, and a notebook when listed) and the **presentation version** (the slides, and the narrated **lecture** video made from the slides and the narration). Don't create `lecture.md`, `slides.md` or any second copy of the content.
|
|
9
9
|
|
|
10
|
+
Web edits and author actions save this same document. Read its latest saved content before changing it. Keep titles, body, steps, narration, parameters, comments and production settings there; checks, builds and publishing read it without regenerating its content. Project scripts may create a new document or request explicit changes through the author actions, with the original source version retained when the change depends on a previous read. They must not reconstruct an existing document from separate page descriptions. Without an author service, one coordinator edits the latest document and preserves unrelated fields.
|
|
11
|
+
|
|
10
12
|
A **workspace** has `presmium.workspace.yaml`; its `documents` patterns name the documents, normally `*/lecture.json`. The **studio** is the browser editor started by `presmium studio`.
|
|
11
13
|
|
|
12
14
|
Terms used throughout:
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Publishing, export and offline
|
|
2
2
|
|
|
3
|
-
`lecture.json` is the only editable source; every output is derived from it. A workspace configuration normally lists `documents: ['*/lecture.json']`; an independent site homepage is configured separately under `site.landing` and is not a teaching document. Ordinary README Markdown is not a document entry. To bring a folder of Markdown notes into a workspace, `presmium import notes --out . --exclude raw` writes one `lecture.json` per note (a page per level-1 and level-2 heading, `[[wikilinks]]` resolved by file name or alias, linked local files copied into the document's `attachments/`) and prints the `documents` patterns that list them
|
|
3
|
+
`lecture.json` is the only editable source; every output is derived from it. A workspace configuration normally lists `documents: ['*/lecture.json']`; an independent site homepage is configured separately under `site.landing` and is not a teaching document. Ordinary README Markdown is not a document entry. To bring a folder of Markdown notes into a workspace, `presmium import notes --out . --exclude raw` writes one `lecture.json` per note (a page per level-1 and level-2 heading, `[[wikilinks]]` resolved by file name or alias, linked local files copied into the document's `attachments/`) and prints the `documents` patterns that list them. After this initial import, edit the generated documents through Web or author actions and publish their saved content. Never publish credentials or operator settings in document JSON.
|
|
4
4
|
|
|
5
5
|
Pick the build from what the teacher hands out, and build only the relevant document and form during routine work. Run document commands in the document folder. Before building, read `metadata.renderers`: it lists the forms (`web`, `slides`, `notebook`, `lecture`) with their options, among them `base`, the URL path a form's site is served at (such as `/course/week1/`). When `base` is already set, keep it and the hosting the teacher already uses. Plugin document settings belong in `metadata.presmium`.
|
|
6
6
|
|