asicrs-build
- Repo stars 28
- License Apache-2.0
- Author updated Live
- Author repo proto-fleet
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @block · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Linux · Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: asicrs-build
description: Use when editing files under `plugin/asicrs/`, `sdk/rust/`, or `server/sdk/v1/pb/` (which the as…
category: engineering
runtime: Docker
---
# asicrs-build output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “What to do / What to avoid” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “What to do / What to avoid” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “What to do / What to avoid”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: asicrs-build
description: Use when editing files under `plugin/asicrs/`, `sdk/rust/`, or `server/sdk/v1/pb/` (which the as…
category: engineering
source: block/proto-fleet
---
# asicrs-build
## When to use
- Use when editing files under `plugin/asicrs/`, `sdk/rust/`, or `server/sdk/v1/pb/` (which the asicrs build also consum…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “What to do / What to avoid” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "asicrs-build" {
input -> user goal + target files + boundaries + acceptance criteria
context -> What to do / What to avoid
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}asicrs-build
just build-plugins and just test-contract rebuild ASIC-rs only when its
freshness check (mtime against the BIN plus a find -newer over
plugin/asicrs sdk/rust server/sdk/v1/pb) trips. That check is robust for
typical edits but skips when the binary mtime is newer than the source —
which is true after a clean checkout or when switching branches.
What to do
- After editing any source under
plugin/asicrs/,sdk/rust/, orserver/sdk/v1/pb/, force a rebuild:- Local development:
just rebuild-plugin asicrs - Docker dev runtime (Linux ARM64): same command — it sets
_asicrs-build-dockerafter removing the platform marker.
- Local development:
- Run
just test-contractif the change affects miner-driver behavior. - If switching between native and Docker runtimes, expect a full rebuild
the first time — the
.asicrs-platformmarker is what disambiguates.
What to avoid
- Don't hand-edit
server/plugins/asicrs-config.yamlto make tests pass — the contract harness rewrites it per suite, and your edits will be overwritten.
Decide Fit First
plugin/asicrs/,sdk/rust/, orserver/sdk/v1/pb/(which the asicrs build also consumes). The A…Design Intent
How To Use It
Boundaries And Review