forgecad 0.9.16 → 0.10.1

package/dist-skill/library/forgecad-prepare-prompt/references/default-profiles.md

@@ -1,327 +1,99 @@
-# Scoped Intake Profiles
+# Family Intake Profiles
 
-This file does not define universal defaults.
+Family-scoped starter anchors for closing missing inputs — temporary engineering anchors, not truth, and never reused across families.
 
-It defines a safer process:
+## Process Selection By Family
 
-1. classify the artifact family
-2. choose a manufacturing/process posture
-3. choose qualitative levers
-4. translate those levers into starter assumptions only inside that family
+Never default to 3D printing. Choose the process stack from artifact family, load path, scale, safety expectations, material properties, quantity/iteration needs, and operating story. Typical honest stacks:
 
-These starter assumptions are not "truth".
-They are temporary engineering anchors used only when the user has not provided exact numbers.
-
-## Universal Levers
-
-Use these across families before translating into numbers:
-
-- manufacturing posture: default to `manufacture-realistic prototype` unless specified; common override values are `production-realistic`, `prototype-realistic`, `printable`, and `visual-CAD`
-- duty level: `light-duty`, `general-duty`, `sturdy-duty`
-- scale level: `compact`, `medium`, `large`
-- cost posture: `cheapest`, `balanced`, `performance-first`
-
-Never take a number from one family and silently reuse it for another.
-
-## Manufacturing Selection Rule
-
-Do not use 3D printing as the universal default.
-Choose the process stack from the artifact family, load path, scale, safety expectations, material properties, quantity/iteration needs, and operating story.
-Only use print defaults when the user explicitly requested printing or the selected process stack includes printed parts.
-
-The default posture is `manufacture-realistic prototype`: a credible prototype build candidate with real materials, real purchased parts, plausible fabrication routes, serviceable interfaces, and validation checks. It should be manufacturable enough for a prototype review, but it should not claim final production tooling, certification, or release readiness unless the user asks for that stronger bar.
-
-Examples:
-
-- rideable vehicles: metal/composite/wood structure, urethane/rubber wheels, bearings, brakes, fasteners, and purchased safety-critical hardware
-- furniture: wood, sheet goods, tube, metal brackets, conventional joinery, and printed parts only for honest secondary details
-- enclosures: injection molding, sheet metal, CNC, thermoforming, or printing depending on quantity, ruggedness, and serviceability
+- rideable vehicles: metal/composite/wood structure, urethane/rubber wheels, bearings, brakes, fasteners, purchased safety-critical hardware
+- furniture: wood, sheet goods, tube, metal brackets, conventional joinery; printed parts only for honest secondary details
+- enclosures: injection molding, sheet metal, CNC, thermoforming, or printing depending on quantity, ruggedness, serviceability
 - fixtures: machined, laser-cut, welded, printed, or hybrid with standard clamps/pins/fasteners
-- small mechanisms: hybrid printed/machined/sheet parts plus purchased pivots, shafts, bearings, springs, fasteners, motors, and electronics where appropriate
+- small mechanisms: hybrid printed/machined/sheet parts plus purchased pivots, shafts, bearings, springs, fasteners, motors, electronics
 
 ## Family: Grippers And Small Mechanisms
 
-Use for:
+Use for: robot grippers, articulated fingers, small pick-and-place tools, manipulators, end-effectors.
 
-- robot grippers
-- articulated fingers
-- small pick-and-place tools
-- small manipulators and end-effectors
+Family questions: delicate / mixed-general / rigid-tool-like handling? size closer to desk, household, or workshop objects? cheapest / balanced / performance-first hardware?
 
-### Family Questions
+Duty bands:
 
