All authors

Claude Skills by reliant-labs
github.com/reliant-labs258 skills0 installs195 views
- QueryRead an environment's app data with forge db query <env> — one read-only statement, the transports (direct, port-forward, control plane, bring-your-own `--addr`), the env's data_access policy (open, audited, deny), the forge_ro role that cannot read forge:secret columns, the JSON document and exit codes.Votes: 0GitHub stars: 10
- RecoveryRecover a wedged dev database without hand-editing schema_migrations or dropping it — a migration marked dirty (repair, then forge db migrate force), a version behind disk, stale dev rows (forge db seed reset), and why force never verifies what it asserts.Votes: 0GitHub stars: 10
- Release GuardThe release-time migration-order guard — what migration manifest a release records, why `forge env build --release` and `forge env deploy` refuse a release an environment's schema has already passed (or, for a shared env, one carrying unmerged migrations), the two waiver flags, and the backfill for releases cut before manifests existed.Votes: 0GitHub stars: 10
- SeedingDevelopment seed data — the runtime seeder derived from the applied schema, `forge db seed` commands, domain vocabulary in db/seeds/vocab.yaml, and hand-authored demo data in db/seeds/custom/.Votes: 0GitHub stars: 10
- Composite FksHow `forge db seed` places a composite foreign key — every column from one parent row, two composites sharing a column, a composite that references its own table, and a composite UNIQUE over composite columns.Votes: 0GitHub stars: 10
- ConstraintsWhich constraints forge db seed can satisfy — CHECKs over one or several columns, UNIQUE, ranked bounds, and status-lifecycle rules written as one-way implications rather than biconditionals, with what the seeder does with a guard it cannot place.Votes: 0GitHub stars: 10
- TargetsWhich project files and which database `forge db seed` acts on — `-C` from any directory, seeding a throwaway postgres with a loopback `--dsn`, `--allow-remote-dsn`, and why apply fails with "seeded nothing".Votes: 0GitHub stars: 10
- VocabThe db/seeds/vocab.yaml reference — pools and per-column vocabularies, time ranges relative to today, booleans and NULL, numeric ranges with step, why every column is drawn independently (so rows are not coherent), and pinning an exact value.Votes: 0GitHub stars: 10
- Soft DeleteSoft delete by convention — a time-typed deleted_at makes Delete a stamp and hides stamped rows — and the forge:no-soft-delete column declaration for a deleted_at that is an archive stamp, where archived rows stay readable and writable and Delete deletes.Votes: 0GitHub stars: 10
- StoreWhich tables (and opted-in views) get a generated store and how it is shaped — every applied table is projected whatever its rpcs, the forge:no-entity opt-out, entity names derived from the table, and where CRUD wiring differs.Votes: 0GitHub stars: 10
- Time BucketsReading time-series data back — why a two-argument date_trunc over a TIMESTAMPTZ silently attributes every total to the wrong day, why TIMESTAMPTZ is still the right column type, and the three-argument form that pins the zone in the query.Votes: 0GitHub stars: 10
- VersioningMigration version numbers — why they are UTC timestamps, the two lint rules that enforce it, and what to do when a migration is refused because the schema already passed its version.Votes: 0GitHub stars: 10
- Write PolicyWho may write a column, and which marker says so — the decision table for forge:read-only vs forge:computed vs forge:generated vs forge:guards vs forge:immutable, row-ownership columns, forge:immutable against accidental full-replace overwrites, forge:version optimistic concurrency, and how a NOT NULL column's DEFAULT applies to an unset field (pointer or ,nullzero).Votes: 0GitHub stars: 10
- DebugDebug methodology — triage running-system evidence, guarded data reads, parallel investigation, and synthesis.Votes: 0GitHub stars: 10
- DashboardsDiagnose empty dashboards by replaying console panels and separating absent data from window, scope, filter and query failures.Votes: 0GitHub stars: 10
- InvestigateInvestigate bugs — hypothesis formation, code tracing, and common Forge failure patterns.Votes: 0GitHub stars: 10
- IsolateIsolate bugs via TDD — top-down bisection from e2e to unit test.Votes: 0GitHub stars: 10
- Multi Cluster E2eDebug a k3d multi-cluster e2e env — read the pod status before theorizing the network, hold the pod up on failure, and the nested-cluster gotchas (image pull, host-gateway DNS, path-MTU) that bite only across clusters.Votes: 0GitHub stars: 10
- ReproduceReproduce bugs — diagnostic logging, runtime evidence collection, and e2e reproduction.Votes: 0GitHub stars: 10
- TelemetryLocal ClickStack telemetry, continuous profiles and live pprof when debugging a forge process.Votes: 0GitHub stars: 10
- DeployShip anything with Reliant Forge — static sites, SPAs, services, workers: declare each workload once, bind it to a runtime per env (host, cluster, hosted), build, deploy, verify, roll forward. A frontend-only site: deploy/static-site.Votes: 0GitHub stars: 10
- Build ContextsDocker build contexts for a forge build — the MAIN context a DockerBuild sends (DockerBuild.context, a path or a pinned forge.GitSource in another repo), the NAMED --build-context entries a Dockerfile COPY --from=s, and which of the two a given Dockerfile actually needs.Votes: 0GitHub stars: 10
- BuildBefore and during the build of an env's artifacts — the pre-flight checks (lint, tests, validate-kcl, doctor), `forge env build <env> --push` and `forge build <env>` with their flags, the one project image and how `args` pick its subcommand, the hosted registry login, the boot config check before a push, and Docker build contexts.Votes: 0GitHub stars: 10
- Byo YamlGetting your own Kubernetes YAML into an env's bundle — forge.Manifests (literal objects), HelmChart delivery = "bundle" (your app's chart), forge.Generated (kustomize/jsonnet/any command that prints YAML).Votes: 0GitHub stars: 10
- Cluster AccessReaching another cluster's API server from a workload — forge.KubeconfigSecret, the two credential models (mint a ServiceAccount vs reuse your own), address modes, and rotation on shared clusters.Votes: 0GitHub stars: 10
- Cluster ConnectConnect a Kubernetes cluster you operate to the control plane so environments can deploy into it — the one auth (an uploaded, scoped ServiceAccount token), the address and CA overrides, the grant derived from what the hub applies, delivery, the issuer, disconnect, and the KCL binding.Votes: 0GitHub stars: 10
- Config CheckThe boot config check `forge env build --push` / `--release` / `forge env deploy` run before pushing — each workload booted with its rendered env under FORGE_CONFIG_CHECK=1, what counts as set, where cross-field rules belong, and the --config-check=gate|warn|off rollout.Votes: 0GitHub stars: 10
- Control Plane Secretforge.ControlPlaneSecret, a Secret whose value the env's declared control plane supplies and renews. What it declares, why a first deploy is never blocked on it, why it needs a connected cluster, how a workload reads it with no restart on renewal, and how Observability derives one automatically for a control-plane OTLP destination.Votes: 0GitHub stars: 10
- Delivery PolicyWhat an env's releases must prove before they ship — `forge.DeliveryPolicy`, the per-env controls (trusted builder, signing, provenance/SBOM, Flux verification, admission verification, signed promotions, vulnerability gate, bundle kinds, approvals, the promotion health gate, required gates, the approval hook), their off/audit/enforce modes and defaults (signing and flux_verify depend on whether the env has a control plane), what bundle signing proves, what is mandatory and NOT in the policy, ...Votes: 0GitHub stars: 10
- Delivery UnitsHow an env's delivery is ordered — trees per cluster × delivery unit × phase for a bundle a reconciler (Flux) applies, unit-by-unit workload rollout for `forge env deploy`, declaring units with `forge.DeliveryUnit` and `delivery_unit`, what `after` means, and when moving an object between units is a stop finding.Votes: 0GitHub stars: 10
- DomainsServing your own hostname — the `forge domain` commands for hosted sites and ports, why a hosted domain is a control-plane resource rather than spec, `Port.domains` on a cluster you operate, and reading a bound domain's state.Votes: 0GitHub stars: 10
- External SecretsThe External Secrets Operator as a forge component (forge.ExternalSecretsOperator) — one hardened, cluster-wide install per cluster, what it renders, the three admission policies, how to bump the pin and verify the image, and the residual risk you accept by running it. Use when you declare the operator, when a SecretStore or ExternalSecret is refused at admission, or when you review what ESO can reach.Votes: 0GitHub stars: 10
- ExternalKeep your own deploy tooling (Helm, Fly.io, Cloud Run, ECS, Argo CD, a script) and let forge drive it — forge.OnExternal's four argv hooks (status, plan, deploy, health), worked recipes for each tool, and the shadow-mode path that proves parity with `forge env verify` before forge deploys anything.Votes: 0GitHub stars: 10
- Flux SafeWhat makes an object wrong only under a reconciler (Flux) — a Job with ttlSecondsAfterFinished, a Job with no spec hash in its name, force on a kind that holds data — the `flux-safe` lint, what the bundle build fixes for you, and the per-tree budget it records.Votes: 0GitHub stars: 10
- FluxFlux in forge — who applies a real env, the opt-in self-hosted delivery (`applier = "flux"`, see deploy/flux/self-hosted), and `forge.flux_chart()` (ControlPlane's Flux Operator plus a hardened FluxInstance, pinned) for a consumer that runs a Flux of its own, such as a control plane's hub. Use when declaring or tuning a Flux install, or deciding who applies an env.Votes: 0GitHub stars: 10
- Self HostedOpt a self-hosted env (no control plane) into being reconciled by a Flux forge installs in its own cluster — `applier = "flux"`, `forge.FluxDelivery`, the one-time `forge env deploy <env> --target flux-delivery` bootstrap, then `forge env deploy <env> [<version>]` to ship each release (push the bundle, point the Flux, wait), what happens when a release needs a permission the Flux was not granted (exit 9), and `forge env status`. Use when an env without a control plane should be delivered by a...Votes: 0GitHub stars: 10
- FrontendsBind a frontend per environment to host, hosted static hosting, a bucket or Firebase; declare build facts, runtime config and domains.Votes: 0GitHub stars: 10
- Hosted CapacityThe hosted capacity pre-flight and QUEUED deploys — what `forge env deploy` and `forge env build --push` check with the control plane before building, which answers queue the deploy (exit 7, waiting on billing) and which refuse it, and the Unimplemented fallback.Votes: 0GitHub stars: 10
- Hosted RegistryThe platform container registry — ONE TOKEN (your control-plane credential, no registry password), why hosted pushes log themselves in, what a bare hosted image resolves to, and how to triage a denied push (realm 401) without reaching for docker login.Votes: 0GitHub stars: 10
- HostingReliant hosting for Reliant Forge projects: the scaffolded staging/prod envs are hosted on Reliant — what `_hosted` / `_hosted_frontend` wire, why the API is one workload (`_api`, the binary's `server`) so the browser reaches every service at one origin, rebinding to a cluster you operate or a frontend to your own bucket, kinds hosting refuses (cron, operator), and how an existing cluster-bound project adopts hosting.Votes: 0GitHub stars: 10
- Interrupted CutA release cut whose images were pushed but whose ledger record was never written (the machine died in between) — re-running the same `forge env build <env> --release <v>` from the same clean commit and forge resumes it from its cut journal, rebuilding nothing; `forge env releases interrupted <env> <v>` says whether it can. Use when a cut retry fails with "already tagged", "Registry tags are immutable" or "an earlier cut … was never recorded".Votes: 0GitHub stars: 10
- K3d RegistryThe k3d local-registry mirror (`localhost:5050` ↔ `registry.localhost:5000`) — why in-cluster pulls need it, what forge configures automatically, and how to fix a pre-existing cluster that ImagePullBackOffs.Votes: 0GitHub stars: 10
- Kcl EvalRead a VALUE out of a project's KCL from a script or a Go test — `forge kcl eval <file> -S <path>`, why a plain `kcl run` cannot resolve `import forge` by design, and the pkg/kcleval Go API.Votes: 0GitHub stars: 10
- Kcl ImportsImport ANOTHER forge project's KCL (its workloads.k, config_gen.k, a shared infra repo's envs) — `[forge_projects]` in deploy/kcl/kcl.mod, either at the version go.mod already pins (replace dir, go.work use, module cache + go.sum) or by a git pin (repo + ref + commit lock, no go.mod), the forge-pin skew refusal, and `forge kcl imports`.Votes: 0GitHub stars: 10
- LifecycleStopping, starting and deleting a HOSTED environment from the CLI — `forge env stop|start|delete`, --target and --wait, billing refusals, data retention and `forge env retained list|purge`, and why `forge env down` is not the same thing; the whole app with `forge app stop|teardown|delete`; plus the domain commands and scope errors.Votes: 0GitHub stars: 10
- LlmCall an LLM from a forge app — declare forge.LLM per env (forge.OnHosted = Reliant's gateway, OpenAI- and Anthropic-compatible; forge.LLMEndpoint = any compatible endpoint), give a workload forge.llm_env(), then use the stock OpenAI or Anthropic SDK with no configuration in code. The per-env key, spend caps and model tiers on Reliant hosting (claimed and unclaimed claimable deploys), what is refused, and the errors you will see.Votes: 0GitHub stars: 10
- Managed Identityforge.ManagedIdentity, an env's users declared in KCL — roles, the applications that sign users in, the workloads that read tokens, share_with, SMTP, seed users — administering a hosted env's users with `forge cloud identity` (verbs, the identity:read/manage scopes, password-set codes), how forge fills each consumer's typed config (jwt_issuer, oidc_client_id, ...) with no app code change, what it delivers per runtime, what is refused, sign-in (owners, signup modes, passkeys, magic links, Goog...Votes: 0GitHub stars: 10
- ModelThe deploy model — every workload declared once in workloads.k and bound per env to a runtime (OnHost, OnCluster, OnHosted, OnCompose, BuildOnly, OnExternal); the scaffolded envs, their binders and the shared env base (deploy/kcl/base) they delegate to, `forge env new --from`, who applies an env, what forge writes into every spec (probes, grace, PDB, strategy, hardening), the hosted restricted profile, per-env config, cross-references, and derived features.Votes: 0GitHub stars: 10
- Offline LedgerBreak-glass for an env whose release ledger is a control plane that is unreachable — `forge env deploy <env> --offline-ledger [--to previous|<release>]` redeploys or ROLLS BACK to a release in this machine's offline copy, by its recorded digests, builds nothing, queues the promotion and replays it on the next successful ledger contact. Use when `forge env deploy` cannot reach the control plane (typically a bad release took it down), and to warm the copy in advance.Votes: 0GitHub stars: 10
- Openbao BootstrapHow forge.OpenBao gets the values it needs before it can serve a read — the seal key and the database password delivered from Google Secret Manager, and the `operator init` output escrowed back to it. Covers `Bundle.bootstrap_source`, `BootstrapSecret.generate`, the two Google service accounts and what each may do, the recovery escrow sink, the escrow warning, and the exact Google-side setup. Use when you declare a self-run OpenBao outside a local env, when a deploy stops at the escrow, or wh...Votes: 0GitHub stars: 10