Use explicit values, inspect every generated line and keep the source document meaningful before visual placement.
Start with the sizing job
An fr track shares remaining grid space; px reserves a fixed track; auto follows intrinsic sizing; and minmax(minimum px, maximum fr) keeps a reviewable floor while participating in leftover space. GridWeave serializes those four profiles exactly and refuses values outside its bounded contract. Prefer fr for flexible proportions, auto for content-led rows, and minmax when a flexible column still needs a deliberate minimum. Fixed pixels can be useful for known rails but should be tested with zoom and translated content.
Count explicit tracks
Each control maps to one explicit entry in grid-template-columns or grid-template-rows. Adding a row or column creates a 1fr track; shrinking is rejected when it would cut through an existing named area. This preserves the model instead of silently moving content. After copying, inspect the list in source control and add responsive changes as ordinary media or container queries where the real component needs them.
Verify the real document order
GridWeave previews the validated visual grid, not the meaning or reading order of your page. Keep source HTML in a logical sequence that works before layout CSS, then test keyboard navigation, zoom, long translated text, narrow widths and assistive technology in the real component. Add responsive breakpoints deliberately in your own stylesheet: the generated explicit tracks describe only the current layout. The capsule stores no layout, so keep accepted CSS and HTML in source control.