Orchestrate an architectural concept workflow across Rhino, Blender, and ComfyUI connectors.
SkillScore83Maintained
Automatic
◆Real Estate & Property pack
Last verified 8/20/2026
What it changes
Passed 18 of 22 test cases with the skill, and 8 of 22 without it.
Without skill35%
With skill83%
Checks it passed that the model alone missed
Updates manifest.json immediately after each successful stage
Assigns materials by layer or object names upon geometry import
Provides connection setup instructions for the missing connector
and 10 more in the full report
11 fixed8 passed either way4 still failing0 broke
Pass-rate lift
+48 pp
Tokens
+6%
Agent turns
0%
Response time
-34%
Model gemini-3.6-flashMeasured 8/20/2026v119 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
I am configuring the photoreal diffusion generator bridge connection. What host address and port should be queried by default if no override variable is specified?
What was checked, without and with the skill
Checked
Without skill
With skill
Defaults to http://127.0.0.1:8188 for the photoreal generator connection
Missed
Passed
case-16 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md57 linessingle file
Architecture Design
Purpose
Orchestrate architectural concept design from brief and references through Rhino massing, Blender rendering, and ComfyUI photoreal output.
Routing
Use when: The user asks to design, model, render, or iterate an architectural concept, floor plan, house, building massing, site plan, facade, or photoreal architecture visualization.
Do not use when: The user only wants a high-level written strategy, a building-code/legal opinion, or structural/MEP engineering certification.
Outputs: Project manifest, Rhino model outputs, Blender scene/render outputs, ComfyUI images, decisions, warnings, and next-step checklist.
Success criteria: The workflow uses connector evidence for every claimed app action, keeps artifacts in a workspace project folder, and asks for approval before destructive changes or long-running renders.
Workflow
Create a workspace project folder under .cowork/architecture-projects/<project-id>/ and use it as COWORK_ARCH_PROJECT_ROOT.
Write brief.json and manifest.json before calling design tools.
Check connector health in this order:
mcp_rhino.health
mcp_blender.health
mcp_comfyui.health
If Rhino is available, create/open the project, import site references, create terrain/setbacks, generate massing, generate floor plans, validate, then export to Blender format.
If Blender is available, import the Rhino export, assign materials by layer/object names, set camera and lighting, render one or more views, and save the scene.
If ComfyUI is available, submit the chosen render plus prompt context through the photoreal workflow, monitor status, and collect outputs.
Update manifest.json after every successful stage with file paths, tool results, warnings, and pending decisions.
Use computer-use tools only as a fallback for native UI actions that have no connector/tool path.
Safety Rules
Never claim Rhino, Blender, or ComfyUI completed a step without a tool result or saved artifact.
Keep all generated files in the project folder; connector file arguments are rejected if they resolve outside COWORK_ARCH_PROJECT_ROOT.
Copy imported user assets into the project folder before mutation.
Ask for confirmation before overwriting source CAD files, deleting generated assets, or starting expensive/long renders.
Treat the result as concept design unless a licensed professional validates code, structure, accessibility, and MEP requirements.