Project templates (--template api/frontend/cli)

[victorpothin]

Problem

Today forge init uses the same generic template for any project. A REST API project has different needs than a React frontend or a CLI tool.

Proposal

Add pre-configured templates with layers and skills suited to each project type.

Expected behavior

forge init --template api        # REST API: all 7 layers
forge init --template frontend   # Frontend: no testing layer (uses own framework)
forge init --template cli        # CLI tool: no docs layer
forge init --template data       # Data pipeline: custom layers
forge init --template infra      # Infra-as-code: focus on planning + execution

What each template defines

• Default active layers
• Domain-specific skills (e.g., api has endpoint design skill)
• Pre-filled examples in FORGE.md
• Common domain Locked Paths

Implementation

• Templates embedded in the binary (like current skills)
• forge init --template with flag, or interactive selection in the wizard
• forge template list to see available templates

Motivation

Reduces setup time and shows that FORGE adapts to different contexts. The existing examples (dotnet-api, rust-backend) already point in this direction.