oas-program

Use when capturing OAS design intent — room requirements, area targets, adjacency rules, circulation rules, or global constraints — before any geometry has been resolved.

查看源码

使用方法

复制安装命令，在自己的智能体环境安装前先检查源码包。
从原始文档核对所需工具、凭据和支持的宿主。
说明输入材料与期望交付物，并对照来源检查输出。

npx skills add https://github.com/autodesk-platform-services/open-architecture-standards-2d-floor-plans --skill oas-program

开始前需了解

安装不包含模型订阅、API 额度或访问文件的权限。
仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。

仓库原始内容

按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。

OAS Program

When to use

Use this skill when the user is describing what they want rather than what exists: target areas, must-be-near rules, circulation preferences, count of rooms, hard limits. Program is the brief; Layout is the answer. If a polygon or wall coordinate is being emitted, you're in oas-layout territory, not here.

Key fields (the document is a flat JSON object, not typed classes)

oas_program, plan_id, title, description — metadata; plan_id links program → layout
design_goal — natural-language intent sentence (helps LLM context)
global_constraints — target_area_m2, max_area_m2, orientation_preference, climate, accessibility_level, etc.
rooms[] — each entry has id, usage, desired_area_m2, must_have, should_have, adjacency, avoid
adjacency — uses prefixed keys: must_touch, should_touch, avoid_touch, must_connect_via
circulation — primary_entry + free-form rules[]
rationale — optional reasoning string per room

Critical rules

Intent only — no resolved geometry. Program documents must not contain boundary_polygon, walls, or coordinates. Resolved geometry lives in OAS-Layout.
`desired_area_m2` accepts `{ "min": X, "max": Y }` or an exact number. Both are valid per the spec — don't reject a scalar.
Constraint strength is encoded by the field prefix, not a flag. must_have/must_touch are hard; should_have/should_touch are soft; avoid_touch is a hard negative. There's no separate hard: true field.
Refer to rooms by program `id`, not Layout ids. Layout ids don't exist yet — adjacency targets are program-level ids like "corridor" or "living_kitchen".
Circulation `rules[]` are natural-language strings. Solvers parse them heuristically; keep them concise and declarative.

Full schema

See docs/program.md for the complete reference, including constraint composition and adjacency weighting.

Related skills

oas-layout — the resolved geometry derived from a program
oas-core — for the vocabulary of usage values shared with Layout

按任务相关推荐

来自同一仓库

oas-layout

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.

安装量: 1
GitHub Stars: 9
最近更新: 5月19日

Apache-2.01 文件

查看详情 →

autodesk-platform-services

社区

oas-geometry

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.

安装量: 1
GitHub Stars: 9
最近更新: 5月19日

Apache-2.01 文件

查看详情 →

autodesk-platform-services

社区