Menu
Use when adding or editing OAS extension blocks — machinery, materials, site, MEP, or Autodesk metadata — that augment a Core or Layout document.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when authoring or editing OAS-Core JSON — rooms, walls, openings (doors/windows), curtain walls, roofs, floor slabs, furniture, railings, or annotations in a 2D floor plan.
Use when writing or debugging OAS geometry — points, polygons, line segments, arcs, circles, spirals, fillets, units, or coordinate conventions. Load before any geometry-heavy edit.
Use when producing or editing fully resolved OAS-Layout JSON — multi-level plans with levels, rooms, walls, openings, slabs, roofs, furniture, railings, and inter-level connections.
Use when capturing OAS design intent — room requirements, area targets, adjacency rules, circulation rules, or global constraints — before any geometry has been resolved.
Use when mapping OAS plans to a visual output — SVG, Canvas, or WebGL — including scale, axis orientation, and z-order layering.
| name | oas-extensions |
| description | Use when adding or editing OAS extension blocks — machinery, materials, site, MEP, or Autodesk metadata — that augment a Core or Layout document. |
Use this skill any time the task involves attaching domain-specific data outside the Core/Layout vocabulary: industrial machinery, materials, MEP systems, site context, or vendor metadata (Autodesk/Revit families, APS URNs). If the data fits a Core entity directly (e.g. a Furniture placement), keep it in Core — don't reach for an extension.
Extension envelope — top-level extensions dictionary keyed by extension nameMachinery — industrial equipment with multi-axis rotation and CAD geometry sourceMaterial — material definitions referenced by id from Core/Layout entitiesSite — site context (boundaries, orientation, surroundings)AutodeskMetadata — Revit family names, APS URNs, vendor-specific identifiers"extensions": { "oas-machinery": { "version": "..." }, "oas-autodesk": { ... } }. Parsers must still accept the legacy array form, but new documents should emit the dictionary.oas-furniture (position, rotation, dimensions, in_room) and oas-3d (wall_height_mm, base_offset_mm, top_profile_points, etc.) are deprecated extension names. Put these fields directly on Core entities; do not declare "oas-furniture" in extensions.version field independent of the OAS document version. Semver applies.rotation_deg (Z, the default), rotation_x_deg, rotation_y_deg. Separate fields in degrees; don't fold them into one.geometry_ref vs geometry_source. Base oas-machinery uses a simple geometry_ref URI/path string. When oas-autodesk is also active, machinery may carry the structured geometry_source object (urn, external_id, item_id, file_name, is_y_up, import_mode, mesh_quality) for APS Model Derivative / ACC imports.revit_family / revit_type, APS external_id, etc., go under oas-autodesk, never inline on Core Wall.type_name.See docs/extensions.md for the full reference, including the dictionary envelope, per-extension schemas (machinery, autodesk, MEP, materials, site), and the 1.0→1.1 migration notes.
oas-core — the document an extension augmentsoas-layout — extensions also attach to resolved layouts (e.g. machinery placed on a floor)