All authors

Claude Skills by reliant-labs
github.com/reliant-labs258 skills0 installs195 views
- CliEvents from a command-line program — pkg/observe/cliev (an anonymous install id, a one-time notice, DO_NOT_TRACK / <APP>_TELEMETRY=off opt-out, always off in CI, `<app> telemetry on|off|status`, a 300 ms batch at exit), the first-run event, and the native ingest key a CLI sends with.Votes: 0GitHub stars: 10
- AnalyzeMeasure what a migration does on a real postgres with forge db analyze — the locks it takes, the tables it rewrites or scans, how long it runs — on a disposable copy of the target; scratch vs dsn (anonymized snapshot) targets, preparing a snapshot (the forge.analyze_target marker, CREATEDB, no connections during the copy), database.analyze config, the five db-analyze-* rules, the forge.db-analyze/v1 JSON document and exit codes.Votes: 0GitHub stars: 10
- Engaged TimeThe automatic page_engaged event every generated web frontend records per page view — view_id, engaged_ms (visible, focused and active time, 30 s idle cutoff, 30 min cap), scroll_pct, entry, resumed — when it is reported (route change, hidden tab, pagehide with a keepalive export), and how to query it (the last report per view_id).Votes: 0GitHub stars: 10
- Public PagesWhich pages a signed-out visitor can open in a gated frontend — the route guard's exact-match `publicExactPaths` and prefix `publicPaths`, why an rpc published with `auth_required` false publishes no page, and how the sidebar hides routes a visitor cannot open (`useCanVisit`).Votes: 0GitHub stars: 10
- ReplaySession replay in forge frontends — the per-env `_session_replay` / `telemetry = forge.BrowserTelemetry {replay = ...}` switch and its hosted ingestion opt-in, the `full`-tier and GPC/DNT gates, hosted dev's replay grant, forced masking, sampling, the runtime's own rrweb recorder (lazy chunk, OTLP/JSON gzipped in a Worker, flush on hide/pagehide with keepalive, replayStart "interaction", replayFlushIntervalMs), and upgrading an app that declared @hyperdx/browser.Votes: 0GitHub stars: 10
- ReliantCI on Reliant (`ci.provider: reliant`) — the Reliant workflows forge writes instead of GitHub Actions (.reliant/workflows/ci.yaml running `forge ci gate`, and the opt-in agent review.yaml), each posting a GitHub check run as the Reliant App. Switching an existing project, activating the triggers, requiring the check in a branch ruleset, forks and untrusted authors, and adding deterministic or agent checks of your own. Use before moving a project's CI off GitHub Actions, or when a Reliant chec...Votes: 0GitHub stars: 10
- CompareReliant Forge and Reliant hosting next to Vercel, Netlify, Supabase, Render, Fly.io or Railway — what one system replaces, where it does not fit (hosted frontends are static exports, so no SSR, server actions or middleware), and what hosting costs, with sources. Load when a user asks "why not Vercel?", "what will this cost?" or which platform to pick.Votes: 0GitHub stars: 10
- Composition GraphMove a project off the legacy Infra / OpenInfra / NewComponents / lifecycle.go / ServeSpec composition onto the composition graph — adopt one root at a time with `//forge:root <name> adopt`, run `forge fix composition-graph`, clear each shape it lists (Infra fields become providers, NewComponents wiring becomes compose.go constructor methods, ServeSpec knobs become reach, with control-plane's as the worked example), then bind deploy workloads to roots.Votes: 0GitHub stars: 10