muapi-floor-plan-rendering

Design Community v1.0.0

Repo stars 3,374
Author repo Generative-Media-Skills

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering. | Name | Type | Required | Defa…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Inputs”, “Steps”, “Phase A — 2D Floor Plan Design”, “Phase B — 3D Rendering”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name muapi-floor-plan-rendering directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Inputs / Steps / Phase A — 2D Floor Plan Design” before expanding.

Boundaries And Review

Dependencies: Prepare Vendor-specific API keys before running a full task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Floor Plan Rendering

Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.

Inputs

Name	Type	Required	Default	Description
`floor_plan_description`	text	yes	—	Description of the floor plan (e.g. "a modern 2-bedroom apartment with a balcony and open kitchen").
`base_plan_image`	image_url	no	—	Optional 2D floor plan image to use as a starting point.

Steps

Phase A — 2D Floor Plan Design

If {{base_plan_image}} is not provided, submit the plan with ONE step to create the 2D blueprint:

Floor Plan Generation — muapi image generate (model=nano-banana-2):
- Prompt: A professional, clean 2D architectural floor plan of {{floor_plan_description}}. Top-down view, technical drawing style, white background, black lines, labeled rooms (Living Room, Kitchen, Bedroom, etc.), high contrast, minimalist design.
- Aspect ratio: 4:3 or 1:1

Present the 2D plan to the user for approval.

Phase B — 3D Rendering

Once the 2D plan is ready, submit the plan to convert it into a realistic 3D visualization:

3D Conversion — muapi image edit (model=nano-banana-2-edit):
- Reference Image: The 2D plan from Phase A.
- Prompt: A stunning, realistic 3D isometric cutaway rendering of the architectural floor plan. Photorealistic textures, warm wooden flooring, modern furniture, soft natural sunlight coming from windows, realistic shadows. High-end architectural visualization, cinematic look, 8k resolution, clean white studio background.
- Aspect ratio: 4:3 or 1:1

After generation, present the final 3D rendering to the user.

Trigger Keywords

3d floor plan, architectural rendering, 2d to 3d plan, house design, interior plan

Notes for the Executing Agent

This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call muapi CLI commands. Use muapi auth configure first if MUAPI_API_KEY is unset.
For model IDs without a CLI alias yet, fall back to the raw endpoint via curl -X POST https://api.muapi.ai/api/v1/<endpoint> -H "x-api-key: $MUAPI_API_KEY" -H 'content-type: application/json' -d '{...}' and poll with muapi predict wait <request_id>.
Substitute {{input_name}} placeholders with the user's actual inputs before issuing each call.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Design
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 92 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @SamurAIGPT · v1.0.0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: Required · Vendor-specific
Detected OS requirements: Windows
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview muapi-floor-plan-rendering.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Floor Plan Rendering

**Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.**

## Inputs

| Name | Type | Required | Default | Description |
|:---|:---|:---|:---|:---|
| `floor_plan_description` | text | yes | — | Description of the floor plan (e.g. "a modern 2-bedroom apartment with a balcony and open kitchen"). |
| `base_plan_image` | image_url | no | — | Optional 2D floor plan image to use as a starting point. |


## Steps

### Phase A — 2D Floor Plan Design

If `{{base_plan_image}}` is not provided, submit the plan with ONE step to create the 2D blueprint:

1. **Floor Plan Generation** — `muapi image generate` (model=`nano-banana-2`):
   - Prompt: `A professional, clean 2D architectural floor plan of {{floor_plan_description}}. Top-down view, technical drawing style, white background, black lines, labeled rooms (Living Room, Kitchen, Bedroom, etc.), high contrast, minimalist design.`
   - Aspect ratio: 4:3 or 1:1

Present the 2D plan to the user for approval.

### Phase B — 3D Rendering

Once the 2D plan is ready, submit the plan to convert it into a realistic 3D visualization:

1. **3D Conversion** — `muapi image edit` (model=`nano-banana-2-edit`):
   - Reference Image: The 2D plan from Phase A.
   - Prompt: `A stunning, realistic 3D isometric cutaway rendering of the architectural floor plan. Photorealistic textures, warm wooden flooring, modern furniture, soft natural sunlight coming from windows, realistic shadows. High-end architectural visualization, cinematic look, 8k resolution, clean white studio background.`
   - Aspect ratio: 4:3 or 1:1

After generation, present the final 3D rendering to the user.

## Trigger Keywords

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Inputs → Steps → Phase A — 2D Floor Plan Design → Phase B — 3D Rendering → Trigger Keywords → Notes for the Executing Agent
terms    -> Floor Plan Generation · 3D Conversion · Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering. · Present the 2D plan to the user for approval. · 1. 3D Conversion — muapi image edit (model=nano-banana-2-edit): - Reference Image: The 2D plan from Phase A. · After generation, present the final 3D rendering to the user. · - This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call muapi CLI commands.
files/cmd -> floorplandescription · baseplanimage · {{baseplanimage}} · muapi image generate · nano-banana-2 · muapi image edit · nano-banana-2-edit · 3d floor plan
body sha256 -> c3d9f70b2f83