block

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.

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.

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).

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.

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.

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.

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.

Use when a shell command in this repo fails with "command not found" for `just`, `buf`, `golangci-lint`, `goimports`, `lefthook`, `ruff`, or any other developer tool. The repo pins its toolchain via Hermit (`.hermit/`); the tools exist on disk but only resolve after the Hermit environment is activated.

Write and publish blog posts for the block/goose open source project

Gas Town × DOK Framework - A two-dimensional model for analyzing AI collaboration maturity and cognitive complexity to reveal growth opportunities.

Use beads (bd) for persistent task tracking in coding projects. A git-backed issue tracker designed for AI agents with dependency graphs, hierarchical tasks, and multi-agent coordination.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Set up API integration with configuration and helper scripts

Comprehensive code review checklist for pull requests

Guidelines for writing effective tests in this project

Capture, validate, review, and evolve a repo-local Ghost fingerprint. Use when the user wants to capture a product fingerprint, update .ghost, brief work from accepted product-experience context, review drift, verify generated UI, compare fingerprints, or record accepted divergence.

Create, validate, recall, and evolve the repo-local Ghost fingerprint bundle. Use when the user wants to scan a product, create or update .ghost, write resources.yml/map.md/survey.json/patterns.yml/checks.yml/intent.md, validate optional decisions/proposals, derive patterns from survey evidence, brief work from the fingerprint, capture a proposal, or promote approved product-experience memory.

Use this skill to generate UI in the arcade design language (Cash Green (`#00D64F` / `#00BD46`) is reserved as accent and surface, never as the default fill of a primary button — `prominent.background = semantic.background.inverse`, so heroes are pure black/white., A "mono" appearance is a parallel reality: every brand reference has a `lightMono` / `darkMono` override that strips green to grey, generated as separate output (`colors-mono.ts`, `ArcadeColorMapping+LightMono.swift`) — accessibility/preference is a build target, not a runtime fork., Single typeface (`CashSans`, plus `CashSansMono` for micro-labels), carried by Square's CDN; every typography token also declares its `dynamic-type-style-uikit` and `dynamic-type-style-swiftui` mapping — type is bonded to platform a11y rails.). Contains the canonical fingerprint and token reference.

Use this skill to generate UI in the market design language (Monochromatic by default: `core.emphasis-fill` ships as `#101010` light / `#FFFFFF` dark even though the source aliases it to `core.blue-fill` — chromatic identity is opt-in via theme overlays, not a base-system trait., A full chromatic palette is defined and reserved: green / forest / teal / blue / sky / purple / pink / burgundy / red / orange / gold / yellow / taupe / brown each ship as a 6-step set (fill, text, 10, 20, 30, 40) but the base system only consumes them through semantic aliases (`success`, `warning`, `critical`, `emphasis`)., A 17-step grayscale ramp from `#FFFFFF` to `#000000` (with a separate `core.constant.gray-*` track) carries most of the visual weight — surfaces, dividers, fills, and text are all neutrals first.). Contains the canonical fingerprint and token reference.

Reason about a fleet of design systems — pairwise distances, cohorts, tracks-graph, world-shape narrative. Use when the user has a directory of (map.md, fingerprint.md) members and wants to understand how they relate, where they cluster, who declares whom as reference, or how the fleet's shape should be summarized for design system leadership. Triggers on phrases like "what does our design world look like", "compare these systems as a fleet", "where do our apps cluster", "who tracks whom", "summarize the fleet", "fleet view", or whenever a `fleet/` directory with member subdirectories is being explored.

Analyzes branch changes to find edge cases, error states, and untested user flow paths in UI code. Use when the user says "find edge cases", "what am I missing", "edge cases", "test my flows", "what could go wrong", or wants to harden a feature before shipping.

Create app e2e tests for the Goose desktop app using the Tauri app test driver. Use when the user wants to generate, write, or verify UI tests that run against the live app.

Senior engineer code review focused on catching issues before they become PR comments. Reviews only changed lines, categorizes issues by priority, and fixes them one by one. Use when the user says "code review", "review my code", "review this branch", or wants pre-PR feedback.

Create a GitHub PR from the current branch: handle uncommitted changes, generate a summary, and submit via gh CLI. Use when the user says "create PR", "open PR", "submit PR", "push PR", or wants to create a pull request.

Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable `.trail.yaml` files as the artifact. Trigger on mentions of Trailblaze, the `trailblaze` CLI, `.trail.yaml` files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on iOS / Android / web — including authoring a custom typed scripted tool, composing an agent's tool surface, or writing a trailmap.

Use when validating or evaluating Trailblaze's out-of-box (OOB) user experience — does what the `trailblaze` skill claims actually match the real installed CLI? Triggers on requests to "validate the Trailblaze skill", "test the Trailblaze OOB experience", "evaluate Trailblaze UX", "check if the skill matches the CLI", "audit the Trailblaze CLI for new-user friction", or running an OOB regression check after the framework changes.

Write or update a devlog entry in the devlog directory. Use when the user asks to write a devlog, record a decision, document what happened, or says "write up what we did".

Requirements-driven development framework. Use when setting up product/engineering requirements documents, checking traceability between requirements and code, verifying document consistency, or working on code in a repo that contains ANCHORS.md files (load the skill to understand the requirements context before making changes).

Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

Monitor and respond to penpal document review comments on markdown files in thoughts/ directories.

Our preferred stars for celestial navigation and astronomical reference

Debugging guidelines and best practices

Prepare and trigger QRGo releases. Use when the user asks to release QRGo, bump the app version, create a patch/minor/major release, trigger release CI, or publish the formula/cask.

Perform an QRGo self review or audit of current changes. Use when the user asks for a self review, audit, review of uncommitted changes, or a final quality pass before commit/PR in the QRGo repo.

Requirements-driven development framework. Use when setting up product/engineering requirements documents, checking traceability between requirements and code, verifying document consistency, or working on code in a repo that contains ANCHORS.md files (load the skill to understand the requirements context before making changes).

Requirements-driven development framework. Use when setting up product/engineering requirements documents, checking traceability between requirements and code, verifying document consistency, or working on code in a repo that contains ANCHORS.md files (load the skill to understand the requirements context before making changes).

Search GitHub issues, PRs, and code using the gh CLI.

Compare and diff files, directories, builds, releases, archives, or binaries. Use when the user wants to compare two versions of something, diff two directories or files, analyze what changed between builds or releases, or examine differences in .ipa, .apk, .aar, .jar, .tar.gz, .tar.bz2, Mach-O binaries, plists, or text files.

Publish the coplan-engine gem to RubyGems. Use when releasing a new version, publishing the gem, or bumping the version.