ralphy example pulls complete reference projects from the ralphy-assets companion repo and lands them under workspace/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
{ 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 intoworkspace/projects/<as>/, and registers the new project in registry.json.
--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:from_example field on the registry entry records the source, so future project show tells you where the project came from.
Examples vs. templates
| Template | Example | |
|---|---|---|
| What you get | shape only (composition + prompt scaffolding) | a populated project |
| Size | KB | MB to hundreds of MB |
| Use when | building a new project in a known format | want a known-good render to compare against |
| Mutability | typed via template use | edit freely after example pull |
| Storage | templates/ (repo) or workspace/templates/ | workspace/projects/<id>/ |
Caching
Tarballs cache underworkspace/.ralph/asset-cache/examples/. A second pull of the same id (with a different --as) reuses the cached download. Wipe with ralphy assets clean.
Related
- Templates — the shape-only counterpart
- Assets — the broader companion-repo flow
- Project verbs — what you do with the extracted project
- cli/commands/example.ts