Kiln Author Asset

Author a Kiln asset

Match the user's scope. A standalone asset needs no project, inventory or design profile. Omitted project selection stays standalone unless KILN_PROJECT was explicitly configured (kiln_discover capabilities shows it); CLI --no-project or MCP projectId: null overrides that default. For project configuration or library materials, including standalone material use, read the project and material workflow, and use the same exact pins on later render, edit, inspect and save calls: a programRef alone selects no project and reconstructs no material context. Project preferences do not establish trusted requirements.

Live Review observes standalone and project operations without controlling the agent. When kiln_review is available, its save action retains the exact completed operation using the displayed expectedRevision, without another evaluation; pinning does not pause execution, and review annotations are not QA acceptance. Consult the tools' current schemas; optional host capabilities must not be assumed present.

Read the program contract when writing source. kiln_discover({}) gives a compact orientation: current families and tags, the starting createRoot/createPart signatures and six entry summaries. Search with kiln_discover({ query }) in ordinary modeling language (curved hollow tube, slats along a line, braced legs, cast iron): the catalog indexes operations, assemblies, recipes and materials rather than object classes, so name the parts and materials. Fetch complete contracts and examples with { ids: ["loftProfiles", "createPart", "createClip"] }, up to six exact, case-sensitive IDs or executable names; copy recipe IDs from results (recipe:material-wood-v1 or material-wood-v1), and a material recipe's summary names the materialRecipe("kiln.material.wood.v1") call to use. Narrow with family, kind: "operation" | "assembly" | "recipe" or tags from the overview, and follow nextOffset with offset. Request { capabilities: true } separately for the runtime, source, export and camera contract. Read the contract before treating a search match as support; a match in explanatory text can concern a limitation. Recipes are optional guidance, and custom geometry remains available.

Make the asset

Establish the subject, scale, style, and destination constraints from the request. Build a recognizable silhouette and meaningful construction details. Name parts by their role. Use metres, +X forward, +Y up, +Z right; ground contact normally sits at Y=0. Forward is the direction the object faces: a bench's sitter faces +X, so its backrest sits toward -X. Part rotation is in degrees and follows the right-hand rule in this frame: [0, 90, 0] turns forward (+X) toward -Z, the object's left; [0, 0, 90] tips +X up to +Y; [90, 0, 0] rolls +Y toward +Z.

Unless exact reconstruction is requested, use reference images to align silhouette, materials and art direction alongside the written brief, not as a requirement to copy every detail. Resolve functional dimensions explicitly. For usable openings, seats and articulated joins, use the interface guidance in geometry recipes.

For Blender, Unity or an FBX handoff, read the engine handoff guide, references/engine-handoff.md in the kiln-qa-asset skill. Prefer direct GLB import; the established exporter remains the default, and the guide explains when an explicitly identified experimental comparison is useful. Preserve the baseline output, report the selected backend and destination checks, and do not change global host settings silently.

Write ordinary JavaScript with meta and build(). Keep dimensions that should change together in named parameters. Use geometry recipes for freeform surfaces, deformations, lofts, Boolean materials, or repeated parts. A model can author its own equations and topology; it does not need to assemble everything from boxes. Build one tier unless the brief asks for level-of-detail tiers; when it does, name and declare them as levels of detail describes.

