Reproduce the audit and captures

Audit and capture commands

node scripts/design-system/audit-radarist.mjs ../radarist-app-v3
node scripts/design-system/capture-radarist.mjs ../radarist-app-v3
python3 scripts/design-system/build-radarist-content.py
node scripts/design-system/verify-design-systems.mjs http://localhost:3000

Capture isolation

Where assets live

Optimized captures and public provenance are in public/design-systems/radarist. PNG originals are in Git-ignored uploads/work/radarist-design-system. The fixture and renderer templates are intentionally retained under scripts/design-system so future captures can be reproduced; they are never imported by the live application.

Component specimens arrange real imports with fictional props. Applied specimens compose the real workspace components. No captured control is recreated as an imitation HTML drawing. The extra specimen padding needed to show open menus does not become a product layout rule.

Refreshing safely

• Audit the current source before changing fixture expectations.
• Keep example.org identities and fictional project records. Do not copy a database dump into the public capture harness.
• Inspect component and API prop shapes when the app changes. A successful render is not proof of backend compatibility.
• Check every capture for loading indicators, clipped menus, blank content, browser errors, and unintended personal data.
• Use native-width containers for compact controls; measure the full open surface before cropping so menus remain attached and unclipped.
• The capture workflow rejects duplicate paths and mismatched intrinsic dimensions. Applied screens and component details use distinct filenames.
• Regenerate optimized assets, run the verification command, compare the manifest, then review both themes and phone views in the actual documentation image viewer.

Template extension

For another product, retain the shared page schema and site renderer. Add its own audit, fixtures, capture imports, and source-specific guidance. Do not reuse Radarist’s palette, corners, component claims or readiness labels as defaults for a different product.