Template save / apply flow

Goal: reuse a team's agreed-upon project structure (brief scaffold + design rules + compile-time contributions) across client projects.

Template sources, priority order

Project Spine resolves templates from these roots (highest priority first):

1. Project-local — ./.project-spine-templates/<name>/ committed to the current repo.
2. User-local — ~/.project-spine/templates/<name>/ on this machine.
3. Bundled — saas-marketing, app-dashboard, design-system, docs-portal, api-service, and monorepo ship with the CLI.

Same name in a higher tier overrides lower tiers.

Flow A — apply an existing template to a new project

spine template list