agentleFS
MakeItEzzz555MakeItEzzz555/Gridline/skills/autocad-dwg-workflow/SKILL.md

autocad-dwg-workflow

Skill39 starsChanged 23 days agoMITView on GitHub

Plan and review safe AutoCAD DWG drawing creation, cleanup, layers, blocks, xrefs, layouts, plotting, AutoLISP/.NET automation and issue preparation. Use for AutoCAD-specific drafting and DWG package workflows.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.

    line 15
  2. Distinctive:

    Use verified AutoCAD command/API surfaces.

    line 21
  3. Very specific:

    Before/after counts and representative handles/attributes are checked.

    line 33
  4. Very specific:

    Do not silently bind/detach/flatten xrefs or purge definitions that may carry standards/data.

    line 40
  5. Distinctive:

    Do not invent command flags/API signatures.

    line 41
  6. Distinctive:

    If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application …

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AutoCAD / DWG Workflow

Protect coordinates, units, references, annotation and issued content; work on versioned copies for automated changes.

Preflight

  • AutoCAD/vertical release, DWG version, OS, units/insertion scale, UCS/WCS, coordinate origin, xrefs, layouts and source/issued status.
  • Layer/block standards, annotation scales, fonts/linetypes, CTB/STB, page setups, title blocks and output requirements.

Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.

Workflow

  1. Inventory model/paper-space entities, layers, blocks/attributes, xrefs, underlays, layouts and plot dependencies.
  2. Define protected geometry/data and exact permitted edit scope; preview entity handles/names/counts before mutation.
  3. Use verified AutoCAD command/API surfaces; dry-run or sample batch operations before full-file changes and save to new paths.
  4. Generate proof PDFs and inspect viewport scales/locks, lineweights, hatches, fonts, clipping, title/revision data and unresolved references.

Deliverables

  • DWG preflight/audit
  • Change or automation plan
  • Layer/block/xref report
  • Plot/issue verification report

Verification

  • Before/after counts and representative handles/attributes are checked; units/origin/extents remain invariant unless explicitly changed.
  • Resulting DWG opens in a compatible AutoCAD environment when available.

For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.

Professional boundaries

  • Do not silently bind/detach/flatten xrefs or purge definitions that may carry standards/data.
  • Do not invent command flags/API signatures; verify release-matched Autodesk docs.

If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.

If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.

Manual Mac read-only inspector

scripts/autocad_native.py doctor reports installed bundle metadata without claiming a live connection. prepare --root ROOT --drawing A-101.dxf --workspace WORKSPACE stages a private new copy and a fixed AutoLISP command. Review the returned file/path, obtain any native load approval and run GRIDLINEINSPECT manually. receipt SESSION console.txt validates captured metadata and hashes. This is manual console transport, not MCP; AUDIT/edit/plot/DWG roundtrip remain NOT_TESTED. Never change host security preferences or load it into an unrelated drawing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.