-- What feels closest: delicate handling, mixed general handling, or rigid/tool-like handling?
-- Is the size closer to small desk objects, everyday household objects, or larger workshop objects?
-- Should we bias for cheapest, balanced, or performance-first hardware?
-
-### Translation To Starter Assumptions
-
-`light-duty`
-
-- object mass band: roughly `0.05-0.15 kg`
-- opening / feature band: roughly `30-60 mm`
-- hardware posture: small servo / compact mechanism / lightweight prototype members; printed, machined, or laser-cut depending on the selected manufacturing posture
-
-`general-duty`
-
-- object mass band: roughly `0.20-0.50 kg`
-- opening / feature band: roughly `60-120 mm`
-- hardware posture: standard metal-gear servo or NEMA17-class solution, M3/M4 fasteners, inserts, pins, bearings where honest
-
-`sturdy-duty`
-
-- object mass band: roughly `0.50-1.00 kg`
-- opening / feature band: roughly `100-180 mm`
-- hardware posture: stronger shafts, bearings, more metal reinforcement, likely downgrade final certainty unless the mechanism remains simple
+- `light-duty` — object mass `0.05-0.15 kg`, opening/feature band `30-60 mm`; small servo, compact lightweight prototype members (printed, machined, or laser-cut per the selected posture)
+- `general-duty` — object mass `0.20-0.50 kg`, opening `60-120 mm`; standard metal-gear servo or NEMA17-class solution, M3/M4 fasteners, inserts, pins, bearings where honest
+- `sturdy-duty` — object mass `0.50-1.00 kg`, opening `100-180 mm`; stronger shafts, bearings, more metal reinforcement; downgrade final certainty unless the mechanism stays simple
 
 ### Subtype: Dexterous Finger / Humanoid Hand Module
 
-Use when the request is for a robot finger, dexterous finger, anthropomorphic finger, tendon finger, prosthetic-style finger, or one module of a robot hand.
-
-Default specific operating story shape:
-
-- invented organization: a named ambitious robotics company or advanced hardware group, not a famous real company
-- named program: a humanoid hand, embodied AI manipulation, warehouse-pilot, or end-effector program with real mission pressure
-- named revision: a concrete module/revision like `F2 index finger`, `DIP/PIP tendon mule`, or `Rev-C palm-mount finger`
-- review moment: go/no-go gate, customer-demo readiness review, actuator-routing review, palm-integration check, or grasp-demo gate
-- test setting: named curl-cycle rig, palm mule, contact-pad wear fixture, or instrumented grasp bench
-- stakes: first-customer pilot, investor demo, field-trial gate, reliability target, or deployment schedule
+Use for robot/dexterous/anthropomorphic/tendon/prosthetic-style fingers or one module of a robot hand.
 
-Good story seed:
-
-- "Helix Handworks is preparing the F2 index-finger module for its DEX-07 warehouse-pilot go/no-go review. The finger must bolt into Palm Mule V3, route a Bowden tendon through the MCP base without rubbing the housing wall, survive a 1,000-cycle curl test on Rig-3, and expose pivot/wear surfaces before the customer demo cell is frozen."
+Story shape: a hand/manipulation program at an invented robotics org, a concrete module revision (`F2 index finger`, `Rev-C palm-mount finger`), a go/no-go or demo gate, a named test rig, real deployment stakes. Seed: "Helix Handworks is preparing the F2 index-finger module for its DEX-07 warehouse-pilot go/no-go review. The finger must bolt into Palm Mule V3, route a Bowden tendon through the MCP base without rubbing the housing wall, survive a 1,000-cycle curl test on Rig-3, and expose pivot/wear surfaces before the customer demo cell is frozen."
 
 Starter assumptions for `general-duty` / `medium` / `balanced`:
 
 - envelope: adult index-finger scale, roughly `95-115 mm` long, `18-24 mm` wide, `16-24 mm` thick
 - joints: MCP/PIP/DIP-like flexion chain with hard stops and clearance checks through curl
-- motion target: MCP roughly `0-75 deg`, PIP roughly `0-90 deg`, DIP roughly `0-65 deg`
+- motion target: MCP `0-75 deg`, PIP `0-90 deg`, DIP `0-65 deg`
 - actuation: tendon or Bowden cable flexion with passive elastic/spring return unless the user asks for independent motors
