skills.rest
ZanzyTHEbar
ZanzyTHEbarCOMMUNITY
Explore all skills by this author →
𝕏@ZacariahHeimGitHub

systems-engineering

Applies deterministic engineering guidance to embedded, firmware, RTOS, and low-level code work.

3|Updated Apr 8, 2025
Search Tags:#code review#concurrency#rust#firmware#embedded#c#rtos
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill systems-engineering-zanzythebar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systems-engineering
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/systems-engineering
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill systems-engineering-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Low-level development in C, C++, Rust, Zig, assembly, and RTOS environments carries risks like undefined behavior, race conditions, timing violations, and irreversible device operations that generic coding advice fails to address. ## Core Features & Use Cases - Constraint Inspection: Prompts review of hardware, OS/RTOS, memory, timing, concurrency, toolchain, and deployment constraints before changing code. - Risk Classification: Treats safety, data loss, undefined behavior, races, and irreversible device operations as high-risk areas requiring explicit handling. - Validation Guidance: Directs verification through the closest executable check, such as unit tests, hardware-in-loop tests, simulators, static analysis, or build checks. - Use Case: When modifying an interrupt handler in a firmware project, use this Skill to surface shared-state ownership, synchronization assumptions, and failure modes before editing. ## Quick Start Ask the assistant to review your embedded C or Rust code for concurrency, memory, and timing risks using the systems-engineering skill.

Frequently Asked Questions about systems-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review embedded C code for concurrency bugs?▼

Review embedded C code by identifying shared state, ownership, and synchronization assumptions across interrupts and tasks. This Skill prompts explicit statements of interrupt behavior and failure modes before any code change.

What should I check before modifying firmware or RTOS code?▼

Check hardware constraints, RTOS behavior, memory layout, timing requirements, toolchain versions, and deployment conditions. The Skill guides inspection of these factors and prefers deterministic behavior over clever abstractions.

Does this Skill support Rust and Zig systems programming?▼

Yes, the Skill covers Rust, Zig, C, C++, assembly, and low-level Go. It applies the same constraint inspection and risk validation approach regardless of language.

How are high-risk device operations validated?▼

High-risk operations like irreversible device actions are validated with the closest executable check available, such as hardware-in-loop tests, simulators, emulators, static analysis, or documented manual verification.

When should I not use a systems engineering review approach?▼

This approach is unnecessary for high-level application code without hardware, timing, memory, or concurrency constraints. It is designed specifically for low-level work where such constraints affect correctness.

Related Skills

Explore More Software Engineering Skills→
FernanSuozaFernanSuoza

embedded-code-development

Implement deterministic embedded firmware changes with explicit resource handling and unit tests.

Community
Advanced
openharmonyinsightopenharmonyinsight
31

openharmony-ut

Automate OpenHarmony unit and fuzz test generation, build, deploy, and execution via hdc.

Official
Advanced
bitwisecookbitwisecook
59

irule-review

Review Tcl iRules for security, taint, and thread safety vulnerabilities.

Community
Advanced
adzerkadzerk
15

tlaplus-more

Write and verify TLA+ and PlusCal specifications with TLC model checking.

Official
Advanced