Files
designcraft/docs/agents.md
T
dotCooCoo 329806477e Data merge: an explicit QR role in text is refused, and the caret follows each field
data.placeholder.add with role qr and the insertion point in text bound
the QR code to the first selected frame, which the caret was not in. It
now returns "qr placeholders bind to a frame", as a QR field there does.

A field inserted at the insertion point left the caret before its
marker, so a second field went in front of the first. The caret now
moves past the marker, as after typing.

Docs: docs/agents.md.
2026-11-12 07:45:10 -08:00

127 lines
8.1 KiB
Markdown

# Driving DesignCraft from agents and scripts
Every user-visible action in DesignCraft is a command (`crates/engine/src/cmd`), and every command is reachable
three ways — pick whichever fits the agent:
| Surface | Use it when | Entry point |
|---|---|---|
| **CLI** | One-shot jobs, shell pipelines, CI: build or edit a document and export it | `designcraft-cli run`, `script`, `app`, `describe`, `commands` |
| **MCP** | Claude and other MCP clients; images of pages and the window come back as content | `designcraft-cli mcp` ([mcp.md](mcp.md)) |
| **Control channel** | Your own client driving the running app (JSON lines over TCP) | `designcraft --control 7979` ([control-protocol.md](control-protocol.md)) |
## Discover commands
```sh
designcraft-cli commands footnote # every command whose id/label/menu mentions "footnote"
designcraft-cli describe xref.insert # label, menu path, shortcut and parameters of one command
```
Parameters are documented on each command (`params`), e.g. `{anchor? | paragraph?: text to find | story? + para?, format?}`.
## Scripts: several commands, later ones using earlier results
A script is one command per line (`command.id {json params}`; `#` comments), JSON lines, or a JSON array of
`{command, params}`, in UTF-8 with or without a byte order mark. A parameter string `"$N.path"` becomes that value
of step N's result: N is the 0-based step index (comments and blank lines are not steps, `$last` is the previous
step) and the path goes through result fields and array indices (`"$1.story"`, `"$3.ids.0"`); `"${N.path}"`
interpolates inside longer strings. Any other string starting with `$` stays as written (`"$1-$2"`, `"$5 off"`), and
`$$` writes a literal `$` anywhere (`"$$1"` passes `$1`, a GREP group). In text parameters `\n` starts a new paragraph and `\u2028` is a forced line
break (`\u000b`, Word's line break, is read as one too). Most commands ignore parameters they don't know instead of rejecting them, so check names with `describe`.
`designcraft-cli script --help` prints this reference.
```sh
cat > page.dcs <<'DCS'
frame.create {"rect": [72, 72, 540, 300], "content": "text", "text": "Results of the survey"}
text.select {"story": "$0.story", "anchor": 0, "focus": 0}
footnote.insert {"text": "Survey run in 2026."}
frame.create {"rect": [72, 320, 540, 500], "content": "text", "text": "See ."}
text.select {"story": "$3.story", "anchor": 4, "focus": 4}
xref.insert {"paragraph": "Results", "format": "Paragraph Text & Page Number"}
DCS
designcraft-cli script page.dcs --save page.designcraft --export page.pdf --export page.png
designcraft-cli script page.dcs --connect 7979 # the same steps, live in the running app
```
The result is JSON: `{"completed": n, "results": [...]}`, plus `failedIndex` / `failedCommand` / `error` when a step
fails (the exit status is non-zero; `--keep-going` records errors and continues). `run --cmd ID=JSON` accepts the
same references, and MCP's `batch` tool takes `commands` or `script` text with them.
`run` works through its arguments in order. `--page`, `--scale` and `--pdf-options` apply to the `--export` /
`--all-pages` that follow them, so one run can write several sizes
(`run --sample --scale 0.5 --export small.png --scale 2 --export large.png`); one with no export after it is an error.
`--export` writes the file type its extension names: `.png` or `.jpg` (a page), `.pdf`, `.designcraft`, `.idml`,
`.epub`, `.html`, and `.rtf` or `.txt` (the story being edited or of the selected frame). A name with no extension
is a PNG of the page; another extension is an error, and nothing runs.
## Table of contents bookmarks
`toc.generate` accepts `createBookmarks: true` to generate page-level PDF bookmarks from the
included paragraph styles and their levels. `toc.update` refreshes their titles, hierarchy and
destinations. Refresh keeps the generated outline at its previous position, preserving manual
bookmarks before and after it; disabling the option removes only the generated
bookmarks. Without `createBookmarks`, `toc.generate` keeps the document's existing TOC setting,
which is off when there is no TOC yet, so a script that makes a new TOC gets no bookmarks unless
it passes `createBookmarks: true`. The Table of Contents dialog differs: its Create PDF Bookmarks
option is on by default for a new TOC, and for an existing one it shows the saved setting.
## Color themes
`color.extractTheme {id?}` previews up to five RGB colours from a placed raster image (or the selected image).
`swatch.addColorTheme {colors, name?}` adds that palette as a colour group in one undo step.
Extraction samples the whole source image on a bounded grid, weights partial transparency, and ignores fully transparent pixels.
The image must contain at most 16 million pixels. PDF/SVG graphics are unsupported. This is local median-cut extraction,
not Adobe's palette algorithm. In the UI, click an image with the Color Theme Tool (Shift+I), or choose Color Theme…
in the Swatches panel menu with one image selected. Cancel keeps the document unchanged.
## PDF/X-4 validation
`designcraft-cli validate-pdf FILE.pdf` prints JSON with `valid` and `issues`, and exits non-zero
when a built-in check fails. Checks cover PDF version, output intent and profile, Info and XMP
identification, image interpolation, encryption, trim boxes, Type 3 fonts, device RGB under a CMYK
output intent, and unembedded fonts drawing visible text (including placed PDF forms). Render
mode 3 (invisible OCR text) is exempt from the font-embedding check. PDF/X-4 export reports these
issues as warnings; it does not embed or outline placed fonts. These checks are not a complete
external PDF/X certification.
## Data merge
`data.source.select {path, sheet?}` links a CSV/TSV/`.xlsx` file to the document (`data.source.update` re-reads it,
`data.source.remove` drops it); `data.fields` lists its fields. `data.placeholder.add {field, role?, story?, at?, end?, item?}`
marks text or a frame as a field (`role`: text, image, qr, hyperlink). An image field (a `@` column) inserted at a text
insertion point, or typed there as `<<name>>`, merges as an inline image at its natural size, scaled down to fit the
frame. The merge writes only text into a table cell or a note: an image field inserted there is refused unless `role`
is `text`, and its `<<name>>` marker, inserted or typed, merges as the path. A QR field (a `#` column) or `role: "qr"`
at a text insertion point is refused; bind it to a frame with `item` instead. A field inserted at the insertion point
puts the caret after its marker. An image
path is absolute or relative to the data file's folder, then the document's; a path that starts with one separator
(`\Photos\a.jpg`) is tried from the drive's root first. `data.options` sets records, tiling and image fitting;
`data.preview {record}` / `data.preview.stop` show one record without saving it.
`data.merge` now **creates a new document** and leaves the template unchanged (the old `spread` parameter, which
appended pages to the template, is an error). It uses the linked source, or inline `csv` / `rows` / `path` / `bytes`:
```sh
echo 'data.merge {"path": "people.csv", "records": "range", "range": "1-20"}' | designcraft-cli script - --in template.designcraft --save merged.designcraft
```
## The running app
```sh
designcraft --sample --control 7979 &
designcraft-cli app type.changeCase '{"case": "title"}' # any command
designcraft-cli app --method ui.screenshot '{"path": "/tmp/w.png"}' # any control-channel method
```
`ui.menu.invoke {command}` without params acts like choosing the menu item: a command labelled "…" opens its
dialog, which `ui.dialog.set` / `ui.dialog.confirm` fill in and close like a user would.
## Parent pages
In the Pages panel, right-click a parent row and choose **Delete Parent**. The equivalent
command is `layout.parents.delete {id}`, using the parent spread's numeric ID. It deletes that
parent's shared artwork and clears its assignments from document pages and other parents.
Local override copies remain as ordinary editable objects; document pages and their own content
remain. Undo restores the parent and its relationships in one step. Deleting the last parent
returns the canvas to document pages. Parent navigation is a separate operation.