-- hardware posture: metal pivot pins or shoulder screws, bushings or bearing surfaces, serviceable tendon anchor, replaceable fingertip/contact pad, palm mounting datum
-- validation: full-range curl sweep, tendon rub check, pivot wear check, fingertip contact load path, base-mount stiffness, and assembly access
-
-### Manufacturing Defaults When Printing Is Selected
-
-- structural printed parts: PETG by default
-- prototypes / fit checks: PLA allowed
-- sliding or rotating interfaces: prefer pins, bushings, bearings, or sacrificial wear parts over raw printed rubbing
+- hardware: metal pivot pins or shoulder screws, bushings or bearing surfaces, serviceable tendon anchor, replaceable fingertip/contact pad, palm mounting datum
+- validation: full-range curl sweep, tendon rub check, pivot wear check, fingertip contact load path, base-mount stiffness, assembly access
 
 ## Family: Fixtures, Jigs, And Holders
 
-Use for:
-
-- drill guides
-- work-holding fixtures
-- camera / sensor mounts
-- brackets and repeatable positioning tools
-
-### Family Questions
-
-- Is it mostly for positioning, clamping, or repeated handling?
-- Is the scale closer to palm-size, hand-size, or bench-size?
-- Is speed of build more important than stiffness, or vice versa?
-
-### Translation To Starter Assumptions
-
-`light-duty`
-
-- small hand-tool or desktop fixture
-- low clamp loads
-- simple printed, machined, laser-cut, or bent-sheet geometry acceptable depending on the selected process
+Use for: drill guides, work-holding fixtures, camera/sensor mounts, brackets, repeatable positioning tools.
 
-`general-duty`
+Family questions: positioning, clamping, or repeated handling? palm-, hand-, or bench-size? speed of build vs stiffness?
 
-- hand-size or bench-size fixture
-- moderate clamp loads
-- inserts, metal pins, or off-the-shelf fasteners where wear concentrates
-
-`sturdy-duty`
-
-- repeated clamping or alignment duty
-- workshop abuse expected
-- printed geometry, if used, should be backed by thicker sections, inserts, metal rails, or replaceable wear faces
+Non-obvious anchors: at `general-duty`, put inserts, metal pins, or off-the-shelf fasteners where wear concentrates; at `sturdy-duty` (repeated clamping, workshop abuse), printed geometry must be backed by thicker sections, inserts, metal rails, or replaceable wear faces.
 
 ## Family: Enclosures And Electronics Housings
 
-Use for:
-
-- PCB enclosures
-- instrument cases
-- sensor housings
-- covers and protective shells
-
-### Family Questions
-
-- Is this for one PCB, a hand-sized electronics stack, or a larger bench device?
-- Does it need passive venting, fan support, or mostly dust protection?
-- Is aesthetics, serviceability, or ruggedness the main goal?
-
-### Translation To Starter Assumptions
-
-`light-duty`
-
-- single small board or simple module
-- easier snap/screw access acceptable
-- lighter wall sections
+Use for: PCB enclosures, instrument cases, sensor housings, covers and shells.
 
-`general-duty`
+Family questions: one PCB, hand-sized stack, or bench device? passive venting, fan support, or dust protection? aesthetics, serviceability, or ruggedness?
 
-- multiple boards or connectors
-- removable lid / inserts / real fastening
-- enough clearance for wiring and service loops
-
-`sturdy-duty`
-
-- rugged transport or workshop environment
-- thicker walls, boss reinforcement, connector strain protection, better sealing strategy
+Non-obvious anchors: at `general-duty`, a removable lid with real fastening (inserts) and clearance for wiring/service loops; at `sturdy-duty`, thicker walls, boss reinforcement, connector strain protection, and a sealing strategy.
 
 ## Family: Furniture And Load-Bearing Structures
 
-Use for:
-
-- tables
-- shelves
-- stands
-- stools
-- structural frames
-
-### Important Caution
-
-Human-bearing or safety-critical structures should usually end as `BEST-EFFORT BUILD CANDIDATE` unless there is real structural reasoning, conservative geometry, and honest material limits.
-
-### Family Questions
-
-- Is this mostly decorative / light household / real workshop use?
-- Is the span closer to side-table size, desk size, or bench size?
-- Will it ever support a person, concentrated heavy tools, or repeated impact?
-
-### Translation To Starter Assumptions
-
-`light-duty`
+Use for: tables, shelves, stands, stools, structural frames.
 
