@lincyaw/skills 1.0.0-rc.40 → 1.0.0-rc.41

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.40",
3
+ "version": "1.0.0-rc.41",
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.40"
39
+ "@lincyaw/kernel": "1.0.0-rc.41"
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.40",
16
- "hash": "477a4bd735059c583d91d0002281458e9c5876e9b61bd2787c61c98a9d71404a"
15
+ "version": "1.0.0-rc.41",
16
+ "hash": "77440b50c582c9f7ed85ea2c279720713fceab7a7c6711cc207eec3a6033c3e3"
17
17
  },
18
18
  {
19
19
  "name": "presmium-animate",
@@ -545,7 +545,7 @@
545
545
  "references/team.md",
546
546
  "references/timeline.md"
547
547
  ],
548
- "version": "1.0.0-rc.40",
548
+ "version": "1.0.0-rc.41",
549
549
  "hash": "76dc5b50143b8134b36c010e5416033652071373500f214f4e7b1792af8a0c4a"
550
550
  },
551
551
  {
@@ -556,7 +556,7 @@
556
556
  "references/plugin.md",
557
557
  "references/testing.md"
558
558
  ],
559
- "version": "1.0.0-rc.40",
559
+ "version": "1.0.0-rc.41",
560
560
  "hash": "af8f48dbe9dbc5bd772fa3d6172ae9c9b96626fec2cd7933b4e08f7c5f154b75"
561
561
  }
562
562
  ]
@@ -43,14 +43,14 @@ Each page has one idea and two versions. The reading version is written like a b
43
43
 
44
44
  When the MCP server `presmium` offers author actions (the studio's assistant; or `presmium mcp` while Presmium Studio or `presmium serve` runs for the project, which a new project's `.mcp.json` connects Claude Code to), change the document through them, the same actions the studio's buttons use. The server's instructions list this order too; each tool describes its own parameters.
45
45
 
46
- 1. **Find the target.** `list_documents`; `get_focus` gives what the author has selected or pointed at, so "this page" or "this paragraph" means that.
47
- 2. **Read the context the edit needs.** An explicit title change goes straight to `rename_page` with `section` (page number from 1, or stable ID) and `title`. For content, use `get_document_outline` and `read_document_part` for the complete values you will change and the relevant surrounding pages. An advertised tool does not require a separate capability request. Parameter schemas come from MCP tools/list; from the command line, `presmium mcp tools <tool>` returns that same definition, and `presmium mcp tools --json` returns all definitions.
48
- 3. **Save in one call.** Use `rename_page` for a title and `edit_document` for canonical operations on text, blocks, steps, narration, timing and assets. The server reads the current source, preflights, saves and verifies the saved source internally; no separate plan/apply/readback requests are needed. Pass optional `source` when the intent depends on a prior read. A 409 requires a fresh read and an explicit decision, never an automatic retry. The owner's MCP credential already authorizes canonical document editing; execution and paid generation keep their confirmation policies. A simple edit's receipt includes the saved source and reported editor/preview synchronization. Plan/apply tools remain for complex reviewed changes, page creation/move/deletion and duplication; deletion retains explicit confirmation. A refused approval is final for that request.
46
+ 1. **Find the target.** `get_context` gives the current saved page, step, narration and actually reported selection. When no editor is connected or several targets are possible, name the document/page explicitly; `list_documents` lists documents. Pending editor state is not saved draft content.
47
+ 2. **Read the context the edit needs.** An explicit title change goes straight to `rename_page` with `section` (page number from 1, or stable ID) and `title`. For content, use `get_document_outline` and `read_document_part` for the complete values you will change and the relevant surrounding pages. An advertised tool does not require a separate capability request. The external MCP catalog is compact. Find additional actions with `operations`, inspect one by name for generated argument summaries, and request `schema:true` only for a complete input definition. Dispatch through the matching read/edit/spend/write/agent operation tool. CLI `presmium mcp tools <tool>` returns a summary, `--schema` the complete input schema and `tools --all --json` the full catalog.
48
+ 3. **Save in one call.** Use `rename_page` for a title, `edit_narration` for a unique exact phrase replacement or deletion, and the discovered `edit_document` operation for canonical operations on text, blocks, steps, narration, timing and assets. Narration edits default to the current editor page/step; missing or ambiguous original text is refused. Comments, voice, caption scale and component parameters also have generated one-call actions such as `comment_create`, `voice_set` and `caption_scale_set`. The server reads the current source, preflights, saves and verifies the saved source internally; no separate plan/apply/readback requests are needed. Pass optional `source` when the intent depends on a prior read. A 409 requires a fresh read and an explicit decision, never an automatic retry. The owner's MCP credential already authorizes canonical document editing; execution and paid generation keep their confirmation policies. A simple edit returns saved/changed and editor status; request details only for diagnostics. Versions, hashes, plans and source readback stay on the server for ordinary edits. Plan/apply tools remain for complex reviewed changes, page creation/move/deletion and duplication; deletion retains explicit confirmation. A refused approval is final for that request.
49
49
  4. **Use the returned evidence.** For a simple edit, report its saved value and editor feedback; do not run whole-document checks or captures by default. Run `check_document` and `get_diagnostics` for code or structural changes, reported failures, or when requested. Fix what you caused; report what you cannot fix. Pending or unavailable editor feedback does not invalidate a successful save or justify repeating the write.
