Keep · astra-grok SKILL.md

Floorplan → walkthrough

WhenUse when the input is a floorplan (image or PDF) and the output is a navigable walkthrough render, camera path, or Three.js orbit of the space. Real-estate, level layout, and set blocking all qualify.

StopMeasure twice: do not extrude walls until scale is confirmed against a labeled dimension. Do not invent rooms not on the plan; mark unknown areas. Do not skip door/window openings — solid boxes are not a walkthrough. Never claim survey accuracy unless dimensions were verified.

Steps

Ingest floorplan (image/PDF). If PDF, rasterize readable pages to `refs/plan.png` via Shell/poppler as needed.
Establish scale: find a labeled dimension; set Blender units (or Three units) so that length matches. Record scale factor in `plan/SCALE.md`. Double-check with a second dimension if present.
Trace walls as thin solids or curves-extrude. Cut doors and windows at plan locations. Add simple floor slab.
Place an eye-height camera (≈1.6 m) and a path through primary rooms — or set up a Three.js orbit pivot at plan center.
Optional: simple materials (wall/floor/glass) from a light look-lock if provided; else neutral gray + accent.
Produce either (a) a short walkthrough render/frames along the path, or (b) a Three.js orbit page. Screenshot key frames.
Write `plan/WALKTHROUGH.md` with scale, assumptions, and file paths.

Oven

Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.)

Done when

Scale documented and checked twice when possible.
Walls/doors/windows match the plan topology.
Walkthrough frames or orbit scene open without errors.
Assumptions (ceiling height, missing labels) listed.

Cross-model

Recipe is fixed: ingest → scale twice → walls/doors → camera path → walkthrough/orbit → notes. Only the OVEN line swaps — PDF/raster and Blender/Three tooling bind to the host; the measure-twice gate stays identical across Astra, Grok Bot, Fable, and Claude.

LoadOVEN: Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.) Done when: - Scale documented and checked twice when possible. - Walls/doors/windows match the plan topology. - Walkthrough frames or orbit scene open without errors. - Assumptions (ceiling height, missing labels) listed.

SourceAstra skills reworked for Grok Bot

Copy SKILL.mdRaw SKILL.md

---
name: "Floorplan → walkthrough"
description: "Use when a floorplan image or PDF must become a scaled 3D walkthrough or orbit scene."
---

# Floorplan → walkthrough

## When
Use when the input is a floorplan (image or PDF) and the output is a navigable walkthrough render, camera path, or Three.js orbit of the space. Real-estate, level layout, and set blocking all qualify.

## Stop
- Measure twice: do not extrude walls until scale is confirmed against a labeled dimension.
- Do not invent rooms not on the plan; mark unknown areas.
- Do not skip door/window openings — solid boxes are not a walkthrough.
- Never claim survey accuracy unless dimensions were verified.

## OVEN
Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.)

## Steps
1. Ingest floorplan (image/PDF). If PDF, rasterize readable pages to `refs/plan.png` via Shell/poppler as needed.
2. Establish scale: find a labeled dimension; set Blender units (or Three units) so that length matches. Record scale factor in `plan/SCALE.md`. Double-check with a second dimension if present.
3. Trace walls as thin solids or curves-extrude. Cut doors and windows at plan locations. Add simple floor slab.
4. Place an eye-height camera (≈1.6 m) and a path through primary rooms — or set up a Three.js orbit pivot at plan center.
5. Optional: simple materials (wall/floor/glass) from a light look-lock if provided; else neutral gray + accent.
6. Produce either (a) a short walkthrough render/frames along the path, or (b) a Three.js orbit page. Screenshot key frames.
7. Write `plan/WALKTHROUGH.md` with scale, assumptions, and file paths.

## Done when
- Scale documented and checked twice when possible.
- Walls/doors/windows match the plan topology.
- Walkthrough frames or orbit scene open without errors.
- Assumptions (ceiling height, missing labels) listed.

## Cross-model
Recipe is fixed: ingest → scale twice → walls/doors → camera path → walkthrough/orbit → notes. Only the OVEN line swaps — PDF/raster and Blender/Three tooling bind to the host; the measure-twice gate stays identical across Astra, Grok Bot, Fable, and Claude.