← ClaudeAtlas

atmos-pt-design-agentlisted

Drive the user's open Atmos Prototype Design board via POST /api/pt-design/agent/invoke: read and edit document.ptx (PTX XML). Use for interactive canvas prototypes. Not Atmos Canvas. Not a wireframe layout engine.
AruNi-01/atmos · ★ 6 · Web & Frontend · score 74
Install: claude install-skill AruNi-01/atmos
# Atmos Prototype Design Agent Operate the **live Prototype Design tab** with HTTP invoke. PTX is a source file. Read it, edit the XML, write the complete file back. ```text Default path: pt_ptx_get → edit XML → pt_ptx_apply → pt_screenshot File path: document.ptx in a .ptd directory (CLI/MCP --file only) ``` --- ## Prerequisites 1. Prototype Design is open (Launchpad or `/pt-design`). Opening the tab is enough. Do **not** start MCP, install a CLI, join a collaboration room, or treat a `.ptdesign.json` as the Agent API. 2. `POST` the invoke URL from the copied prompt (loopback Atmos Server). Include `client_id` from that prompt when more than one tab is open. `/pt-design` is `global`. 3. Fresh `request_id` (UUID) on every call. ```json { "request_id": "<uuid>", "tool": "pt_ptx_get", "args": {}, "client_id": "global" } ``` --- ## Decision tree (load references on demand) | User intent | What to do | Load reference | |-------------|------------|----------------| | Build or change the board | Workflow below | *(this file only)* | | Which tags/attrs a type uses | `pt_catalog_list` (copy `xmlExample`) | [`references/catalog.md`](references/catalog.md) | | Dashboard, metrics, or a chart | `pt_catalog_list` — copy a `chart.*` `xmlExample` | [`references/catalog.md`](references/catalog.md) | | Screenshot / live vs file | Workflow below | [`references/board.md`](references/board.md) | | Full tool args / error codes / offline `.ptd` | — | [`references/command-refe