50
50
  5. **Inspect appearance when the task needs it.** For layout and animation work, `capture_slides` returns the changed page at rest, with `at` for animation moments and `measure` for element boxes. `capture_reading` checks reading layout and phone width; `capture_overview` reviews a deck. Capture only the affected scope. Saved source and reported editor synchronization do not prove visual layout or playback. Don't script a browser for this.
51
51
  6. **Voiceover and outputs are explicit.** Editing narration never generates audio. Read `get_voiceover_status`, tell the author the engine, the voice and the number of sentences (a cloud engine charges for them), and call `start_voiceover` only after the author agrees; without an MCP host, `presmium voiceover` gives the same report and generates with `--yes`. `build` and `get_builds` make and list outputs. Details in [Lecture production](references/lecture.md) and [Publishing](references/publishing.md).
52
52
 
53
- Undo is `undo_document_change`; `get_document_history` lists the saved changes.
53
+ Discover `undo_document_change` for saved history and `get_document_history` for its entries. `editor_action` controls advertised browser actions, supplying connection/revision/source metadata internally and waiting briefly for a real acknowledgement. Pending returns a request reference to inspect; never resend an action merely because its acknowledgement was lost. Native unsaved editor history remains a separate browser capability.
54
54
 
55
55
  To connect an AI tool: a project made by `presmium new` has `.mcp.json` for Claude Code; otherwise run `claude mcp add presmium -- presmium mcp` or `codex mcp add presmium -- presmium mcp` in the project. `presmium mcp` relays to the Presmium Studio or `presmium serve` running for the project and follows it when it starts again (a `presmium dev` only previews: it has no author actions and takes no pictures); with neither running it only reads, checks and exports, and the author starts `presmium studio` then reconnects the server. A script or pipeline without an MCP client calls the same tools of the running service from the project's directory: `presmium mcp tools` lists them, `presmium mcp call <tool> '<JSON arguments>'` prints the result as JSON, and `--out <dir>` saves the pictures a capture returns as PNG files.
56
56
 
@@ -1,6 +1,6 @@
1
1
  # Editing with the studio and an agent
2
2
 
3
- For an explicit title change use `rename_page` with the page number or stable ID and title. For other canonical content changes use `edit_document` with operations. Both read the source, preflight, save through the Web transaction/history and verify saved content inside one call; pass optional source when intent depends on an earlier read. Their receipt includes observed editor synchronization separately from saved source and prepared preview. Pending feedback never means that the save should be repeated. Use plan/apply tools when a change needs separate impact review. The local owner's MCP credential authorizes canonical editing without a second Studio confirmation; execution, browser control and paid generation retain their own policies. CLI parameter discovery is automatic: `presmium mcp tools <tool>` returns the live tools/list definition, including inputSchema, and `tools --json` returns all definitions. Do not look up tool parameters in implementation source.
3
+ For an explicit title change use `rename_page` with the page number or stable ID and title. For other canonical content changes use `edit_document` with operations. Both read the source, preflight, save through the Web transaction/history and verify saved content inside one call; pass optional source when intent depends on an earlier read. Their default receipt is saved/changed plus editor status; details are opt-in. `get_context` reads the current saved editor target; `edit_narration` replaces a unique exact phrase while preserving cue/pronunciation atoms. Pending feedback never means that the save should be repeated. Use plan/apply tools when a change needs separate impact review. The local owner's MCP credential authorizes canonical editing without a second Studio confirmation; execution, browser control and paid generation retain their own policies. External MCP exposes a compact catalog: use `operations` to discover actions and generated argument summaries, then the dispatcher matching its kind; `schema:true` opts into a complete definition. CLI parameter discovery is automatic: `presmium mcp tools <tool>` returns generated summaries, `--schema` returns inputSchema and `tools --all --json` returns the full catalog. Do not look up tool parameters in implementation source.
4
4
 
5
5
  For an external HTTP MCP client, start Studio and configure `http://127.0.0.1:4321/mcp` (Streamable HTTP) with `Authorization: Bearer <token>` from the token file printed at startup. Studio preserves both for the same launch directory across restarts and upgrades. With `--host 0.0.0.0`, use the printed network MCP URL from other machines. A second Studio needs a different fixed `--preview-port`; an occupied port fails instead of silently changing the URL.
6
6