Generate Go and Next.js infrastructure from forge.v1-annotated proto contracts.
npx skills add https://github.com/reliant-labs/forge --skill forge-reliant-labs
Please help me install this Agent Skill. Skill: forge Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge Command: npx skills add https://github.com/reliant-labs/forge --skill forge-reliant-labs
Forge removes the tedious, error-prone boilerplate of wiring middleware, mocks, observability, auth, test harnesses, and CI/CD that teams otherwise rebuild by hand.
forge generate as the canonical pipeline to turn forge.v1-annotated protos into a consistent infrastructure surface.Ask the AI: generate the entire Forge infrastructure for my project using its current proto service definitions and refresh any idempotent outputs.
High-intent search queries and answers about installing and using this skill.
To generate production infrastructure from proto definitions, use the generate pipeline to turn forge.v1-annotated protos into Go stubs, TypeScript clients, mocks, middleware, and deployment configs while preserving your business logic.
Yes, regenerating infrastructure from proto is idempotent and enforces strict boundary ownership, ensuring your user-owned business logic, DB layer, and entity types remain untouched during the continuous generation workflow.
Proto-driven code generation for CI/CD and observability middleware is the process of using forge.v1 proto extensions to automatically scaffold deployment configs and wire auth and observability middleware into your Go and Next.js projects.
Yes, proto annotation-based scaffolding works with both Go and Next.js projects, generating TypeScript clients and Go stubs from your canonical proto service definitions, entities, and methods configured in the forge.yaml file.
The best way to automate mock generation and test harnesses from proto contracts is to define your services using forge.v1 extensions and run the generate pipeline to safely output these artifacts alongside your other infrastructure.
You should not use automated infrastructure generation from proto annotations if your project requires custom middleware wiring that cannot be standardized, or if you need to manually own the deployment configuration outside the forge.yaml boundary.
reliant-labsMigrates forge projects from KCL env-var groups to forge.yaml per-environment config.
StudentCristianDesign CI/CD pipelines, infrastructure provisioning, and deployment observability.
sammcjApply Go 1.24+ testing best practices to test files and strategies.
pure-golangStandardize gqlgen GraphQL development with separated contract code and thin resolvers.