c-cpp-dev
Use when writing, reviewing, or refactoring C/C++ code, especially on 32-bit ARM embedded targets. NOT for formatting-only changes, simple file reads, non-embedded C/C++ (desktop/server), or C#/Java despite the 'C' in the name.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when writing, reviewing, or refactoring C/C++ code, especially on 32-bit ARM embedded targets. NOT for formatting-only changes, simple file reads, non-embedded C/C++ (desktop/server), or C#/Java despite the 'C' in the name.
Use when debugging embedded firmware issues — analyzing crash logs, investigating state machine lockups, tracing sensor/signal anomalies, or performing structured root-cause analysis after a crash has been located. For fault-register and stack-frame triage, load hardfault-triage
Use when writing or reviewing embedded C firmware, FreeRTOS tasks, ISR handlers, NVM/flash storage, or sensor driver state machines. NOT for documentation-only RTOS references, conceptual RTOS discussions, or bare-metal projects without an RTOS or sensor subsystem.
Use when reviewing design documents, architecture specs, technical proposals, or plans that make claims about API names, file paths, enum values, counts, or mechanism feasibility — a lightweight claim-by-claim check against the codebase with evidence. Built into embedded-workbenc
Use when triaging processor exception crashes — HardFault, MemManage, BusFault, UsageFault, data/prefetch abort, illegal instruction, or watchdog timeout. Covers fault-register interpretation, stack-frame extraction, PC-to-source resolution, and root-cause classification.
Use when building, flashing, or packaging firmware with Keil MDK (UV4 CLI, ARMCLANG), analyzing .map files for ROM/RAM optimization and memory budget, or diagnosing Keil-specific build failures. NOT for non-Keil build systems (Makefile, CMake, IAR, GCC-only). For crash triage see
Use when reviewing or fixing async protocols, retries, ACK/NACK handling, pending flags, timeout logic, or state-machine lockups in embedded firmware. NOT for generic network protocol design (TCP/HTTP/MQTT) unless targeting embedded firmware stack.
Turn project work into personalized, channel-specific publication packages and deliver reviewed posts through Buffer API. Use for preparing product demos, adapting project artifacts for social channels, or publishing an approved package.
Reads industry structure with Porter's Five Forces and profiles rivals on capability and cost, giving a clear view of who you compete with and how attractive the industry really is.
Decomposes cost changes into volume, rate, and mix effects to identify the true root cause of cost escalation or decline.
Builds an answer-first plan by stating disprovable hypotheses and, for each, the "what would prove me wrong" test and the exact analysis that settles it, so the team tests instead of boiling the ocean.
Turns raw findings into ranked insights by laddering each finding up the so-what chain from observation to implication to the action it demands.
Decomposes one big question into a MECE issue tree or hypothesis tree of testable sub-questions, with branches ranked by impact so the team analyzes what matters first.
Prepares for a hostile room by pre-morteming the pushback, surfacing the hardest questions your recommendation will face, and drafting a tight, evidence-backed answer to each.
Turns a vague symptom or an over-broad brief into a one-page SCQA problem statement and a single decision-shaped key question the work must answer.
Maps a core process end to end with Lean value-stream analysis and redesigns it to remove waste and fix broken handoffs.
Catalog captured:2026-11-21