Ecosystem
They are registered together at activation and share a single committed registry, but each owns a distinct part of the tree. Knowing which command owns which directory is most of what there is to learn.
| Kind of content | Lives in | Its own repo | Managed by |
|---|---|---|---|
| Learning track | Dev/Learn/<lang> | one per language | learn |
| Portfolio project | Workspace/<lang>/<name> | one per project | polyforge |
| Template | Dev/Templates/<name> | one per template | forge |
All three are gitignored inside the PolyForge repo and restored on demand from polyforge.registry.toml.
Workspace and toolchain management. Runs only inside a PolyForge workspace — it walks up the directory tree to find the root.
A standalone command, registered alongside polyforge at activation. Owns everything under Dev/Learn/<lang>/.
Your personal template library. Each template is its own private GitHub repo under Dev/Templates/<name>/, flagged as a GitHub template repository.
Tiered tracks per language — setup, basics, data structures, intermediate, advanced — plus a gap-filling daily playground that always knows which day comes next.
Every template is its own private GitHub repo, created and flagged as a template repository for you. Register once, pull it back on any machine.
Python, Go, Rust, Node, Java, Dart, Flutter, C++ — declared in modular TOML fragments, installed only when you ask. Nothing downloads behind your back.
The tooling repo stays clean. Tracks, projects and templates live in their own repos and are restored on demand from a committed registry.
These ship with a Workspace/<lang>/ area. Anything mise can install can join them — seeadding a language.