Stomra · Guide
Modelling with your AI assistant
How to get good, light models from the assistant you connect to Stomra, and how to teach it your way of building once.
How the assistant works in Stomra
Stomra has no AI of its own. You connect the assistant you already use, such as Claude or ChatGPT, through the Stomra connector, and it works in your projects with your rights and no more. Stomra with your AI assistant says how to connect it.
- It works in your tab. Reading works from the project's saved state. Changes, pictures and exports are made in your open Stomra tab, where you see them happen (see your assistant without an open tab).
- Every change is a command. The assistant changes the model through the same checked commands as your own edits. A command that does not fit the model is refused with a sentence that says why, and nothing is written.
- Everything can be undone. Each batch of commands is one Undo step, and it goes into the project's history like your own work.
- It reads a guide first. Stomra hands the assistant an operating guide: a short core for every session and a topic for each kind of work (roofs, timber framing, precast, MEP, views, the Handbook and more). The assistant reads the topic before it works on what the topic covers.
Most of what follows is already in that guide, so a good assistant does it unasked. Knowing it helps you steer: you can ask for the right thing, and you can tell when the work is going the wrong way.
Start a session well
- Open the project in a tab. With the project open, the assistant can change it, draw pictures and make files. With several tabs open, tell it which project you mean.
- Let it read the project first. It reads a summary of the project (levels, grids, types, views, sheets and counts), its files and what the Handbook holds for it. If a previous session left a handoff note, it tells you where the work stands before it changes anything.
- Give it the brief. On a new job, paste the brief and attach the drawings. The assistant files the brief in the project (Files ▸ Brief), so the next session and your colleagues read the same thing. It asks what the drawings leave out, such as a storey height or the scale, instead of guessing.
- Say who decides. The assistant follows a fixed order: the building code, then your word and the client's for this task, then the project's own decisions, then your organisation's lessons, worked examples and general instructions, then Stomra's defaults. When you want something done differently from the Handbook, just say so.
Small steps you can follow
The assistant models in your live project, in small coherent steps you can watch: a wall run with its openings, a beam with its supports, a detail with its notes. Each step is one batch and one Undo step. It explains the next step, applies it, looks at the result and corrects it before it goes on.
- Steer as it works. You do not need to approve every routine step. If you edit the model yourself, the assistant reads what you changed and reconciles its next steps with your work instead of replacing it. Say "pause" and it stops writing.
- A dry run for anything new. The assistant can try a batch without writing it. A dry run reports every problem at once, so it fixes them all before the real run.
- A named version before a large change. Before it changes every exterior wall type or renumbers the sheets, ask it to save a named version. Afterwards it can compare against that version and tell you exactly what changed. Project ▸ History shows every version.
- An alternative to try things. To try a roof or a layout while the main model stays as it is, ask for an alternative. The assistant asks before it starts one.
- A batch is not a race. A batch can hold up to 500 commands, but that is a ceiling, not a target. Unless you ask for unattended bulk work, expect steps you can follow on screen.
Ask for the light form
A model gets heavy in a few predictable ways: a fill drawn as many single lines, insulation drawn as a zigzag of lines, a repeated object stored again and again, an outline traced by hand over a cut. None of them is forbidden; each makes the model slower to open, draw and change, and none follows the design when it moves. In Stomra each has a light form that draws the same thing as one object.
| Instead of | Ask for | Why it is better |
|---|---|---|
| A hatch drawn as many lines | A region with a pattern | One object; its outline can follow the model |
| Batt insulation drawn as lines | An insulation item | One object along a path, scaled to its thickness |
| Battens, tiles or screws drawn one by one | A repeating detail | One row with a spacing |
| A fixing or profile drawn again in every detail | A 2D family from the Handbook, or a new one | Drawn once, placed many times, kept for the next project |
| The model's cut traced in 2D lines | Nothing: the model draws its cut | The cut follows the next edit; traced lines do not |
| The same house or room modelled again | A group placed several times | Change one instance and every instance follows |
| A dimension with typed text | A dimension that measures | Move the geometry and the value follows |
| Delete and rebuild to change something | An update of what is there | Keeps the element's history, hosts and tags |
Stomra's guide already tells the assistant to draft with the item that draws most at once, and never to trace the cut in lines. A sentence from you settles it for good: "Hatches are regions, insulation is an insulation item, never single lines." Said as a lasting rule, the assistant keeps it as a lesson (see Teach it once).
Model what is counted, draft the rest. What is counted, checked or seen in other views belongs in the model: walls, layers, beams, pipes. Fixings, sealant, membrane laps, flashings, notes and most hatches belong in 2D on the model's cut. A detail at 1:5 is mostly 2D; a plan at 1:100 is mostly model.
When the model is right but a cut draws wrong, the assistant does not bend the model to make one drawing look right. It overrides the look in that view, drafts over it, and offers to report the problem to Stomra.
Read little, ask precisely
Your assistant has a limited budget for each answer, and a large project does not fit in one read. Stomra is built so that it never has to load everything.
The map first
A project is stored as a tree of folders by discipline, level and category. The assistant reads the map, then the folder the task is about.
Summary, index, full
A few kilobytes for the project, a short row per element, and the whole record only for the elements it is about to change.
Ask, do not load
To count, add up or find, it asks a query ("how many windows on level 2, by type") instead of reading every element.
Only what changed
After one read, it asks for the changes since then. Between sessions, a named version is the base to compare with.
You help by asking about a place and a thing: "the beams on level 2 in grid C–D" gets a precise answer faster than "check the structure".
Point instead of describing
Saying where something is in words is slow and easy to get wrong. Stomra gives you three ways to point.
Work orders written while you walk the model, and prompts sent from the AI sketch, are in Work orders.
The AI sketch
Draw over any view with the AI sketch pen: ring what you mean, draw a line or an arrow to where it should go, add a short note. The assistant reads the sketch as a picture of the view with your strokes, which elements each stroke rings or crosses, and their positions in the model. From the sketch's menu, Send prompt to assistant freezes the sketch together with your words and sends them as a prompt; the assistant carries out waiting prompts in turn.
Work orders in walk mode
While you walk the model, aim at something and press O to write a work order: "Move this 1 m to the right". The order keeps what you aimed at, where you stood and two pictures, so "right" means your right. You follow orders in Project ▸ Work orders.
- For your own orders, the assistant says in a sentence what it would do and asks, or goes ahead if you told it to.
- For someone else's order, it proposes the change: you see the model as it would be, with the difference tinted, and answer yes or no.
- If an order can be read two ways, it asks the order's author rather than guessing.
- Say "take my orders as I write them" and it listens while you walk, proposing each change where you stand.
What you aim at
While you walk, the assistant can see where you stand and what you aim at. "Move this door" in the chat means the door in front of you, with no order written.
Teach it once: lessons and the Handbook
How the Handbook itself works, with shelves, ratings and which source wins, is in The Handbook.
When you correct the assistant or tell it how you always do something, it does what you asked and then keeps it, so nobody has to say it again. A correction for this time only ("just here", "in this room") is done and never kept.
Lessons are also learned from your edits of the assistant's work: see Lessons learned.
Lessons
A lesson is a short rule in your own words, kept at once with the scope your words give it:
| Scope | Example |
|---|---|
| The organisation | "We always put switches at 1100 mm above the floor." |
| A kind of building | "In our halls the slab on ground is 3 × 100 mm EPS." |
| This project | "The client wants oak thresholds throughout." |
| You alone | "Answer me in Swedish." |
- You see it at once. A card, Learned while you worked, shows what was kept, with Undo. In the Handbook, Lessons learned lists every lesson with who said it, their words, and how often it has been used.
- Narrowest first. The assistant applies the project's lessons before the kind of building's, then the organisation's, then your own, and says which it followed ("per L-3").
- Wrong lessons fade out. When you say a lesson was wrong, the assistant does what you ask and strikes it; three strikes take it out. A changed rule ("switches at 1000 now") becomes the lesson's next version.
- Some lessons do the work themselves. A lesson about a value, such as a height, can fill that value in on new elements, for the assistant and for people alike. A lesson Stomra can check, such as "pipes follow walls and the roof", can become a check that warns wherever the model breaks it, whoever drew it. Checks only warn; they change nothing.
- From time to time, a review. The assistant reviews the lessons: close pairs to merge, lessons nobody used for 90 days, and lessons that have held long enough to belong in the Handbook.
The Handbook
The Handbook is the formal side: how your organisation builds, written by its editors. It holds worked examples (when a method applies, what to ask first, the measures that govern it, the recipe, what has gone wrong before and when it is done), drawing examples and general instructions with their named values. Before the assistant models something a worked example covers, it reads the example, asks its questions, follows its recipe and says which example it followed.
When what you ask differs from a value in a general instruction, the assistant asks once: update the Handbook, keep a deviation for this project only, or keep the Handbook's value. An editor's change is in force at once; a member's is a draft for an editor.
The fastest way to good results across a team is a Handbook with a few worked examples for the parts you build most, and lessons for the rest. The assistant then follows your firm's way of building from the first session.
Check and hand over
- Against the drawing. When the assistant builds from a PDF drawing, it can lay the page under the plan and look at its model over it, room by room: a red line beside a wall is a wall out of place, red with nothing over it is a wall not yet built. You see the same underlay on your screen, so you can check it.
- Quantities. Stomra's quantities are the model's. Before it calls quantities done, the assistant checks rows against the drawings by a second route and says what it checked.
- A handoff. At the end of a session it writes a session note and updates the project's handoff: what was done, what is left, what it assumed and why. The next session, yours or a colleague's, starts from there.
Prompts that work
Read the project and tell me where it stands before you change anything.
Model the ground floor walls from the PDF in Brief, one wall run at a time,
and check each level against the drawing before you go on.
Draft detail 3 on the section's cut: regions for materials, an insulation
item for the mineral wool, a repeating detail for the battens. No single lines.
Save a version called "Before facade change", change all exterior walls
to our new exterior wall type, then tell me what changed.
Take my work orders as I write them.
From now on: in our villas, switches go at 1100 mm. Keep that.