Keep one part in view.
Keep the current carton or case visible as the user changes contents and protection. Preserve the selected camera direction.
A light industrial interface for an algorithmic packaging API. Measured dimensions, real reference photographs and inspectable calculation results support each decision.
Keep the current carton or case visible as the user changes contents and protection. Preserve the selected camera direction.
Distinguish the configurable envelope, live dimension checks and recorded native results. Name the calculation behind each result.
Use mineral surfaces, graphite type and fine rules. Reserve violet for interaction.
02 / Foundations
#245EAD on #EDF4FF
#216E4E on #EAF6EF
#8A5A13 on #FFF5DD
#B53737 on #FDEFEF
The packaging API for cartons and cases.
Define the protection.
Review the part, protective insert and container before engineering approval.
Parts and requirements
PART ENVELOPE · 214 × 110 × 65 mm
6 px10 px16 pxFlat editorial surfaces first. Use the radius scale for controls and genuine working panels.
03 / Components
Keep destructive actions explicit and contextual.
Prepared dimensions and nominal catalog data support this example. No customer scan has been processed.
Use this state only after the server confirms the record was saved.
A customer design requires engineering review of the part, protective insert and container before production approval.
Use a positive number, or leave this optional field empty.
Prototype describes the capability of the current experience. Review required describes a decision that needs a person to verify it. Neither state certifies a protective design or a transport outcome.
04 / Product patterns
Give each result its input, its scope and its next useful action.
Show packaging, interior dimensions and protection in a persistent recap. Suggestions become selections only after an explicit action.
Offer top and perspective views, a section view and camera reset. Keep controls reachable on mobile.
Never present the three recorded examples as one project or imply that editing the configurator regenerates their CAD files.
This component specimen compares prepared part envelopes with catalog dimensions using a local rule. The product configurator uses the screening API.
Prepared dimensions for this component example.
ZARGES K470-40568 is the suggested reference. This choice applies only to the component preview and is not saved.
Prepared part envelope: 520 × 300 × 150 mm, plus 10 mm allowance on each side. The local rule checks nominal dimensions with horizontal rotation. Container geometry, loading access, protective insert material and transport requirements need engineering review.
Manufacturer references support comparison. They do not establish a supplier partnership, availability or approved fit.
05 / Writing & behavior
Use a concrete verb and name its object. Keep one clear action at each decision point.
Distinguish part dimensions, nominal container dimensions and declared weight.
Show which data and checks support the result. Confirm success only after the operation completes.
Logical order, visible focus, Escape to close a dialog.
Keep the next action stable. Show only the inputs needed for the current step.
Preserve orientation while editing. Render on demand and respect reduced motion; provide a useful dimensional fallback.
Use an asymmetric composition with one large product scene. Keep flat surfaces and fine rules; use metal, foam and plastic materials with credible contact shadows.
Move only to explain a selected change. Camera reset is explicit, dimension changes preserve direction, and static recorded results do not imply a running calculation.
Keep view, selection and export controls keyboard accessible. Respect reduced motion. Show a dimensional fallback if 3D is unavailable. A geometric check does not approve production.
06 / Implementation
import { Button, Field, Badge } from './ui';
<Badge tone="warning">Review required</Badge>
<Field label="Parts and requirements"
htmlFor="project">
<textarea rows={3} />
</Field>
<Button type="submit">
Save project brief
</Button>Semantic colors, typography, spacing, shape and interaction values in JSON.
Download JSONComponent contracts, product vocabulary and contribution rules are versioned with the source.
docs/DESIGN_SYSTEM.mdExtend a shared component before introducing a new visual convention.