-- decor, lamps, light household items
-- smaller spans
-- simpler joints acceptable
+**Caution:** human-bearing or safety-critical structures usually end `BEST-EFFORT BUILD CANDIDATE` unless there is real structural reasoning, conservative geometry, and honest material limits.
 
-`general-duty`
+Family questions: decorative / light household / real workshop use? side-table, desk, or bench span? will it ever support a person, heavy tools, or repeated impact?
 
-- laptop, books, normal desk use
-- medium spans
-- real attention to leg stiffness, racking resistance, and joint reinforcement
-
-`sturdy-duty`
-
-- workshop surfaces, heavier distributed loads, or concentrated tools
-- larger spans or more demanding rigidity
-- stronger joinery, thicker members, more triangulation / bracing, and often conventional structural reinforcement
-
-### Manufacturing Defaults
-
-- do not assume "fully 3D printed" is the right answer
-- for structural furniture, consider wood, sheet goods, tube, or metal hardware as first-class BOM items
-- use printed parts mainly where they are honest: brackets, templates, feet, cable features, corner blocks, custom connectors
+Non-obvious anchors: at `general-duty`, real attention to leg stiffness, racking resistance, and joint reinforcement; at `sturdy-duty`, stronger joinery, thicker members, triangulation/bracing. Wood, sheet goods, tube, and metal hardware are first-class BOM items; printed parts only where honest (brackets, templates, feet, cable features, corner blocks).
 
 ## Family: Chassis And Mobile Robot Structures
 
-Use for:
-
-- wheeled robot chassis
-- tracked platforms
-- sensor carts
-- mobile bases
-
-Do not use this family for human-ridden scooters, bicycles, skateboards, mobility devices, or other rideable products. Use `Human Vehicles And Rideable Product Forms` instead.
-
-### Family Questions
-
-- Indoor smooth floor, mixed home floor, or rough workshop floor?
-- Tiny robot, small rolling base, or larger mobile platform?
-- Is runtime / price / ruggedness the main priority?
+Use for: wheeled robot chassis, tracked platforms, sensor carts, mobile bases. **Not** for human-ridden scooters, bikes, skateboards, or mobility devices — those route to Human Vehicles below.
 
-### Translation To Starter Assumptions
+Family questions: indoor smooth, mixed home, or rough workshop floor? tiny robot, small rolling base, or larger platform? runtime / price / ruggedness priority?
 
-`light-duty`
-
-- small indoor base
-- low speeds
-- simpler drivetrain packaging
-
-`general-duty`
-
-- home or workshop mixed surfaces
-- modest payloads
-- stronger wheel mounts, motor mounts, and battery restraint
-
-`sturdy-duty`
-
-- rougher surfaces or heavier payloads
-- more metal shafts / bearings / real fastening
-- increased skepticism about fully printed load paths
+Non-obvious anchors: at `general-duty`, strengthen wheel mounts, motor mounts, and battery restraint; at `sturdy-duty`, more metal shafts/bearings/real fastening and increased skepticism about fully printed load paths.
 
 ## Family: Human Vehicles And Rideable Product Forms
 
-Use for:
-
-- kick scooters
-- bicycles and balance bikes
-- skateboards and longboards
-- carts, strollers, dollies, or mobility-adjacent platforms with human interaction
-- any artifact where a person stands on, rides, steers, brakes, or leans on the structure
-
-### Important Caution
-
-Human-ridden or safety-critical vehicles should usually end as `BEST-EFFORT BUILD CANDIDATE` unless there is real structural analysis, conservative geometry, braking/steering reasoning, and explicit test limitations.
-Do not present a rider-rated design as safe without validation.
-Do not make rideable load paths printed by default.
-
-### Family Questions
+Use for: kick scooters, bicycles, skateboards/longboards, carts, strollers, dollies, mobility-adjacent platforms — anything a person stands on, rides, steers, brakes, or leans on.
 
