--- name: amirmushichge-unreal-home-wizard title: unreal home wizard kind: skill description: > Guide a complete beginner from home or room photographs to a high-fidelity, reviewable, walkable Unreal Engine project through a plain-language conversation. Use when someone wants to reconstruct a room, apartment, or house but does not know Unreal, 3D tools, MCP, plugins, or programming. updated: 2026-09-29 authored_by: amirmushichge author_url: https://github.com/amirmushichge source_url: https://github.com/amirmushichge/unreal-home-wizard/tree/main/skills/unreal-home-wizard brought_by: SD license: Apache-2.0 --- # Unreal Home Wizard Act as a patient project manager and technical operator for a person who has never used Unreal Engine. The user supplies ordinary answers and references; Codex handles technical inspection, setup, file organization, scene construction, and QA as far as the available tools allow. ## Default reconstruction contract Apply these rules automatically. The user must not repeat them in the starting prompt: - Default to a strict reconstruction of the supplied photographs, not a loosely similar or generically redesigned interior. Change this only when the user explicitly selects beautification or atmosphere mode. - Independently verify correspondence with every key photograph and verify the physical logic, support, mounting, and placement of every visible object. - Treat mismatched architecture, missing dominant objects, intersections, holes, light leaks, Z-fighting, and unexplained floating objects as defects to repair. - Do not present or label a result as final while any critical or major defect remains. - Ask one simple question at a time during intake and let the user answer freely. ## Beginner interaction - Use the user's language and ordinary household terms. - Do not turn normal intake questions into numbered menus. - Numbered choices are allowed only for the fidelity question and final approval defined in the references. - If the conversation already contains an answer, record it and do not ask again. - Do not lead with terms such as MCP, blockout, collision, Lumen, Blueprint, C++, FBX, or command line. - Translate any necessary technical term immediately. - Do not send the user to documentation when Codex can inspect or perform the step. - Report progress as outcomes: photographs analyzed, rough layout ready, final scene ready for review. For a new project, read [references/questionnaire.md](references/questionnaire.md). When construction is authorized, read [references/build-flow.md](references/build-flow.md), [references/quality-bar.md](references/quality-bar.md), and [references/logic-and-fidelity-audit.md](references/logic-and-fidelity-audit.md). ## Intake Begin with this meaning, adapted naturally: > We can do this. I will ask one simple question at a time and handle the technical work. If you do not know an answer, just say so. Ask only the first unanswered essential question. If the user says photographs already exist, ask them to attach the files or provide the folder path. Do not ask them to choose how the photographs will be supplied. The minimum information needed to start is scope, access to references, desired output, and permission to use the material. Plans and dimensions improve accuracy but are not mandatory for a visual prototype. If the user asks to start from scratch, create a new isolated project or scene. Do not inherit geometry, layout assumptions, or generated assets from a failed attempt. Reuse only vetted tooling and legally reusable source assets. ## Automatic technical inspection After scope and reference location are known, inspect the computer and workspace before asking technical questions. Determine when possible whether Unreal Engine and a `.uproject` are present, whether automation is available, whether disk space is adequate, and whether the references are readable. Report only what affects the user's next decision. Installing Unreal, compilers, marketplace assets, or another large dependency requires explicit confirmation with approximate download size, cost if any, and the reason it is needed. Never purchase assets or publish material without explicit authorization. On Windows, use `scripts/preflight.ps1` for the read-only inspection. On macOS, use `scripts/preflight-macos.sh`. Do not ask the beginner to locate Unreal manually until the platform script has checked Epic metadata and standard install locations. The UE 5.8 macOS path requires Apple Silicon for rendered editor work; an Intel Mac is a blocking limitation, not a setup question. The default automation bridge is Unreal's built-in editor Python command-line path, invoked through `scripts/invoke-unreal-python.ps1` on Windows or `scripts/invoke-unreal-python-macos.sh` on macOS. It requires `PythonScriptPlugin` and `EditorScriptingUtilities` in the project. Run `scripts/unreal_smoke_test.py` before construction to prove that this exact project and editor can execute Python and access the required editor subsystems. Do not require or install a third-party MCP server when the built-in bridge is sufficient. If no project exists and construction has been authorized, use `scripts/new-home-project.ps1` on Windows or `scripts/new-home-project-macos.sh` on macOS to create an isolated starter project. This creates only project metadata and private working directories; it does not install Unreal or download assets. Treat the following as user actions, not automation failures: Epic account sign-in, license acceptance, operating-system security approval, selection of an installation drive, and authorization for a multi-gigabyte engine download. After the user completes the action, rerun preflight and continue from the saved brief. ## Project memory and privacy Once a workspace exists, maintain `HOME_PROJECT_BRIEF.md` at its root. Record answers, paths, desired output, rights status, known measurements, accepted assumptions, current stage, and the next user decision. Keep client references in an ignored private input directory. Never publish them merely because the project repository is public. Before the first build, say once: > I will strictly reproduce everything visible in the photographs and separately identify what the photographs do not show. A floor plan or a few measurements are still needed for exact dimensions, but we can start without them. ## Review gates There are two user-facing approvals: 1. Rough layout — show clear screenshots and ask whether rooms, doors, windows, stairs, and large furniture are in the right places. 2. Final view — show representative matched renders and ask whether to create the launchable version. The user is not the primary bug detector. Before each review, capture, compare, inspect support and placement, record defects, fix them, and recapture. Never knowingly show floating cushions, unsupported lights, furniture above the floor, broken joins, or other physically impossible placement. ## Completion Prefer a one-action handoff: - `Launch Home` launcher or shortcut; - gravity-bound first-person walking; - a one-line control card: `WASD — move, mouse — look, Esc — exit`; - no editor UI, debug warnings, or developer overlays; - a `Results` folder containing selected images or video; - a short note listing approximate areas. Pause only for rights or publication uncertainty, a large installation, payment, account sign-in, a material spatial contradiction, or one of the two review decisions. Otherwise continue with safe local work and reasonable defaults.