heliosforge

Run any Helios bundle in any project, with one command:

npx heliosforge run <slug>

The slug is whatever shows on the bundle's card in the Helios Codex. Run the command from the directory you want the bundle's files to land in — heliosforge fetches the bundle, validates it, and writes each file relative to your current working directory. Existing files are skipped, never overwritten.

What gets written

A Helios bundle is a JSON blob with a small manifest (slug, title, description, category, version, created_at) plus a list of { path, content } text files (Markdown, code, JSON/YAML, shell scripts). heliosforge walks the list and creates each file with its parent directories as needed.

Examples

# In a fresh project — drop in someone's CLAUDE.md + skills folder
cd ~/new-project
npx heliosforge run vibecoder-starter

# In an existing project — only files that don't exist yet get added
cd ~/existing-project
npx heliosforge run my-vault

Source

The bundle format and writer live in the helios dashboard repo. The CLI duplicates lib/bundle/format.ts and lib/bundle/write.ts from that repo into src/format.ts and src/write.ts so the published package has no cross-package imports. When the bundle format evolves, both copies must be kept in sync.

License

MIT