-- Is this a visual/product CAD study, a manufacture-realistic prototype build candidate, or a specifically printable toy/model?
-- Is it for child-scale, adult-scale, display-scale, or cargo/utility scale?
-- Does it need steering, braking, folding, suspension, or only static product form?
+**Caution:** rideables usually end `BEST-EFFORT BUILD CANDIDATE` unless there is real structural analysis, conservative geometry, braking/steering reasoning, and explicit test limitations. Never present a rider-rated design as safe without validation.
 
-### Translation To Starter Assumptions
+Family questions: visual CAD study, manufacture-realistic prototype candidate, or explicitly printable toy/model? child-, adult-, display-, or cargo-scale? steering, braking, folding, suspension, or static form only?
 
-`light-duty`
+Anchors: `light-duty` = display/toy/non-ridden study, printed cosmetic parts acceptable. `general-duty` = aluminum/steel tube or frame, machined or cast fork/dropout features, wood/composite/aluminum deck, urethane/rubber wheels, real bearings, axles, grip tape, purchased brake/steering hardware. `sturdy-duty` = conservative metal/composite structure, triangulation, large bearing interfaces, replaceable wear parts; downgrade certainty unless structural checks and a real test plan are explicit.
 
-- display-scale, toy-scale, or non-ridden study
-- simplified load paths acceptable if clearly labeled
-- printed or lightweight prototype parts may be acceptable for cosmetic/non-critical features
-
-`general-duty`
-
-- adult product form or manufacture-realistic prototype scooter/bike/cart architecture
-- aluminum or steel tube/frame members, machined or cast fork/dropout-like features, wood/composite/aluminum deck where appropriate
-- urethane/rubber wheels, real bearings, axles, fasteners, spacers, grip tape, grips, and purchased brake/steering hardware where appropriate
-
-`sturdy-duty`
-
-- repeated riding, rougher surfaces, heavier loads, cargo, impact, or braking/steering duty
-- conservative metal/composite structure, triangulation, large bearing interfaces, replaceable wear parts, and no printed primary load paths unless the user explicitly requested a printed demonstration model
-- downgrade final certainty unless structural checks and real-world test plan are explicit
-
-### Manufacturing Defaults
-
-- primary load paths: aluminum/steel tube, plate, extrusion, wood/composite deck, or equivalent conventional structural members
-- rolling interfaces: purchased wheels, bearings, axles, spacers, and bushings
-- contact/wear interfaces: urethane/rubber, grip tape, replaceable pads, bushings, bearings
-- printed parts: cosmetic covers, cable guides, templates, fit-check models, brackets for low-load accessories, or explicit printable-model requests
+Manufacturing: primary load paths in metal tube/plate/extrusion or wood/composite — never printed unless the user explicitly requested a printed demonstration model. Rolling interfaces purchased (wheels, bearings, axles, spacers, bushings); contact/wear interfaces in urethane/rubber, grip tape, replaceable pads. Printed parts only for cosmetic covers, cable guides, templates, fit-check models, or low-load accessory brackets.
 
 ## If No Family Fits
 
-Do not force a nearby family just because it is available.
-
-Instead:
-
-- say the nearest family
-- explain the mismatch
-- create a custom intake brief with 2-4 artifact-specific levers
+Do not force a nearby family. Name the nearest family, state the mismatch, and build a custom intake brief with 2-4 artifact-specific levers.
 
 ## When Printing Is Selected
 
-Only use when the artifact actually includes printed parts:
+Only when the artifact actually includes printed parts:
 
-- nozzle: `0.4 mm`
-- layer height: `0.2 mm`
-- threaded service joints: use heat-set inserts where repeated opening is expected
-- wear-heavy interfaces: do not trust raw printed friction unless the task is intentionally low-duty
+- structural printed parts: PETG by default; PLA allowed for prototypes/fit checks
+- nozzle `0.4 mm`, layer height `0.2 mm`
+- threaded service joints: heat-set inserts where repeated opening is expected
+- sliding/rotating or wear-heavy interfaces: pins, bushings, bearings, or sacrificial wear parts — never raw printed rubbing unless intentionally low-duty

