name: cad-callout-pair-layout description: Plan and style CAD callouts with ordinary LEADER, associated single-line MTEXT and a yellow dot. The Agent reads the inner frame, chooses regions and ordering, then uses bounded geometry checks and verified native tools. Use for new or adjusted callouts, not engineering quantities, frames or plotting.

CAD Callout Style and Layout

Source preview v0.6 uses Agent-led planning. 完整中文规则, planning guide, input/acceptance, transport contract. The unchanged v0.3 pairwise solver is an optional local repair tool; its fixed angle/extension limits do not constrain Agent planning. An unresolved ID returns to the Agent for judgment, not necessarily to the user.

1. Read the usable inner frame first. Query native extents of candidate frames, including proxies/blocks, and identify the correct continuous inner rectangle visually. A proxy bounding box need not equal an inner frame. If unavailable, derive a representative viewport or estimate from available evidence; record native, visual, viewport-derived or estimated evidence and units. About 1:400–1:500 and 175 metres per road sheet are project hints, not fixed dimensions. Prefer the inner frame; occasional overflow is a lower-priority fallback, while actual clipping must be resolved.
2. Let the Agent choose regions and order. Inspect the road, anchors, dense content and usable blank spaces before writing labels. Prefer readable areas outside the road. Confirmed gray residual background has very low avoidance weight and can be overlaid; do not lengthen leaders simply to avoid it. Protect current annotations and effective engineering information. Internal readable spaces may be used when necessary. Same-opening anchor order is an initial preference, not a crossing-free theorem on curved roads.
3. Plan before placement. The Agent may specify A/B/C directly, or ask a small tool to fit within selected regions/order/openings. Use native formatted text bounds, including superscripts, rather than character counts or MTEXT wrapping width. Keep point anchors fixed; other anchors must remain on their confirmed target. Do not seed a whole deliverable with arbitrary positions.
4. Check, apply, read back and inspect. scripts/review_layout.py checks explicit plans, supplied keepouts, soft frame limits and known clipping. It does not read CAD, choose regions, classify gray content or move labels. Apply via verified native tools and independently read associations, actual dimensions and positions. Fix isolated issues locally; widespread or recurring overlap requires revisiting regions/order. Gray-background permission does not make dense road hatch a preferred text area. Inspect complete labels against hatch edges, effective lines and viewport clipping. When printing is requested, inspect the actual requested-CTB PDF.

Native callout and editing

Use ordinary three-vertex LEADER associated with MTEXT and an actually yellow anchor dot, not MLeader. Preserve approved content, quantities and base geometry. B–C follows frame horizontal, with approved text gap, a strictly obtuse B angle and no leader crossing its own text. Read actual task-approved style overrides; historical metre-based dimensions are examples, not universal defaults. Automatic scale selection/resizing remains unimplemented.

Verify native AnnotationOffset, Dimtad and regeneration, not just stored vertices. See stable association/tail. Keep native objects editable and new layers unlocked; do not explode or rasterize them. On an initial field trial, edit one MTEXT in the native editor and restore it, then read back anchor/association/horizontal nonzero tail. Significant text-width changes need coordinated tail maintenance; arbitrary edits are not promised automatic equal-width tails.

Execution and evidence

Discover actual runtime schemas and uniquely bind process/full path/backend before writes. Unknown writes are queried by their original request, never replayed under new IDs. Report native capability gaps; task-authorized alternatives do not bypass refusals or fences. This Skill ships no CAD writer, arbitrary-code adapter, fonts or engineering DWG. Foundation supplies reusable operations; the Agent/Skill supplies engineering presentation judgment.

The accepted 35-callout field example displays the second-area PDF crop and its pm.ctb PDF. Annotation writes/readback/save used Foundation MCP; manual editing used CAD UI; explicitly authorized COM performed plotting. It is a local-case validation, not all-drawing or all-version certification. See evidence. The optional BZYD manual utility remains separate and is not an Agent execution backend.

CAD Callout Pair Layout — AutoCAD Annotation Skill & BZYD

中文 · Install · Compatibility · Evidence

Agent-led CAD callout planning, with small geometry tools for reliable repetitive checks. Source preview v0.6 reads the inner frame first, plans regions/order/openings, then applies and reviews native results. The v0.3 pairwise solver remains available for local repair.

• Ordinary LEADER + associated editable MTEXT and yellow dot.
• Agent judgment for road/gray background, usable regions and dense junctions.
• Read-only explicit-plan geometry review; verified native application and visual feedback.
• Accepted 35-callout field trial; automatic scale resizing is still a future interface.

Defaults/native history come from metre-based road drawings. Other professions, planting/species labels and millimetre styles require adaptation and are not validated. The AI Skill/solver has no native writer or automatic installer; optional manual Lisp is separate. No fonts, engineering DWGs or legacy COM helpers are bundled; the selected second-area PDF and crop are display evidence. Try the synthetic example.

The new 35-callout field trial separates native MCP annotation evidence from authorized COM plotting. Historical evidence and remaining limits are listed in validation.

CAD Agent Foundation supplies supported reusable native operations and execution governance. This Skill supplies style parameters/placement rules; missing operations do not appear by installing it. The related cad-distress-annotation supplies engineering scope/classification. Repository: cad-callout-pair-layout.

The anonymous display case is a comprehensive historical project Python/AutoCAD COM workflow, not Foundation-only execution proof. Reproduction requires the stated components, verified extra native operations and cleared inputs; no automatic CAD replay dataset is included.

Owned source/instructions: Apache-2.0; dependency terms remain separate. Notices. Relevant terms: AutoCAD, CAD annotation, ordinary LEADER, MTEXT, callout layout, CAD Agent Skill, MCP / Model Context Protocol. This Skill is not an MCP server or Autodesk product.

Optional manual utility: BZYD, English/Chinese ANSI editions. It adjusts existing callouts without Foundation/Python. AutoCAD2026 Chinese historical tests exist; AutoCAD2022 and the translated English native path remain unverified.

Structure and CAD2022/2026 support by component. Native dimensions are a future independent Skill, not a reason to widen this package's current support claims.

Accepted field result

PDF · Evidence / 实战说明