db-generation-hygiene

Name: Db Generation Hygiene
Author: block

// Use when editing `server/sqlc/queries/**/*.sql`, `server/sqlc.yaml`, or creating a new `server/migrations/*.sql` file. sqlc query and schema source changes require running `just gen` so `server/generated/sqlc/` stays in sync. Edits to *existing* migration files are owned by the `migration-immutability` skill instead.

تشغيل في Manus

$ git log --oneline --stat

stars:٣٠

forks:٧

updated:٣٠ أبريل ٢٠٢٦ في ١٧:٠٧

SKILL.md

readonly

name	db-generation-hygiene
description	Use when editing `server/sqlc/queries/*/.sql`, `server/sqlc.yaml`, or creating a new `server/migrations/.sql` file. sqlc query and schema source changes require running `just gen` so `server/generated/sqlc/` stays in sync. Edits to existing* migration files are owned by the `migration-immutability` skill instead.

db-generation-hygiene

Server DB access goes through sqlc-generated bindings. Source of truth is split between migrations (server/migrations/) and queries (server/sqlc/queries/); generated Go lives under server/generated/sqlc/.

What to do

After the SQL edit is complete, run just gen from the repo root.
Confirm the expected diff lands under server/generated/sqlc/. If unrelated generated files change, the branch was already stale before this edit — call that out.
Commit SQL source and generated output together.

What to avoid

Do not hand-edit server/generated/sqlc/.

related-skills.json

نفس المستودع

asicrs-build.md

from "block/proto-fleet"

Use when editing files under `plugin/asicrs/`, `sdk/rust/`, or `server/sdk/v1/pb/` (which the asicrs build also consumes). The ASIC-rs plugin is a Rust binary built via Docker and cached against an `.asicrs-platform` marker; source changes that bypass `just _asicrs-build` or `just rebuild-plugin asicrs` will leave the loaded plugin stale.

2026-04-3030

buf-version-pinning.md

from "block/proto-fleet"

Use when editing `buf.yaml`, `buf.lock`, or any `buf.gen.yaml` (root, server, or SDK). Generator plugin versions in `buf.gen.yaml` are tightly coupled to the generated code consumers (Connect-RPC client, sqlc, SDK shapes); a version bump can produce a large unrelated diff and break downstream code that relies on specific output shapes.

2026-04-3030

client-boundaries.md

from "block/proto-fleet"

Use when editing files under `client/src/shared/`, `client/src/protoOS/`, or `client/src/protoFleet/`. Enforces app-import boundaries (`shared/` cannot import apps; `protoOS` and `protoFleet` cannot import each other) and the no-new-`console.log` rule (`console.error` and the existing build-version logger are fine).

2026-04-3030

docker-compose-dev.md

from "block/proto-fleet"

Use when editing `server/docker-compose.yaml` or `server/docker-compose.base.yaml`, or when troubleshooting a `just dev` startup. Proto Fleet requires Docker host networking on macOS/Windows; service definitions split between `base` (shared) and the runtime override file.

2026-04-3030

fake-rig-fixtures.md

from "block/proto-fleet"

Use when editing `server/fake-antminer/` or `server/fake-proto-rig/`. These are test doubles consumed by `tests/plugin-contract/`, the E2E suites, and the local `just dev` stack — behavior changes here ripple silently into all three surfaces.

2026-04-3030

go-work-sync.md

from "block/proto-fleet"

Use when editing any `go.mod` or `go.sum` under `server/`, `plugin/`, or `tests/`, or when modifying root `go.work` / `go.work.sum`. Module dependency changes require running `go work sync` from the repo root so workspace lock data stays consistent.

2026-04-3030

package.json