Document Forge proto file conventions and annotation rules for code generation.
npx skills add https://github.com/reliant-labs/forge --skill proto-reliant-labs
Please help me install this Agent Skill. Skill: proto Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/proto Command: npx skills add https://github.com/reliant-labs/forge --skill proto-reliant-labs
Proto files in Forge projects can silently drift from the conventions that drive reliable code generation, causing failing builds, out-of-sync ORM state, and confusing generator errors.
Ask the skill to review your proto file named service task definitions and tell you what to change so it satisfies Forge entity, field, and CRUD conventions before you run forge lint --conventions.
High-intent search queries and answers about installing and using this skill.
Proto file conventions for CRUD and ORM code generation require correct forge/v1/forge.proto imports, one service per file, and explicit pk and tenant/timestamps annotations on entity messages to ensure proper layer generation.
Running buf generate alone causes ORM out-of-sync checks because it bypasses Forge's canonical workflow. You must run the forge generate, forge lint, and forge build sequence to ensure generated artifacts and ORM state remain aligned.
To annotate multi-tenancy and timestamps in Forge proto entity messages, apply explicit tenant and timestamp annotations directly within your entity definitions, ensuring the generator correctly scopes data and tracks creation or modification times.
Proto field and enum rules for safe evolution in Forge projects require using stable field numbers, reserving deleted fields, following enum requirements, and including optional filter fields in List requests to handle greenfield and migrated projects safely.
To structure List RPC requests and responses in Forge proto files, follow Forge CRUD conventions by including optional filter fields in the request and defining the correct request and response structures to pass lint checks.
reliant-labsSplit multi-service protobuf files into one .proto per service with shared types.
reliant-labsRename internal-package contract.go elements to canonical Service, Deps, and New signatures.
NolanPicEnforce frontend component coding standards in Claude Code workflows.
pohlai88Document and enforce AFENDA-NEXUS database schema patterns with Drizzle ORM and PostgreSQL.
