AGENT SKILL

rust-embedded

Engineer and review no-std, firmware, interrupt, DMA, peripheral, allocator, panic, binary-size, timing, and hardware-targeted Rust. Use for embedded or target-constrained repositories. Do not claim hardware behavior from host-only compilation.

License 许可
Apache-2.0
所属仓库
RawSocketLabs/rsl
最近更新
2026-11-15
Stars
★ 2
Forks
0

01 前言 Front Matter

name
rust-embedded
description
Engineer and review no-std, firmware, interrupt, DMA, peripheral, allocator, panic, binary-size, timing, and hardware-targeted Rust. Use for embedded or target-constrained repositories. Do not claim hardware behavior from host-only compilation.

02 资源文件 3

03 SKILL.md 正文

Engineer Embedded Rust

Establish the target contract

  1. Read $rust-core, exact target triples and hardware revisions, linker and memory scripts, toolchain, no_std and allocation policy, HAL/PAC ownership, interrupt model, panic strategy, bootloader, flashing, and hardware CI.
  2. Read embedded contracts.
  3. Identify which behavior is target-independent, simulator-testable, architecture-specific, board-specific, timing-sensitive, or safety-critical.

Design

Keep core logic host-testable where possible. Make allocator and heap use, blocking, interrupt masking, critical sections, atomics, DMA buffer ownership, alignment, cache coherency, volatile access, peripheral state, power/reset, and panic behavior explicit. Avoid hidden std, runtime, filesystem, thread, or wall-clock assumptions.

Route API contracts to $rust-api-design, target features and dependencies to $rust-dependencies-security, interrupts and shared state to $rust-async-concurrency, unsafe register/ABI work to $rust-unsafe-ffi, measurement to $rust-performance, and evidence to $rust-testing.

Verify

Run host tests for portable logic and real target builds for every first-class configuration. Use emulator or hardware tests, interrupt/race tests, size and stack checks, timing measurements, and fault/panic/reset tests as required. Separate compiled, emulated, flashed, and observed-hardware evidence.

Output

Record capability contract, target matrix, allocation and panic policy, timing and size budgets, unsafe/interrupt boundaries, exact evidence, unavailable hardware, and residual risks.

04 同仓库更多 Skills

RawSocketLabs
RawSocketLabs/rsl

rust-unsafe-ffi

Design and review unsafe Rust, safe wrappers, manual Send or Sync, ABI boundaries, foreign ownership, callbacks, and FFI build integration. Use whenever unsafe code or a foreign interface is introduced, changed, or relied upon. Do not use unsafe merely to bypass borrow checking or for unmeasured optimization.

★ 2
RawSocketLabs
RawSocketLabs/rsl

rust-testing

Select, implement, and assess Rust unit, integration, documentation, property, fuzz, snapshot, concurrency, unsafe, protocol, benchmark, and verification evidence. Use whenever behavior changes or claims need proof. Do not run every tool mechanically when the repository or risk makes it inapplicable.

★ 2
RawSocketLabs
RawSocketLabs/rsl

rust-skill-maintenance

Maintain this modular Rust skills system, including canonical content, manifests, references, profiles, generated adapters, migrations, examples, evaluations, releases, and compatibility. Use when changing the skills repository itself. Do not hand-edit generated adapters.

★ 2
RawSocketLabs
RawSocketLabs/rsl

rust-review

Review Rust diffs, commits, branches, and designs for actionable correctness, soundness, security, compatibility, concurrency, protocol, performance, testing, and maintainability risks. Use for review or pre-merge assessment. Do not modify code unless separately requested.

★ 2
RawSocketLabs
RawSocketLabs/rsl

rust-repository-onboarding

Inspect, interview, profile, configure, and install the modular Rust engineering skills into a repository. Use when adopting or refreshing these skills, generating repository-specific Rust rules, or creating validation workflows. Never finalize policy before repository inspection and user approval.

★ 2
RawSocketLabs
RawSocketLabs/rsl

rust-protocol

Engineer and review binary protocols, wire formats, builders, encoders, parsers, framing, stateful messages, bit ordering, integrity, correction, malformed input, and conformance. Use for protocol or serializer code. Do not apply protocol rules to unrelated in-memory models.

★ 2