All authors

Claude Skills by reliant-labs
github.com/reliant-labs258 skills0 installs195 views
- User CountsWho the console counts as an active, new or returning user — an event that is not activity (observe.TrackState, observe.WithStateEvents, track(…, {state: true}), forge.ProjectAnalytics.not_activity) and a user who is not counted (staff, monitors: exclude_users_with, exclude_user_ids), the project rules every user count (Users dashboard, Overview Users card, forge obs users) compiles in.Votes: 0GitHub stars: 10
- ProfilesContinuous profiles — what pkg/observe captures and pushes over OTLP, when profiling is on (local ClickStack by default, signals.profiles elsewhere), the otel-profiles collector and its ClickHouse tables, and exporting flamegraphs with forge obs profile.Votes: 0GitHub stars: 10
- QueryThe feedback loop from the CLI — forge obs status for what is wrong now, forge obs check after a deploy, then issues, traces, logs, endpoints and metrics; forge env releases for what was live when; forge db query for the rows. Backends (local ClickStack, the control plane), the JSON contract, suggested next commands, and the exit codes a CI gate branches on.Votes: 0GitHub stars: 10
- IssuesFiltering and assigning issues by person with `forge obs issues --assignee` and `forge obs issue assign` — how `me` is resolved from the verified credential (never a stored login), why an organization automation token is refused, how `none` maps to the API's unassigned flag, and what a local env answers.Votes: 0GitHub stars: 10
- Release HealthHow `forge obs check` judges a release in depth — when the after window starts (the live time a promotion's apply and cluster-rollout gates record, which a retried promotion reaches after its first promoted_at), per-endpoint latency, per-endpoint error rate with its error_rate_min_errors floor and baseline_window, attribution — version_share, window_not_live, rollout_incomplete and findings[].unattributed, which keep another version's findings from failing a release — the issue thresholds (ne...Votes: 0GitHub stars: 10
- SessionsInvestigate what one user did — forge obs sessions to find the sessions that raised errors, forge obs session for the timeline (navigation, clicks, failed requests, errors), then the issue, trace and logs its ids lead to. What the timeline never holds, and its JSON shapes.Votes: 0GitHub stars: 10
- Tracing Lintforge lint --tracing — the four rules that keep a request in one trace (log-without-ctx with its autofix, raw-http-client, raw-sql-open, contract-uninstrumented), lint.tracing.log_wrappers for your own logging helpers, and adopting the rules in a large codebase.Votes: 0GitHub stars: 10
- UptimeUptime checks — outside-in HTTP probes of a hosted env's public frontends and routes, run by the platform on a schedule. `forge.UptimeCheck` / `forge.Uptime` in KCL (a url, a route, or a hosted target; method, interval, timeout, expected status and body), the checks forge derives with no declaration and how to opt out, the `uptime.check.up` / `uptime.check.duration` / `tls.cert.expiry_seconds` metrics, and the UptimeCheckFailing / CertificateExpiring alerts.Votes: 0GitHub stars: 10
- Proto BreakingProtobuf evolution discipline — deprecate first, reserve removed tags, version-rev for hard breaks, gate breaking changes in CI.Votes: 0GitHub stars: 10
- Proto SplitSplit a multi-service proto file into per-service files — when to split, how to identify shared types, and the commit-per-phase discipline that keeps each step shippable.Votes: 0GitHub stars: 10
- ProtoProto file reference — annotations, CRUD conventions, field rules, and common mistakes.Votes: 0GitHub stars: 10
- GuardsDeclare forge:guards on custom RPC request fields so scaffolded edit pages respect domain transitions; detect stale pages and misspelled markers.Votes: 0GitHub stars: 10
- HooksThe React Query hooks forge generates from a service proto — read vs write classification, forge:query-scope, paged use<Rpc>Infinite, and <svc>Queries / <svc>Mutations for reads and writes outside React.Votes: 0GitHub stars: 10
- List FiltersDeclare range and prefix filters on a List request with (forge.v1.filter) so the generated List op applies them; no hand-written List handler for a time window or a key prefix.Votes: 0GitHub stars: 10
- SecretsThe forge secret-provider model — declare a secret once as a reference, bind its value per-env via a provider (a gitignored YAML secret store for dev/local, external for prod/staging), and let forge resolve + inject it into the services that declare it. forge projects use no .env files. KCL stays pure — no secret values ever in rendered output.Votes: 0GitHub stars: 10
- Service LayerBusiness logic behind an interface — Service interface in domain types, Deps struct of interface-typed deps, sentinel errors at the storage edge.Votes: 0GitHub stars: 10
- TransactionsTransactions in a forge service — s.deps.DB.RunTx(ctx, orm.Serializable|orm.ReadCommitted, fn) carries the transaction in ctx so stores and generated delegates join it; there is no default isolation, and choosing the level is choosing a correctness argument (no locks + retry, or a lock + one attempt); orm.AfterCommit for side effects; the lock-free state-transition recipe; BeginDetached; how RunTransaction/WithTx relate.Votes: 0GitHub stars: 10
- ServicesScaffold and wire new services, packages, and frontends in a Forge project.Votes: 0GitHub stars: 10
- ShutdownGraceful shutdown of a forge server — the drain sequence (readiness flip, pre-stop, listener drain, teardown), long-lived streams (SSE, websockets, Connect streams) ended inside the budget instead of holding it, the client contract for a drained Connect stream (OK + x-forge-drained, or Unavailable via RedialOnDrain), websockets closing 1012 through AfterDrain with their cleanup run, the soft "say goodbye" signal, DrainReserve, and using the same pieces from a main that runs its own listener.Votes: 0GitHub stars: 10
- ShapesFind project symbols across proto, schema, handlers, hooks and stores with forge project shapes; inspect library APIs without hunting generator source.Votes: 0GitHub stars: 10
- BlobstoreFile uploads and downloads (images, documents, attachments) — declare a forge.Bucket per env, hand a workload its connection with forge.bucket_env, presign an upload in a handler with forge/pkg/blobstore, PUT it straight from the browser, confirm it with Stat. Dev runs MinIO; Reliant hosting provisions the bucket (forge.OnHosted); anywhere else use any S3-compatible bucket (S3, R2, GCS).Votes: 0GitHub stars: 10
- TestingTesting Go services and packages — testkit's real-postgres harness, generated contract mocks, pkg/tdd, the task test lanes and their build tags.Votes: 0GitHub stars: 10
- E2eEnd-to-end tests — full stack, multi-service flows, browser testing.Votes: 0GitHub stars: 10
- FlowFlow tests — hand-write a full multi-entity RPC test: seed the FK spine with seedplan.SeedGraph, drive the real service against a migrated DB, assert the derived result, and cover the negative/gap case.Votes: 0GitHub stars: 10
- IntegrationIntegration tests — real database, build tags, transaction isolation.Votes: 0GitHub stars: 10
- PatternsCopy-paste-ready test patterns — table-driven via the pkg/tdd library for RPC handlers, contract methods, and contract mocks; pure validators stay hand-rolled.Votes: 0GitHub stars: 10
- UnitUnit tests — hermetic, fast, handler-level tests using generated mocks.Votes: 0GitHub stars: 10
- Ui Native PackageThe `@<scope>/ui-native` workspace package — what ships, the web/native gap, ownership rules, and when to outgrow it for Tamagui or Unistyles.Votes: 0GitHub stars: 10
- WorkersBackground workers — adding, implementing, and testing workers (including cron-scheduled).Votes: 0GitHub stars: 10
- Code ReviewCode review orchestration methodology — triage-based reviewer spawning, finding synthesis, and structured review reportingVotes: 0GitHub stars: 10
- Architecture ReviewArchitecture review methodology — design-level analysis, high-leverage refactoring recommendations, and correctness-focused code assessmentVotes: 0GitHub stars: 10
- Code Hygiene ReviewCode hygiene review methodology — correctness bugs, test quality issues, LLM antipatterns, and migration safety checklistVotes: 0GitHub stars: 10
- Performance ReviewPerformance and concurrency review methodology — scalability analysis, race condition detection, and resource leak identificationVotes: 0GitHub stars: 10
- Security ReviewSecurity review methodology — vulnerability detection, injection analysis, authentication and access-control verification, and structured security reportingVotes: 0GitHub stars: 10
- Ux Review MethodologyUX review methodology — browser-based application auditing, accessibility testing, responsive verification, and structured UX reportingVotes: 0GitHub stars: 10
- Conflict ResolverResolve git merge and rebase conflicts by understanding both branches' intent, classifying conflict types, and making intelligent merge decisionsVotes: 0GitHub stars: 10
- Documentation WritingDocumentation methodology — narrative-driven technical writing, teaching vs reference distinction, and investigation-based accuracyVotes: 0GitHub stars: 10
- General AgentGeneral-purpose agent methodology — discovery-first approach, spawn delegation, handing findings to sub-agents via durable briefing files, and batching independent work into fan-out wavesVotes: 0GitHub stars: 10
- Git OperationsGit operations methodology — conventional commits, branching strategies, conflict resolution, and version control best practicesVotes: 0GitHub stars: 10
- Planning MethodologyStrategic planning methodology — research delegation, plan synthesis, and structured implementation planning with security and correctness prioritiesVotes: 0GitHub stars: 10
- RefactorCode refactoring methodology — systematic code transformation patterns, tool selection strategies, and behavior-preserving techniquesVotes: 0GitHub stars: 10
- Migration GuidanceMigration methodology — discovering, evaluating, and converting configuration from Claude Code, Cursor, Codex, and Windsurf into ReliantVotes: 0GitHub stars: 10
- Research MethodologyComprehensive investigation methodology for codebase analysis, system architecture discovery, and technical researchVotes: 0GitHub stars: 10
- Simplification AssessmentAssess whether refactoring should precede implementation — load this when evaluating if code needs simplification before making changesVotes: 0GitHub stars: 10
- Testing MethodologyTesting methodology — test harness design, mock strategies, flakiness prevention, and structured test planningVotes: 0GitHub stars: 10
- Ux DesignUI/UX design methodology — trend research, accessible component architecture, responsive design, and performance-optimized interfacesVotes: 0GitHub stars: 10
- Validation HarnessCreate validation harnesses to verify fixes and features work end-to-end. Load this skill when you've made multiple fix attempts that haven't worked, when working on UI flows or multi-step integrations, or when you need to prove a fix actually works before declaring it done. Covers E2E test setup (Playwright, Cypress), API smoke tests, mock strategies for gRPC/REST backends, and parameterized test patterns.Votes: 0GitHub stars: 10
- ConnectConnect an agent or chat app to forge over MCP — the local server (npx -y @reliantlabs/forge mcp) for the repo tools, and the hosted Reliant Forge connector (https://api.reliantapi.com/forge/mcp, OAuth sign-in, no install) for the account tools — with the exact steps for Claude (claude.ai, Desktop, Code), ChatGPT, VS Code, Cursor, Goose and Reliant, and which tool lives where.Votes: 0GitHub stars: 10
- AiThe built-in AI hub — LLM and workflow monitoring every hosted forge app gets from its OpenTelemetry GenAI spans (pkg/obsbuiltin's AI dashboards, the console's AI group) — runs, success, duration, model calls and tokens by workflow, node, agent, model, provider, user and org, errors and retries, tools; the attribute contract (gen_ai.* plus forge.ai.*), emitting it with pkg/observe/genai, why AI spans are never sampled, and what cost it shows (only a gateway-reported one).Votes: 0GitHub stars: 10
- Actor PrivacyWho a server-side product event is about (observe.WithActor, opaque ids only), the no-personal-data rule for properties and its three enforcement points (observe.LooksLikePII, the ingest gateway's scrub, forgeconv-product-event-pii), and opt-out with observe.SetConsentSource (fails closed).Votes: 0GitHub stars: 10