tekton

Create a new Revit project or family file from scratch when the user asks to build, generate, author or 'make me' a Revit (.rvt/.rfa) file, a room, an electrical room, walls, a panelboard, switchboard, transformer, lighting layout, or a family — from a plain-English prompt, an IFC file, or an existing .rvt to extend. Asks the recipient's Revit YEAR first (Revit cannot open a newer file; 2026/2025/2024 build natively on certified bases, older years get an honest fallback plus IFC), then runs the tekton front door in ONE call (scripts/_bootstrap.py go author --prompt | --ifc | --rvt --target-version YEAR) and returns the .rvt plus the honest per-release status, PROOF-ONLY stamps and manifest. Also handles 'turn this IFC into Revit' and 'give me the Three.js/IFC handoff for a prompt'. Formats, examples and caveats are in the skill body and references/.

Author, export, validate, harden, and hand off 3D building/MEP models from Claude Design (three.js three-d-stage pages) so they land in Autodesk Revit as clean, correctly-categorized, as-editable-as-possible elements. Use whenever the user wants to build or export a model 'for Revit', download or generate IFC from Claude Design or three.js, make an IFC file open or link cleanly in Revit, model electrical/MEP equipment for Revit (panelboards, switchboards, transformers, lighting, trapeze hangers, conduit racks, cable tray, disconnects), validate/harden/repair an existing .ifc, map IFC property sets onto Revit shared parameters, or prepare a shop-drawing / coordination-model handoff for a Revit user. Covers the tagging contract for the canonical ifc-export.js, the sandbox scripts (validate_ifc.py, harden_ifc.py, report.py, generate_ifc.py), and the Revit-side checklist (Link vs Open IFC, shared parameters, version limits). Not for editing .rvt binaries or non-Revit CAD.

Inspect, validate or audit a Revit .rvt/.rfa file when the user asks whether a file is valid, what is in it, why it fails to open, whether created elements will render (load-vs-render), for a panel schedule, or for a seed/content audit. Runs scripts/rvt_validate.py, the render inspector (python -m rvt.render.inspect), scripts/seed_audit.py and scripts/panel_schedule.py, then explains the results in plain language. How to read validator layers, LOADED-vs-RENDERED verdicts and the audit report is in the skill body.

Author, edit, inspect and validate NATIVE Autodesk Revit .rvt files with the bundled reverse-engineered `rvt` engine (pure Python; install once with `pip install ./lib` from the plugin root). Use whenever the user has an actual .rvt (not IFC) and wants to open/inspect it (streams, class schema, elements, tables), make a proven content edit (e.g. change text such as a title, panel name or note and re-emit a file Autodesk still opens), re-write a .rvt end-to-end, or run the mandatory pre-delivery self-checks (gzip CRC, per-page ECC, block walker, record stamps) before an Autodesk-Viewer acceptance test. Also the entry point for the in-progress element-creation API (add_wall / add_family_instance). For IFC authoring/validation/hardening use the sibling tekton-ifc skill instead. Always states which capabilities are viewer-proven vs in-progress and never overclaims.