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