All authors

Claude Skills by reliant-labs
github.com/reliant-labs258 skills0 installs195 views
- ForgeLoad first in any Reliant Forge project — static site, SPA, landing page, docs site, web/mobile app or API. What the project gets with no setup (traces, per-endpoint latency and errors, alerts, release health checks, build-once deploys), the two paths, the commands that print forge's whole surface, the pre-flight checklist that stops you hand-writing what forge already scaffolds, and the rules.Votes: 0GitHub stars: 10
- ActivityThe typed activity stream (forge/pkg/activity). How to declare on an rpc which activity event it records (verb, target, env), how the one interceptor writes it, how to opt a mutation out, how to write transactionally or from a non-RPC actor, and how to store and list activity_events.Votes: 0GitHub stars: 10
- AdapterOutbound boundary translators. One adapter per third-party system / queue / storage backend; narrow interface, vendor-neutral callers.Votes: 0GitHub stars: 10
- AdoptBring your app — start anywhere. What forge does for an EXISTING repo (any language, any CI, any cloud) with no rewrite and no required order — standalone linters, playbooks, runtime libraries, hosted monitoring (forge obs init), deploys recorded from your own CI (forge release record), parity with your deploy tooling (forge.OnExternal + forge env verify), forge-driven deploys (--kind app) and hosting, your own migration tool, ownership knobs, polyrepo, previews, gates, secrets, codegen — plu...Votes: 0GitHub stars: 10
- DeployForge deploys an existing app in any language (Express, Django, Rails, Spring, …) from its own Dockerfile, without rewriting it, in tiers you can stop after — 1 ship it (`forge project new --in-place --kind app` writes forge.yaml + deploy/kcl from its Dockerfile and compose file — DockerBuild, managed Postgres, migrations job, secrets — then the dev loop and deploy; the templates it writes are here to review or write by hand), 2 see it (OpenTelemetry → dashboards, alerts, obs check verdicts),...Votes: 0GitHub stars: 10
- Librariesforge's runtime libraries in an existing app, with no forge project — Go's github.com/reliant-labs/forge/pkg/* (observe, svcerr, middleware, pgtest, testkit, …) and npm's @reliantlabs/forge-web-runtime (/node initNodeTelemetry, browser telemetry, Connect interceptors). What each is good for standalone, how to add it, and how to verify.Votes: 0GitHub stars: 10
- Lintersforge's linters on a repo that is not a forge project — which lanes run standalone (migration safety on db/migrations/*.up.sql; in a Go module tracing, time-bucketing, slow tests; go test -json readers), what each flags, the per-file waivers, scoping legacy migrations, and the CI step to add beside the user's own jobs.Votes: 0GitHub stars: 10
- MonitoringInstrument an existing app, in any language, to the telemetry shape forge reads — resource attributes, one JSON log line per request, request id, one server span, RED metrics, recovery, /healthz and /readyz — with forge's own Go code as the reference to translate and initNodeTelemetry for Node. Where the data can go — the user's own backend, or Reliant's hosted store for any app via forge obs init — and how to verify it.Votes: 0GitHub stars: 10
- Api OpenapiEmit OpenAPI 3 specs from your proto services as a buf pipeline step — opt-in via `api.openapi: true` in forge.yaml. The spec is a projection of proto, so the proto file stays the single source of truth. Also — bring your own OpenAPI 3 spec: declare it as a `forge.API` and forge validates and lists it (what works today, and what does not yet).Votes: 0GitHub stars: 10
- Api RestREST URLs on top of Connect handlers via connectrpc.com/vanguard — opt-in runtime transcoding (no parallel codegen), default annotations on CRUD RPCs, and composition with api.openapi.Votes: 0GitHub stars: 10
- ApiWrite Connect RPC handlers — the pb-through model (every RPC is a method on the handler package's `*Service` working with wire types + `s.deps`), CRUD via `// forge:entity` + `pkg/crud`, error handling with `svcerr.Wrap`, and testing.Votes: 0GitHub stars: 10
- HttpHitting Connect RPC handlers with plain HTTP+JSON — URL shape, Content-Type rules, streaming caveats, and the `forge api curl` helper for building copy-pasteable curl invocations.Votes: 0GitHub stars: 10
- Role InterfaceExtend a service's Repository without breaking sibling fakes — the opt-in role-interface pattern for parallel-migration rounds, and when to promote it back onto Repository.Votes: 0GitHub stars: 10
- ArchitectureArchitecture map — project structure, generated vs hand-written code, the generate pipeline, wiring, files-not-to-edit, and a naming + related-skills index. Deep topic detail lives in the owning skills (proto, db, contracts, service-layer, observability, testing, deploy).Votes: 0GitHub stars: 10
- Graph ChecksWhat forge lint checks about the composition graph — reach (forge-graph-unreachable, //forge:standby, declaring roots one at a time), root-only nodes (//forge:root-only), audience (//forge:audience), the least-knowledge Deps rules under --conventions and their severities, forge fix narrow-deps, migrating a pre-graph Infra/NewComponents project with forge fix composition-graph, and opt-in construction rollback (ConstructionRollbackTimeout, BuildWithRollback).Votes: 0GitHub stars: 10
- Audit JsonReading `forge project audit --json` and `forge project map --json` — the JSON shapes, common jq queries, CI integration patterns, and the additive-extension contract that keeps consumers stable as new finding types appear.Votes: 0GitHub stars: 10
- Ci WorkflowDrop-in GitHub Actions workflow that runs `forge project audit --json` + `forge project map --json`, uploads them as artifacts, fails on error status, and posts a PR summary comment.Votes: 0GitHub stars: 10
- AuthAuthentication — managed identity as the default (forge.ManagedIdentity fills the validator's issuer, audience and the login broker's credentials; bring-your-own issuer is the escape hatch), the owned SetupAuth validator (JWT default with OIDC discovery, Clerk/Firebase variants), the fail-closed interceptor, mixed public/authenticated APIs via auth_required, and how to tell from source whether a server authenticates. Sub-skills: authorization, dev-loop, frontend, shared-issuer, external-provi...Votes: 0GitHub stars: 10
- Api KeysAPI keys as a credential — what every scaffold already wires (`X-API-Key` or `Bearer fk_…`, routed by shape to a key validator installed after `OpenInfra`), the `APIKeyValidator` seam you fill in over your own table on the handlers' pool, `forge/pkg/apikey`'s Generate/Hash/LookupPrefix/Verify, and `Claims.Credential` (`IsAPIKey`), the unforgeable mark of a key-authenticated call.Votes: 0GitHub stars: 10
- AuthorizationTurning an IdP identity into an application principal — the enrichClaims DB-backed seam and its rejection codes, why request validation belongs to protovalidate instead, app-owned provisioning via a public Register RPC, why binding an invitation or membership by email must require devidp.User.EmailVerified, and declaring an owner column so forge fails a build that ships unscoped.Votes: 0GitHub stars: 10
- ChainThe auth interceptor chain's two caller-shaped seams — audiences (one serverkit chain and listener per kind of caller, enforced from the proto's `audience`) and publishing one rpc with `auth_required` false, including why a public handler sees no claims and how to handle the anonymous case.Votes: 0GitHub stars: 10
- Dev LoopGetting a token locally — the dev IdP that comes up with `forge env up` for a real browser sign-in (start here), what it declares vs. what a deploy-time job converges and publishes, hand-minting against a shared secret for API-only smoke tests, and the traps that are not your wiring (host-header instance routing, opaque-vs-JWT access tokens).Votes: 0GitHub stars: 10
- External ProviderRunning a forge app on an identity provider of its own (Supabase, Auth0, Clerk, Firebase, Cognito, any OIDC issuer) instead of managed identity — the issuer swap in config.k, the Clerk and Firebase validators, naming the provider on the auth middleware's sign-in heartbeat (ChainDeps.AuthProvider, in code), passing Caller when the app's auth keeps the caller in its own context, and the three ways to emit the standard auth events.Votes: 0GitHub stars: 10
- FrontendThe browser half of authentication — native sign-in (the browser POSTs credentials to the app's own API and gets an HttpOnly session cookie; the server runs the whole OIDC flow), the scaffolded sign-in screen and route guard, why there is no token in JavaScript, and what React Native does instead.Votes: 0GitHub stars: 10
- Shared IssuerRunning a forge app against a shared, operated identity provider (a managed Zitadel) — jwt_roles_claim and Zitadel's project-roles map, the JWKS snapshot fallback that lets a restart survive an issuer outage (what is trusted and when), and idp_broker_token_file for rotating the login broker's token without a restart.Votes: 0GitHub stars: 10
- AuthoringAuthoring a service proto — mark entities with `// forge:entity` and let scaffold inject their CRUD, declare every custom rpc yourself (CRUD is decided by the exact rpc name; `// forge:custom`), declare the authoritative route when two FKs reach one parent (`forge:ref`), and the shape in four lines (SQL is schema truth, proto is wire truth, an entity is both halves).Votes: 0GitHub stars: 10
- BinariesNon-server long-running binaries — when to use `forge scaffold binary` vs `forge scaffold worker` vs `forge scaffold service`, plus the lifecycle and deploy story.Votes: 0GitHub stars: 10
- Config FilesLoading a binary's typed config from a YAML/JSON file — --config and the per-binary <BINARY>_CONFIG path variable, precedence, the override, what a missing or invalid file does, and how a root and a command config share one flat file.Votes: 0GitHub stars: 10
- SubtreesSubtree configs — one typed config several commands of a binary load (every command at or below a path), without every process loading it; registration, the loader's path check, the collision rules and the KCL projection.Votes: 0GitHub stars: 10
- CiGitHub Actions workflows forge generates — what ships out of the box, the Tier-1 vs Tier-2 boundary, how to add custom workflows alongside the generated ones without losing them on regeneration, and how `forge ci` helper subcommands fit in.Votes: 0GitHub stars: 10
- ExtendingHow to extend the scaffolded CI — add a check to the gate (ci.gate.extra_checks), add a job that needs its own runner, add a parallel Tier-2 workflow (release, deploy previews, notifications, coverage upload, extra scanners), or switch one of forge's workflows off when the repo has its own (ci.workflows). Use before adding a job to ci.yml or a new file under .github/workflows/.Votes: 0GitHub stars: 10
- GateThe local CI gate — `task ci` / `task ci:checks` / `forge ci gate`. What each lane runs, the four rules (every failure reported, a skip is not a pass and needs CI_SKIP, pinned tools, the job summary), how checks run concurrently (after, mutates_tree, heavy host slots, --jobs), the verdict cache (`PASS (cached <sha>)`), affected-package unit tests on a branch (CI_FULL), CI_ONLY / CI_REPORT / CI_LOG_DIR, tiers per CI event (--tier pr|queue|main|full, --event) and the forge.ci.gate/v1 --json doc...Votes: 0GitHub stars: 10
- Lint RolloutThe project's lint dials — `lint.lanes` to switch a whole lane off, `lint.rules` for one rule's severity, `lint.allow_skip` for a lane that could not run — and why a new or tightened `forge lint` rule is a warning for one release before it gates - introduced_in / gates_from, how your forge.yaml forge_version decides, the "new in vX; gates from vY" note and the verdict line that counts it, --json's grace object, lint.rules to gate early or extend the grace period, and how a forge author declar...Votes: 0GitHub stars: 10
- SlotsHost-wide heavy slots — why heavy work (test lanes, builds, codegen, full lints, gate checks) queues on a shared machine, `forge slot run` / `forge slot status`, FORGE_HEAVY_SLOTS / FORGE_SLOTS_DIR / FORGE_SLOT_HELD, which forge commands take a slot on their own, and how nesting avoids deadlock. Use when a command prints "waiting for a heavy slot", when sizing a shared machine, or when wrapping your own heavy task.Votes: 0GitHub stars: 10
- ToolchainHow CI resolves the project's Forge pin and installs codegen tools and frontend dependencies before verifying generated files.Votes: 0GitHub stars: 10
- ContractsUsing forge's contract system — when to use contract.go, how to write one, what forge generate produces, integrating with tests.Votes: 0GitHub stars: 10
- Package MarkersThe package-level contract markers — //forge:exclude-contract (no contract, no mock) and //forge:not-a-component (a contract package the server does not compose) — when each is legitimate, what forge refuses, and how gofmt places //forge: directives.Votes: 0GitHub stars: 10
- DbDatabase work — SQL migrations as the single schema source of truth, projected by forge generate into entity structs, ORM, CRUD wiring, and frontend pages.Votes: 0GitHub stars: 10
- Append OnlyImmutable ledgers — declare append-only tables in migrations so the generated stores and delegates cannot update or delete them.Votes: 0GitHub stars: 10
- BirthBirthing an entity's table from its proto message — `forge scaffold entity --from-proto`, one-time birth, no import path, the birth markers (append-only, secret, read-only, generated, soft-delete) baked into your owned migration, and the proto → SQL column mapping.Votes: 0GitHub stars: 10
- Closed SetsKeep a CHECK constraint and the Go set it mirrors equal — declare `forge:closed-set <set>` on the constraint, and forge lint's closed-sets lane names missing and extra values and prints (or `forge db migration new --closed-set` writes) the forward migration.Votes: 0GitHub stars: 10
- ConstraintsSchema declarations a migration makes beyond columns — the column write policy (ownership, forge:immutable, forge:version), append-only tables, the authoritative route when two FKs reach one parent (forge:ref), CHECKs that mirror a Go set (forge:closed-set), derived values (generated vs computed), and status-lifecycle CHECKs as implications.Votes: 0GitHub stars: 10
- Crud OverridesDiverge from generated CRUD without forking the projection — override op fields in your owned handlers_crud.go, the per-op seams (op.Filters, op.Fetch, op.Persist) a per-caller policy attaches to, what the Update op already does for read-only fields, and the one set-based UPDATE that replaces a List + per-row update loop.Votes: 0GitHub stars: 10
- DashboardsDashboards over your database — the forge_dash role and its lifecycle (ManagedDatabase.dashboards in KCL turns its login on), granting it exactly the columns a panel needs with an ordinary migration, revoking in a later one, the migrator's read-only check, the recorded limits (row cap, timeout, concurrency), kubedial credentials by role, and why the allowlist is Postgres privileges rather than an SQL parser.Votes: 0GitHub stars: 10
- Deploy MigrationsHow a deployed environment applies schema migrations — migrations embedded in the binary, the rendered migration initContainer, replica races and advisory locking, failure modes, and where AUTO_MIGRATE still fits.Votes: 0GitHub stars: 10
- Derived ValuesColumns whose value is computed rather than entered — a same-row derivation is a GENERATED column declared at birth with `// forge:generated <expr>`, an other-rows rollup is a plain `forge:computed` column the owning RPC writes — plus the postgres rules a generated expression must meet.Votes: 0GitHub stars: 10
- Generated OrmWhat the generated ORM does — Go field types, plain INSERTs with RETURNING, defaults and managed timestamps, drift-guarded _orm.go files, column and constraint allowlists, bound statements, NotFound on by-key methods, transactions, the <Entity>Store interfaces — plus overriding generated CRUD and the one data-access path for custom queries (_repo_ext.go).Votes: 0GitHub stars: 10
- Migration TimeoutsWhy a migration never waits forever for a lock — the default lock_timeout (5s), statement_timeout (30m) and retry (5 attempts), the per-migration `-- forge:lock-timeout` / `-- forge:statement-timeout` header directives, CREATE INDEX CONCURRENTLY and its INVALID-index cleanup, and the run-wide flags.Votes: 0GitHub stars: 10
- Orm And SafetyWhere the generated ORM lands (database.orm.package), and the per-project database opt-outs — `//forge:no-orm` in internal/db (or `features: {orm: false}` in forge.yaml) to skip the generated ORM, and `-- forge:allow-destructive` in a migration to allow one destructive change — plus how the database itself is derived, and the lint rules for a migration file that cannot run as one transaction (CONCURRENTLY, enum values).Votes: 0GitHub stars: 10
- Own Migration ToolKeep your migration tool — goose, atlas, flyway, dbmate, golang-migrate or your own command — and your migrations directory, and still get forge's ORM projection, seeding, migration safety and `forge db migrate`. The forge.yaml `database.migrations` hook, per-tool examples, what forge runs and with which environment, what changes (and what does not), and how to migrate on deploy.Votes: 0GitHub stars: 10