菜单
Write pyRevit IronPython tools for Revit with correct project structure, coding conventions, and WPF/MVVM patterns. Use when creating or editing pyRevit pushbutton scripts, shared libs, bundle.yaml, XAML views, or ViewModels.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create and run CAD/BIM API tests using pytest via RevitDevTool Named Pipe bridge. Use when writing new pytest test files for Revit/AutoCAD/Civil3D API, adding test fixtures for host documents/elements, running tests against a live host instance, setting up conftest.py with PEP 723 dependencies, or asking "how do I test Revit API with pytest". Covers test structure, fixtures, lazy imports, transactions, auto-rollback, dependency injection, and CLI options.
Build and test Revit add-ins with correct configurations for Revit 2022-2027 (NET 4.8, NET 8.0, NET 10.0). Use when building, compiling, testing, packaging Revit projects, or when the user mentions Revit versions, build configurations, testing across multiple Revit versions, or the ModularPipelines build system.
Retrieve and analyze Revit API documentation through the local Revit API Docs MCP server. Use when answering questions about Autodesk Revit API classes, methods, properties, version differences, obsolete or changed APIs, migration between Revit 2020-2027, or when writing/reviewing Revit API code that needs authoritative docs.
| name | pyrevit-ironpython |
| description | Write pyRevit IronPython tools for Revit with correct project structure, coding conventions, and WPF/MVVM patterns. Use when creating or editing pyRevit pushbutton scripts, shared libs, bundle.yaml, XAML views, or ViewModels. |
from Autodesk.Revit import DB, never from Autodesk.Revit.DB import *HOST_APP.doc/HOST_APP.uidoc at module level; pass as parametersengine.clean: true — enable during development for module reload; disable in release for cached performance"{}".format(x) not f-strings, ParentClass.__init__(self) not super()# type: (str, int) -> boolconstants/models/services/viewmodels/views/utilslib/ naming convention — extension-level lib/ for shared code, pushbutton-level lib/ for tool-specific code# Imports — at module top
from Autodesk.Revit import DB
from pyrevit import HOST_APP
from pyrevit.compat import get_elementid_value_func
element_id_value = get_elementid_value_func() # utility — safe to cache
# Revit API calls — always inside methods, doc passed as parameter
def collect_schedules(doc):
# type: (DB.Document) -> list[DB.ViewSchedule]
return list(DB.FilteredElementCollector(doc).OfClass(DB.ViewSchedule).ToElements())
def main():
# type: () -> None
doc = HOST_APP.doc # local scope only
schedules = collect_schedules(doc)
title: My Tool Name
context: doc-project # doc-project | zero-doc | selection
tooltip:
en_us: |
Version = 1.0
Description: ...
author: "Author.Name"
engine:
clean: true # development: true (reload modules); release: false (cached, faster)
| File | When to Read |
|---|---|
| Project Structure | Extension layout, bundle hierarchy, shared vs local lib, entry point pattern |
| Coding Conventions | Python 2/3 compat, import rules, type hints, transactions, error reporting |
| WPF & MVVM | ObservableBase, RelayCommand, WPFWindow, notifications, XAML templates |