# Applying and reviewing a capture

Read this when the user requests a sample, implementation, or correction alongside a capture.

## Select the applicable mode

Match the target task to the guide's captured surface. If only public-site rules exist, inspect available product evidence before treating them as application rules. Where evidence remains unavailable, label the adaptation as proposed. Preserve explicit user choices when they differ from the source.

Use the target project's adopted components and icon family where they fit. Choose additional dependencies for a concrete need. A component library supplies implementation mechanics; the captured guide supplies hierarchy, density, geometry, and state treatment. Keep verified source packages separate from implementation choices, including substitute fonts and custom icons.

## Apply relationships before decoration

Establish composition, reading order, type roles, density, and alignment first. Then apply color, borders, corners, and imagery. For working interfaces, inspect shared header baselines, row rhythm, grouped controls, pane boundaries, and scroll ownership when relevant. Preserve relationships without requiring every product to copy the source's pane count or navigation.

## Compare the rendered result

Save a baseline before revising an existing implementation. Compare the reference and rendered result at comparable viewport sizes and states. Check the defining decisions individually, including what belongs inside the interface versus its surrounding presentation. Correct visible mismatches before calling the implementation reviewed.

Exercise the main task through the real interface. Check narrow layouts when in scope; preserve access to actions and data as columns or panes move. Verify relevant hover, focus, selected, disabled, and scrolling behavior. Keep screenshots of the final reviewed state and report the checks actually run.

Feed repeated or clearly demonstrated mismatches back into the guide. Scope each correction to its evidence; preserve useful rules for other surfaces. An implementation screenshot demonstrates an interpretation, not a measurement of the source.
