Skill UI

A specialized skill for writing highly efficient, memory-safe, and robust C code. This guide focuses on best practices for systems programming, including rigorous memory management (malloc/free), advanced pointer arithmetic, POSIX compliance, multi-threading (pthreads), and embedded systems constraints. It emphasizes using static analysis tools, implementing comprehensive error handling, and ensuring performance through proper profiling. Ideal for complex, low-level system tasks.

Guides engineers through initializing MCUs, crafting RTOS-aware drivers, and tuning power/timing for STM32, ESP32, and bare-metal targets; covers constraint analysis, interrupt safety, resource tracking, and validation with static analysis and real-time debugging.

A comprehensive guide detailing advanced offensive fuzzing methodologies. It covers the full lifecycle from target identification (parsers, network protocols, kernels) to tool selection (AFL++, libFuzzer, Honggfuzz, syzkaller), building harnesses, curating seed corpora, executing fuzz campaigns, and finally, performing crash triage and vulnerability analysis. Essential for security researchers and embedded systems developers.

This toolset provides a comprehensive development workflow for iterating on MicroPython applications (such as Claude Buddy, Hello, and Snake) on the Cardputer-Adv device. It allows developers to add new apps, push single updated .py files without full re-flashing, monitor device serial logs, or execute one-shot REPL commands directly from the host machine. Essential for rapid prototyping and debugging embedded systems.

A comprehensive guide for bringing RuView CSI sensing nodes (ESP32-S3/C6) online. This skill covers the full lifecycle: building the embedded firmware, flashing the device, provisioning WiFi credentials, and confirming the Continuous Sensing Image (CSI) data stream. Essential for physical hardware deployment and debugging of complex sensing systems.

A comprehensive guide detailing the required structure and technical rigor for writing papers in sensing and embedded systems (SenSys). It mandates replacing vague adjectives with concrete, measured metrics (e.g., energy in joules, latency in milliseconds) and structuring the argument around a clear 'pain $\to$ gap $\to$ mechanism $\to$ measured behavior' arc on the first page. Essential for academic researchers and engineers.