@agent-native/core 0.136.4 → 0.137.0

package/corpus/templates/plan/app/components/plan/CanvasArea.tsx

@@ -77,6 +77,18 @@ type WorldPoint = {
   y: number;
 };
 
+type ClientPoint = {
+  x: number;
+  y: number;
+};
+
+type PinchGesture = {
+  pointerIds: [number, number];
+  startDistance: number;
+  startMidpoint: ClientPoint;
+  startView: CanvasView;
+};
+
 type PendingMarkup = {
   mode: "text" | "callout";
   origin: WorldPoint;
@@ -140,6 +152,10 @@ export function CanvasArea({
     [canvas.viewport?.pan?.x, canvas.viewport?.pan?.y, canvas.viewport?.zoom],
   );
   const [view, setView] = useState<CanvasView>(initialView);
+  const viewRef = useRef(view);
+  viewRef.current = view;
+  const activePointersRef = useRef(new Map<number, ClientPoint>());
+  const pinchGestureRef = useRef<PinchGesture | null>(null);
   const [drag, setDrag] = useState<{
     pointerId: number;
     startX: number;
@@ -581,8 +597,48 @@ export function CanvasArea({
   const onPointerDown = (event: ReactPointerEvent<HTMLDivElement>) => {
     if (event.button !== 0 && event.button !== 1) return;
     const target = event.target as HTMLElement;
+    const activePointers = activePointersRef.current;
     // Don't start a pan when grabbing interactive chrome (zoom controls etc.).
-    if (event.button === 0 && target.closest("[data-plan-interactive]")) return;
+    if (
+      event.button === 0 &&
+      target.closest("[data-plan-interactive]") &&
+      activePointers.size === 0
+    ) {
+      return;
+    }
+    activePointers.set(event.pointerId, {
+      x: event.clientX,
+      y: event.clientY,
+    });
+    if (activePointers.size >= 2) {
+      const pointerIds = Array.from(activePointers.keys()).slice(0, 2) as [
+        number,
+        number,
+      ];
+      const first = activePointers.get(pointerIds[0]);
+      const second = activePointers.get(pointerIds[1]);
+      if (!first || !second) return;
+      const rect = viewportRef.current?.getBoundingClientRect();
+      const startMidpoint = getMidpoint(first, second);
+      pinchGestureRef.current = {
+        pointerIds,
+        startDistance: getDistance(first, second),
+        startMidpoint: rect
+          ? {
+              x: startMidpoint.x - rect.left,
+              y: startMidpoint.y - rect.top,
+            }
+          : startMidpoint,
+        startView: viewRef.current,
+      };
+      setDrag(null);
+      setDraftCallout(null);
+      setPendingMarkup(null);
+      event.preventDefault();
+      event.stopPropagation();
+      event.currentTarget.setPointerCapture(event.pointerId);
+      return;
+    }
     if (!isEditableShortcutTarget(target)) {
       event.currentTarget.focus({ preventScroll: true });
     }
@@ -674,6 +730,37 @@ export function CanvasArea({
         onPointerDown={onPointerDown}
         onKeyDown={onViewportKeyDown}
         onPointerMove={(event) => {
+          const activePointer = activePointersRef.current.get(event.pointerId);
+          if (activePointer) {
+            activePointer.x = event.clientX;
+            activePointer.y = event.clientY;
+          }
+          const pinchGesture = pinchGestureRef.current;
+          if (pinchGesture) {
+            const first = activePointersRef.current.get(
+              pinchGesture.pointerIds[0],
+            );
+            const second = activePointersRef.current.get(
+              pinchGesture.pointerIds[1],
+            );
+            const rect = viewportRef.current?.getBoundingClientRect();
+            if (!first || !second || !rect) return;
+            const midpoint = getMidpoint(first, second);
+            const currentMidpoint = {
+              x: midpoint.x - rect.left,
+              y: midpoint.y - rect.top,
+            };
+            updateView(() =>
+              viewForPinchGesture({
+                gesture: pinchGesture,
+                currentDistance: getDistance(first, second),
+                currentMidpoint,
+              }),
+            );
+            event.preventDefault();
+            event.stopPropagation();
+            return;
+          }
           if (draftCallout?.pointerId === event.pointerId) {
             const point = clientPointToWorld(event);
             if (!point) return;
@@ -697,6 +784,28 @@ export function CanvasArea({
           }));
         }}
         onPointerUp={(event) => {
+          activePointersRef.current.delete(event.pointerId);
+          if (pinchGestureRef.current) {
+            event.preventDefault();
+            event.stopPropagation();
+            if (event.currentTarget.hasPointerCapture(event.pointerId)) {
+              event.currentTarget.releasePointerCapture(event.pointerId);
+            }
+            const remaining = Array.from(
+              activePointersRef.current.entries(),
+            )[0];
+            pinchGestureRef.current = null;
+            if (remaining) {
+              setDrag({
+                pointerId: remaining[0],
+                startX: remaining[1].x,
+                startY: remaining[1].y,
+                panX: viewRef.current.pan.x,
+                panY: viewRef.current.pan.y,
+              });
+            }
+            return;
+          }
           if (draftCallout?.pointerId === event.pointerId) {
             const point = clientPointToWorld(event) ?? draftCallout.current;
             event.preventDefault();
@@ -722,7 +831,9 @@ export function CanvasArea({
             setDrag(null);
           }
         }}
-        onPointerCancel={() => {
+        onPointerCancel={(event) => {
+          activePointersRef.current.delete(event.pointerId);
+          pinchGestureRef.current = null;
           setDraftCallout(null);
           setDrag(null);
         }}
@@ -838,6 +949,7 @@ export function CanvasArea({
       <div
         className="plan-canvas-zoom absolute bottom-3 left-3 z-10 flex items-center gap-0.5 rounded-lg border border-plan-line bg-plan-chrome p-0.5 shadow-md backdrop-blur"
         data-plan-interactive
+        title={t("raw.canvas.zoomHint")}
       >
         <Button
           type="button"
@@ -912,6 +1024,18 @@ function surfaceOf(frame: PlanArtboard): PlanWireframeSurface {
   return frame.surface ?? frame.wireframe?.surface ?? "desktop";
 }
 
+/**
+ * Keep the surface width stable while allowing long screens to reserve a
+ * taller, non-scrolling artboard in canvas mode.
+ */
+export function canvasFrameSize(frame: PlanArtboard) {
+  const preset = SURFACE_SIZE[surfaceOf(frame)];
+  return {
+    width: preset.width,
+    height: Math.max(preset.height, frame.height ?? preset.height),
+  };
+}
+
 function sameCanvasView(a: CanvasView, b: CanvasView) {
   return (
     Math.abs(a.zoom - b.zoom) < 0.0001 &&
@@ -980,11 +1104,9 @@ function layoutArtboards(frames: PlanArtboard[]): PlanArtboard[] {
 
   return frames.map((frame) => {
     const surface = surfaceOf(frame);
-    const preset = SURFACE_SIZE[surface];
-    // SURFACE owns the footprint/aspect — ignore any model-supplied width/height
-    // so a popover is always ~square and can never render "too wide".
-    const width = preset.width;
-    const height = preset.height;
+    // Surface owns the width/aspect. A larger explicit height is the
+    // non-scrolling escape hatch for long HTML screens on the canvas.
+    const { width, height } = canvasFrameSize(frame);
 
     if (frame.x !== undefined || frame.y !== undefined) {
       return {
@@ -1038,10 +1160,7 @@ function CanvasArtboard({
   onDesignElementSelect?: (selection: DesignElementSelection) => void;
 }) {
   const surface = surfaceOf(frame);
-  const preset = SURFACE_SIZE[surface];
-  // SURFACE-locked footprint (see layoutArtboards) — model width/height ignored.
-  const width = preset.width;
-  const height = preset.height;
+  const { width, height } = canvasFrameSize(frame);
   const label = frame.label ?? block?.title;
   // Report the frame's real rendered height so board connectors can anchor to
   // the content box (frames are capped at `height` but usually shorter).
@@ -2280,6 +2399,43 @@ function connectorRoute(
   };
 }
 
+export function viewForPinchGesture(input: {
+  gesture: PinchGesture;
+  currentDistance: number;
+  currentMidpoint: ClientPoint;
+}): CanvasView {
+  const { gesture, currentDistance, currentMidpoint } = input;
+  const nextZoom = clamp(
+    gesture.startView.zoom * (currentDistance / gesture.startDistance),
+    MIN_ZOOM,
+    MAX_ZOOM,
+  );
+  const worldX =
+    (gesture.startMidpoint.x - gesture.startView.pan.x) /
+    gesture.startView.zoom;
+  const worldY =
+    (gesture.startMidpoint.y - gesture.startView.pan.y) /
+    gesture.startView.zoom;
+  return {
+    zoom: nextZoom,
+    pan: {
+      x: currentMidpoint.x - worldX * nextZoom,
+      y: currentMidpoint.y - worldY * nextZoom,
+    },
+  };
+}
+
+function getMidpoint(first: ClientPoint, second: ClientPoint): ClientPoint {
+  return {
+    x: (first.x + second.x) / 2,
+    y: (first.y + second.y) / 2,
+  };
+}
+
+function getDistance(first: ClientPoint, second: ClientPoint) {
+  return Math.max(Math.hypot(first.x - second.x, first.y - second.y), 1);
+}
+
 function distance(a: WorldPoint, b: WorldPoint) {
   return Math.hypot(a.x - b.x, a.y - b.y);
 }

package/corpus/templates/plan/app/i18n/en-US.ts

@@ -157,6 +157,7 @@ const messages = {
       artboardCanvas: "Plan artboard canvas",
       zoomIn: "Zoom in",
       zoomOut: "Zoom out",
+      zoomHint: "Hold ⌘/Ctrl and scroll to zoom",
       markupSaveFailed: "Couldn't save markup. Try again.",
     },
     document: {

package/corpus/templates/plan/changelog/2026-08-04-canvas-zoom-controls-now-explain-the-command-ctrl-plus-scrol.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-08-04
+---
+
+Canvas zoom controls now explain the Command/Ctrl plus scroll shortcut

package/corpus/templates/plan/changelog/2026-08-04-pinch-to-zoom-is-now-supported-on-touchscreens-in-visual-pla.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-08-04
+---
+
+Pinch to zoom is now supported on touchscreens in visual plan canvases

package/corpus/templates/plan/shared/plan-content.ts

@@ -1495,12 +1495,27 @@ export const questionFormDataSchema: z.ZodType<PlanQuestionFormBlock["data"]> =
     submitLabel: z.string().trim().max(400).optional(),
   });
 
+/**
+ * Rich-text stores Markdown as runtime text. A fully escaped one-line payload
+ * ("### Heading\\n\\nBody") renders as one giant heading, so reject that shape at
+ * the shared schema instead of persisting a document that only looks valid.
+ * Escapes are still fine when they occur alongside real line breaks, such as
+ * an intentional `\\n` inside a code example.
+ */
+const planMarkdownSchema = z
+  .string()
+  .max(100_000)
+  .refine(
+    (value) => value.includes("\n") || !value.includes("\\n"),
+    "Rich-text Markdown must use actual line breaks, not a fully escaped `\\n` string.",
+  );
+
 export const planBlockSchema: z.ZodType<PlanBlock> = z.lazy(() =>
   z.discriminatedUnion("type", [
     baseBlockSchema.extend({
       type: z.literal("rich-text"),
       data: z.object({
-        markdown: z.string().max(100_000),
+        markdown: planMarkdownSchema,
       }),
     }),
     baseBlockSchema.extend({
@@ -2758,7 +2773,7 @@ const planContentPatchUnion = z.discriminatedUnion("op", [
     op: z.literal("update-rich-text"),
     blockId: idSchema,
     title: z.string().trim().min(1).max(180).optional(),
-    markdown: z.string().max(100_000).optional(),
+    markdown: planMarkdownSchema.optional(),
   }),
   z.object({
     op: z.literal("update-custom-html"),

package/dist/cli/skills-content/canvas.d.ts

@@ -1,4 +1,4 @@
-export declare const CANVAS_SURFACE_CORE = "<!-- SHARED-CORE:canvas-surface START -->\n\n**The coordinate rule.** The `surface` locks each artboard's footprint and\naspect \u2014 never set artboard width/height and never use coordinates inside the\nwireframe HTML; board-level artboard `x`/`y` IS allowed when it creates clear\nlanes. Let canvas auto-placement handle simple one-row boards.\n\n**Lay out mixed canvases in lanes.** When a canvas contains broad browser /\ndesktop frames plus compact `mobile`, `popover`, or `panel` surfaces, do not put\neverything in one horizontal strip. Use board-level artboard `x`/`y` to reserve\nlanes with generous empty space: main flow on one row, compact surfaces in their\nown column or row, and loading/error states in a lower row. Keep at least 96px\nbetween rendered artboard rectangles plus room for annotation gutters; when a\nbroad browser/desktop frame sits beside a compact panel/popover, leave at least\n160px so frame borders, labels, and hover controls never touch. Connect only\nneighboring steps; never draw a long connector that skips across unrelated\nframes. Connector labels must sit in open canvas space. If the label would touch\nor cross either artboard, remove the label and explain the transition with a\nnearby annotation instead. Before handoff, inspect the top canvas at default zoom\nand move any frame whose label, connector, or annotation crosses another frame.\n\n**Board-unit spacing defaults.** The canvas coordinate system uses approximately 2 board units per screen pixel. `browser` frames occupy roughly 700 \u00D7 600 board units; `desktop` frames roughly 900 \u00D7 700 board units. Apply these minimum x/y gaps when placing frames explicitly \u2014 any less and frames will touch or overlap:\n\n- x-gap between `browser` frames: **\u2265 1100** (700-unit frame + 400-unit gutter)\n- x-gap between `desktop` frames: **\u2265 1300** (900-unit frame + 400-unit gutter)\n- y-gap between rows of any surface: **\u2265 1400** (includes frame height + section header + buffer)\n\nWhen in doubt, use larger values \u2014 the canvas auto-zooms to fit everything.\n\n**Canvas annotations are designer notes on the artboard.** When a top canvas is\npresent, sprinkle design-review notes near the frames they explain: a short\nheading, supporting text, and bullets \u2014 plain text layers, never bordered or\nshadowed cards, and never a box around a frame. The renderer spaces notes away\nfrom frames, so place each note by the frame it describes. Use an arrow only to\npoint at one specific control or transition; for a broad frame-level note, write\ntext beside the frame with no connector. Connectors are for real sequences only \u2014\nnever fake \"Step 1 \u2192 Step 2\" lines between independent states.\n\n**Do not create overlapping annotations.** Anchor each ordinary note to the\nframe it explains with `targetId` + `placement` (top/right/bottom/left), and\nomit `type` or use `type: \"note\"`. The renderer parks notes in a gutter beside\nthe frame and lays them out automatically. Do not use `type: \"callout\"`,\n`type: \"text\"`, `type: \"arrow\"`, x/y, or points for ordinary notes; those are\nfreeform review-markup layers and must be reserved for intentional markup in\nopen canvas space. Reserve arrows for a note that must point at one specific\ncontrol inside a frame; a note that simply sits beside its frame needs no arrow.\n\n**Patching.** Edit one wireframe, canvas annotation, diagram, or block with targeted `contentPatches`\n(for example `patch-wireframe-html`, `patch-diagram-html`, `update-block`,\n`replace-blocks`, `update-canvas-annotation`) rather\nthan regenerating the whole plan. `contentPatches` are part of the public MCP\naction schema, so Claude Code, Codex, Cursor, and other hosts can make surgical\nedits. If an agent is working from exported source files, use\n`read-visual-plan-source` / `patch-visual-plan-source`: `plan.mdx` holds\nfrontmatter plus markdown/document blocks, `canvas.mdx` holds\n`<DesignBoard>/<Section>/<Artboard>/<Screen>/<Annotation>/<Connector>`, and the\npatch action normalizes the MDX back into the same JSON runtime model. JSON is\nthe canonical runtime shape; MDX is the repo-friendly authoring/export surface.\nIn the browser, humans edit `rich-text` prose inline; agents should still use\n`update-rich-text` content patches or source patches for prose, and use\ncomments/structured patches for canvas, artboard, wireframe, and diagram edits.\nNever send a partial top-level `content` object as a shortcut to add a canvas,\nframe, or block: `content` is a full structured replacement, so omitted blocks\nor surfaces can disappear. If a full replacement is truly unavoidable, read the\ncomplete source/JSON first, include every existing block and surface in the new\npayload, and verify the source/export immediately after the update.\n\n**Never emit a titled artboard with no interior wireframe content.** Every artboard\nyou place on the canvas must carry an `html` wireframe or reference a wireframe\nblock via `blockId`; when using `blockId`, the referenced `wireframe` /\n`legacy-wireframe` block must remain in the plan. If you remove a duplicate\nwireframe from the document body, first move its `data` inline onto the\ncorresponding `content.canvas.frames[*].wireframe` / `legacyWireframe`. A\nlabel-only frame or a frame pointing at a deleted block renders empty and is\nrejected at parse time. If you only have a title, write it as a section header or\nannotation, not an empty artboard.\n\n**UI mockups belong in the top visual review area.** Static UI/product visuals\nlive on the canvas; multi-step UI flows get both canvas wireframes and a\nprototype. When the user asks for a mockup, UI state, loading state, layout,\nscreen, or visual comparison, make the canvas the primary home for that static\nvisual. When the user asks for a prototype or the plan contains a sequence the\nreviewer must feel, keep the canvas artboards and add `content.prototype` so the\ntop surface shows Wireframes / Prototype tabs. Architecture/code diagrams stay\ninline in the document (the SKILL.md Visual Surface Choice section owns that\nrule) unless the user explicitly asks for a spatial board. Document blocks\ncan explain, compare, or map implementation, but they should not host the\nprimary UI mockup or prototype just because `custom-html`, screenshots, or prose\nare easier to produce. If the canvas/prototype surface cannot represent the\nrequested UI fidelity, still keep the closest top-surface representation and\ncall out or extend the needed renderer capability. A skeleton/loading mockup\nalso lives in a canvas artboard \u2014 never move a mockup out of the canvas.\n\n**Storyboards are canvas artifacts, not document diagrams.** When the requested\noutput is a product flow, onboarding journey, \"light storyboard\", or canvas\nwireframe, author the flow as multiple top-canvas artboards with real screen\ncontent and neighboring connectors. Keep document-body `diagram` blocks for\narchitecture and mechanics that are not themselves user-visible screens. A\nstoryboard made from a single inline HTML diagram is the wrong surface.\n\nFor abstract product concepts, use the canvas to create the first \"I get it\"\nmoment: one real app state near the top showing how the concept appears to a\nuser, followed by separate annotations or diagrams for mechanics. Do not make\nthe first artboard a hybrid of app UI and architecture notes; the app screen\nshould be inspectable as product UI on its own.\n\n**Legacy kit tree.** Older plans set a `screen` array of `{ el, ...props }` kit\nnodes instead of `html`; the renderer still accepts and displays it so saved\nplans round-trip, but new plans emit `html`. Do not author fresh kit-tree\nscreens, and do not put nested kit components such as `<FrameScreen>`, `<Card>`,\n`<Row>`, `<Title>`, or `<Btn>` inside a canvas `<Screen>`. A new canvas artboard\nwith kit-tree children is a defect: replace it with\n`<Screen surface=\"...\" html={...} />` using the HTML wireframe rules. The HTML\npath is the one that gets the renderer-owned surface sizing, theme tokens,\nsketch/clean toggle, and safe text layout used by good document-body\nwireframes. Likewise, old or imported plans may carry coordinate-based regions\nor free-float x/y on notes; those are legacy escape hatches the renderer still\nshows but you must never produce. The gutter parks notes by `targetId` +\n`placement`, and the coordinate rule at the top of this file governs all\nnew-plan placement.\n\n<!-- SHARED-CORE:canvas-surface END -->";
-export declare const CANVAS_REFERENCE_MD = "# Canvas & artboard placement \u2014 single source of truth\n\nThis file is the canonical guide for how the visual-plan canvas works: artboard\nplacement, lane layout, annotations, patching, and the legacy kit tree. Read it\nin full before authoring or editing any canvas/artboard content; do not author\ncanvas layouts from memory or paraphrase these rules per mode.\n\n<!-- SHARED-CORE:canvas-surface START -->\n\n**The coordinate rule.** The `surface` locks each artboard's footprint and\naspect \u2014 never set artboard width/height and never use coordinates inside the\nwireframe HTML; board-level artboard `x`/`y` IS allowed when it creates clear\nlanes. Let canvas auto-placement handle simple one-row boards.\n\n**Lay out mixed canvases in lanes.** When a canvas contains broad browser /\ndesktop frames plus compact `mobile`, `popover`, or `panel` surfaces, do not put\neverything in one horizontal strip. Use board-level artboard `x`/`y` to reserve\nlanes with generous empty space: main flow on one row, compact surfaces in their\nown column or row, and loading/error states in a lower row. Keep at least 96px\nbetween rendered artboard rectangles plus room for annotation gutters; when a\nbroad browser/desktop frame sits beside a compact panel/popover, leave at least\n160px so frame borders, labels, and hover controls never touch. Connect only\nneighboring steps; never draw a long connector that skips across unrelated\nframes. Connector labels must sit in open canvas space. If the label would touch\nor cross either artboard, remove the label and explain the transition with a\nnearby annotation instead. Before handoff, inspect the top canvas at default zoom\nand move any frame whose label, connector, or annotation crosses another frame.\n\n**Board-unit spacing defaults.** The canvas coordinate system uses approximately 2 board units per screen pixel. `browser` frames occupy roughly 700 \u00D7 600 board units; `desktop` frames roughly 900 \u00D7 700 board units. Apply these minimum x/y gaps when placing frames explicitly \u2014 any less and frames will touch or overlap:\n\n- x-gap between `browser` frames: **\u2265 1100** (700-unit frame + 400-unit gutter)\n- x-gap between `desktop` frames: **\u2265 1300** (900-unit frame + 400-unit gutter)\n- y-gap between rows of any surface: **\u2265 1400** (includes frame height + section header + buffer)\n\nWhen in doubt, use larger values \u2014 the canvas auto-zooms to fit everything.\n\n**Canvas annotations are designer notes on the artboard.** When a top canvas is\npresent, sprinkle design-review notes near the frames they explain: a short\nheading, supporting text, and bullets \u2014 plain text layers, never bordered or\nshadowed cards, and never a box around a frame. The renderer spaces notes away\nfrom frames, so place each note by the frame it describes. Use an arrow only to\npoint at one specific control or transition; for a broad frame-level note, write\ntext beside the frame with no connector. Connectors are for real sequences only \u2014\nnever fake \"Step 1 \u2192 Step 2\" lines between independent states.\n\n**Do not create overlapping annotations.** Anchor each ordinary note to the\nframe it explains with `targetId` + `placement` (top/right/bottom/left), and\nomit `type` or use `type: \"note\"`. The renderer parks notes in a gutter beside\nthe frame and lays them out automatically. Do not use `type: \"callout\"`,\n`type: \"text\"`, `type: \"arrow\"`, x/y, or points for ordinary notes; those are\nfreeform review-markup layers and must be reserved for intentional markup in\nopen canvas space. Reserve arrows for a note that must point at one specific\ncontrol inside a frame; a note that simply sits beside its frame needs no arrow.\n\n**Patching.** Edit one wireframe, canvas annotation, diagram, or block with targeted `contentPatches`\n(for example `patch-wireframe-html`, `patch-diagram-html`, `update-block`,\n`replace-blocks`, `update-canvas-annotation`) rather\nthan regenerating the whole plan. `contentPatches` are part of the public MCP\naction schema, so Claude Code, Codex, Cursor, and other hosts can make surgical\nedits. If an agent is working from exported source files, use\n`read-visual-plan-source` / `patch-visual-plan-source`: `plan.mdx` holds\nfrontmatter plus markdown/document blocks, `canvas.mdx` holds\n`<DesignBoard>/<Section>/<Artboard>/<Screen>/<Annotation>/<Connector>`, and the\npatch action normalizes the MDX back into the same JSON runtime model. JSON is\nthe canonical runtime shape; MDX is the repo-friendly authoring/export surface.\nIn the browser, humans edit `rich-text` prose inline; agents should still use\n`update-rich-text` content patches or source patches for prose, and use\ncomments/structured patches for canvas, artboard, wireframe, and diagram edits.\nNever send a partial top-level `content` object as a shortcut to add a canvas,\nframe, or block: `content` is a full structured replacement, so omitted blocks\nor surfaces can disappear. If a full replacement is truly unavoidable, read the\ncomplete source/JSON first, include every existing block and surface in the new\npayload, and verify the source/export immediately after the update.\n\n**Never emit a titled artboard with no interior wireframe content.** Every artboard\nyou place on the canvas must carry an `html` wireframe or reference a wireframe\nblock via `blockId`; when using `blockId`, the referenced `wireframe` /\n`legacy-wireframe` block must remain in the plan. If you remove a duplicate\nwireframe from the document body, first move its `data` inline onto the\ncorresponding `content.canvas.frames[*].wireframe` / `legacyWireframe`. A\nlabel-only frame or a frame pointing at a deleted block renders empty and is\nrejected at parse time. If you only have a title, write it as a section header or\nannotation, not an empty artboard.\n\n**UI mockups belong in the top visual review area.** Static UI/product visuals\nlive on the canvas; multi-step UI flows get both canvas wireframes and a\nprototype. When the user asks for a mockup, UI state, loading state, layout,\nscreen, or visual comparison, make the canvas the primary home for that static\nvisual. When the user asks for a prototype or the plan contains a sequence the\nreviewer must feel, keep the canvas artboards and add `content.prototype` so the\ntop surface shows Wireframes / Prototype tabs. Architecture/code diagrams stay\ninline in the document (the SKILL.md Visual Surface Choice section owns that\nrule) unless the user explicitly asks for a spatial board. Document blocks\ncan explain, compare, or map implementation, but they should not host the\nprimary UI mockup or prototype just because `custom-html`, screenshots, or prose\nare easier to produce. If the canvas/prototype surface cannot represent the\nrequested UI fidelity, still keep the closest top-surface representation and\ncall out or extend the needed renderer capability. A skeleton/loading mockup\nalso lives in a canvas artboard \u2014 never move a mockup out of the canvas.\n\n**Storyboards are canvas artifacts, not document diagrams.** When the requested\noutput is a product flow, onboarding journey, \"light storyboard\", or canvas\nwireframe, author the flow as multiple top-canvas artboards with real screen\ncontent and neighboring connectors. Keep document-body `diagram` blocks for\narchitecture and mechanics that are not themselves user-visible screens. A\nstoryboard made from a single inline HTML diagram is the wrong surface.\n\nFor abstract product concepts, use the canvas to create the first \"I get it\"\nmoment: one real app state near the top showing how the concept appears to a\nuser, followed by separate annotations or diagrams for mechanics. Do not make\nthe first artboard a hybrid of app UI and architecture notes; the app screen\nshould be inspectable as product UI on its own.\n\n**Legacy kit tree.** Older plans set a `screen` array of `{ el, ...props }` kit\nnodes instead of `html`; the renderer still accepts and displays it so saved\nplans round-trip, but new plans emit `html`. Do not author fresh kit-tree\nscreens, and do not put nested kit components such as `<FrameScreen>`, `<Card>`,\n`<Row>`, `<Title>`, or `<Btn>` inside a canvas `<Screen>`. A new canvas artboard\nwith kit-tree children is a defect: replace it with\n`<Screen surface=\"...\" html={...} />` using the HTML wireframe rules. The HTML\npath is the one that gets the renderer-owned surface sizing, theme tokens,\nsketch/clean toggle, and safe text layout used by good document-body\nwireframes. Likewise, old or imported plans may carry coordinate-based regions\nor free-float x/y on notes; those are legacy escape hatches the renderer still\nshows but you must never produce. The gutter parks notes by `targetId` +\n`placement`, and the coordinate rule at the top of this file governs all\nnew-plan placement.\n\n<!-- SHARED-CORE:canvas-surface END -->\n";
-export declare const CANVAS_REFERENCE_POINTER = "The canvas is the single source of truth for static UI mockups: the `surface`\nlocks each artboard's footprint, mixed surfaces lay out\nin lanes, annotations are plain-text designer notes anchored by\n`targetId`/`placement`, and edits are surgical `contentPatches`. Before\nauthoring or editing ANY canvas, artboard, or annotation, READ\n`references/canvas.md` in this skill directory \u2014 it is the single source of truth\nfor canvas/artboard mechanics. Do not author canvas layouts from memory.";
+export declare const CANVAS_SURFACE_CORE = "<!-- SHARED-CORE:canvas-surface START -->\n\n**The coordinate rule.** The `surface` sets each artboard's default footprint\nand width \u2014 never set width or use coordinates inside the wireframe HTML.\nBoard-level artboard `x`/`y` IS allowed when it creates clear lanes. A\nlarger explicit artboard `height` is allowed when the screen's content needs\nmore vertical room; canvas frames do not scroll, so reserve enough height to\nshow the entire UI. Let canvas auto-placement handle simple one-row boards.\n\n**Lay out mixed canvases in lanes.** When a canvas contains broad browser /\ndesktop frames plus compact `mobile`, `popover`, or `panel` surfaces, do not put\neverything in one horizontal strip. Use board-level artboard `x`/`y` to reserve\nlanes with generous empty space: main flow on one row, compact surfaces in their\nown column or row, and loading/error states in a lower row. Keep at least 96px\nbetween rendered artboard rectangles plus room for annotation gutters; when a\nbroad browser/desktop frame sits beside a compact panel/popover, leave at least\n160px so frame borders, labels, and hover controls never touch. Connect only\nneighboring steps; never draw a long connector that skips across unrelated\nframes. Connector labels must sit in open canvas space. If the label would touch\nor cross either artboard, remove the label and explain the transition with a\nnearby annotation instead. Before handoff, inspect the top canvas at default zoom\nand move any frame whose label, connector, or annotation crosses another frame.\n\n**Board-unit spacing defaults.** The canvas coordinate system uses approximately 2 board units per screen pixel. `browser` frames occupy roughly 700 \u00D7 600 board units; `desktop` frames roughly 900 \u00D7 700 board units. Apply these minimum x/y gaps when placing frames explicitly \u2014 any less and frames will touch or overlap:\n\n- x-gap between `browser` frames: **\u2265 1100** (700-unit frame + 400-unit gutter)\n- x-gap between `desktop` frames: **\u2265 1300** (900-unit frame + 400-unit gutter)\n- y-gap between rows of any surface: **\u2265 1400** (includes frame height + section header + buffer)\n\nWhen in doubt, use larger values \u2014 the canvas auto-zooms to fit everything.\n\n**Full-content artboards.** Canvas frames are pan/zoom surfaces, not scroll\ncontainers. Keep wireframe HTML in natural document flow without an inner\nscroll region or fixed child height. If the screen is taller than the default\nsurface preset, set the artboard's `height` to the measured content height plus\nbreathing room; keep the surface width unchanged. Before handoff, inspect the\nbottom edge of every artboard at default zoom and confirm no control, row, or\nfooter is clipped.\n\n**Canvas annotations are designer notes on the artboard.** When a top canvas is\npresent, sprinkle design-review notes near the frames they explain: a short\nheading, supporting text, and bullets \u2014 plain text layers, never bordered or\nshadowed cards, and never a box around a frame. The renderer spaces notes away\nfrom frames, so place each note by the frame it describes. Use an arrow only to\npoint at one specific control or transition; for a broad frame-level note, write\ntext beside the frame with no connector. Connectors are for real sequences only \u2014\nnever fake \"Step 1 \u2192 Step 2\" lines between independent states.\n\n**Do not create overlapping annotations.** Anchor each ordinary note to the\nframe it explains with `targetId` + `placement` (top/right/bottom/left), and\nomit `type` or use `type: \"note\"`. The renderer parks notes in a gutter beside\nthe frame and lays them out automatically. Do not use `type: \"callout\"`,\n`type: \"text\"`, `type: \"arrow\"`, x/y, or points for ordinary notes; those are\nfreeform review-markup layers and must be reserved for intentional markup in\nopen canvas space. Reserve arrows for a note that must point at one specific\ncontrol inside a frame; a note that simply sits beside its frame needs no arrow.\n\n**Patching.** Edit one wireframe, canvas annotation, diagram, or block with targeted `contentPatches`\n(for example `patch-wireframe-html`, `patch-diagram-html`, `update-block`,\n`replace-blocks`, `update-canvas-annotation`) rather\nthan regenerating the whole plan. `contentPatches` are part of the public MCP\naction schema, so Claude Code, Codex, Cursor, and other hosts can make surgical\nedits. If an agent is working from exported source files, use\n`read-visual-plan-source` / `patch-visual-plan-source`: `plan.mdx` holds\nfrontmatter plus markdown/document blocks, `canvas.mdx` holds\n`<DesignBoard>/<Section>/<Artboard>/<Screen>/<Annotation>/<Connector>`, and the\npatch action normalizes the MDX back into the same JSON runtime model. JSON is\nthe canonical runtime shape; MDX is the repo-friendly authoring/export surface.\nIn the browser, humans edit `rich-text` prose inline; agents should still use\n`update-rich-text` content patches or source patches for prose, and use\ncomments/structured patches for canvas, artboard, wireframe, and diagram edits.\nNever send a partial top-level `content` object as a shortcut to add a canvas,\nframe, or block: `content` is a full structured replacement, so omitted blocks\nor surfaces can disappear. If a full replacement is truly unavoidable, read the\ncomplete source/JSON first, include every existing block and surface in the new\npayload, and verify the source/export immediately after the update.\n\n**Never emit a titled artboard with no interior wireframe content.** Every artboard\nyou place on the canvas must carry an `html` wireframe or reference a wireframe\nblock via `blockId`; when using `blockId`, the referenced `wireframe` /\n`legacy-wireframe` block must remain in the plan. If you remove a duplicate\nwireframe from the document body, first move its `data` inline onto the\ncorresponding `content.canvas.frames[*].wireframe` / `legacyWireframe`. A\nlabel-only frame or a frame pointing at a deleted block renders empty and is\nrejected at parse time. If you only have a title, write it as a section header or\nannotation, not an empty artboard.\n\n**UI mockups belong in the top visual review area.** Static UI/product visuals\nlive on the canvas; multi-step UI flows get both canvas wireframes and a\nprototype. When the user asks for a mockup, UI state, loading state, layout,\nscreen, or visual comparison, make the canvas the primary home for that static\nvisual. When the user asks for a prototype or the plan contains a sequence the\nreviewer must feel, keep the canvas artboards and add `content.prototype` so the\ntop surface shows Wireframes / Prototype tabs. Architecture/code diagrams stay\ninline in the document (the SKILL.md Visual Surface Choice section owns that\nrule) unless the user explicitly asks for a spatial board. Document blocks\ncan explain, compare, or map implementation, but they should not host the\nprimary UI mockup or prototype just because `custom-html`, screenshots, or prose\nare easier to produce. If the canvas/prototype surface cannot represent the\nrequested UI fidelity, still keep the closest top-surface representation and\ncall out or extend the needed renderer capability. A skeleton/loading mockup\nalso lives in a canvas artboard \u2014 never move a mockup out of the canvas.\n\n**Storyboards are canvas artifacts, not document diagrams.** When the requested\noutput is a product flow, onboarding journey, \"light storyboard\", or canvas\nwireframe, author the flow as multiple top-canvas artboards with real screen\ncontent and neighboring connectors. Keep document-body `diagram` blocks for\narchitecture and mechanics that are not themselves user-visible screens. A\nstoryboard made from a single inline HTML diagram is the wrong surface.\n\nFor abstract product concepts, use the canvas to create the first \"I get it\"\nmoment: one real app state near the top showing how the concept appears to a\nuser, followed by separate annotations or diagrams for mechanics. Do not make\nthe first artboard a hybrid of app UI and architecture notes; the app screen\nshould be inspectable as product UI on its own.\n\n**Legacy kit tree.** Older plans set a `screen` array of `{ el, ...props }` kit\nnodes instead of `html`; the renderer still accepts and displays it so saved\nplans round-trip, but new plans emit `html`. Do not author fresh kit-tree\nscreens, and do not put nested kit components such as `<FrameScreen>`, `<Card>`,\n`<Row>`, `<Title>`, or `<Btn>` inside a canvas `<Screen>`. A new canvas artboard\nwith kit-tree children is a defect: replace it with\n`<Screen surface=\"...\" html={...} />` using the HTML wireframe rules. The HTML\npath is the one that gets the renderer-owned surface sizing, theme tokens,\nsketch/clean toggle, and safe text layout used by good document-body\nwireframes. Likewise, old or imported plans may carry coordinate-based regions\nor free-float x/y on notes; those are legacy escape hatches the renderer still\nshows but you must never produce. The gutter parks notes by `targetId` +\n`placement`, and the coordinate rule at the top of this file governs all\nnew-plan placement.\n\n<!-- SHARED-CORE:canvas-surface END -->";
+export declare const CANVAS_REFERENCE_MD = "# Canvas & artboard placement \u2014 single source of truth\n\nThis file is the canonical guide for how the visual-plan canvas works: artboard\nplacement, lane layout, annotations, patching, and the legacy kit tree. Read it\nin full before authoring or editing any canvas/artboard content; do not author\ncanvas layouts from memory or paraphrase these rules per mode.\n\n<!-- SHARED-CORE:canvas-surface START -->\n\n**The coordinate rule.** The `surface` sets each artboard's default footprint\nand width \u2014 never set width or use coordinates inside the wireframe HTML.\nBoard-level artboard `x`/`y` IS allowed when it creates clear lanes. A\nlarger explicit artboard `height` is allowed when the screen's content needs\nmore vertical room; canvas frames do not scroll, so reserve enough height to\nshow the entire UI. Let canvas auto-placement handle simple one-row boards.\n\n**Lay out mixed canvases in lanes.** When a canvas contains broad browser /\ndesktop frames plus compact `mobile`, `popover`, or `panel` surfaces, do not put\neverything in one horizontal strip. Use board-level artboard `x`/`y` to reserve\nlanes with generous empty space: main flow on one row, compact surfaces in their\nown column or row, and loading/error states in a lower row. Keep at least 96px\nbetween rendered artboard rectangles plus room for annotation gutters; when a\nbroad browser/desktop frame sits beside a compact panel/popover, leave at least\n160px so frame borders, labels, and hover controls never touch. Connect only\nneighboring steps; never draw a long connector that skips across unrelated\nframes. Connector labels must sit in open canvas space. If the label would touch\nor cross either artboard, remove the label and explain the transition with a\nnearby annotation instead. Before handoff, inspect the top canvas at default zoom\nand move any frame whose label, connector, or annotation crosses another frame.\n\n**Board-unit spacing defaults.** The canvas coordinate system uses approximately 2 board units per screen pixel. `browser` frames occupy roughly 700 \u00D7 600 board units; `desktop` frames roughly 900 \u00D7 700 board units. Apply these minimum x/y gaps when placing frames explicitly \u2014 any less and frames will touch or overlap:\n\n- x-gap between `browser` frames: **\u2265 1100** (700-unit frame + 400-unit gutter)\n- x-gap between `desktop` frames: **\u2265 1300** (900-unit frame + 400-unit gutter)\n- y-gap between rows of any surface: **\u2265 1400** (includes frame height + section header + buffer)\n\nWhen in doubt, use larger values \u2014 the canvas auto-zooms to fit everything.\n\n**Full-content artboards.** Canvas frames are pan/zoom surfaces, not scroll\ncontainers. Keep wireframe HTML in natural document flow without an inner\nscroll region or fixed child height. If the screen is taller than the default\nsurface preset, set the artboard's `height` to the measured content height plus\nbreathing room; keep the surface width unchanged. Before handoff, inspect the\nbottom edge of every artboard at default zoom and confirm no control, row, or\nfooter is clipped.\n\n**Canvas annotations are designer notes on the artboard.** When a top canvas is\npresent, sprinkle design-review notes near the frames they explain: a short\nheading, supporting text, and bullets \u2014 plain text layers, never bordered or\nshadowed cards, and never a box around a frame. The renderer spaces notes away\nfrom frames, so place each note by the frame it describes. Use an arrow only to\npoint at one specific control or transition; for a broad frame-level note, write\ntext beside the frame with no connector. Connectors are for real sequences only \u2014\nnever fake \"Step 1 \u2192 Step 2\" lines between independent states.\n\n**Do not create overlapping annotations.** Anchor each ordinary note to the\nframe it explains with `targetId` + `placement` (top/right/bottom/left), and\nomit `type` or use `type: \"note\"`. The renderer parks notes in a gutter beside\nthe frame and lays them out automatically. Do not use `type: \"callout\"`,\n`type: \"text\"`, `type: \"arrow\"`, x/y, or points for ordinary notes; those are\nfreeform review-markup layers and must be reserved for intentional markup in\nopen canvas space. Reserve arrows for a note that must point at one specific\ncontrol inside a frame; a note that simply sits beside its frame needs no arrow.\n\n**Patching.** Edit one wireframe, canvas annotation, diagram, or block with targeted `contentPatches`\n(for example `patch-wireframe-html`, `patch-diagram-html`, `update-block`,\n`replace-blocks`, `update-canvas-annotation`) rather\nthan regenerating the whole plan. `contentPatches` are part of the public MCP\naction schema, so Claude Code, Codex, Cursor, and other hosts can make surgical\nedits. If an agent is working from exported source files, use\n`read-visual-plan-source` / `patch-visual-plan-source`: `plan.mdx` holds\nfrontmatter plus markdown/document blocks, `canvas.mdx` holds\n`<DesignBoard>/<Section>/<Artboard>/<Screen>/<Annotation>/<Connector>`, and the\npatch action normalizes the MDX back into the same JSON runtime model. JSON is\nthe canonical runtime shape; MDX is the repo-friendly authoring/export surface.\nIn the browser, humans edit `rich-text` prose inline; agents should still use\n`update-rich-text` content patches or source patches for prose, and use\ncomments/structured patches for canvas, artboard, wireframe, and diagram edits.\nNever send a partial top-level `content` object as a shortcut to add a canvas,\nframe, or block: `content` is a full structured replacement, so omitted blocks\nor surfaces can disappear. If a full replacement is truly unavoidable, read the\ncomplete source/JSON first, include every existing block and surface in the new\npayload, and verify the source/export immediately after the update.\n\n**Never emit a titled artboard with no interior wireframe content.** Every artboard\nyou place on the canvas must carry an `html` wireframe or reference a wireframe\nblock via `blockId`; when using `blockId`, the referenced `wireframe` /\n`legacy-wireframe` block must remain in the plan. If you remove a duplicate\nwireframe from the document body, first move its `data` inline onto the\ncorresponding `content.canvas.frames[*].wireframe` / `legacyWireframe`. A\nlabel-only frame or a frame pointing at a deleted block renders empty and is\nrejected at parse time. If you only have a title, write it as a section header or\nannotation, not an empty artboard.\n\n**UI mockups belong in the top visual review area.** Static UI/product visuals\nlive on the canvas; multi-step UI flows get both canvas wireframes and a\nprototype. When the user asks for a mockup, UI state, loading state, layout,\nscreen, or visual comparison, make the canvas the primary home for that static\nvisual. When the user asks for a prototype or the plan contains a sequence the\nreviewer must feel, keep the canvas artboards and add `content.prototype` so the\ntop surface shows Wireframes / Prototype tabs. Architecture/code diagrams stay\ninline in the document (the SKILL.md Visual Surface Choice section owns that\nrule) unless the user explicitly asks for a spatial board. Document blocks\ncan explain, compare, or map implementation, but they should not host the\nprimary UI mockup or prototype just because `custom-html`, screenshots, or prose\nare easier to produce. If the canvas/prototype surface cannot represent the\nrequested UI fidelity, still keep the closest top-surface representation and\ncall out or extend the needed renderer capability. A skeleton/loading mockup\nalso lives in a canvas artboard \u2014 never move a mockup out of the canvas.\n\n**Storyboards are canvas artifacts, not document diagrams.** When the requested\noutput is a product flow, onboarding journey, \"light storyboard\", or canvas\nwireframe, author the flow as multiple top-canvas artboards with real screen\ncontent and neighboring connectors. Keep document-body `diagram` blocks for\narchitecture and mechanics that are not themselves user-visible screens. A\nstoryboard made from a single inline HTML diagram is the wrong surface.\n\nFor abstract product concepts, use the canvas to create the first \"I get it\"\nmoment: one real app state near the top showing how the concept appears to a\nuser, followed by separate annotations or diagrams for mechanics. Do not make\nthe first artboard a hybrid of app UI and architecture notes; the app screen\nshould be inspectable as product UI on its own.\n\n**Legacy kit tree.** Older plans set a `screen` array of `{ el, ...props }` kit\nnodes instead of `html`; the renderer still accepts and displays it so saved\nplans round-trip, but new plans emit `html`. Do not author fresh kit-tree\nscreens, and do not put nested kit components such as `<FrameScreen>`, `<Card>`,\n`<Row>`, `<Title>`, or `<Btn>` inside a canvas `<Screen>`. A new canvas artboard\nwith kit-tree children is a defect: replace it with\n`<Screen surface=\"...\" html={...} />` using the HTML wireframe rules. The HTML\npath is the one that gets the renderer-owned surface sizing, theme tokens,\nsketch/clean toggle, and safe text layout used by good document-body\nwireframes. Likewise, old or imported plans may carry coordinate-based regions\nor free-float x/y on notes; those are legacy escape hatches the renderer still\nshows but you must never produce. The gutter parks notes by `targetId` +\n`placement`, and the coordinate rule at the top of this file governs all\nnew-plan placement.\n\n<!-- SHARED-CORE:canvas-surface END -->\n";
+export declare const CANVAS_REFERENCE_POINTER = "The canvas is the single source of truth for static UI mockups: the `surface`\nsets each artboard's default footprint and width, while an explicit taller\n`height` keeps long non-scrolling screens fully visible; mixed surfaces lay out\nin lanes, annotations are plain-text designer notes anchored by\n`targetId`/`placement`, and edits are surgical `contentPatches`. Before\nauthoring or editing ANY canvas, artboard, or annotation, READ\n`references/canvas.md` in this skill directory \u2014 it is the single source of truth\nfor canvas/artboard mechanics. Do not author canvas layouts from memory.";
 //# sourceMappingURL=canvas.d.ts.map

package/dist/cli/skills-content/canvas.js

@@ -2,10 +2,12 @@
 // (visual-recap renders standalone wireframes, not a canvas).
 export const CANVAS_SURFACE_CORE = `<!-- SHARED-CORE:canvas-surface START -->
 
-**The coordinate rule.** The \`surface\` locks each artboard's footprint and
-aspect — never set artboard width/height and never use coordinates inside the
-wireframe HTML; board-level artboard \`x\`/\`y\` IS allowed when it creates clear
-lanes. Let canvas auto-placement handle simple one-row boards.
+**The coordinate rule.** The \`surface\` sets each artboard's default footprint
+and width — never set width or use coordinates inside the wireframe HTML.
+Board-level artboard \`x\`/\`y\` IS allowed when it creates clear lanes. A
+larger explicit artboard \`height\` is allowed when the screen's content needs
+more vertical room; canvas frames do not scroll, so reserve enough height to
+show the entire UI. Let canvas auto-placement handle simple one-row boards.
 
 **Lay out mixed canvases in lanes.** When a canvas contains broad browser /
 desktop frames plus compact \`mobile\`, \`popover\`, or \`panel\` surfaces, do not put
@@ -29,6 +31,14 @@ and move any frame whose label, connector, or annotation crosses another frame.
 
 When in doubt, use larger values — the canvas auto-zooms to fit everything.
 
+**Full-content artboards.** Canvas frames are pan/zoom surfaces, not scroll
+containers. Keep wireframe HTML in natural document flow without an inner
+scroll region or fixed child height. If the screen is taller than the default
+surface preset, set the artboard's \`height\` to the measured content height plus
+breathing room; keep the surface width unchanged. Before handoff, inspect the
+bottom edge of every artboard at default zoom and confirm no control, row, or
+footer is clipped.
+
 **Canvas annotations are designer notes on the artboard.** When a top canvas is
 present, sprinkle design-review notes near the frames they explain: a short
 heading, supporting text, and bullets — plain text layers, never bordered or
@@ -143,7 +153,8 @@ ${CANVAS_SURFACE_CORE}
 // files so the SKILL.md stays lean (progressive disclosure); the agent loads the
 // detail on demand.
 export const CANVAS_REFERENCE_POINTER = `The canvas is the single source of truth for static UI mockups: the \`surface\`
-locks each artboard's footprint, mixed surfaces lay out
+sets each artboard's default footprint and width, while an explicit taller
+\`height\` keeps long non-scrolling screens fully visible; mixed surfaces lay out
 in lanes, annotations are plain-text designer notes anchored by
 \`targetId\`/\`placement\`, and edits are surgical \`contentPatches\`. Before
 authoring or editing ANY canvas, artboard, or annotation, READ

package/dist/cli/skills-content/visual-plan-skill.d.ts

@@ -1,2 +1,2 @@
-export declare const VISUAL_PLANS_SKILL_MD = "---\nname: visual-plan\ndescription: >-\n  Turn ordinary text plans into rich interactive visual plans with diagrams,\n  file maps, annotated code, open questions, and UI/prototype review when\n  useful.\nmetadata:\n  visibility: exported\n---\n\n# Agent-Native Plans\n\nAgent-Native Plans is structured visual planning mode for coding agents. Build\nthe plan you would normally write in Markdown, but as a scannable document with\neditable blocks mixed in: inline diagrams, code snippets,\nopen questions, and an optional top visual review area (wireframe canvas, live\nprototype, or both in tabs). Architecture and backend plans stay document-only;\nUI and product plans start with the top canvas/prototype (the Visual Surface\nChoice section owns that rule).\n\n`/visual-plan` is the packaged command and main entry point. Choose the review\nmode from the task: UI-first when the work is primarily product UI and review\nshould start with screens, prototype-first when review should start with a\nfunctional live prototype, design-first when review needs full-fidelity branded\nscreens, or visual-intake when the user explicitly wants a questionnaire before\nplanning. When a Codex, Claude Code, Markdown, or pasted plan already exists,\n`/visual-plan` uses that source plan as the starting point and builds the review\nsurface from it instead of starting over.\n\n## When To Use\n\nCreate or adapt a visual plan whenever the plan would be better as a reviewable\nartifact than a chat paragraph. This includes modest work such as a single UI\nsurface with states, a small workflow, a before/after product change, or a\ncomponent/API/data-shape decision that needs alignment, plus larger multi-file,\nambiguous, long-running, risky, or UI-heavy work. Use it when architecture /\ndata flow / UI direction / options / open questions would benefit from inline\ndiagrams or structured blocks, when the user needs to react to a direction\nbefore you implement, or when an existing text plan needs a richer review\nsurface.\n\n## Plan Discipline\n\n- **Gate thoughtfully.** A visual plan is a richer review surface, not only a\n  tool for giant projects. Use it when the user needs to see, compare, comment\n  on, or approve a direction before code, even for a modest UI/state/workflow\n  change. Skip it for truly trivial, unambiguous work \u2014 typos, one-line fixes, a\n  single well-specified function, anything whose diff you could describe in one\n  sentence \u2014 and just make the change. Never pad a plan with filler and never\n  ship a single-step plan.\n- **Research before you draft.** Read the real files, actions, schema, and\n  patterns first; name actual files, symbols, and data shapes instead of\n  inventing them. Check existing `actions/` before proposing endpoints and prefer\n  named client helpers over raw fetch. Delegate wide exploration to a sub-agent.\n  Lead with reuse: for each step, name what it reuses \u2014 existing actions, schema,\n  components, helpers \u2014 before what it adds, so the plan explains the genuinely new\n  delta instead of redescribing what already exists.\n- **Decide the hard-to-reverse bets first.** For non-trivial backend, data, or API\n  work, sketch where the feature is headed, then call out the decisions that are\n  expensive to undo once data or callers depend on them \u2014 wire format, public ids,\n  data-model shape, auth and ownership boundaries \u2014 and get those right in the plan\n  even if most of the feature ships later. Then scope to the smallest first cut that\n  proves the approach without foreclosing it, stating both what is in and what is\n  explicitly deferred.\n- **Keep examples at the right altitude.** When the user's idea is a broad\n  framework, product, or operating-model change, do not collapse it into the\n  first concrete example, provider, or sync path they mention. Separate the core\n  abstraction from motivating examples and app/provider adapters. Use examples\n  to make the plan legible, but label them as examples unless they are the whole\n  requested scope.\n- **Publish standalone plans.** If the user pasted, referenced, or already has a\n  Codex / Claude Code / Markdown plan, treat it as source material, but rewrite\n  the published plan as a clean standalone proposal. Preserve the source plan's\n  useful intent and codebase facts, label inferred visuals as inferred, and avoid\n  revision language such as \"preserve the prior plan\", \"do not drop the old\n  idea\", \"unlike the previous version\", or \"this revision changes...\". A reader\n  who never saw the chat or earlier drafts should understand the plan.\n- **Make the first read concrete.** If the plan is meant to be shared with\n  someone outside the chat, or if the concept is abstract, lead near the top with\n  one concrete product example before mode tables, architecture, or roadmaps. For\n  UI-capable concepts, that usually means a top-canvas app state that shows the\n  real user workflow in product terms. Do not rely on phrases that only make\n  sense in conversation, and do not frame the plan as \"not the old idea\"; state\n  the positive model directly.\n- **Planning is read-only.** Make no source edits while building or reviewing the\n  plan. Start editing only after the user approves the direction.\n- **Clarify vs. assume.** Do not ask how to build it \u2014 explore and present the\n  approach and options in the plan. Ask a clarifying question only when an\n  ambiguity would change the design and you cannot resolve it from the code; use\n  the host agent's normal ask-user-question flow and batch 2-4 high-leverage\n  questions before finalizing. Do not call `create-visual-questions` for\n  ordinary clarification or preflight; reserve it for the visual-intake mode when\n  the user explicitly asks for a visual intake questionnaire. Otherwise state the\n  assumption explicitly and proceed, and keep anything unresolved in the plan's\n  single bottom `question-form` Open Questions block. For complex plans, do a\n  final open-question pass before handoff: if a decision would affect\n  architecture, scope, UX, data shape, or rollout, either decide it in the plan\n  with rationale or put it in that bottom form with a recommended default.\n- **The plan is the approval gate.** After surfacing it, ask the user to review\n  and approve before you write code, and name which files/areas the work touches.\n  Presenting the plan and requesting sign-off is the approval step \u2014 do not ask a\n  separate \"does this look good?\" question.\n- **The document is the source of truth, not the chat.** When scope shifts,\n  update the plan with `update-visual-plan` rather than only changing course in\n  chat, and make the updated document stand alone. Do not describe the update as\n  a correction to an earlier draft inside the plan itself. Re-read the approved\n  plan before major steps.\n\n## Create A Structured Agent-Native Plan \u2014 Never Inline\n\nThe deliverable is ALWAYS a structured Agent-Native Plan, not a chat-only plan.\nThe hosted Plan MCP connector (`plan` server, or legacy `agent-native-plans`) is\nthe default collaboration and commenting surface; it is not a reason to reject\nthe planning pattern as an external dependency or rented layer. Plans are\nportable source artifacts (`plan.mdx`, optional `canvas.mdx` /\n`prototype.mdx`, JSON, and HTML export), and ownership-sensitive workflows can\nuse local-files mode or a self-hosted/custom Plan app URL without abandoning the\nskill's review discipline. Do not advise the user to skip `/visual-plan` because\nthe default surface is hosted; choose the right Plan mode for the user's\nownership, privacy, sharing, and branding needs.\n\nBy default, create the plan via the Plan MCP connector and NEVER hand it over as\ninline chat content \u2014 no Markdown prose, ASCII sketch, table, or fenced\nwireframe. If the `plan` (or legacy `agent-native-plans`) tools are not visible,\ndiscover them through the host's `tool_search` first; if they are still missing,\nSTOP and give the user the client-specific reconnect step rather than improvising\nan inline plan. Before publishing, or whenever a connector or auth error appears,\nREAD `references/connection.md` in this skill directory \u2014 it is the single source\nof truth for the never-inline rule, connector discovery, and the per-client\nreconnect steps. Local-files privacy mode (after Tool Guidance) is the exception.\n\n## Core Workflow\n\nThis section describes the default hosted Plan MCP workflow. If\n`AGENT_NATIVE_PLANS_MODE=local-files` is set, or the user asks for fully local\nfiles/no hosted Plan writes, use **Local-Files Privacy Mode** instead; carry\nforward only the code-research and plan-composition guidance here.\n\n1. Follow the host agent's normal planning flow: inspect the codebase, delegate\n   wide exploration when useful, gather the info needed, and ask native\n   clarifying questions as needed before generating the plan. If a source plan\n   already exists, gather its exact text from the user's paste, a referenced\n   file, or recent visible agent context; do not invent source text.\n2. Call `get-plan-blocks` for the authoritative block catalog \u2014 do not author\n   from memorized tags. Then call the mode-matched create tool:\n   `create-visual-plan` for document-first plans (architecture, backend, data,\n   refactor, API), `create-ui-plan` for UI-first plans, `create-prototype-plan`\n   for prototype-first plans, `create-plan-design` for design-first plans,\n   `create-visual-questions` only when the user explicitly asks for a visual\n   intake questionnaire. When a source plan already exists,\n   pass it as `planText` and preserve the original plan's useful intent while\n   producing a standalone plan document, not a revision memo.\n3. For UI/product plans, compose the top canvas first with the primary\n   wireframes and annotated states, then write the document with native blocks\n   (see `references/canvas.md` and `references/document-quality.md`). For\n   broad product architecture plans with a user-facing implication, add a\n   concrete \"what this looks like in the app\" visual before the abstract\n   architecture or mode tables. Keep the document close to the standalone\n   Markdown plan the agent would normally output. If an existing plan was\n   provided, carry forward the right facts and decisions without referring to\n   the previous draft or explaining how this version differs. For non-visual\n   plans, skip the top visual surface (Visual Surface Choice below owns the rule)\n   and put `diagram`, `data-model`,\n   `api-endpoint`, `diff`, `file-tree`, `code`, and `annotated-code` blocks\n   directly next to the relevant prose.\n   Wide document layout is renderer-owned and intentionally allowlisted: only\n   literal code-review surfaces (`diff`, `annotated-code`) and `tabs` blocks\n   with vertical orientation or diff-like children break out wider than prose.\n   Keep `api-endpoint`, `openapi-spec`, `data-model`, `json-explorer`,\n   `wireframe`, question, and `custom-html` blocks in normal document flow unless\n   their own renderer says otherwise.\n4. Surface the returned Plans link or inline MCP App and ask the user to review.\n   Always include the actual URL in chat so the next step is a click in CLI or\n   other text-only hosts. When the host exposes an embedded browser/preview panel\n   and a tool can open arbitrary URLs there, open the returned plan URL\n   automatically for convenient review \u2014 a convenience and smoke test, never the\n   only handoff or the access\n   model. Plans should load out of the box for the local agent and local browser\n   session; if a signed-in embedded browser cannot read a local plan that an\n   anonymous/tool check can read, fix the app/action ownership or access path\n   rather than patching one plan by hand. For high-stakes plans (architecture,\n   backend, data, multi-file, or risky), also kick off the self-review pass in\n   **Self-Review Before Handoff** while the user reads, instead of blocking the\n   handoff on it.\n5. For hosted plans, call `get-plan-feedback` before editing, after review,\n   after any long pause,\n   and before the final response. Treat `anchorDetails`, resolver intent, recent\n   review events, and any focused screenshots from browser handoff as the source\n   of truth for exactly what changed and exactly what each comment points at.\n6. For hosted plans, apply changes with `update-visual-plan`, preferring\n   targeted `contentPatches`.\n   Treat the top-level `content` payload as a full replacement, not a merge; do\n   not send a partial `content` object to add a canvas or one block. If a full\n   replacement or `replace-blocks` is unavoidable, call `get-visual-plan`\n   immediately before the write, pass its `plan.updatedAt` as\n   `expectedUpdatedAt`, and carry forward every existing block and visual\n   surface. Never reuse a revision from an earlier read or feedback payload.\n   For source-control friendly edits, use granular `patch-visual-plan-source`\n   operations against the MDX files instead of regenerating the plan;\n   `replace-file` is also destructive and requires the same fresh\n   `expectedUpdatedAt` fence.\n7. After every hosted-plan write, call `get-visual-plan` again and compare the\n   persisted text, block IDs/counts, canvas frames, and prototype with the\n   intended result. A successful mutation response is not proof that unrelated\n   content survived. If the edit addressed agent-targeted feedback, only after\n   this verification call `resolve-plan-comment` for the thread and\n   `consume-plan-feedback` for its comments; do both so addressed feedback is\n   neither visibly open nor returned as pending work.\n8. For hosted plans, export with `export-visual-plan` only when the user wants a\n   shareable receipt or repo-check-in artifacts.\n\n## Self-Review Before Handoff\n\nThis adversarial self-review pass is opt-in, not default: run it only for\nhigh-stakes plans \u2014 irreversible migrations, security-sensitive work, or when\nthe user explicitly asks for extra rigor \u2014 and skip it otherwise. It roughly\ndoubles the cost of plan generation, so the default for small, UI-only,\nsingle-decision, or ordinary plans is to skip it, not to run it. Keep the pass\ncheap and non-blocking when it does run:\n\n- **Surface the plan first, review concurrently.** Post the link and let the user\n  start reading, then run the review in parallel \u2014 never make the user wait on it.\n- **Review the written plan; do not re-research.** Critique the plan text and its\n  own blocks. The grounding was already done while drafting, so the review checks\n  the output instead of re-exploring the repo.\n- **Spawn one skeptical reviewer** whose only job is to find what is weak, missing,\n  or wrong \u2014 not to praise. Point it at: hard-to-reverse decisions made implicitly\n  or not at all (wire format, public ids, data-model shape, auth, ownership); steps\n  not anchored in real files or symbols; a menu of options where the plan should\n  commit to one; obvious missing decisions (\"what happens when X?\", \"why not Y?\");\n  and padding or single-step filler.\n- **Fix vs. ask.** Apply clear-cut fixes yourself with `update-visual-plan`\n  `contentPatches` \u2014 vague non-goals, unanchored claims, an obvious missing\n  decision. Route genuine judgment calls back to the user instead: add them to the\n  bottom `question-form` Open Questions block or batch them into the normal\n  ask-user-question flow. Do not silently decide them.\n- **Do not surprise the user mid-read.** On a large plan, apply the patches before\n  the editor loads; otherwise note briefly that a self-review is running so the\n  plan changing under them is expected. When you next respond, summarize what the\n  review changed and what it surfaced for the user to decide.\n\n## Visual Surface Choice\n\nChoose the surface before creating the plan or after reading the source plan. Do\nnot add visual chrome by default:\n\nFor UI/product plans, the top canvas is usually the primary review surface. Put\nthe first meaningful wireframes there, not buried as document-body blocks. Use\nmultiple canvas artboards when states matter, such as the default view, an\noverflow menu or popover, a side panel, loading, or error. Put short annotations\nbeside frames with `targetId` plus `placement`; keep implementation details,\ntradeoffs, file maps, data contracts, risks, and verification in the document\nbody below the canvas.\n\nWhen the user asks for a flow, storyboard, journey, wireframe, canvas, or \"what\nthis looks like\", treat that as a canvas-first request. Make one artboard per\nuser-visible state, connect only adjacent transitions, and use short canvas\nannotations for the product notes. Do not substitute a document-body `diagram`\nblock for the requested storyboard just because HTML diagrams are faster to\nwrite; diagrams belong below the canvas for backend mechanics, architecture, or\ndata-flow explanation.\n\nKeep product wireframes and explanatory/meta diagrams separate. Start with pure\nscreens that look like the app state under discussion, without callout prose or\narchitecture notes embedded inside the UI. Put arrows, labels, contracts, data\nflow, and mode explanations in separate annotations, separate canvas diagrams,\nor the document body.\n\nWhen the plan touches an existing app, inspect the current shell/components\nbefore drawing. The first artboard should look like the real app at the same\ndensity: existing sidebars, toolbar placement, overflow menus, app chrome, and\nframework agent chrome stay in their real places. Model secondary surfaces as\nseparate states, such as a top-right overflow popover, sheet, panel, loading\nstate, or separate AgentSidebar, rather than inventing a permanent inspector or\nfolding framework chrome into the product UI.\n\n- **No visual surface** for architecture-only, backend-only, data migration,\n  copy-only, or otherwise non-visual plans. Do not use the top canvas for\n  architecture diagrams, dependency maps, file plans, API contracts, or\n  data-flow-only reviews. Use a strong document with local inline diagrams\n  only when relationships need a visual explanation, usually one spatial diagram\n  per recommendation or decision. Prefer grouped regions, layers, quadrants,\n  matrices, or before/after panels over a single-axis chain unless the\n  relationship is truly sequential.\n- **Canvas only** for one static screen, a before/after comparison, a component\n  state, a small popover, or a visual direction that does not require clicking.\n  Put those wireframes in `content.canvas` and omit `content.prototype`.\n- **Canvas + prototype** for multi-step UI flows, onboarding, wizards,\n  review/approval flows, navigation changes, or anything where the reviewer\n  needs to operate the behavior. Keep the static wireframes in\n  `content.canvas`, add the aligned functional prototype in\n  `content.prototype`, and rely on the top visual tabs to switch between them.\n  When both surfaces are present, open the Wireframes tab by default; the\n  prototype remains available as the interactive follow-up view.\n- **Prototype-first** when the user asks to operate the UI or when interaction is\n  the main question. Use `create-prototype-plan`, which still preserves static\n  mocks where useful.\n\nFor mixed canvas + prototype plans, reuse the same real labels, app statuses,\nand screen ids across both surfaces. The canvas is the inspectable static reference;\nthe prototype is the interactive version of that same flow, not a separate\ndesign direction.\n\nTreat \u201Chigher fidelity,\u201D \u201Cpixel-accurate,\u201D \u201Cpolished mockup,\u201D \u201Cproduction-like,\u201D\n\u201Creal design,\u201D and \u201Cnot a sketch/wireframe\u201D as design-first language even when\nthe request also says \u201Cmockup.\u201D For a new plan, use `create-plan-design`. For\nan existing plan, keep the same plan id and call `update-visual-plan` with a\n`set-visual-render-mode` patch using `renderMode: \"design\"` plus the upgraded\nscreen HTML/CSS in the same update. Ground the result in the real app shell,\ntokens, typography, spacing, and states, and add stable `data-design-id`\ntargets. Put scoped styles in each screen's `css` field, never in a `<style>`\ntag. The viewer-local Clean toggle only changes one browser's wireframe\npreference; it is not a fidelity upgrade. Do not create a duplicate plan to\nhandle a fidelity follow-up.\n\n## Wireframe quality \u2014 read `references/wireframe.md`\n\nUI recap/plan wireframes must meet a strict quality bar \u2014 full-width chrome,\npinned bottom bars, real product content, before/after comparability, the right\n`surface` preset, `--wf-*` tokens instead of hex, and no `<html>`/`<style>`/font\ntags. Before authoring ANY wireframe / `<Screen>` / `WireframeBlock`, READ\n`references/wireframe.md` in this skill directory \u2014 it is the single source of\ntruth for HTML wireframe quality, shared word for word with `/visual-plan`\nand `/visual-recap`. Do not author wireframes from memory.\n\n## Canvas \u2014 read `references/canvas.md`\n\nThe canvas is the single source of truth for static UI mockups: the `surface`\nlocks each artboard's footprint, mixed surfaces lay out\nin lanes, annotations are plain-text designer notes anchored by\n`targetId`/`placement`, and edits are surgical `contentPatches`. Before\nauthoring or editing ANY canvas, artboard, or annotation, READ\n`references/canvas.md` in this skill directory \u2014 it is the single source of truth\nfor canvas/artboard mechanics. Do not author canvas layouts from memory.\nCanvas artboards use the same HTML wireframe path as document-body\n`WireframeBlock` screens: author `<Screen surface=\"...\" html={...} />` with a\nsemantic HTML fragment. Do not author fresh kit-tree children such as\n`<FrameScreen>`, `<Card>`, `<Row>`, or `<Btn>` inside canvas `<Screen>` tags;\nthose are legacy compatibility markup for old plans and produce brittle canvas\nlayouts.\n\n## Document quality \u2014 read `references/document-quality.md`\n\nThe document is a serious technical plan, not marketing: outcome-first,\nprose-first, self-contained, built from the right native blocks, with open\nquestions in a single bottom `question-form` and a pre-handoff visual check.\nBefore authoring the plan document, READ `references/document-quality.md` in this\nskill directory \u2014 it is the single source of truth for the document quality bar.\nDo not write the document from memory.\n\n## Good vs. bad exemplar \u2014 read `references/exemplar.md`\n\nFor a worked example of the bar \u2014 a great UI-first plan and `/visual-plan`, plus\nthe anti-patterns to avoid \u2014 READ `references/exemplar.md` in this skill\ndirectory before authoring a plan.\n\n## Tool Guidance\n\n- `create-visual-plan`: start one structured visual plan per agent task/run, or\n  import an existing text plan by passing `planText`; `content` may include no\n  visual surface, canvas only, or canvas + prototype.\n- `create-ui-plan`: start a UI-first plan when the work is primarily product UI.\n- `create-prototype-plan`: start a prototype-first plan with a functional top\n  review surface. If the interaction itself must also be high fidelity, set each\n  screen's `renderMode` to `design` and pass scoped styles through `css`;\n  otherwise use `create-plan-design` for design-first review.\n- `create-plan-design`: start a full-fidelity branded Design-tab plan with an\n  optional matching Prototype tab.\n- `convert-visual-plan-to-prototype`: convert an existing HTML wireframe canvas\n  into a prototype plan.\n- `create-visual-questions`: use only when the user explicitly asks for a visual\n  intake questionnaire, not as `/visual-plan` preflight.\n- `update-visual-plan`: revise content, status, or comments with targeted\n  `contentPatches` (see Core Workflow steps 6-7). Use\n  `set-visual-render-mode` with `renderMode: \"design\"` when promoting an\n  existing plan to high fidelity, together with deliberate screen HTML/CSS;\n  render mode alone only removes sketch treatment. `replace-blocks` and full\n  `content` replacement require `expectedUpdatedAt` from a fresh\n  `get-visual-plan` call.\n- `read-visual-plan-source`: read the normalized plan as `plan.mdx`,\n  optional `canvas.mdx`, optional `.plan-state.json`, and JSON.\n- `patch-visual-plan-source`: apply granular MDX AST patches by stable block,\n  artboard, annotation, component, or wireframe-node id. Prefer those targeted\n  operations; `replace-file` requires `expectedUpdatedAt` from a fresh\n  `get-visual-plan` call.\n- `import-visual-plan-source`: create or replace a plan from an MDX folder.\n- `get-visual-plan`: read the current structured plan, exported HTML,\n  annotations, and `plan.updatedAt`; it also returns the MDX folder for source\n  workflows. Re-read immediately before a destructive write for its concurrency\n  fence and again after every write to verify persisted state.\n- `get-plan-feedback`: read unconsumed human feedback. Use it frequently; it\n  returns grouped threads, exact anchor details, expected resolver, and recent\n  review-event payloads so agents can act only on the comments meant for them.\n- `get-plan-blocks`: resolve block tags before authoring \u2014 do not memorize tags;\n  call this first to get the authoritative tag names, required fields, and prop\n  shapes from the live block registry.\n- `export-visual-plan`: export HTML, Markdown fallback, structured JSON, and MDX\n  files for repo check-in.\n\nWhen the user critiques a plan's look or structure, fix the renderer or this\nskill \u2014 never hand-edit one stored plan. Turn feedback into better guidance.\n\n## Local-Files Privacy Mode \u2014 read `references/local-files.md`\n\nWhen the user wants no hosted Plan database writes \u2014 no DB writes, no Plan MCP\npublish, fully local/offline/private planning, repo-owned source-controlled\nartifacts, or `AGENT_NATIVE_PLANS_MODE=local-files` \u2014 do not call any hosted Plan\ntool except the schema-only `get-plan-blocks` catalog lookup. Author a local MDX\nfolder and\npreview it with `plan local check` / `plan local serve` / `plan local verify`.\nBefore using local-files mode, READ `references/local-files.md` in this skill\ndirectory \u2014 it is the single source of truth for the full contract (catalog\nlookup, MDX folder layout, the local bridge commands, and the hosted tools you\nmust not call). Carry forward only the code-research and plan-composition\nguidance from Core Workflow; everything hosted is replaced by the local bridge.\n\n## Interpreting comment anchors\n\nThis section applies to hosted plans with `get-plan-feedback` /\n`update-visual-plan`. In local-files mode, do not call hosted feedback or update\ntools; interpret file/chat feedback directly, edit the MDX files, rerun the\nlocal bridge check/serve/verify command, and report the new local URL.\n\n`get-plan-feedback` returns rich anchors \u2014 read them before acting on any comment.\n\n- **Coordinate frames.** `targetX`/`targetY` are percentages *within* the\n  element named by `targetSelector`/`targetKind`. Bare `x`/`y` are percentages\n  of the whole plan document. `canvasX`/`canvasY` are raw board-world pixels on\n  the design canvas (board size given when available).\n- **Wireframe pins.** Anchors on wireframes include `targetNodeId` and\n  `targetNodePath` (e.g. `card > list > listItem \"Acme Inc\"`) identifying the\n  exact kit node. Use `targetNodeId` directly with wireframe node patch ops;\n  use `data-design-id` values from design artboards with\n  `update-design-element-style`. Prefer the node id/path over raw coordinates;\n  fall back to coordinates plus the focused screenshot (red ring marks the exact\n  point) only when no node id is present.\n- **Text quotes.** Resolve `textQuote` against current prose using\n  `contextBefore`/`contextAfter` for disambiguation. If `ambiguous: true`, ask\n  the user \u2014 do not guess which occurrence is meant.\n- **Detached comments.** `get-plan-feedback` flags threads whose quoted text no\n  longer exists as `detached` (in `detachedThreads`). Reconcile these against\n  rewritten content \u2014 never silently drop them.\n- **Routing.** `resolutionTarget` is the only routing signal: act on `agent`,\n  treat `human` as context only. `@mentions` are people to notify, never a\n  routing signal.\n- **Two-axis state.** Mark every ingested comment as consumed\n  (`consumedCommentIds` on `update-visual-plan`). Set `status=resolved` only on\n  agent-targeted comments you actually addressed; leave human-targeted comments\n  open. When an edit addresses feedback, first re-read the persisted plan and\n  verify the requested change. Only then call `resolve-plan-comment` for the\n  addressed thread and `consume-plan-feedback` for its comments; never mark\n  addressed feedback along only one axis.\n\n## Visibility & Sharing\n\nUse `set-resource-visibility` to change who can see a plan (e.g. public, login,\nor org-scoped). Use `share-resource` to grant specific users or roles access\nby email or role. Gate visibility before sharing any plan that covers\nunreleased or private work \u2014 default to the narrowest scope that meets the\nreview need.\n\n## Setup & Authentication\n\nThere are two ways into Plans.\n\n**Coding agent (CLI).** Install once with the Agent-Native CLI. The command\ninstalls the Plans skills, registers the hosted Plans MCP connector, and runs\nauth/setup for the selected local client(s) in the same step (a one-time browser\nsign-in at setup \u2014 this is intended), so the first tool call in that client does\nnot hit an OAuth wall:\n\n```bash\nnpx @agent-native/core@latest skills add visual-plans\n```\n\nAfter that, `/visual-plan`, `/visual-recap`, and `/visualize-repo` are the\ninstalled slash commands. If you only need one command, use\n`skills add visual-plan`, `skills add visual-recap`, or\n`skills add visualize-repo` instead. The other planning modes\n(`create-ui-plan`, `create-prototype-plan`, `create-plan-design`,\n`create-visual-questions`) are MCP tools reachable from `/visual-plan`, not\nseparate slash commands. Pass `--no-connect` to register the connector without\nauthenticating, then run\n`npx @agent-native/core@latest connect https://plan.agent-native.com --client all`\nwhenever you are ready, or choose a narrower `--client`. Auth and MCP tool\nloading are per client config/session.\n\n**Browser (people you share with).** Open the Plans editor and create & edit\nwith no sign-up \u2014 you work as a guest. Sign in only when you want to save or\nshare; signing in claims the plans you made as a guest into your account.\n\nSharing and commenting require an account: public/shared plans are viewable by\nanyone with the link, but commenting on them needs an agent-native account.\n\nFor fully offline, no-account use, run the Plans app locally and sync plans to\nyour repo as MDX. This local mode is a separate advanced path, not the default\nhosted flow.\n\nFor repo-wide visual docs, run\n`npx @agent-native/core@latest visualize-repo --open` to create/update\n`agent-native.json`, seed `.agent-native/visual-docs/repo-overview`, and open\nthe local bridge.\n\nIf a Plans tool returns `needs auth`, `Unauthorized`, or `Session terminated`, do\nnot keep retrying it \u2014 stop and give the user the per-client reconnect step from\n`references/connection.md`, then continue once the connector is available.\n\nHosted default: connect `https://plan.agent-native.com/mcp`. Do\nnot put shared secrets in skill files.\n";
+export declare const VISUAL_PLANS_SKILL_MD = "---\nname: visual-plan\ndescription: >-\n  Turn ordinary text plans into rich interactive visual plans with diagrams,\n  file maps, annotated code, open questions, and UI/prototype review when\n  useful.\nmetadata:\n  visibility: exported\n---\n\n# Agent-Native Plans\n\nAgent-Native Plans is structured visual planning mode for coding agents. Build\nthe plan you would normally write in Markdown, but as a scannable document with\neditable blocks mixed in: inline diagrams, code snippets,\nopen questions, and an optional top visual review area (wireframe canvas, live\nprototype, or both in tabs). Architecture and backend plans stay document-only;\nUI and product plans start with the top canvas/prototype (the Visual Surface\nChoice section owns that rule).\n\n`/visual-plan` is the packaged command and main entry point. Choose the review\nmode from the task: UI-first when the work is primarily product UI and review\nshould start with screens, prototype-first when review should start with a\nfunctional live prototype, design-first when review needs full-fidelity branded\nscreens, or visual-intake when the user explicitly wants a questionnaire before\nplanning. When a Codex, Claude Code, Markdown, or pasted plan already exists,\n`/visual-plan` uses that source plan as the starting point and builds the review\nsurface from it instead of starting over.\n\n## When To Use\n\nCreate or adapt a visual plan whenever the plan would be better as a reviewable\nartifact than a chat paragraph. This includes modest work such as a single UI\nsurface with states, a small workflow, a before/after product change, or a\ncomponent/API/data-shape decision that needs alignment, plus larger multi-file,\nambiguous, long-running, risky, or UI-heavy work. Use it when architecture /\ndata flow / UI direction / options / open questions would benefit from inline\ndiagrams or structured blocks, when the user needs to react to a direction\nbefore you implement, or when an existing text plan needs a richer review\nsurface.\n\n## Plan Discipline\n\n- **Gate thoughtfully.** A visual plan is a richer review surface, not only a\n  tool for giant projects. Use it when the user needs to see, compare, comment\n  on, or approve a direction before code, even for a modest UI/state/workflow\n  change. Skip it for truly trivial, unambiguous work \u2014 typos, one-line fixes, a\n  single well-specified function, anything whose diff you could describe in one\n  sentence \u2014 and just make the change. Never pad a plan with filler and never\n  ship a single-step plan.\n- **Research before you draft.** Read the real files, actions, schema, and\n  patterns first; name actual files, symbols, and data shapes instead of\n  inventing them. Check existing `actions/` before proposing endpoints and prefer\n  named client helpers over raw fetch. Delegate wide exploration to a sub-agent.\n  Lead with reuse: for each step, name what it reuses \u2014 existing actions, schema,\n  components, helpers \u2014 before what it adds, so the plan explains the genuinely new\n  delta instead of redescribing what already exists.\n- **Decide the hard-to-reverse bets first.** For non-trivial backend, data, or API\n  work, sketch where the feature is headed, then call out the decisions that are\n  expensive to undo once data or callers depend on them \u2014 wire format, public ids,\n  data-model shape, auth and ownership boundaries \u2014 and get those right in the plan\n  even if most of the feature ships later. Then scope to the smallest first cut that\n  proves the approach without foreclosing it, stating both what is in and what is\n  explicitly deferred.\n- **Keep examples at the right altitude.** When the user's idea is a broad\n  framework, product, or operating-model change, do not collapse it into the\n  first concrete example, provider, or sync path they mention. Separate the core\n  abstraction from motivating examples and app/provider adapters. Use examples\n  to make the plan legible, but label them as examples unless they are the whole\n  requested scope.\n- **Publish standalone plans.** If the user pasted, referenced, or already has a\n  Codex / Claude Code / Markdown plan, treat it as source material, but rewrite\n  the published plan as a clean standalone proposal. Preserve the source plan's\n  useful intent and codebase facts, label inferred visuals as inferred, and avoid\n  revision language such as \"preserve the prior plan\", \"do not drop the old\n  idea\", \"unlike the previous version\", or \"this revision changes...\". A reader\n  who never saw the chat or earlier drafts should understand the plan.\n- **Make the first read concrete.** If the plan is meant to be shared with\n  someone outside the chat, or if the concept is abstract, lead near the top with\n  one concrete product example before mode tables, architecture, or roadmaps. For\n  UI-capable concepts, that usually means a top-canvas app state that shows the\n  real user workflow in product terms. Do not rely on phrases that only make\n  sense in conversation, and do not frame the plan as \"not the old idea\"; state\n  the positive model directly.\n- **Planning is read-only.** Make no source edits while building or reviewing the\n  plan. Start editing only after the user approves the direction.\n- **Clarify vs. assume.** Do not ask how to build it \u2014 explore and present the\n  approach and options in the plan. Ask a clarifying question only when an\n  ambiguity would change the design and you cannot resolve it from the code; use\n  the host agent's normal ask-user-question flow and batch 2-4 high-leverage\n  questions before finalizing. Do not call `create-visual-questions` for\n  ordinary clarification or preflight; reserve it for the visual-intake mode when\n  the user explicitly asks for a visual intake questionnaire. Otherwise state the\n  assumption explicitly and proceed, and keep anything unresolved in the plan's\n  single bottom `question-form` Open Questions block. For complex plans, do a\n  final open-question pass before handoff: if a decision would affect\n  architecture, scope, UX, data shape, or rollout, either decide it in the plan\n  with rationale or put it in that bottom form with a recommended default.\n- **The plan is the approval gate.** After surfacing it, ask the user to review\n  and approve before you write code, and name which files/areas the work touches.\n  Presenting the plan and requesting sign-off is the approval step \u2014 do not ask a\n  separate \"does this look good?\" question.\n- **The document is the source of truth, not the chat.** When scope shifts,\n  update the plan with `update-visual-plan` rather than only changing course in\n  chat, and make the updated document stand alone. Do not describe the update as\n  a correction to an earlier draft inside the plan itself. Re-read the approved\n  plan before major steps.\n\n## Create A Structured Agent-Native Plan \u2014 Never Inline\n\nThe deliverable is ALWAYS a structured Agent-Native Plan, not a chat-only plan.\nThe hosted Plan MCP connector (`plan` server, or legacy `agent-native-plans`) is\nthe default collaboration and commenting surface; it is not a reason to reject\nthe planning pattern as an external dependency or rented layer. Plans are\nportable source artifacts (`plan.mdx`, optional `canvas.mdx` /\n`prototype.mdx`, JSON, and HTML export), and ownership-sensitive workflows can\nuse local-files mode or a self-hosted/custom Plan app URL without abandoning the\nskill's review discipline. Do not advise the user to skip `/visual-plan` because\nthe default surface is hosted; choose the right Plan mode for the user's\nownership, privacy, sharing, and branding needs.\n\nBy default, create the plan via the Plan MCP connector and NEVER hand it over as\ninline chat content \u2014 no Markdown prose, ASCII sketch, table, or fenced\nwireframe. If the `plan` (or legacy `agent-native-plans`) tools are not visible,\ndiscover them through the host's `tool_search` first; if they are still missing,\nSTOP and give the user the client-specific reconnect step rather than improvising\nan inline plan. Before publishing, or whenever a connector or auth error appears,\nREAD `references/connection.md` in this skill directory \u2014 it is the single source\nof truth for the never-inline rule, connector discovery, and the per-client\nreconnect steps. Local-files privacy mode (after Tool Guidance) is the exception.\n\n## Core Workflow\n\nThis section describes the default hosted Plan MCP workflow. If\n`AGENT_NATIVE_PLANS_MODE=local-files` is set, or the user asks for fully local\nfiles/no hosted Plan writes, use **Local-Files Privacy Mode** instead; carry\nforward only the code-research and plan-composition guidance here.\n\n1. Follow the host agent's normal planning flow: inspect the codebase, delegate\n   wide exploration when useful, gather the info needed, and ask native\n   clarifying questions as needed before generating the plan. If a source plan\n   already exists, gather its exact text from the user's paste, a referenced\n   file, or recent visible agent context; do not invent source text.\n2. Call `get-plan-blocks` for the authoritative block catalog \u2014 do not author\n   from memorized tags. Then call the mode-matched create tool:\n   `create-visual-plan` for document-first plans (architecture, backend, data,\n   refactor, API), `create-ui-plan` for UI-first plans, `create-prototype-plan`\n   for prototype-first plans, `create-plan-design` for design-first plans,\n   `create-visual-questions` only when the user explicitly asks for a visual\n   intake questionnaire. When a source plan already exists,\n   pass it as `planText` and preserve the original plan's useful intent while\n   producing a standalone plan document, not a revision memo.\n3. For UI/product plans, compose the top canvas first with the primary\n   wireframes and annotated states, then write the document with native blocks\n   (see `references/canvas.md` and `references/document-quality.md`). For\n   broad product architecture plans with a user-facing implication, add a\n   concrete \"what this looks like in the app\" visual before the abstract\n   architecture or mode tables. Keep the document close to the standalone\n   Markdown plan the agent would normally output. If an existing plan was\n   provided, carry forward the right facts and decisions without referring to\n   the previous draft or explaining how this version differs. For non-visual\n   plans, skip the top visual surface (Visual Surface Choice below owns the rule)\n   and put `diagram`, `data-model`,\n   `api-endpoint`, `diff`, `file-tree`, `code`, and `annotated-code` blocks\n   directly next to the relevant prose.\n   Wide document layout is renderer-owned and intentionally allowlisted: only\n   literal code-review surfaces (`diff`, `annotated-code`) and `tabs` blocks\n   with vertical orientation or diff-like children break out wider than prose.\n   Keep `api-endpoint`, `openapi-spec`, `data-model`, `json-explorer`,\n   `wireframe`, question, and `custom-html` blocks in normal document flow unless\n   their own renderer says otherwise.\n4. Surface the returned Plans link or inline MCP App and ask the user to review.\n   Always include the actual URL in chat so the next step is a click in CLI or\n   other text-only hosts. When the host exposes an embedded browser/preview panel\n   and a tool can open arbitrary URLs there, open the returned plan URL\n   automatically for convenient review \u2014 a convenience and smoke test, never the\n   only handoff or the access\n   model. Plans should load out of the box for the local agent and local browser\n   session; if a signed-in embedded browser cannot read a local plan that an\n   anonymous/tool check can read, fix the app/action ownership or access path\n   rather than patching one plan by hand. For high-stakes plans (architecture,\n   backend, data, multi-file, or risky), also kick off the self-review pass in\n   **Self-Review Before Handoff** while the user reads, instead of blocking the\n   handoff on it.\n5. For hosted plans, call `get-plan-feedback` before editing, after review,\n   after any long pause,\n   and before the final response. Treat `anchorDetails`, resolver intent, recent\n   review events, and any focused screenshots from browser handoff as the source\n   of truth for exactly what changed and exactly what each comment points at.\n6. For hosted plans, apply changes with `update-visual-plan`, preferring\n   targeted `contentPatches`.\n   Treat the top-level `content` payload as a full replacement, not a merge; do\n   not send a partial `content` object to add a canvas or one block. If a full\n   replacement or `replace-blocks` is unavoidable, call `get-visual-plan`\n   immediately before the write, pass its `plan.updatedAt` as\n   `expectedUpdatedAt`, and carry forward every existing block and visual\n   surface. Never reuse a revision from an earlier read or feedback payload.\n   For source-control friendly edits, use granular `patch-visual-plan-source`\n   operations against the MDX files instead of regenerating the plan;\n   `replace-file` is also destructive and requires the same fresh\n   `expectedUpdatedAt` fence.\n7. After every hosted-plan write, call `get-visual-plan` again and compare the\n   persisted text, block IDs/counts, canvas frames, and prototype with the\n   intended result. A successful mutation response is not proof that unrelated\n   content survived. If the edit addressed agent-targeted feedback, only after\n   this verification call `resolve-plan-comment` for the thread and\n   `consume-plan-feedback` for its comments; do both so addressed feedback is\n   neither visibly open nor returned as pending work.\n8. For hosted plans, export with `export-visual-plan` only when the user wants a\n   shareable receipt or repo-check-in artifacts.\n\n## Self-Review Before Handoff\n\nThis adversarial self-review pass is opt-in, not default: run it only for\nhigh-stakes plans \u2014 irreversible migrations, security-sensitive work, or when\nthe user explicitly asks for extra rigor \u2014 and skip it otherwise. It roughly\ndoubles the cost of plan generation, so the default for small, UI-only,\nsingle-decision, or ordinary plans is to skip it, not to run it. Keep the pass\ncheap and non-blocking when it does run:\n\n- **Surface the plan first, review concurrently.** Post the link and let the user\n  start reading, then run the review in parallel \u2014 never make the user wait on it.\n- **Review the written plan; do not re-research.** Critique the plan text and its\n  own blocks. The grounding was already done while drafting, so the review checks\n  the output instead of re-exploring the repo.\n- **Spawn one skeptical reviewer** whose only job is to find what is weak, missing,\n  or wrong \u2014 not to praise. Point it at: hard-to-reverse decisions made implicitly\n  or not at all (wire format, public ids, data-model shape, auth, ownership); steps\n  not anchored in real files or symbols; a menu of options where the plan should\n  commit to one; obvious missing decisions (\"what happens when X?\", \"why not Y?\");\n  and padding or single-step filler.\n- **Fix vs. ask.** Apply clear-cut fixes yourself with `update-visual-plan`\n  `contentPatches` \u2014 vague non-goals, unanchored claims, an obvious missing\n  decision. Route genuine judgment calls back to the user instead: add them to the\n  bottom `question-form` Open Questions block or batch them into the normal\n  ask-user-question flow. Do not silently decide them.\n- **Do not surprise the user mid-read.** On a large plan, apply the patches before\n  the editor loads; otherwise note briefly that a self-review is running so the\n  plan changing under them is expected. When you next respond, summarize what the\n  review changed and what it surfaced for the user to decide.\n\n## Visual Surface Choice\n\nChoose the surface before creating the plan or after reading the source plan. Do\nnot add visual chrome by default:\n\nFor UI/product plans, the top canvas is usually the primary review surface. Put\nthe first meaningful wireframes there, not buried as document-body blocks. Use\nmultiple canvas artboards when states matter, such as the default view, an\noverflow menu or popover, a side panel, loading, or error. Put short annotations\nbeside frames with `targetId` plus `placement`; keep implementation details,\ntradeoffs, file maps, data contracts, risks, and verification in the document\nbody below the canvas.\n\nWhen the user asks for a flow, storyboard, journey, wireframe, canvas, or \"what\nthis looks like\", treat that as a canvas-first request. Make one artboard per\nuser-visible state, connect only adjacent transitions, and use short canvas\nannotations for the product notes. Do not substitute a document-body `diagram`\nblock for the requested storyboard just because HTML diagrams are faster to\nwrite; diagrams belong below the canvas for backend mechanics, architecture, or\ndata-flow explanation.\n\nKeep product wireframes and explanatory/meta diagrams separate. Start with pure\nscreens that look like the app state under discussion, without callout prose or\narchitecture notes embedded inside the UI. Put arrows, labels, contracts, data\nflow, and mode explanations in separate annotations, separate canvas diagrams,\nor the document body.\n\nWhen the plan touches an existing app, inspect the current shell/components\nbefore drawing. The first artboard should look like the real app at the same\ndensity: existing sidebars, toolbar placement, overflow menus, app chrome, and\nframework agent chrome stay in their real places. Model secondary surfaces as\nseparate states, such as a top-right overflow popover, sheet, panel, loading\nstate, or separate AgentSidebar, rather than inventing a permanent inspector or\nfolding framework chrome into the product UI.\n\n- **No visual surface** for architecture-only, backend-only, data migration,\n  copy-only, or otherwise non-visual plans. Do not use the top canvas for\n  architecture diagrams, dependency maps, file plans, API contracts, or\n  data-flow-only reviews. Use a strong document with local inline diagrams\n  only when relationships need a visual explanation, usually one spatial diagram\n  per recommendation or decision. Prefer grouped regions, layers, quadrants,\n  matrices, or before/after panels over a single-axis chain unless the\n  relationship is truly sequential.\n- **Canvas only** for one static screen, a before/after comparison, a component\n  state, a small popover, or a visual direction that does not require clicking.\n  Put those wireframes in `content.canvas` and omit `content.prototype`.\n- **Canvas + prototype** for multi-step UI flows, onboarding, wizards,\n  review/approval flows, navigation changes, or anything where the reviewer\n  needs to operate the behavior. Keep the static wireframes in\n  `content.canvas`, add the aligned functional prototype in\n  `content.prototype`, and rely on the top visual tabs to switch between them.\n  When both surfaces are present, open the Wireframes tab by default; the\n  prototype remains available as the interactive follow-up view.\n- **Default to wireframes.** A clean, minimal UI, a high UX bar, or references\n  to Linear/Vercel describe the content and density bar; they do not request\n  full-fidelity design mode. Use renderer-owned wireframes unless the user\n  explicitly asks for branded, pixel-accurate, production-like, or full visual\n  design. This keeps every canvas screen inspectable and its full content visible.\n- **Prototype-first** when the user asks to operate the UI or when interaction is\n  the main question. Use `create-prototype-plan`, which still preserves static\n  mocks where useful.\n\nFor mixed canvas + prototype plans, reuse the same real labels, app statuses,\nand screen ids across both surfaces. The canvas is the inspectable static reference;\nthe prototype is the interactive version of that same flow, not a separate\ndesign direction.\n\nTreat \u201Chigher fidelity,\u201D \u201Cpixel-accurate,\u201D \u201Cpolished mockup,\u201D \u201Cproduction-like,\u201D\n\u201Creal design,\u201D and \u201Cnot a sketch/wireframe\u201D as design-first language even when\nthe request also says \u201Cmockup.\u201D For a new plan, use `create-plan-design`. For\nan existing plan, keep the same plan id and call `update-visual-plan` with a\n`set-visual-render-mode` patch using `renderMode: \"design\"` plus the upgraded\nscreen HTML/CSS in the same update. Ground the result in the real app shell,\ntokens, typography, spacing, and states, and add stable `data-design-id`\ntargets. Put scoped styles in each screen's `css` field, never in a `<style>`\ntag. The viewer-local Clean toggle only changes one browser's wireframe\npreference; it is not a fidelity upgrade. Do not create a duplicate plan to\nhandle a fidelity follow-up.\n\n## Wireframe quality \u2014 read `references/wireframe.md`\n\nUI recap/plan wireframes must meet a strict quality bar \u2014 full-width chrome,\npinned bottom bars, real product content, before/after comparability, the right\n`surface` preset, `--wf-*` tokens instead of hex, and no `<html>`/`<style>`/font\ntags. Before authoring ANY wireframe / `<Screen>` / `WireframeBlock`, READ\n`references/wireframe.md` in this skill directory \u2014 it is the single source of\ntruth for HTML wireframe quality, shared word for word with `/visual-plan`\nand `/visual-recap`. Do not author wireframes from memory.\n\n## Canvas \u2014 read `references/canvas.md`\n\nThe canvas is the single source of truth for static UI mockups: the `surface`\nlocks each artboard's footprint, mixed surfaces lay out\nin lanes, annotations are plain-text designer notes anchored by\n`targetId`/`placement`, and edits are surgical `contentPatches`. Before\nauthoring or editing ANY canvas, artboard, or annotation, READ\n`references/canvas.md` in this skill directory \u2014 it is the single source of truth\nfor canvas/artboard mechanics. Do not author canvas layouts from memory.\nCanvas artboards use the same HTML wireframe path as document-body\n`WireframeBlock` screens: author `<Screen surface=\"...\" html={...} />` with a\nsemantic HTML fragment. Do not author fresh kit-tree children such as\n`<FrameScreen>`, `<Card>`, `<Row>`, or `<Btn>` inside canvas `<Screen>` tags;\nthose are legacy compatibility markup for old plans and produce brittle canvas\nlayouts.\n\n## Document quality \u2014 read `references/document-quality.md`\n\nThe document is a serious technical plan, not marketing: outcome-first,\nprose-first, self-contained, built from the right native blocks, with open\nquestions in a single bottom `question-form` and a pre-handoff visual check.\nBefore authoring the plan document, READ `references/document-quality.md` in this\nskill directory \u2014 it is the single source of truth for the document quality bar.\nDo not write the document from memory.\n\n## Good vs. bad exemplar \u2014 read `references/exemplar.md`\n\nFor a worked example of the bar \u2014 a great UI-first plan and `/visual-plan`, plus\nthe anti-patterns to avoid \u2014 READ `references/exemplar.md` in this skill\ndirectory before authoring a plan.\n\n## Authoring invariants\n\nTreat these as data-integrity checks, not optional polish:\n\n- `content` is a complete replacement. Pass either `content` or the mode's\n  convenience arrays (`screens`/`transitions` or `states`/`components`),\n  never both. The create actions reject mixed sources so a second payload cannot\n  silently discard CSS, frames, or document blocks.\n- A design screen's scoped `css` is part of the artifact. Keep it on both the\n  prototype screen and its matching canvas frame, and use renderer-owned\n  `--wf-*` tokens for portable color and typography.\n- Rich-text `data.markdown` must contain actual runtime line breaks. Do not\n  hand a plan a one-line Markdown value containing literal `\\n` escape text,\n  which renders the whole section as one heading. Escaped newlines are fine in\n  code examples when the surrounding Markdown still has real line breaks.\n- Canvas artboards do not scroll. Keep wireframe HTML in natural flow and set a\n  larger frame `height` when a screen exceeds the surface preset; preserve the\n  surface width and inspect the bottom edge at default zoom before handoff.\n- After every hosted write, re-read the structured content and inspect the live\n  Plan surface. A valid JSON payload is not proof that CSS loaded or Markdown\n  rendered into the intended heading, paragraph, and list structure.\n\n## Tool Guidance\n\n- `create-visual-plan`: start one structured visual plan per agent task/run, or\n  import an existing text plan by passing `planText`; `content` may include no\n  visual surface, canvas only, or canvas + prototype.\n- `create-ui-plan`: start a UI-first plan when the work is primarily product UI.\n- `create-prototype-plan`: start a prototype-first plan with a functional top\n  review surface. If the interaction itself must also be high fidelity, set each\n  screen's `renderMode` to `design` and pass scoped styles through `css`;\n  otherwise use `create-plan-design` for design-first review.\n- `create-plan-design`: start a full-fidelity branded Design-tab plan with an\n  optional matching Prototype tab.\n- `convert-visual-plan-to-prototype`: convert an existing HTML wireframe canvas\n  into a prototype plan.\n- `create-visual-questions`: use only when the user explicitly asks for a visual\n  intake questionnaire, not as `/visual-plan` preflight.\n- `update-visual-plan`: revise content, status, or comments with targeted\n  `contentPatches` (see Core Workflow steps 6-7). Use\n  `set-visual-render-mode` with `renderMode: \"design\"` when promoting an\n  existing plan to high fidelity, together with deliberate screen HTML/CSS;\n  render mode alone only removes sketch treatment. `replace-blocks` and full\n  `content` replacement require `expectedUpdatedAt` from a fresh\n  `get-visual-plan` call.\n- `read-visual-plan-source`: read the normalized plan as `plan.mdx`,\n  optional `canvas.mdx`, optional `.plan-state.json`, and JSON.\n- `patch-visual-plan-source`: apply granular MDX AST patches by stable block,\n  artboard, annotation, component, or wireframe-node id. Prefer those targeted\n  operations; `replace-file` requires `expectedUpdatedAt` from a fresh\n  `get-visual-plan` call.\n- `import-visual-plan-source`: create or replace a plan from an MDX folder.\n- `get-visual-plan`: read the current structured plan, exported HTML,\n  annotations, and `plan.updatedAt`; it also returns the MDX folder for source\n  workflows. Re-read immediately before a destructive write for its concurrency\n  fence and again after every write to verify persisted state.\n- `get-plan-feedback`: read unconsumed human feedback. Use it frequently; it\n  returns grouped threads, exact anchor details, expected resolver, and recent\n  review-event payloads so agents can act only on the comments meant for them.\n- `get-plan-blocks`: resolve block tags before authoring \u2014 do not memorize tags;\n  call this first to get the authoritative tag names, required fields, and prop\n  shapes from the live block registry.\n- `export-visual-plan`: export HTML, Markdown fallback, structured JSON, and MDX\n  files for repo check-in.\n\nWhen the user critiques a plan's look or structure, fix the renderer or this\nskill \u2014 never hand-edit one stored plan. Turn feedback into better guidance.\n\n## Local-Files Privacy Mode \u2014 read `references/local-files.md`\n\nWhen the user wants no hosted Plan database writes \u2014 no DB writes, no Plan MCP\npublish, fully local/offline/private planning, repo-owned source-controlled\nartifacts, or `AGENT_NATIVE_PLANS_MODE=local-files` \u2014 do not call any hosted Plan\ntool except the schema-only `get-plan-blocks` catalog lookup. Author a local MDX\nfolder and\npreview it with `plan local check` / `plan local serve` / `plan local verify`.\nBefore using local-files mode, READ `references/local-files.md` in this skill\ndirectory \u2014 it is the single source of truth for the full contract (catalog\nlookup, MDX folder layout, the local bridge commands, and the hosted tools you\nmust not call). Carry forward only the code-research and plan-composition\nguidance from Core Workflow; everything hosted is replaced by the local bridge.\n\n## Interpreting comment anchors\n\nThis section applies to hosted plans with `get-plan-feedback` /\n`update-visual-plan`. In local-files mode, do not call hosted feedback or update\ntools; interpret file/chat feedback directly, edit the MDX files, rerun the\nlocal bridge check/serve/verify command, and report the new local URL.\n\n`get-plan-feedback` returns rich anchors \u2014 read them before acting on any comment.\n\n- **Coordinate frames.** `targetX`/`targetY` are percentages *within* the\n  element named by `targetSelector`/`targetKind`. Bare `x`/`y` are percentages\n  of the whole plan document. `canvasX`/`canvasY` are raw board-world pixels on\n  the design canvas (board size given when available).\n- **Wireframe pins.** Anchors on wireframes include `targetNodeId` and\n  `targetNodePath` (e.g. `card > list > listItem \"Acme Inc\"`) identifying the\n  exact kit node. Use `targetNodeId` directly with wireframe node patch ops;\n  use `data-design-id` values from design artboards with\n  `update-design-element-style`. Prefer the node id/path over raw coordinates;\n  fall back to coordinates plus the focused screenshot (red ring marks the exact\n  point) only when no node id is present.\n- **Text quotes.** Resolve `textQuote` against current prose using\n  `contextBefore`/`contextAfter` for disambiguation. If `ambiguous: true`, ask\n  the user \u2014 do not guess which occurrence is meant.\n- **Detached comments.** `get-plan-feedback` flags threads whose quoted text no\n  longer exists as `detached` (in `detachedThreads`). Reconcile these against\n  rewritten content \u2014 never silently drop them.\n- **Routing.** `resolutionTarget` is the only routing signal: act on `agent`,\n  treat `human` as context only. `@mentions` are people to notify, never a\n  routing signal.\n- **Two-axis state.** Mark every ingested comment as consumed\n  (`consumedCommentIds` on `update-visual-plan`). Set `status=resolved` only on\n  agent-targeted comments you actually addressed; leave human-targeted comments\n  open. When an edit addresses feedback, first re-read the persisted plan and\n  verify the requested change. Only then call `resolve-plan-comment` for the\n  addressed thread and `consume-plan-feedback` for its comments; never mark\n  addressed feedback along only one axis.\n\n## Visibility & Sharing\n\nUse `set-resource-visibility` to change who can see a plan (e.g. public, login,\nor org-scoped). Use `share-resource` to grant specific users or roles access\nby email or role. Gate visibility before sharing any plan that covers\nunreleased or private work \u2014 default to the narrowest scope that meets the\nreview need.\n\n## Setup & Authentication\n\nThere are two ways into Plans.\n\n**Coding agent (CLI).** Install once with the Agent-Native CLI. The command\ninstalls the Plans skills, registers the hosted Plans MCP connector, and runs\nauth/setup for the selected local client(s) in the same step (a one-time browser\nsign-in at setup \u2014 this is intended), so the first tool call in that client does\nnot hit an OAuth wall:\n\n```bash\nnpx @agent-native/core@latest skills add visual-plans\n```\n\nAfter that, `/visual-plan`, `/visual-recap`, and `/visualize-repo` are the\ninstalled slash commands. If you only need one command, use\n`skills add visual-plan`, `skills add visual-recap`, or\n`skills add visualize-repo` instead. The other planning modes\n(`create-ui-plan`, `create-prototype-plan`, `create-plan-design`,\n`create-visual-questions`) are MCP tools reachable from `/visual-plan`, not\nseparate slash commands. Pass `--no-connect` to register the connector without\nauthenticating, then run\n`npx @agent-native/core@latest connect https://plan.agent-native.com --client all`\nwhenever you are ready, or choose a narrower `--client`. Auth and MCP tool\nloading are per client config/session.\n\n**Browser (people you share with).** Open the Plans editor and create & edit\nwith no sign-up \u2014 you work as a guest. Sign in only when you want to save or\nshare; signing in claims the plans you made as a guest into your account.\n\nSharing and commenting require an account: public/shared plans are viewable by\nanyone with the link, but commenting on them needs an agent-native account.\n\nFor fully offline, no-account use, run the Plans app locally and sync plans to\nyour repo as MDX. This local mode is a separate advanced path, not the default\nhosted flow.\n\nFor repo-wide visual docs, run\n`npx @agent-native/core@latest visualize-repo --open` to create/update\n`agent-native.json`, seed `.agent-native/visual-docs/repo-overview`, and open\nthe local bridge.\n\nIf a Plans tool returns `needs auth`, `Unauthorized`, or `Session terminated`, do\nnot keep retrying it \u2014 stop and give the user the per-client reconnect step from\n`references/connection.md`, then continue once the connector is available.\n\nHosted default: connect `https://plan.agent-native.com/mcp`. Do\nnot put shared secrets in skill files.\n";
 //# sourceMappingURL=visual-plan-skill.d.ts.map