plans-to-walkthrough
Turn an architect's drawing set (PDF floor plans, elevations, sections) into a to-scale 3D model of the house that opens in a browser, with first-person walk mode, a dollhouse cutaway, a tape-measure tool and real sun and shadows. Use this whenever someone has plans, blueprints, construction drawings or a floor plan for a house, addition, renovation or apartment and wants to walk through it, see it in 3D, get a feel for room sizes, ceiling heights or daylight, check how furniture fits, or share a 3D view with family or a builder, even if they never say "3D model" or "walkthrough".
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/testinprod-ai--plans-to-walkthrough)HTML
<a href="/listings/testinprod-ai--plans-to-walkthrough"><img src="/api/listings/testinprod-ai--plans-to-walkthrough/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
These steps run a script from the network that findsafeskills does not scan.
Open cmux. You will see a prompt waiting for you to type. Paste this line and press Enter:
curl -fsSL https://claude.ai/install.sh | bash
On Windows, open PowerShell and use this instead:
irm https://claude.ai/install.ps1 | iex
When it finishes, type `claude` and press Enter. The first time, your browser opens so you can sign in.
If cmux does not flag the tab when Claude finishes a job, run `cmux hooks setup` once and restart Claude Code.
Prefer no terminal at all? The Claude desktop app has a Code tab that does the same job. The skill works there too, as long as the session runs on your own computer.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 118 lines
- ---
- name: plans-to-walkthrough
- description: Turn an architect's drawing set (PDF floor plans, elevations, sections) into a to-scale 3D model of the house that opens in a browser, with first-person walk mode, a dollhouse cutaway, a tape-measure tool and real sun and shadows. Use this whenever someone has plans, blueprints, construction drawings or a floor plan for a house, addition, renovation or apartment and wants to walk through it, see it in 3D, get a feel for room sizes, ceiling heights or daylight, check how furniture fits, or share a 3D view with family or a builder, even if they never say "3D model" or "walkthrough".
- ---
- # Plans to walkthrough
- The owner of a house project usually cannot read drawings the way their architect can. What they want is to stand in the kitchen and feel whether it is big enough. This skill builds that: a model typed in from the drawings in real feet and inches, shown in a single web page they can walk around in.
- The value is accuracy and honesty. A pretty model with a wrong ceiling height misleads the owner about the one thing they came for. So the method is: read dimensions off the drawings, check the model against the drawings mechanically, and tell the owner exactly what was assumed.
- ## What you are building
- A project folder with three things:
- - `tools/build_data.py`: the single source of truth. The house is typed here as calls like `W()` for a wall, `O()` for an opening, `R()` for a room. Running it writes `house-data.js`.
- - `house-data.js`: generated. Never edit it by hand, because the next build overwrites it.
- - `index.html`: the viewer. It only draws what the data says, so almost all the work is in `build_data.py`.
- Start by copying `assets/template/` from this skill into the project folder. The template holds a small invented example house; build it and open it once so you know what a working result looks like, then replace the example section with the real house. Read `references/model-format.md` before typing geometry: it lists every helper, the settings block, material names and the viewer's URL parameters.
- Geometry is typed in by you, by reading the sheets. Do not try to auto-trace walls from the PDF linework. Drawing sets mix walls, dimensions, hatches and notes in ways that defeat tracing, and a traced model cannot tell you which numbers are trustworthy.
- ## Setup
- Python 3 with PyMuPDF and Pillow (make a virtual environment), and Chrome or Chromium for the automated checks. If Chrome is missing, the model still builds and the owner can open `index.html` directly, but you lose the walk test and screenshots, so say so.
- ## Workflow
- ### 1. Ask what the owner wants from it
- Usually it is scale and feel, not finishes. Ask which rooms they care about most and whether there is anything they are unsure of in the design. Unless asked, leave furniture and finishes out at first: guessed sofas and guessed cabinet colours get mistaken for the architect's intent. Add them later, when the owner asks, and label them as guesses.
- ### 2. Survey the drawing set
- Run `scripts/render_sheets.py info SET.pdf`. Make a short table for yourself: which page is which plan, which are elevations, sections, interior elevations, and the scale of each.
- Things that go wrong here:
- - **Scale differs from sheet to sheet**, and sometimes from what the title block says (a plan may be printed reduced). Confirm each sheet's scale by measuring a written dimension: find a dimension string, measure the same distance in points, and divide. Do this for every sheet you take numbers from.
- - **Pages are often stored rotated.** The script outputs "sheet coordinates" as a person sees the sheet: x to the right, y down, in feet.
- - **North is rarely up.** Find the north arrow and record the angle; the sun needs it.
- ### 3. Fix the coordinate system and the heights
- - Use one plan sheet (normally the ground floor) as the master. Every other floor is typed in its own sheet's coordinates and shifted by a fixed offset, measured on something that passes through both floors such as a stair or a chimney. Check the offset on a second feature.
- - Heights come from sections and elevations: floor-to-floor, ceiling heights, window sills and heads, roof plate and pitch. Height zero is the ground-floor finished floor.
- - Prefer a written dimension to a scaled measurement every time. When you have to scale from linework, mark the room `basis="scaled"` so the viewer shows the owner that the size is approximate (about an inch either way at quarter-inch scale).
- ### 4. Type the house in, one floor at a time
- Order that works: exterior walls, interior walls, openings, rooms (name, ceiling height, floor), stairs and landings, then built-ins. Use `scripts/render_sheets.py crop` to read details at high resolution and `text` to find written dimensions and room names.
- After each batch, run the overlay check, which draws the model over the plan raster:
- ```
- python3 <skill>/scripts/render_sheets.py page SET.pdf 2 --ppf 54 -o sheets/full2.png # once per plan page
- python3 tools/build_data.py --overlay sheets --pages 2,3 --ppf 54 # writes sheets/overlay0.png, overlay1.png
- ```
- Look at the overlay yourself. Walls should sit on the drawn walls and openings on the drawn doors and windows. This catches most mistakes within minutes, long before the 3D view would reveal them.
- Write down every guess in `notes` as you make it, in plain language the owner can follow ("Closet partitions upstairs are partly assumed"). The viewer shows these in its Assumptions panel. Keep a separate list of questions that only the architect can answer, such as a hatch that could be a low built-in or a full wall, or two dimensions that disagree.
- ### 5. Build and run the walk test
- ```
- python3 tools/build_data.py
- python3 <skill>/scripts/check.py qa index.html
- ```
- The walk test flood-fills from the start room as a person walking, and reports which rooms were reached and where someone could step off an unguarded edge. An unreached room nearly always means a missing or misplaced door opening, or a wall drawn across a doorway. An unguarded drop means a missing guard or stair wall. Fix these before showing anyone; they are real modelling errors, and they are the kind an owner trips over in the first minute.
- ### 6. Look at it, cheaply
- Take screenshots with `scripts/check.py shot` and compare them with the elevations and sections: window positions, roof shape, how the stair lands. Screenshots are large, so if you can delegate, send them to a subagent that reports back in words, and keep them out of the main conversation.
- ### 7. Roof, exterior and site
- Add roofs from the roof plan and elevations, then exterior materials from the elevation notes. The ground is flat by default. Real terrain comes with the surroundings step below; outside the United States a height grid can be supplied by hand as `tools/site_dem.json` (see the Terrain section of `references/model-format.md`). Where survey data and the drawings disagree about grade, model what the drawings show and put the conflict on the architect list.
- Set the site's approximate latitude, longitude and rotation in the settings block so the sun is right. Round the location to the nearest town; that is accurate enough for sun angles and keeps the exact address out of the file.
- ### 7b. Real surroundings (optional, United States only)
- Owners light up when they see their actual yard: the neighbours' houses, their own trees, the slope of the lot. It also makes the sun study honest, because a 70 ft tree to the south changes a room's winter light more than any window does. `scripts/fetch_site.py` builds this from public data: USGS lidar for terrain, roof shapes and tree heights, OpenStreetMap for building outlines and roads, and a public aerial photo for the ground. The commands, in order, are in the Surroundings section of `references/model-format.md`.
- Ask before you start, because this is the one step that sends the home's location to outside services:
- - Ask for the street address (or a map pin) and say plainly what happens with it: one lookup with the US Census geocoder, then map-area requests to USGS and OpenStreetMap. Go ahead only if the owner agrees. If they would rather not, keep the flat site.
- - After `register`, show the owner the overlay image (the house outline drawn on the aerial photo) and ask them to confirm it sits on their house the right way round, with the street on the correct side. A rectangular house fits its outline four ways, and the script cannot always tell which is right; the owner can, at a glance.
- - For a renovation or addition, register using only the part of the footprint that exists today.
- - Ask what has changed since the survey. The lidar and photo are usually a few years old, so ask about trees that were cut or planted, and about fences, sheds, decks and pools, none of which the data captures. Ask too which trees the project will remove.
- Then tell the owner what they are looking at: tree positions and heights are measured, their shapes are generic; neighbours are simplified masses; the data is as old as the survey. Trees standing where the design puts building or paving are dropped automatically and listed in `notes`. Read that list to the owner, because sometimes it reveals a tree they did not realise the design removes.
- Surroundings make the location recognisable to anyone who knows the area. Mention that again before publishing a link, and offer the option of sharing with surroundings switched off.
- ### 8. Hand it to the owner, then correct
- Give the owner the model along with two short lists: what was assumed, and what to ask the architect. Expect corrections, since they know things the drawings do not say. When the owner's statement conflicts with your reading of a drawing, the owner wins; record it in `notes` as their decision. When you reinterpret something on your own, say that it is an interpretation and ask them to confirm it.
- Furniture and finishes come now, if wanted, room by room. Use the furniture helpers for simple blocks at true size (a 7 ft sofa, a 3 x 6 ft table), which is what answers "does it fit". Take finishes from the interior elevations and the owner's choices, and do not make up a finish schedule.
- ### 9. Sharing
- The model is two files, `index.html` and `house-data.js`. If you can publish web pages for the user (for example as a Claude artifact, with `house-data.js` as a supporting file), offer that, because a link is the easiest thing to send to family or a builder and it works on a phone. Otherwise zip the two files. Ask before publishing: plans show where someone lives and how their house is laid out, so the owner decides who gets the link.
- ## Working habits that matter on a long project
- - **Keep a handoff note** in the project folder: conventions (scales, offsets, which way is north), what is done, open questions, how to test. These projects run over many sessions, and the coordinate conventions are impossible to re-derive quickly.
- - **Rebuild and re-run the walk test after every change**, and report its result truthfully, including when something was changed but not yet checked in a screenshot.
- - **Treat the address, drawings and layout as private.** Do not send them to outside services beyond what the owner asked for.
- - **Do not present guesses as the design.** Everything not on the drawings goes in `notes`.
- ## Limits to tell the user about
- The model is made of axis-aligned boxes, so walls that run at an angle or curve are approximated or need custom work in the viewer. See the limits section of `references/model-format.md` for storey count and roof types. Daylight shows direct sun and shadows for the real date and time, but not light bouncing around a room, so indoor brightness is indicative only. It is a tool for feeling scale and catching surprises, not a rendering and not a substitute for the architect's drawings.
README.md · README · 116 lines
- # Plans to walkthrough
- A skill for Claude that turns an architect's drawing set (a PDF of floor plans, elevations and sections) into a to-scale 3D model of the house. The model opens in a web browser. You can walk through it, look at it as a dollhouse, measure things, and see where the sun falls at any date and time.
- This guide assumes you have used the Claude app but not Claude Code. It takes about 20 minutes to get set up.
- ## 1. What is different about Claude Code
- In the Claude app you chat, and Claude hands things back to you. Claude Code is the same Claude, but it works directly in a folder on your computer: it reads the files there, writes new ones, and runs programs. That is what this skill needs, because building the model means reading your PDF, writing the model files and testing them, many times over.
- Two things to know before you start:
- - **It asks before it acts.** When Claude wants to change a file or run a command, it shows you what and waits. Press Enter to allow it.
- - **One folder per project.** Make a folder for your house, put the PDF in it, and start Claude Code there. Everything it makes stays in that folder.
- Claude Code is included in the Pro, Max, Team and Enterprise plans, so you sign in with the account you already have.
- ## 2. Install cmux (Mac only)
- Claude Code runs in a terminal, the text window programmers use. cmux is a free terminal app for Mac made for working with Claude Code, and it removes most of the learning curve:
- - A sidebar lists your projects as tabs, so you click between them.
- - A tab lights up when Claude has finished or needs an answer from you, so you can leave it working and come back.
- - It has a built-in browser, so the 3D model can open next to the conversation.
- - It restores your sessions when you reopen it.
- Download it from https://cmux.com ("Download for Mac"), open the file, and drag cmux into Applications.
- Shortcuts worth learning on day one:
- | Keys | What it does |
- |---|---|
- | Cmd+N | New workspace (one per project) |
- | Cmd+1 to Cmd+8 | Jump to a workspace |
- | Cmd+D | Split the window side by side |
- | Cmd+B | Show or hide the sidebar |
- | Cmd+Shift+U | Go to the latest notification |
- On Windows, skip this section. Use the Code tab in the Claude desktop app, or Windows Terminal.
- ## 3. Install Claude Code
- Open cmux. You will see a prompt waiting for you to type. Paste this line and press Enter:
- ```
- curl -fsSL https://claude.ai/install.sh | bash
- ```
- On Windows, open PowerShell and use this instead:
- ```
- irm https://claude.ai/install.ps1 | iex
- ```
- When it finishes, type `claude` and press Enter. The first time, your browser opens so you can sign in.
- If cmux does not flag the tab when Claude finishes a job, run `cmux hooks setup` once and restart Claude Code.
- Prefer no terminal at all? The Claude desktop app has a Code tab that does the same job. The skill works there too, as long as the session runs on your own computer.
- ## 4. Install the skill
- Paste this into the terminal (not into Claude):
- ```
- git clone https://github.com/testInProd-ai/plans-to-walkthrough ~/.claude/skills/plans-to-walkthrough
- ```
- The first time you use `git` on a Mac, it may offer to install "command line developer tools". Say yes, wait for it to finish, and run the line again.
- To get updates later:
- ```
- git -C ~/.claude/skills/plans-to-walkthrough pull
- ```
- To check it is installed, start Claude Code and type `/skills`. You should see `plans-to-walkthrough` in the list.
- The model-building steps use Python and Google Chrome. Macs have what is needed once Chrome is installed; Claude will tell you if anything is missing and offer to set it up.
- ## 5. Your first session
- 1. Make a folder, for example `house` in Documents, and put your drawing set PDF in it.
- 2. In cmux, press Cmd+N and choose that folder, then type `claude`.
- 3. Say what you want in your own words, for example:
- > Here are the plans for our renovation. Build me a 3D walkthrough so I can get a feel for the room sizes.
- Claude will look through the drawings, ask you a few questions, and start building. A first walkable model of a whole house usually takes a session or two. It will tell you what it assumed and what to ask your architect.
- Then correct it. You know things the drawings do not say, and telling Claude "there's no door there" or "that wall is only counter height" is how the model gets right.
- ## 6. Add your real yard and neighbours (optional, US only)
- Once the house itself is right, you can ask:
- > Add the real surroundings: our lot, the trees and the neighbours' houses.
- Claude will ask for your address and your permission to look it up. It uses public data only: government lidar surveys for the ground, tree heights and roof shapes, OpenStreetMap for building outlines, and a public aerial photo. It will show you a picture of your house outline on the aerial photo so you can confirm it is the right way round, and ask what has changed since the survey, because the data is usually a few years old and does not include fences or sheds.
- After that, the sun slider shows the shade from your actual trees and neighbours, summer and winter.
- ## 7. Things you will want to know in the first hour
- - **Stop it:** press Esc. Work done so far is kept.
- - **Show it a picture:** copy a screenshot, then press Ctrl+V in Claude Code (yes, Ctrl, even on a Mac).
- - **Start fresh:** `/clear` starts a new conversation in the same folder. Your files are untouched.
- - **Pick up where you left off:** `/resume` lists past conversations.
- - **Long conversations get slow and expensive.** Ask Claude to "write a handoff note", then `/clear` and say "pick up from the handoff".
- - **Leave:** type `/exit`.
- ## What the model is and is not
- It is typed in from your drawings in real feet and inches, so sizes, ceiling heights and window positions are what the architect drew. Anything Claude had to guess is listed in the model's Assumptions panel. Sun and shadows are calculated for your location, date and time. Light bouncing around inside rooms is not, so indoor brightness is only a rough guide. It is a tool for feeling the space and catching surprises early. It does not replace the drawings or your architect.
- Your plans show where you live and how your house is laid out. Claude will ask before publishing the model as a link, and you choose who gets it.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.