Start with a job, not a download pile
A useful first model solves one visible problem. Perhaps your empty courtyard needs a barrel beside a doorway, or a lantern that gives the player a landmark. Write that job in one sentence before browsing. A small, readable silhouette is often more valuable than a folder containing hundreds of unrelated props. Meshsmiths makes original pieces with catalogue records so you can compare their shape, scale and cost before making them part of a scene.
Open the catalogue and apply its live Free filter. The brief defines the Free tier as under 600 triangles per piece; that is not a total scene allowance. Check the current free flag and access information instead of deciding that anything with a public preview is free. Quench barrel and Workshop lantern are real starting records. Read their current details before choosing, because counts, release state and availability belong to a particular version, not to this article.
Separate access from permission
Free access does not mean that an asset is public domain, and an accessible image does not grant permission to distribute a model. Read the licence page and the selected version's provenance and delivery status. Keep those records beside the file you receive. You are checking both whether the service will let you obtain a format and what the recorded terms allow you to do with that delivered copy. If either answer is missing, mark the gap rather than assuming permission.
The Cairn is a helpful counterexample. The public agent brief uses its actual GLB bytes for a cold-start check, but its 613 triangles place it outside the under-600 Free definition. That showcase URL is neither a token-download grant nor a blanket reuse licence. Do not label the Cairn a free-tier tutorial asset just because you can load its sample. Start with a released, entitled version of a smaller prop when your aim is a reusable project asset.
Budget instances and measure metres
Count every placement. Twelve copies of a 424-triangle barrel would contribute 5,088 triangles before the ground, characters or lights are considered. That arithmetic is an illustration based on the checked barrel snapshot, not a claim that every barrel setting has the same count. Read the current preview measurement after changing knobs. Also watch material count, shadows and draw calls: a low polygon count alone cannot guarantee a smooth frame on an older phone.
Meshsmiths uses metres, Y-up and positive Z forward. Origins rest on Y zero and footprints are centred in X and Z. Compare the record's size_m with a simple metre reference in your own scene. The Foundry yard kit uses a four-metre grid for structural placement, but a loose prop still needs a sensible position and ground contact. Do not apply that grid to every other kit. Read each kit's usage contract and sample uneven terrain rather than guessing its height.
Export what you see and name what you saved
Set the prop's supported knobs, then use the existing Use it panel. Its ES module download is a static snapshot: the factory reconstructs the current geometry and visible parts, with those knob values already baked. Its GLB tab exports the object on the table and reloads the binary through GLTFLoader before saving. Neither output should be described as a live hosted parametric factory. Record the piece ID, selected values and local filename so a teammate knows what was captured.
For a plain three.js scene, save the downloaded module beside your scene module, import its default createPiece function, and add createPiece() to your scene. For a GLB, use GLTFLoader with the local filename instead. The source snippets document both paths. Browser proof checked GLB round trips for specific barrel and lantern samples; it did not test every catalogue piece, every combination or an engine build. Unity tooling remains untested here, and the Godot recipe is guidance rather than an engine certificate.
Leave a trail your future self can follow
Finish the experiment with one screenshot, the exported file and a short manifest. Include the piece ID, position, rotation, scale, knobs, measured triangles and licence findings. Keep unanswered questions visible. If you ask an agent to help, read prompt.txt first and give it this app's origin rather than an old localhost example. Ask it to discover real records, not invent download tokens or capabilities. A successful preview_scene reply is a compatibility summary, not a rendered or exported assembly.
A good free-model exercise ends with a small scene you understand. Check the silhouette from the actual camera, walk around the prop, and make sure it does not cover an interaction target. If the catalogue cannot supply the shape you need, describe that gap instead of renaming a near match. You can expand to a kit after the first import works, but keep the same discipline: exact identities, explicit access, measured budgets and a clear account of what was actually tested.
Real records used in this guide
- Quench barrel
quench-barrel - Workshop lantern
workshop-lantern - Cairn · not Free tier
prp_cairn - Foundry yard
foundry-yard
Check the selected version’s release, rights and access before using any file.