getting-started

Scaffold a Forge CLI workspace with services, frontends, and workflow assets.

4|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/reliant-labs/forge --skill getting-started-reliant-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: getting-started
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/getting-started
Command: npx skills add https://github.com/reliant-labs/forge --skill getting-started-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forge project starters prevent slow, error-prone setup by giving you a ready-to-run scaffold and a clear workflow for evolving proto, infrastructure, and business logic.

Core Features & Use Cases

  • Create a complete Forge workspace from a single command, with optional services and Next.js frontends.
  • Generate infrastructure safely from proto using forge generate after API changes.
  • Evolve the database independently through migrations that update SQL schema and ORM functions without forcing proto rewrites.
  • Use-case: Start a new product backend with one or more RPC services plus a frontend, then iterate on endpoints and data model while keeping generated code separate from your handlers.

Quick Start

Create a new project by running: forge new my-app --mod github.com/acme/my-app --service users --frontend web

Frequently Asked Questions about getting-started

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new Forge project with services and a frontend?

To scaffold a Forge project, run the forge new command with your module path, specified services, and a frontend flag to generate a complete working workspace.

How do I generate infrastructure from proto after changing an API endpoint?

Run forge generate after API changes to safely regenerate infrastructure from proto definitions, ensuring you never edit generated directories by hand.

Can I evolve database schemas independently without rewriting proto definitions?

Yes, you can evolve the database independently through migrations that update SQL schemas and ORM functions without forcing proto rewrites.

Do I need a valid project manifest to start local development with Forge?

Yes, local development requires a valid Forge project manifest, which the scaffolding process uses to generate infrastructure and guide safe regeneration.

What is the best way to keep generated code separate from business logic handlers?

The best way to separate code is to follow safe regeneration rules from the scaffolding workflow, iterating on endpoints and data models while avoiding manual edits to generated directories.

Why should I use project scaffolding instead of manual setup for a new RPC backend?

Project scaffolding prevents slow, error-prone manual setup by providing a ready-to-run workspace and a clear workflow for evolving proto, infrastructure, and business logic.