Skip to main content
ralphy example pulls complete reference projects from the ralphy-assets companion repo and lands them under .ralphy/workspaces/<ws>/projects/<as>/. Templates give you the shape; examples give you a working project, end-to-end, with assets and logs already populated. Use them for visual regression baselines, agent fine-tuning fodder, or as the starting point for a tweak-it-from-here variant.

ralphy example list

Returns { manifestUpdated, examples: [{ id, template, sizeMB, via, description }] }. The size column matters — examples can be 80–400 MB depending on render length and whether refs are included.

ralphy example pull <example-id>

Downloads the tarball, SHA-256 verifies, extracts into .ralphy/workspaces/<ws>/projects/<as>/, and registers the new project in registry.json.
The --as <project-id> flag is required — you pick the local id. The verb refuses if the destination already exists; pick a different --as to retry.

What lands on disk

An extracted example is a regular project, identical in shape to one you’d create from scratch:
The from_example field on the registry entry records the source, so future project show tells you where the project came from.

Examples vs. templates

If you want to start from a known-good render and iterate, pull the example. If you want to start from scratch in a known format, use the template.

Caching

Tarballs cache under .ralphy/cache/assets/examples/. A second pull of the same id (with a different --as) reuses the cached download. Wipe with ralphy assets clean.