lace-mcp 0.0.2-alpha.20 → 0.0.2-alpha.22

package/README.md

@@ -29,7 +29,7 @@ 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 |
+| `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 |
 

package/SKILL.md

@@ -13,10 +13,23 @@ Lace surfaces adoption insights as actionable decisions. When a decision is appr
 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`.
 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 thread rationale, or `include: "all"` when you need screenshots, cropped image, and rationale together.
+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.
 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:
+
+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).
+3. **Page vocabulary** — the `<page-elements>` list shows nearby elements with `in:parentTag` context. Scan it to understand the target's neighborhood and confirm you're editing the right instance.
+4. **Bbox coordinates** — normalized 0–100 percentages. Use as a spatial hint (top-left vs bottom-right), not a pixel-precise locator. Helpful when text matching is ambiguous.
+5. **Anchor state** — `anchor_state="detached"` means the element moved since the review. Fall back to text + role matching, then sibling context, then ask the user. `anchor_state="reanchored"` means the system re-found it — trust the current metadata.
+6. **Crop image** — `include="crop"` returns both the full page screenshot and a zoomed crop of the target element. Use the full screenshot for spatial context and the crop for visual detail.
+
+**Priority order:** visible text + role → DOM context / siblings → vocabulary neighbors → bbox position → crop image.
+
 ## Troubleshooting
 
 - If `search_decisions` returns an authentication error, tell the user to run `npx lace-mcp install <editor>` to re-authenticate.