services

Scaffold and wire Forge mono-repo services, workers, packages, and frontends.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the repetitive setup work required to add new network-facing services, workers, internal packages, and frontends to a Forge mono-repo while ensuring consistent production-grade wiring.

Core Features & Use Cases

  • Scaffold wired components: Create a new Connect RPC service, background worker (including cron workers), internal Go package with a contract, or a Next.js/React Native frontend using the appropriate Forge command.
  • Maintain a correct wiring cycle: Define contracts, generate code, implement business logic, and apply custom dependencies in the designated setup location without editing generated files.
  • Ensure repo conventions stay consistent: Respect Forge-managed port assignment and naming conventions (including hyphenated service names and consistent on-disk/package identifiers).

Quick Start

Use it to scaffold a new API endpoint service by running the command forge add service admin-server, then update the proto contract, run forge generate, and implement the generated handler logic.

Frequently Asked Questions about services

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

FAQPage Schema
How do I scaffold a new Connect RPC service in a Forge mono-repo?

To scaffold a Connect RPC service, run `forge add service [name]`, update the proto contract, run `forge generate` to bootstrap registrations, and implement custom wiring in `pkg/app/setup.go`.

What is the correct workflow for wiring internal packages and frontends in Forge?

The wiring cycle requires defining contracts, running `forge generate` to regenerate Go code and bootstrap registrations, and applying custom dependencies only in `pkg/app/setup.go` while letting `forge.yaml` manage ports.

Can I use Forge to scaffold both web and mobile frontends?

Yes, Forge supports scaffolding wired Next.js and React Native frontends inside the mono-repo while ensuring consistent production-grade wiring and naming conventions across web and mobile applications.

How do I add a background worker with a cron schedule using Forge CLI?

Use the `forge add` command to scaffold a background worker, including cron schedules, after which Forge manages the wiring and registration to ensure the worker integrates consistently within the mono-repo.

Why should I avoid editing generated files when wiring services?

Avoid editing generated files because `forge generate` regenerates Go code and bootstrap registrations; custom dependencies and business logic must be implemented exclusively in `pkg/app/setup.go` to prevent wiring conflicts.

Does Forge manage port assignments for new services?

Yes, Forge manages port assignments automatically through the `forge.yaml` configuration file, ensuring consistent production-grade wiring and preventing port conflicts when adding new network-facing services.