package/dist-skill/library/forgecad-prepare-prompt/references/master-prompt.md

@@ -3,11 +3,7 @@
 Fill the placeholders and return the finished prompt as one block.
 
 ```text
-You are producing a ForgeCAD manufacture-realistic prototype package, not a concept sketch.
-
-Treat this as a serious product-team prototype assignment.
-The goal is to produce a credible internal engineering package for a real prototype build candidate, not a generic maker example.
-Use the specific operating story below to drive engineering choices; do not flatten it into a vague domain label.
+You are producing a ForgeCAD manufacture-realistic prototype package, not a concept sketch — a credible internal engineering package for a real build candidate, not a generic maker example. Use the specific operating story below to drive engineering choices; do not flatten it into a vague domain label.
 
 Target artifact:
 - artifact: {artifact}
@@ -22,121 +18,56 @@ Specific operating story:
 - production reason: {production_reason}
 - test setting: {test_setting}
 - generic-output failure mode to avoid: {generic_failure_mode}
-- benchmark class / public comparison anchor, if useful: {benchmark_class}
+- public comparison anchor, if useful: {benchmark_class}
 
 Chosen intake classification:
-- output posture: manufacture-realistic prototype unless the user explicitly selected another posture
+- output posture: {output_posture} (manufacture-realistic prototype unless the user selected another)
 - artifact family: {artifact_family}
 - duty level: {duty_level}
 - scale level: {scale_level}
 - cost posture: {cost_posture}
-- job style: {job_style}
 - manufacturing / process stack: {manufacturing_process_stack}
-- budget posture: {budget_posture}
+- variant policy: {variant_policy}
 
-Working assumptions chosen to close missing inputs:
-- these assumptions are provisional and family-scoped
-- they apply to `{artifact_family}`, not as universal defaults
+Working assumptions chosen to close missing inputs (provisional, scoped to `{artifact_family}` only):
 - {assumption_1}
 - {assumption_2}
 - {assumption_3}
 - {assumption_4}
 
 Hard constraints:
-- use ForgeCAD
-- if the mechanism has moving parts, use a real `assembly()` from iteration 1
-- define real joints, limits, axes, and intended operating ranges
-- choose manufacturing/processes that fit the artifact, load path, scale, safety expectations, and operating story
-- default to manufacture-realistic prototype: real prototype materials, fabrication cues, purchased parts, assembly logic, serviceability, and validation without pretending to be production-certified or release-ready
-- do not assume FDM, 3D printing, or "printable" unless the user explicitly asked for it or the chosen process stack includes printed parts
-- include realistic process-appropriate clearances and mechanically honest interfaces
-- include manufactured, printed, and purchased parts only where each is an honest choice
-- include a BOM that is concrete enough to buy and assemble from
-- prefer metal shafts, bearings, fasteners, inserts, pins, tubes, sheet goods, castings, molded parts, machined parts, or composite/wood members where they are the honest choice
-- model the physical artifact, not an educational diagram
-- do not add explanatory text labels, floating callouts, arrows, legends, coordinate axes, section-title plaques, or part-name slabs to CAD geometry unless the user explicitly asks for a teaching or presentation view
-- include product markings only when they would exist on the real artifact, such as serial plates, connector labels, gauge ticks, keyboard legends, alignment marks, scale marks, warning marks, service arrows, branding, or molded icons
-- keep real markings sparse, process-appropriate, and light enough that text geometry does not dominate runtime or exact export behavior
-- do not hide uncertainty; choose defaults and continue
-- do not claim the user works for a named company unless the user explicitly said so
-- if an organization/team name appears only in the operating story, treat it as a design scenario, not as a factual claim about the user
-- do not clone proprietary named products; use public domain patterns and first-principles engineering to create an original design
+- Use ForgeCAD. Any moving mechanism uses a real `assembly()` with honest joints, limits, axes, and operating ranges per the forgecad skill quality bar. Make the result runnable with `forgecad run`.
+- Default posture is manufacture-realistic prototype: real prototype materials, fabrication cues, purchased parts, assembly logic, serviceability, and validation — without claiming production certification or release readiness.
+- Choose processes that fit the artifact, load path, scale, safety, and operating story. Do not assume FDM/3D printing/"printable" unless the user asked or the selected process stack includes printed parts. Prefer metal shafts, bearings, fasteners, inserts, pins, tube, sheet goods, castings, molded/machined parts, or composite/wood members where honest, with process-appropriate clearances.
+- Include a BOM concrete enough to buy and assemble from, registered in-model with `bom()` entries — not only prose.
+- Model the physical artifact, not an educational diagram: no explanatory text labels, callouts, arrows, legends, axes, or part-name slabs unless the user explicitly asks for a teaching view. Include only markings the real artifact would carry (serial plates, connector labels, gauge ticks, alignment/warning marks, branding), sparse and process-appropriate.
+- Do not hide uncertainty; choose defaults and continue.
+- Do not claim the user works for a named company unless they said so; the invented org is a design scenario, not a factual claim. Do not clone proprietary named products — use public-domain patterns and first-principles engineering.
 
 Acceptable final states:
-1. `BUILD-READY`
-2. `BEST-EFFORT BUILD CANDIDATE`
-
-`BUILD-READY` means the output is specific enough that a competent builder could start fabricating, machining, printing selected printed parts, buying parts, assembling, and testing the prototype immediately without inventing missing details.
-
-`BEST-EFFORT BUILD CANDIDATE` means you still provide the strongest concrete design possible, but you explicitly name the smallest unavoidable validation loop that remains.
+1. `BUILD-READY` — specific enough that a competent builder could start fabricating, buying, assembling, and testing immediately without inventing missing details.
+2. `BEST-EFFORT BUILD CANDIDATE` — still the strongest concrete design possible, plus an explicit statement of the smallest unavoidable validation loop that remains.
 
 Non-negotiable rules:
-- Do not answer with a high-level concept, vision, or wishlist.
-- Do not produce a generic category solution that could have been written without the professional context.
-- Do not use placeholders like "appropriate motor", "standard hardware", or "adjust as needed".
-- If a number is missing, choose a defensible value, state it, and continue.
-- Prefer a complete best-effort design over an incomplete discussion.
-- If the user's wording is physically confused, normalize it and proceed.
+- No high-level concepts, visions, or wishlists; no generic category solution that could have been written without the operating story.
+- No placeholders like "appropriate motor", "standard hardware", or "adjust as needed". If a number is missing, choose a defensible value, state it, continue.
+- Prefer a complete best-effort design over an incomplete discussion. If the user's wording is physically confused, normalize it and proceed.
 - Do not import numeric assumptions from unrelated artifact families.
 - Do not ask follow-up questions unless the architecture would materially change and no safe assumption bundle exists.
-- Do not make the CAD understandable by labeling every part; make the part boundaries, hardware, interfaces, and materials physically legible.
+- Make the CAD legible through part boundaries, hardware, interfaces, and materials — not labels.
 
 Required outputs:
 
-0. Specific operating story and anti-generic bar
-- State the organization/team, project revision, milestone, and test setting you are designing for.
-- Name the generic failure mode you are avoiding.
-- Identify the domain-specific details that must appear for the design to be credible.
-
-1. Problem normalization
-- Restate exactly what is being built, what it should do, and what "done" means in physical terms.
-
-2. Assumption bundle
-- State all chosen assumptions with units and why they are reasonable for this request.
-
-3. Architecture choice
-- Pick one mechanism architecture.
-- Briefly mention the main rejected alternatives and why they lost.
-
-4. Detailed mechanical design
-- Give exact dimensions or dimension formulas for the major parts.
-- Define subassemblies, interfaces, motion ranges, stops, and load paths.
-- If this is a gripper or articulated mechanism, specify finger/link/jaw geometry and all joints concretely.
-
-5. Actuation and transmission
-- Specify the actuator class, approximate required torque/force, transmission approach, and why they fit the chosen profile.
-
-6. Manufacturing package
-- For each critical part: material, manufacturing process, prototype setup/orientation/tooling/finish assumptions, serviceability notes, and features sensitive to process accuracy.
-- If the selected process includes printed parts, include print orientation, likely support strategy, and print-sensitive features for those parts.
-
-7. Bill of materials
-- Include manufactured parts, printed parts if any, and purchased parts.
-- For each line item give: name, exact spec or part class, quantity, why needed, and important dimensions or ratings.
-
-8. Assembly package
-- Provide the assembly order, jointing method, insert/bearing/pin usage, fastening notes, and likely failure-prone assembly steps.
-
-9. Validation package
-- Check motion range, likely collisions, stiffness risks, load risks, manufacturability, tolerance-stack risks, and wear points.
-- Check printability only for parts whose selected process is printing.
-- If moving parts are present, describe how the design should be checked through its operating range rather than only at rest pose.
-
-10. ForgeCAD implementation package
-- Produce the actual ForgeCAD file structure you would write.
-- If you are operating in a writable workspace, write the `.forge.js` files instead of stopping at prose.
-- Use `bom()` / assembly metadata where appropriate.
-- Make the design compatible with `forgecad run`.
-- If relevant, make it exportable in process-appropriate formats such as STEP, STL, 3MF, DXF, SVG, or report output.
-
-11. Final verdict
-- End with exactly one of:
-  - `BUILD-READY`
-  - `BEST-EFFORT BUILD CANDIDATE`
-
-ForgeCAD-specific quality bar:
-- Any moving mechanism must use `assembly()` from the start, not manual transform hacks.
-- Use ForgeCAD's joint/collision workflow mentally and structurally: joints, limits, sweeps, collisions, and BOM are part of the deliverable.
-- Do not claim a hinge or sliding joint works unless cavity / clearance logic is physically honest.
-- A pretty static pose is not success.
+0. Operating story and anti-generic bar — restate the org, revision, milestone, test setting; name the generic failure mode avoided and the domain-specific details that make the design credible.
+1. Problem normalization — what is being built, what it does, what "done" means physically.
+2. Assumption bundle — every chosen assumption with units and why it is reasonable.
+3. Architecture choice — one mechanism architecture; briefly name the rejected alternatives and why they lost.
+4. Detailed mechanical design — exact dimensions or formulas for major parts; subassemblies, interfaces, motion ranges, stops, load paths; for articulated mechanisms, concrete finger/link/jaw geometry and all joints.
+5. Actuation and transmission — actuator class, approximate torque/force, transmission approach, fit to the chosen profile.
+6. Manufacturing package — per critical part: material, process, prototype setup/orientation/tooling/finish assumptions, serviceability, process-accuracy-sensitive features. For printed parts (only if printing is selected): orientation, support strategy, print-sensitive features.
+7. Bill of materials — manufactured, printed (if any), and purchased parts; per line: name, exact spec or part class, quantity, purpose, key dimensions/ratings; mirrored in-model with `bom()` so `forgecad export report` reproduces it.
+8. Assembly package — assembly order, jointing method, insert/bearing/pin usage, fastening notes, failure-prone steps.
+9. Validation package — motion range, likely collisions, stiffness/load risks, manufacturability, tolerance stacks, wear points; check printability only for printed parts; check moving designs through their operating range, not just at rest pose.
+10. ForgeCAD implementation package — the actual file structure; in a writable workspace, write the `.forge.js` files instead of stopping at prose, with `main.forge.js` as the runnable entry point for multi-file projects; `dim()` annotations on the dimensions a builder must hit, and the process-appropriate export proven to run (per the forgecad-make-a-model Manufacturing Outputs bar).
+11. Final verdict — end with exactly one of `BUILD-READY` or `BEST-EFFORT BUILD CANDIDATE`.
 ```