muapi-floor-plan-rendering
- Repo stars 3,374
- Author updated Live
- Author repo Generative-Media-Skills
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 92 / 100 · audit passed
- Author / version / license
- @SamurAIGPT · v1.0.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Required · Vendor-specific
- Operating systems
- Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: muapi-floor-plan-rendering
description: Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.…
category: design
runtime: no special runtime
---
# muapi-floor-plan-rendering output preview
## PART A: Task fit
- Use case: Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering. | Name | Type | Required | Default | Description | |:---|:---|:---|:---|:---| | floorplandescription | text | yes | — | Description of the floor plan (e.g. "a modern 2-bedroom apartment with a balcony and open kitchen"). | requires Vendor-specific API key. Wor….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Inputs / Steps / Phase A — 2D Floor Plan Design” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering. | Name | Type | Required | Default | Description | |:---|:---|:---|:---|:---| | floorplandescription | text | yes | — | Description of the floor plan (e.g. "a modern 2-bedroom apartment with a balcony and open kitchen"). | requires Vendor-specific API key. Wor…”.
- **02** When the source has headings, the agent prioritizes “Inputs / Steps / Phase A — 2D Floor Plan Design” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Inputs / Steps / Phase A — 2D Floor Plan Design”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: muapi-floor-plan-rendering
description: Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.…
category: design
source: SamurAIGPT/Generative-Media-Skills
---
# muapi-floor-plan-rendering
## When to use
- Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering. | Name | Type | Requi…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Inputs / Steps / Phase A — 2D Floor Plan Design” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "muapi-floor-plan-rendering" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Inputs / Steps / Phase A — 2D Floor Plan Design
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | may access external network resources
guardrails -> requires Vendor-specific API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
- Prompt:
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
muapiCLI commands. Usemuapi auth configurefirst ifMUAPI_API_KEYis 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 withmuapi predict wait <request_id>. - Substitute
{{input_name}}placeholders with the user's actual inputs before issuing each call.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review