lace-mcp 0.0.2-alpha.28 → 0.0.2-alpha.29

package/SKILL.md

@@ -7,14 +7,16 @@ description: Use when implementing approved Lace decisions, applying approved UI
 
 Lace surfaces adoption insights as actionable decisions. When a decision is approved in the Lace overlay, this skill turns it into a code change.
 
+Comments come from two places: review pages (`source: "review"`) and pins dropped on the user's live screen (`source: "screen-context"`). Both flow through `search_comments` and `apply_comment` identically.
+
 ## Steps
 
 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_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.
+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. Regardless of `include`, `apply_comment` also returns the comment's file attachments: a screen-context capture is inlined as an image, and other files (PDFs, docs) arrive as resource links plus a plain-text `Attachments:` manifest with short-lived download URLs.
+6. Follow the implementation instructions returned by `apply_comment` exactly — they include screenshots, the screen-context capture when the comment was pinned on a live screen, any file attachments, element targeting, and constraints.
 7. Implement the minimal code change described. Do not refactor or modify anything outside the target element.
 
 ## Element Grounding Strategies
@@ -27,8 +29,9 @@ When `apply_comment` returns metadata, use these fields to locate the target ele
 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.
+7. **Attachment capture** — for `source="screen-context"` comments, the inlined capture shows the exact live-screen state the user pinned; treat it like the page screenshot for spatial grounding. Open linked file attachments if the comment references them.
 
-**Priority order:** visible text + role → DOM context / siblings → vocabulary neighbors → bbox position → crop image.
+**Priority order:** visible text + role → DOM context / siblings → vocabulary neighbors → bbox position → crop image. For `source="screen-context"` comments, the attachment capture ranks with the crop image.
 
 ## Troubleshooting