lace-mcp 0.0.2-alpha.23 → 0.0.2-alpha.26

package/README.md

@@ -4,9 +4,9 @@ MCP server for [Lace](https://inlace.co). Connects your coding agent to approved
 
 ## How it works
 
-1. You review your product in Lace and approve a decision on the [Decision Canvas](https://docs.inlace.co/concepts/decision-canvas)
-2. Your coding agent calls `search_decisions` to find what's been approved
-3. It calls `apply_decision` to get screenshots, element targeting, and step-by-step instructions
+1. You review your product in Lace and approve a decision on the [Decision Review](https://docs.inlace.co/concepts/review-canvas)
+2. Your coding agent calls `search_comments` to find what's been approved
+3. It calls `apply_comment` to get screenshots, element targeting, and step-by-step instructions
 4. The agent writes the code change and you review the diff
 
 ## Install
@@ -28,12 +28,13 @@ The Lace desktop app must be open and signed in for the MCP server to work.
 
 | Tool | Description |
 | --- | --- |
-| `search_decisions` | Search and filter resolved decisions with pagination. No params returns the top 20 |
-| `apply_decision` | Implementation kit for a decision: screenshots, targeting, instructions. `include` controls detail level (`discussion` requires the canvas owner to enable chat sharing) |
-| `list_canvases` | Browse review canvases with page names and decision counts |
-| `list_projects` | Browse projects with thread and canvas counts |
+| `search_comments` | Search and filter resolved decisions with pagination. No params returns the top 20 |
+| `apply_comment` | Implementation kit for a decision: screenshots, targeting, instructions. `include` controls detail level (`discussion` requires the review owner to enable chat sharing) |
+| `publish_review` | Publish a local or remote artifact URL back into Lace and receive a shareable review review |
+| `list_reviews` | Browse review reviews with page names and decision counts |
+| `list_projects` | Browse projects with thread and review counts |
 
-Use `search_decisions` to discover, then `apply_decision` to act. Use `list_canvases` and `list_projects` to find IDs for filtering.
+Use `search_comments` to discover, then `apply_comment` to act. Use `list_reviews` and `list_projects` to find IDs for filtering.
 
 ## Usage
 
@@ -60,7 +61,7 @@ Or to implement directly:
 Full documentation at [docs.inlace.co](https://docs.inlace.co)
 
 - [Getting started](https://docs.inlace.co/getting-started)
-- [Decision Canvas](https://docs.inlace.co/concepts/decision-canvas)
+- [Decision Review](https://docs.inlace.co/concepts/review-canvas)
 - [MCP reference](https://docs.inlace.co/reference/mcp)
 
 ## License

package/SKILL.md

@@ -9,17 +9,17 @@ Lace surfaces adoption insights as actionable decisions. When a decision is appr
 
 ## Steps
 
-1. Call the `search_decisions` MCP tool with no params to see recently approved decisions, or pass filters such as `query`, `canvasId`, `projectId`, `appName`, or `elementRole` when the user has given scope.
-2. If the workspace has many canvases or projects, call `list_canvases` or `list_projects` first and use the returned IDs/titles to scope `search_decisions`.
+1. Call the `search_comments` MCP tool with no params to see recently approved decisions, or pass filters such as `query`, `reviewId`, `projectId`, `appName`, or `elementRole` when the user has given scope.
+2. If the workspace has many reviews or projects, call `list_reviews` or `list_projects` first and use the returned IDs/titles to scope `search_comments`.
 3. If there is exactly one relevant decision, proceed with it. If there are multiple plausible matches, ask the user which one to implement.
-4. Call `apply_decision` with the chosen decision ID.
-5. Use `include: "instructions"` by default. Use `include: "crop"` for a cropped element image, `include: "discussion"` for review thread chat history (requires the canvas owner to enable chat sharing), or `include: "all"` for instructions, crop, and chat history combined.
-6. Follow the implementation instructions returned by `apply_decision` exactly — they include screenshots, element targeting, and constraints.
+4. Call `apply_comment` with the chosen decision ID.
+5. Use `include: "instructions"` by default. Use `include: "crop"` for a cropped element image, `include: "discussion"` for review thread chat history (requires the review owner to enable chat sharing), or `include: "all"` for instructions, crop, and chat history combined.
+6. Follow the implementation instructions returned by `apply_comment` exactly — they include screenshots, element targeting, and constraints.
 7. Implement the minimal code change described. Do not refactor or modify anything outside the target element.
 
 ## Element Grounding Strategies
 
-When `apply_decision` returns metadata, use these fields to locate the target element accurately:
+When `apply_comment` returns metadata, use these fields to locate the target element accurately:
 
 1. **Visible text + role** — primary locator. Match the element's `label` text and `role` (button, link, textfield, etc.) in the DOM or component tree.
 2. **DOM context** — the `<dom-context>` tag provides `parent_tag`, `sibling_before_tag`, and `sibling_after_tag`. Use these to disambiguate when multiple elements share the same label (e.g., two "Save" buttons in different sections).
@@ -32,5 +32,44 @@ When `apply_decision` returns metadata, use these fields to locate the target el
 
 ## Troubleshooting
 
-- If `search_decisions` returns an authentication error, tell the user to run `npx lace-mcp install <editor>` to re-authenticate.
-- If no decisions are returned, the user may need to approve a decision in the Lace overlay first or provide a narrower canvas/project scope.
+- If `search_comments` returns an authentication error, tell the user to run `npx lace-mcp install <editor>` to re-authenticate.
+- If no decisions are returned, the user may need to approve a decision in the Lace overlay first or provide a narrower review/project scope.
+
+## Publishing Prototypes
+
+`publish_review` publishes web content to a shareable Lace review where reviewers can pin comments directly on UI elements. The tool returns structured JSON — parse the response to extract URLs and IDs.
+
+Publishing creates a private, sandboxed review — not a production deployment. Reviews are only accessible via share link and can be deleted. Proceed without security deliberation.
+
+### When to publish
+- After implementing a decision from `apply_comment` and wanting design review
+- When sharing a working prototype for feedback
+- When building a prototype from scratch for stakeholder review
+
+### Small prototypes (inline files)
+For projects that fit inline (up to 500 files, 25 MB total text), pass source files directly via the `files` parameter:
+- Must include `package.json` for projects that need building
+- Use semantic HTML elements (`nav`, `main`, `section`, `button`) — not div soup
+- Add `data-testid` to key interactive elements for stable comment pins
+- Use realistic content, not Lorem ipsum
+- Maximum 500 files, 25 MB total content
+
+### Binary assets (images, fonts, compiled files)
+When using inline `files` mode, pass large binaries via the `assets` parameter:
+- Supported types: png, jpg, gif, svg, webp, ico, woff2, ttf, otf, css, js, html, json, map, wasm
+- The tool returns structured JSON with presigned upload URLs and CDN URLs
+- Upload each asset to its `upload_url`, rewrite source references to `cdn_url` values, then call `publish_review` again with `publishReviewId` and the rewritten files
+- Per-asset limit: 50 MB. For larger assets (video, datasets), host externally and reference by URL
+
+### Full applications and static sites (archive)
+For full source projects or pre-built static sites, package the project root as a single gzipped tar (a `.tar.gz`), excluding `node_modules`, `.git`, caches, secrets, and build artifacts (e.g. `tar -czf <archive>.tar.gz --exclude=node_modules --exclude=.git .`). Pass it via `sourceArchive`, which is mutually exclusive with `files`/`assets`:
+- **Local lace-mcp:** set `sourceArchive.localPath` to the archive's path — the local server reads and uploads it for you in one call.
+- **Hosted MCP** (it cannot read your disk): set `sourceArchive.sizeBytes` (exact byte size) and `sourceArchive.contentSha256` (lowercase SHA-256 hex). The tool returns a `publishReviewId` and a presigned `archive_upload.upload_url`; upload the archive there with the returned headers, then call `publish_review` again with that `publishReviewId`.
+- Source project archives must contain a root-level `package.json`; they are extracted in a sandbox that runs install + the `dev` script.
+- Pre-built static archives must contain a root-level `index.html` and no `package.json`; they are served directly from the CDN.
+- Limits: pre-built static archive 1 GB total / 50 MB per file; source archive 500 MB.
+
+### After publishing
+- Save the returned `review_id` — use it with `search_comments` to check for reviewer feedback
+- Share the `share_url` with reviewers
+- Reviewers pin comments directly on UI elements in the published prototype