Use a measured Pascal room and your item’s dimensions to check its footprint, spacing, and missing measurements with Claude Code or Codex.
Check whether a sofa, desk, or wardrobe occupies the available floor space before
changing your layout. Pascal’s furniture-fit skill helps your agent compare a
measured room with an item’s dimensions and report footprint fits, footprint
does not fit, or insufficient evidence.The assessment can stay read-only: a prospective item does not need to be added to
your project.
Start with a room in Pascal whose dimensions match your measurements. A floor-plan
image needs a known scale; a photo alone does not establish room dimensions.Have these details ready:
The project, room, and floor you want checked.
The item’s width, height, and depth, including units and the source of the
measurements. Use the real product’s dimensions, not a similar catalog model.
The intended position and rotation. If you cannot identify the position precisely,
ask the agent to help locate it before assessing fit.
The minimum spacing you want around the item, such as 60 cm.
Install Pascal agent skills, then connect the project
store you use. The setup guide covers Claude Code and Codex separately.
For a prospective item that is not already in the scene, use the local CLI preview
described in the setup guide. It supports checking supplied dimensions without
placing the item. Hosted and older releases can expose fewer checks; your agent
must inspect the connected tools and explain any limitation.
If your project is in the hosted editor, save it and choose Share → Check furniture
fit. Copy the task and project context into your agent. Use an API key for the
personal or organization workspace that contains the project. A local MCP connection
does not automatically open or copy a hosted project.
Replace the bracketed details with your own measurements. If you used the Share
action, add these details to its copied task:
Use the furniture-fit skill to assess [item] in project [project ID],room [room name], on [floor].The item is [width] wide, [height] high, and [depth] deep, in [units].These dimensions come from [measurement or product specification].Test it at [precise position] with [rotation] and [minimum spacing].Keep the assessment read-only. Confirm the project and room before checking.If a required measurement or the position is missing, ask for it first.Report the footprint result, the dimensions and spacing you checked,what remains unknown, and whether the project changed.
This synthetic example uses an empty room 4.20 m wide and 3.60 m deep. The sofa is
2.10 m wide, 0.82 m high, and 0.95 m deep. Its center is at [2.10, 0, 1.50] in
the example’s coordinates, with zero rotation and 0.60 m requested spacing.
Synthetic plan view. The dashed outline adds the requested 0.60 m spacing around the sofa footprint.
The verified result for this example is footprint fits:
Check
Result
Horizontal footprint
X 1.05–3.15 m and Z 1.025–1.975 m, inside the measured room bounds.
Smallest boundary margin
1.025 m, greater than the requested 0.60 m.
Other furniture
No item collision; this example contains no other furniture.
Project changes
None. The project version, graph hash, and node count stayed the same.
Height, door swing, and delivery
Not checked. The example has no door and supplies no measured overhead clearance or delivery route.
The room-boundary comparison is separate from the item-collision check. An empty
collision list alone does not show that an item stays inside a room.
If you provide a wardrobe’s width and height but omit its depth, the useful answer
is insufficient evidence, followed by a request for the depth. The agent should
keep the measurements you supplied and ask only for the missing information that
blocks the assessment.A photograph without scale, an unspecified position, or a catalog placeholder can
also leave the result unresolved. Supply the missing evidence, then ask the agent to
repeat the check.
A footprint result describes the tested position, dimensions, and spacing. Height
clearance needs separate measured overhead geometry. Door swing, delivery through
halls or stairs, packaging, assembly, and detailed mesh contact need their own
evidence; a footprint pass does not establish them.When exact rectangular room and item dimensions are safe to share, the agent can
include an Open dimension-only footprint pre-check link. It opens the no-sign-in
calculator with those dimensions and tests 0° and 90°. The link carries no project,
account, or credential identifiers and does not replace the report’s scene-backed
collision, door, height, or delivery evidence. No sign-in is required, but opening the
link sends its visible measurement values to Pascal and may retain them in browser
history and service request logs. Its clearance means equal room-boundary clearance on
every side, not item-to-item spacing. The agent should create it only after you request
the hosted link or confirm that those measurements may be sent to Pascal.The calculator’s Copy result JSON action creates a deterministic, machine-readable
record of the same empty rectangular footprint check. It contains the entered dimensions,
both tested orientations, spare or shortfall values, and the unsupported checks. It does
not contain a project, revision, URL, account, workspace, person, credential, or timestamp.
Copying records a coarse usage event; the JSON and its measurements are not included in
that event. Pascal’s existing analytics identity or workspace context may still accompany
the event when you are signed in.Keep the report with the measurements and position it used. If you change the item,
room, rotation, or spacing, ask for a new assessment. Once you choose a layout, you
can place and arrange the item yourself or give your
agent a separate instruction to change the project.