For connected assemblies, derive mating points from shared dimensions in the same local frame. Identify the intended neighbor at each end of a support, and separate those joints from nearby parts that need clearance. beamBetween uses the endpoints you supply; it does not find the frame (Discovery's joined-frame recipe shows the pattern). A centerline wheel uses side: 'center'; wheel side describes placement identity, not single- or double-sided fork design.

Submit code once to kiln_render or kiln_validate, then retain its programRef, including on a failed build; in a generated asset workspace, node kiln.mjs source asset.kiln.js imports a file directly. Copy the returned reference exactly for later views and edits: built-in stores return short handles such as p_7c94a132b8e0, and full SHA-256 references also work. Do not construct a handle or retransmit the program. A rejected build names its cause when Kiln can tell it and adds Source check: with the codes and lines kiln_validate finds (TEMPORAL_DEAD_ZONE, MATERIAL_RECIPE_OVERRIDE, UNSAFE_GLOBAL_ACCESS and others); fix those lines first.

For CLI camera files and PNG export, use camera commands.

Review what matters

For the joints or gaps the brief depends on, use kiln_inspect with measure: { mode: 'surface', from: { subject: { path: A } }, to: { subject: { path: B } } }, substituting exact returned part paths. Check each end of a support against its intended neighbor, including the fittings that attach it to the body; a fitting touching a cable or pin does not establish that the fitting itself is mounted. Check required gaps separately. Read measurement.status and the closest points alongside an in-context view. Zero can mean touching or intersecting, and a whole-assembly minimum may find an unrelated contact; keep unmeasured interfaces unverified even when structural QA passes. Batch up to 12 intended pairs with surfacePairs: [[A, B], [C, D]]. Each entry is an exact listParts path such as /Park%20Bench[0]/Bench[0]/Mesh_Seat[0], or an unambiguous node name as measure takes; createPart("Seat", ...) names its mesh Mesh_Seat. Read every surfaceMeasurements.results entry; status: partial includes failed or unfinished checks. Set image: false and omit camera controls for numeric checks after reviewing a relevant image.

Choose views that answer a question: a broad sheet establishes shape; a part-local view reveals a seam, underside or hidden attachment. Use the camera recipes for image count, exact part framing, explicit cameras and separate images. Read returned part paths instead of constructing them. The render response lists the first 24 part paths (every path that fits only with detail: "full") and partsTruncated when there are more; then use kiln_inspect({ programRef, image: false, listParts: { query: "part name" } }), which searches nested names and paths, and follow partListing.nextOffset with the same reference and query. Omit the query to list everything; add placement: true for world position, rotation, scale and bounds per part. A missing preview entry does not mean the part failed to export.

Inspect the actual images. Render on the default neutral grey backdrop first; only when a sheet you have seen shows a part merging with it, add backdrop to capture: light when the merging part is darker than the grey (near-black iron, dark wood), dark when it is lighter (near-white, pale grey, emissive), and read the echoed capture.backdrop. Check silhouette, proportion, orientation, attachment, and ground contact. If the request calls for a finished asset, repair concrete gaps visible at its intended viewing distance rather than stopping at a blockout. Do not repeat the same render without a new question or change.

Do not darken albedo to compensate for review lighting; preserve the intended material colour and check material-faithful GPU views and the destination renderer. Base colour is the factor multiplied by the texture; tinting both can darken the colour twice, so keep one neutral or choose the factor so their product in linear colour space equals the intended albedo.

For specified openings and travel limits, measure usable space including protruding teeth, fasteners or trim; nominal plate spacing alone does not establish clearance. For overall dimensions, use the rendered revision's bounds.size in metres, including projections and attached parts, and state separately when a measurement describes only a body or centerline. Source parameters are not measured extents.

viewFidelity.materialFaithful: false means geometry evidence, not verified PBR appearance; check the camera and fallback receipts too, and a GPU connection alone is not evidence that the requested view was used. In auto mode the first view that needs PBR shading starts a compatible local render service on demand, so node kiln.mjs service status showing no listener before that view is expected. Animation needs intermediate-pose review and interiors may need cutaway views. Use kiln_screenshot_animation for clip sampling, or in a CLI workspace node kiln.mjs animation RETURNED_REF --clip CLIP_NAME --phases 0,0.017,0.31,0.68,1 --views motion.png --render gpu --json (--render cpu for geometry only) and read the PNG; phases are fractions of clip duration and sample the exported animation without editing posed copies into source. Check poseBounds against requested ground clearance and dimensions at those poses, including tread and other protrusions; choose phases inside a geometric repeat, since quarter turns of 16 repeated lugs all show the same alignment. Sampled bounds do not prove continuous contact or collision safety.