skills.rest
hebackus
hebackusCOMMUNITY
Explore all skills by this author →
GitHub

acad-xdata-dictionaries

Manage per-drawing and per-entity metadata with XData, XRecord, and dictionaries.

3|Updated Feb 17, 2026
Search Tags:#nod#civil-3d#autocad-api#xdata#xrecord#extension-dictionary#named-object-dictionary
One-click install
npx skills add https://github.com/hebackus/c3d-api-plugin --skill acad-xdata-dictionaries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acad-xdata-dictionaries
Source: https://github.com/hebackus/c3d-api-plugin/tree/main/skills/acad-xdata-dictionaries
Command: npx skills add https://github.com/hebackus/c3d-api-plugin --skill acad-xdata-dictionaries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persisting custom per-drawing or per-entity metadata in Civil 3D and AutoCAD drawings is essential for configuration, auditing, and tooling integration. XData, XRecord, and dictionaries (NOD and extension dictionaries) provide a scalable approach to store lightweight key-value data and structured records alongside CAD data.

Core Features & Use Cases

  • XData: attach lightweight key-value data to any DBObject using a RegApp name and a ResultBuffer.
  • Named Object Dictionary (NOD): store drawing-wide dictionaries of XRecord data for configuration and cross-drawing access.
  • Extension Dictionaries: per-entity dictionaries to hold large or structured data without cluttering entities.
  • Reading and writing: demonstrates writing and reading XData, XRecord, and dictionary-stored data from objects and the drawing.

Quick Start

Register your application in RegAppTable and attach a small XData buffer to an entity.

Frequently Asked Questions about acad-xdata-dictionaries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attach custom per-entity metadata in AutoCAD using XData?▼

To attach XData in AutoCAD, register your application in the RegAppTable and apply a ResultBuffer of key-value pairs to the target DBObject. This stores lightweight metadata directly on the entity for later retrieval.

What is the difference between XData and extension dictionaries in Civil 3D?▼

XData stores lightweight key-value data on any DBObject, while extension dictionaries hold larger or structured XRecord data per-entity. Dictionaries prevent cluttering the object and support complex configuration persistence.

When should I use the Named Object Dictionary for drawing-wide configuration in AutoCAD?▼

Use the Named Object Dictionary (NOD) when you need to store drawing-wide configuration data or share XRecord data across drawings. NOD provides a central, scalable location for persistent application settings.

How do I read and write XRecord data in an AutoCAD extension dictionary?▼

You write XRecord data by creating an extension dictionary on the entity and adding entries via ResultBuffer. Reading involves traversing the dictionary and extracting the stored structured values back into your application.

Can I persist drawing-wide configuration settings in Civil 3D without external files?▼

Yes, you can persist drawing-wide configuration in Civil 3D without external files by using the Named Object Dictionary. It stores XRecord data inside the drawing, ensuring settings travel with the file and share across contexts.

Related Skills

Explore More Software Engineering Skills→
thinking-machines-labthinking-machines-lab
4.0k

setup

Guide Tinker installation, environment setup, API key provisioning, and verification.

Official
Intermediate
zhcndoczhcndoc

session-logs

Analyze JSONL session logs with jq and ripgrep to locate past conversations.

Official
Intermediate
hebackushebackus
3

acad-editor-input

Automate AutoCAD point, entity, and string input prompts with typed value filters.

Community
Intermediate
hebackushebackus
3

acad-database-operations

Copy layers, blocks, and symbol-table records between Civil 3D/AutoCAD databases.

Community
Advanced