DOCA Common
Examples
- "Tasks submit but nothing completes." — start at the progress
engine and ctx lifecycle, not a per-library rewrite.
- "DOCA_ERROR_BAD_STATE from doca_ctx_start." — walk the Common
lifecycle order before blaming Flow or RDMA.
Instructions
Follow Loading order below. Open the tasks companion for configure /
build / run. Open the capabilities companion for ctx / buf / pe /
log. Do not open every companion file.
Where to start: This skill is the foundation every DOCA app
loads first — before doca-flow, doca-rdma, doca-eth, doca-comch, or
any other higher-level library. Every doca_<library>_* context is
built on top of doca_ctx, every device handle is a doca_dev
discovered through doca_devinfo, every zero-copy buffer is a
doca_buf from a doca_buf_inventory over a doca_mmap, every
task completion drains through a doca_pe, and every log line emits
through doca_log. Open the capabilities companion when
the question is what does Common express on this install; open
the tasks companion when the user wants to do something
(configure / build / modify / run / test / debug). If the user has
not installed DOCA yet, route to
doca-setup/SKILL.md first. If the user is
already past the foundation and asking a library-specific question
(e.g. "how do I program a Flow pipe"), load the matching per-library
skill alongside this one — they cross-link back here for the shared
primitives.
Example questions this skill answers well
The CLASSES of doca-common questions this skill is built to answer,
each with one worked example. The agent should treat the class as
the load-bearing piece — the worked example is a single instance.
- "What is the doca-common foundation I have to set up BEFORE I
open a doca-flow / doca-rdma / doca-eth / … context?" — worked
example: "I'm starting a brand-new DOCA Flow program on
BlueField-3; what's the doca-common skeleton I need before I open
the Flow port?". Answered by the universal foundation walk in
configure +
ctx +
dev +
progress engine.
- "How do I discover a device and gate on its capabilities before
trusting the public docs?" — worked example: "I want to use
doca_eth_txq but the docs hint at a feature only on certain
firmware bands". Answered by the capability-discovery rule
(doca_devinfo_create_list → doca_*_cap_* against the active
doca_devinfo is the runtime authority) indev +
use.
- "What's the doca_buf / doca_mmap / doca_buf_inventory wiring
for zero-copy I/O, and what's the lifecycle order?" — worked
example: "I want to register a user-space buffer with my device,
carve it into N data-plane buffers, and reference-count them
across multiple DOCA libraries". Answered by the zero-copy
buffer model in
buf +
the buffer-lifecycle walk inconfigure +
use.
- "How does the progress engine work and where do I have to call
it?" — worked example: "my doca_rdma task submits cleanly but
nothing completes — what loop am I missing?". Answered by the PE
surface in
progress engine
- the run-loop pattern in ## run.
- "Why don't my DOCA log lines appear at the level I expect, and
what's the difference between
--sdk-log-level and the app-side
setter?" — worked example: "I set --sdk-log-level 60 (DEBUG), my
own DOCA_LOG_DBG lines still don't print". Answered by the
two-tier log model in ## log
- the tier-flip iteration in ## log.
- "What does this
DOCA_ERROR_* from a doca_buf_* / doca_ctx_*
/ doca_dev_* / doca_pe_* / doca_log_* call mean?" —
worked example: "DOCA_ERROR_BAD_STATE from doca_ctx_start".
Answered by the Common overlay on the cross-library DOCA_ERROR_*
taxonomy inError taxonomy
debug that escalates to
doca-debug/SKILL.md.
Audience
This skill serves every external developer building applications
that consume any DOCA library — i.e., users whose code calls any
doca_* symbol (directly in C/C++, or through FFI/bindings from
another language). Whether the user's primary library is doca-flow,
doca-rdma, doca-eth, doca-comch, doca-dma, doca-rmax, doca-sha,
doca-aes-gcm, doca-erasure-coding, or any other, the doca-common
surface is under it and the user will hit doca_buf, doca_ctx,
doca_dev, doca_pe, and doca_log as part of the first-app
journey. It is not for NVIDIA developers contributing to DOCA
Common itself.
Language scope
DOCA Common ships as a C library with pkg-config module name
doca-common. The shipped samples that demonstrate Common primitives
live inside every per-library samples tree (any
/opt/mellanox/doca/samples/<library>/<sample>/*_main.c is a worked
example of the universal foundation — doca_devinfo_create_list
→ doca_dev_open → per-library doca_ctx create → doca_pe_create
→ doca_pe_connect_ctx → doca_ctx_start → submit work → drive
doca_pe_progress → drain completions → doca_ctx_stop → destroy).
C and C++ consumers are the canonical case and the worked examples
in the tasks companion assume that path. Other-language consumers (Rust, Go,
Python, …) consume the same *.so through FFI or language-specific
bindings; the skill's contribution in that case is to keep the
universal foundation walk, the lifecycle, the capability-discovery
rule, the PE-drives-completion rule, and the two-tier log model
language-neutral, and to route the agent to the public C ABI as the
authoritative surface that any wrapper will eventually call.
When to load this skill
Load this skill whenever the user is doing any hands-on DOCA
work — it is the foundation. Concretely:
- Setting up the universal DOCA-side skeleton before opening any
per-library context (Flow, RDMA, Eth, Comch, DMA, Rmax, …).
- Discovering devices and representors and gating capability use
on the active
doca_devinfo via the doca_*_cap_* family.
- Wiring
doca_mmap + doca_buf_inventory + doca_buf for
zero-copy I/O that crosses libraries (e.g. doca-eth feeds
doca-dma feeds doca-rdma — they share the same buf surface).
- Driving the progress engine (
doca_pe_create /
doca_pe_connect_ctx / doca_pe_progress) — the universal
task-completion drain every DOCA Core context relies on.
- Wiring DOCA Log into a fresh app or modifying a shipped sample to
add the user's own per-component log lines via the two-tier
(
--sdk-log-level vs app-side registry) model.
- Debugging a
DOCA_ERROR_* returned from any doca_buf_* /
doca_ctx_* / doca_dev_* / doca_pe_* / doca_log_* call —
the Common surface is where most lifecycle / capability /
permission errors first surface for higher-level libraries.
- Designing or extending non-C bindings (Rust, Go, Python, …) that
wrap any DOCA library — for the universal foundation surface
(buf, ctx, dev, pe, log) the wrapper has to expose first.
Do not load this skill for library-specific Flow, RDMA, Eth,
Comch, DMA, Rmax, … questions in isolation — load the matching
per-library skill alongside this one. Do not load this skill for
general DOCA orientation, install of DOCA itself, or
"where do I find docs". For those, use
doca-public-knowledge-map/SKILL.md
or doca-setup/SKILL.md.
What this skill provides
This is a thin loader. The body keeps only the orientation
needed to pick the right next file. The substantive Common material
lives in two companion files:
- the capabilities companion — what doca-common expresses on this install:
the
## Capabilities and modes overview of the universal
primitives every DOCA application touches; the five subsystem
H2s (## log, ## buf, ## ctx, ## dev, ## progress engine) that own the per-primitive surface; the
## Version compatibility doca-common-specific overlay;
the ## Error taxonomy Common-side view of the universal
DOCA_ERROR_* set; the ## Observability surface (logs, PE
events, capability snapshots); and the ## Safety policy overlay
on the bundle-wide hardware-safety meta-policy.
- the tasks companion — step-by-step workflows for the universal verbs
(
configure, build, modify, run, test, debug, use)
PLUS a ## log verb-side that covers the two-tier log model in
workflow form. Plus a Deferred task verbs block that points
install / deploy / rollback questions at the right next skill.
The skill assumes a host or BlueField where DOCA is already
installed at the standard location and the user has the privileges
their public install profile expects. It does not cover installing
DOCA — that path goes through
doca-setup/SKILL.md.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or templates
bundle. To keep the boundary clean, it deliberately does not
contain — and pull requests should not add:
- Pre-written DOCA application source code, in any language.
The verified Common usage shows up inside every shipped DOCA
sample at
/opt/mellanox/doca/samples/<library>/<sample>/*_main.c
and inside every shipped reference application. The agent's job
is to route the user to those files and prescribe a minimum-diff
modification on them via the universal modify-a-sample workflow
in
doca-programming-guide/SKILL.md.
- Standalone build manifests (
meson.build,
CMakeLists.txt, Cargo.toml, setup.py, go.mod, …) parked
inside the skill. The agent constructs the build manifest in
the user's project directory against the user's installed DOCA,
where pkg-config --modversion doca-common is the source of
truth.
- A
samples/, bindings/, or reference/ subtree of any
kind. A mock or incomplete artifact in this skill's tree, even
one labeled "reference", is misleading: users will read it as
buildable.
Loading order
- Read this skill first to confirm the user's question is in
scope.
- For the universal primitives (
log / buf / ctx / dev /
progress engine), the pkg-config --modversion doca-common
anchor, the Common error overlay, observability, and safety
policy, see the capabilities companion.
- For step-by-step workflows — configure, build, modify, run,
test, debug, use, log — see the tasks companion.
Both companion files cross-link to each other,
doca-version/SKILL.md for the canonical
version-handling rules,
doca-programming-guide/SKILL.md
for the universal modify-a-shipped-sample workflow and the
cross-library DOCA_ERROR_* taxonomy,
doca-debug/SKILL.md for the cross-cutting
debug ladder, and
doca-public-knowledge-map/SKILL.md
whenever the right answer is "look it up in the public docs or the
installed package layout" rather than "Common-specific guidance".
Related skills
doca-public-knowledge-map/SKILL.md —
the routing table for every public DOCA documentation source and
the on-disk layout of an installed DOCA package. Always available
alongside this skill; this skill expects to be able to defer
documentation-finding and install-layout questions there instead
of duplicating them.
doca-setup/SKILL.md — env preparation,
install verification, and the I have no install yet path with
the public NGC DOCA container (nvcr.io/nvidia/doca/doca) as the
universal Stage-1 fallback. This skill assumes its preconditions
are satisfied.
doca-version/SKILL.md — canonical DOCA
version-handling rules (four-way match, NGC semantics,
headers-win-over-docs). pkg-config --modversion doca-common is
the build-time anchor every DOCA install carries; this skill's
## Version compatibility overlays the Common-specific notes on
top.
doca-programming-guide/SKILL.md —
general DOCA programming patterns shared by every library: the
canonical pkg-config + meson build pattern, the universal
modify-a-shipped-sample first-app workflow, the universal
lifecycle, the cross-library DOCA_ERROR_* taxonomy, and the
program-side debug order. This skill is the primitives layer
the programming-guide patterns rest on.
doca-debug/SKILL.md — the cross-cutting
debug ladder (install / version / build / link / runtime /
program / driver) and the verbosity-escalation surface. DOCA Log
is the foundation doca-debug builds its runtime-debug story on;
this skill is where the two-tier log model and the universal
lifecycle errors first surface, and doca-debug cross-links here
for both.
doca-structured-tools-contract/SKILL.md —
the bundle's structured-tools precedence rule (detect / prefer /
fall back / report). The Command appendix in
the tasks companion honors this contract.
doca-hardware-safety/SKILL.md —
the cross-cutting hardware-safety meta-policy this skill's
## Safety policy overlays.
- Per-library skills (
doca-flow, doca-rdma, doca-eth,
doca-comch, doca-dma, doca-rmax, doca-sha, doca-aes-gcm,
doca-erasure-coding, doca-compress, doca-dpa, doca-gpunetio,
doca-pcc, doca-sta, doca-telemetry, doca-urom,
doca-verbs, doca-argp, doca-devemu,
doca-dpdk-bridge, …) — every per-library skill cross-links
back to this skill for the foundation primitives. Loading this
skill alongside any of them is the recommended default.
1---2license: Apache-2.03name: doca-common4description: >5 Use this skill whenever the user is doing hands-on DOCA programming on6 a BlueField DPU or ConnectX NIC and needs the foundation primitives7 every per-library context rests on — walking the doca_ctx lifecycle,8 discovering doca_dev / doca_devinfo and gating on doca_*_cap_* before9 trusting a feature, wiring doca_mmap / doca_buf_inventory / doca_buf10 for zero-copy I/O across libraries, driving doca_pe for completions,11 or DOCA Log's two-tier (--sdk-log-level vs app-side) model. Trigger12 even when the user does not say "DOCA Common" — typical implicit13 phrasings include "my tasks submit but nothing completes",14 "DOCA_ERROR_BAD_STATE from doca_ctx_start", "--sdk-log-level does15 nothing for my DOCA_LOG_DBG lines", "share a buf between doca_dma and16 doca_rdma", or "crashes far from the offending line". Refuse and route17 elsewhere for per-library questions in isolation (load doca-flow /18 doca-rdma / doca-eth alongside), installing DOCA (doca-setup), or doc19 lookup (doca-public-knowledge-map).20metadata:21 source: https://skillmd.com/skills/nvidia/doca-common22 author: NVIDIA <doca-feedback@nvidia.com>23 kind: library24 doca_version: "3.5"25 tags:26 - doca27 - common28 - core29compatibility: >30 Requires DOCA SDK installed at /opt/mellanox/doca on Linux (Ubuntu31 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC32 attached. doca-common is present on every healthy DOCA install;33 reads the user's local install via `pkg-config --modversion34 doca-common` and inspects /opt/mellanox/doca/{lib,include,samples,applications}.35 The validation steps require a live DOCA install.36---3738# DOCA Common3940## Examples4142- **"Tasks submit but nothing completes."** — start at the progress43 engine and ctx lifecycle, not a per-library rewrite.44- **"DOCA_ERROR_BAD_STATE from doca_ctx_start."** — walk the Common45 lifecycle order before blaming Flow or RDMA.4647## Instructions4849Follow Loading order below. Open the tasks companion for configure /50build / run. Open the capabilities companion for ctx / buf / pe /51log. Do not open every companion file.5253**Where to start:** This skill is the **foundation every DOCA app54loads first** — before doca-flow, doca-rdma, doca-eth, doca-comch, or55any other higher-level library. Every `doca_<library>_*` context is56built on top of `doca_ctx`, every device handle is a `doca_dev`57discovered through `doca_devinfo`, every zero-copy buffer is a58`doca_buf` from a `doca_buf_inventory` over a `doca_mmap`, every59task completion drains through a `doca_pe`, and every log line emits60through `doca_log`. Open the capabilities companion when61the question is *what does Common express* on this install; open62the tasks companion when the user wants to *do* something63(configure / build / modify / run / test / debug). If the user has64not installed DOCA yet, route to65`doca-setup/SKILL.md` first. If the user is66already past the foundation and asking a library-specific question67(e.g. *"how do I program a Flow pipe"*), load the matching per-library68skill alongside this one — they cross-link back here for the shared69primitives.7071## Example questions this skill answers well7273The CLASSES of doca-common questions this skill is built to answer,74each with one worked example. The agent should treat the *class* as75the load-bearing piece — the worked example is a single instance.7677- **"What is the doca-common foundation I have to set up BEFORE I78 open a doca-flow / doca-rdma / doca-eth / … context?"** — worked79 example: *"I'm starting a brand-new DOCA Flow program on80 BlueField-3; what's the doca-common skeleton I need before I open81 the Flow port?"*. Answered by the universal foundation walk in82 ## configure +83 ## ctx +84 ## dev +85 ## progress engine.86- **"How do I discover a device and gate on its capabilities before87 trusting the public docs?"** — worked example: *"I want to use88 `doca_eth_txq` but the docs hint at a feature only on certain89 firmware bands"*. Answered by the capability-discovery rule90 (`doca_devinfo_create_list` → `doca_*_cap_*` against the active91 `doca_devinfo` is the runtime authority) in92 ## dev +93 ## use.94- **"What's the doca_buf / doca_mmap / doca_buf_inventory wiring95 for zero-copy I/O, and what's the lifecycle order?"** — worked96 example: *"I want to register a user-space buffer with my device,97 carve it into N data-plane buffers, and reference-count them98 across multiple DOCA libraries"*. Answered by the zero-copy99 buffer model in100 ## buf +101 the buffer-lifecycle walk in102 ## configure +103 ## use.104- **"How does the progress engine work and where do I have to call105 it?"** — worked example: *"my doca_rdma task submits cleanly but106 nothing completes — what loop am I missing?"*. Answered by the PE107 surface in108 ## progress engine109 + the run-loop pattern in ## run.110- **"Why don't my DOCA log lines appear at the level I expect, and111 what's the difference between `--sdk-log-level` and the app-side112 setter?"** — worked example: *"I set `--sdk-log-level 60` (DEBUG), my113 own `DOCA_LOG_DBG` lines still don't print"*. Answered by the114 two-tier log model in ## log115 + the tier-flip iteration in ## log.116- **"What does this `DOCA_ERROR_*` from a `doca_buf_*` / `doca_ctx_*`117 / `doca_dev_*` / `doca_pe_*` / `doca_log_*` call mean?"** —118 worked example: *"`DOCA_ERROR_BAD_STATE` from `doca_ctx_start`"*.119 Answered by the Common overlay on the cross-library `DOCA_ERROR_*`120 taxonomy in121 ## Error taxonomy122 + the layered ladder in123 ## debug that escalates to124 `doca-debug/SKILL.md`.125126## Audience127128This skill serves **every external developer building applications129that consume any DOCA library** — i.e., users whose code calls *any*130`doca_*` symbol (directly in C/C++, or through FFI/bindings from131another language). Whether the user's primary library is doca-flow,132doca-rdma, doca-eth, doca-comch, doca-dma, doca-rmax, doca-sha,133doca-aes-gcm, doca-erasure-coding, or any other, the doca-common134surface is *under* it and the user will hit `doca_buf`, `doca_ctx`,135`doca_dev`, `doca_pe`, and `doca_log` as part of the first-app136journey. It is *not* for NVIDIA developers contributing to DOCA137Common itself.138139## Language scope140141DOCA Common ships as a C library with `pkg-config` module name142`doca-common`. The shipped samples that demonstrate Common primitives143live *inside* every per-library samples tree (any144`/opt/mellanox/doca/samples/<library>/<sample>/*_main.c` is a worked145example of the universal foundation — `doca_devinfo_create_list`146→ `doca_dev_open` → per-library `doca_ctx` create → `doca_pe_create`147→ `doca_pe_connect_ctx` → `doca_ctx_start` → submit work → drive148`doca_pe_progress` → drain completions → `doca_ctx_stop` → destroy).149C and C++ consumers are the canonical case and the worked examples150in the tasks companion assume that path. Other-language consumers (Rust, Go,151Python, …) consume the same `*.so` through FFI or language-specific152bindings; the skill's contribution in that case is to keep the153universal foundation walk, the lifecycle, the capability-discovery154rule, the PE-drives-completion rule, and the two-tier log model155language-neutral, and to route the agent to the public C ABI as the156authoritative surface that any wrapper will eventually call.157158## When to load this skill159160Load this skill whenever the user is doing **any** hands-on DOCA161work — it is the foundation. Concretely:162163- Setting up the universal DOCA-side skeleton before opening any164 per-library context (Flow, RDMA, Eth, Comch, DMA, Rmax, …).165- Discovering devices and representors and gating capability use166 on the active `doca_devinfo` via the `doca_*_cap_*` family.167- Wiring `doca_mmap` + `doca_buf_inventory` + `doca_buf` for168 zero-copy I/O that crosses libraries (e.g. doca-eth feeds169 doca-dma feeds doca-rdma — they share the same buf surface).170- Driving the progress engine (`doca_pe_create` /171 `doca_pe_connect_ctx` / `doca_pe_progress`) — the universal172 task-completion drain every DOCA Core context relies on.173- Wiring DOCA Log into a fresh app or modifying a shipped sample to174 add the user's own per-component log lines via the two-tier175 (`--sdk-log-level` vs app-side registry) model.176- Debugging a `DOCA_ERROR_*` returned from any `doca_buf_*` /177 `doca_ctx_*` / `doca_dev_*` / `doca_pe_*` / `doca_log_*` call —178 the Common surface is where most lifecycle / capability /179 permission errors first surface for higher-level libraries.180- Designing or extending non-C bindings (Rust, Go, Python, …) that181 wrap any DOCA library — for the universal foundation surface182 (buf, ctx, dev, pe, log) the wrapper has to expose first.183184Do **not** load this skill for library-specific Flow, RDMA, Eth,185Comch, DMA, Rmax, … questions in isolation — load the matching186per-library skill alongside this one. Do **not** load this skill for187general DOCA orientation, install of DOCA itself, or188*"where do I find docs"*. For those, use189`doca-public-knowledge-map/SKILL.md`190or `doca-setup/SKILL.md`.191192## What this skill provides193194This is a **thin loader**. The body keeps only the orientation195needed to pick the right next file. The substantive Common material196lives in two companion files:197198- the capabilities companion — what doca-common expresses on this install:199 the `## Capabilities and modes` overview of the universal200 primitives every DOCA application touches; the five subsystem201 H2s (`## log`, `## buf`, `## ctx`, `## dev`, `## progress202 engine`) that own the per-primitive surface; the203 `## Version compatibility` doca-common-specific overlay;204 the `## Error taxonomy` Common-side view of the universal205 `DOCA_ERROR_*` set; the `## Observability` surface (logs, PE206 events, capability snapshots); and the `## Safety policy` overlay207 on the bundle-wide hardware-safety meta-policy.208- the tasks companion — step-by-step workflows for the universal verbs209 (`configure`, `build`, `modify`, `run`, `test`, `debug`, `use`)210 PLUS a `## log` verb-side that covers the two-tier log model in211 workflow form. Plus a `Deferred task verbs` block that points212 install / deploy / rollback questions at the right next skill.213214The skill assumes a host or BlueField where DOCA is already215installed at the standard location and the user has the privileges216their public install profile expects. It does not cover installing217DOCA — that path goes through218`doca-setup/SKILL.md`.219220## What this skill deliberately does not ship221222This skill is **agent guidance**, not a samples or templates223bundle. To keep the boundary clean, it deliberately does not224contain — and pull requests should not add:225226- **Pre-written DOCA application source code, in any language.**227 The verified Common usage shows up inside every shipped DOCA228 sample at `/opt/mellanox/doca/samples/<library>/<sample>/*_main.c`229 and inside every shipped reference application. The agent's job230 is to route the user to those files and prescribe a minimum-diff231 modification on them via the universal modify-a-sample workflow232 in233 `doca-programming-guide/SKILL.md`.234- **Standalone build manifests** (`meson.build`,235 `CMakeLists.txt`, `Cargo.toml`, `setup.py`, `go.mod`, …) parked236 inside the skill. The agent constructs the build manifest *in237 the user's project directory* against the user's installed DOCA,238 where `pkg-config --modversion doca-common` is the source of239 truth.240- **A `samples/`, `bindings/`, or `reference/` subtree** of any241 kind. A mock or incomplete artifact in this skill's tree, even242 one labeled "reference", is misleading: users will read it as243 buildable.244245## Loading order2462471. Read this skill first to confirm the user's question is in248 scope.2492. **For the universal primitives (`log` / `buf` / `ctx` / `dev` /250 `progress engine`), the `pkg-config --modversion doca-common`251 anchor, the Common error overlay, observability, and safety252 policy, see the capabilities companion.**2533. **For step-by-step workflows — configure, build, modify, run,254 test, debug, use, log — see the tasks companion.**255256Both companion files cross-link to each other,257`doca-version/SKILL.md` for the canonical258version-handling rules,259`doca-programming-guide/SKILL.md`260for the universal modify-a-shipped-sample workflow and the261cross-library `DOCA_ERROR_*` taxonomy,262`doca-debug/SKILL.md` for the cross-cutting263debug ladder, and264`doca-public-knowledge-map/SKILL.md`265whenever the right answer is "look it up in the public docs or the266installed package layout" rather than "Common-specific guidance".267268## Related skills269270- `doca-public-knowledge-map/SKILL.md` —271 the routing table for every public DOCA documentation source and272 the on-disk layout of an installed DOCA package. Always available273 alongside this skill; this skill expects to be able to defer274 documentation-finding and install-layout questions there instead275 of duplicating them.276- `doca-setup/SKILL.md` — env preparation,277 install verification, and the *I have no install yet* path with278 the public NGC DOCA container (`nvcr.io/nvidia/doca/doca`) as the279 universal Stage-1 fallback. This skill assumes its preconditions280 are satisfied.281- `doca-version/SKILL.md` — canonical DOCA282 version-handling rules (four-way match, NGC semantics,283 headers-win-over-docs). `pkg-config --modversion doca-common` is284 the build-time anchor *every* DOCA install carries; this skill's285 `## Version compatibility` overlays the Common-specific notes on286 top.287- `doca-programming-guide/SKILL.md` —288 general DOCA programming patterns shared by every library: the289 canonical `pkg-config` + meson build pattern, the universal290 modify-a-shipped-sample first-app workflow, the universal291 lifecycle, the cross-library `DOCA_ERROR_*` taxonomy, and the292 program-side debug order. This skill is the *primitives* layer293 the programming-guide patterns rest on.294- `doca-debug/SKILL.md` — the cross-cutting295 debug ladder (install / version / build / link / runtime /296 program / driver) and the verbosity-escalation surface. DOCA Log297 is the foundation `doca-debug` builds its runtime-debug story on;298 this skill is where the two-tier log model and the universal299 lifecycle errors first surface, and `doca-debug` cross-links here300 for both.301- `doca-structured-tools-contract/SKILL.md` —302 the bundle's structured-tools precedence rule (detect / prefer /303 fall back / report). The Command appendix in304 the tasks companion honors this contract.305- `doca-hardware-safety/SKILL.md` —306 the cross-cutting hardware-safety meta-policy this skill's307 `## Safety policy` overlays.308- Per-library skills (`doca-flow`, `doca-rdma`, `doca-eth`,309 `doca-comch`, `doca-dma`, `doca-rmax`, `doca-sha`, `doca-aes-gcm`,310 `doca-erasure-coding`, `doca-compress`, `doca-dpa`, `doca-gpunetio`,311 `doca-pcc`, `doca-sta`, `doca-telemetry`, `doca-urom`,312 `doca-verbs`, `doca-argp`, `doca-devemu`,313 `doca-dpdk-bridge`, …) — every per-library skill cross-links314 back to this skill for the foundation primitives. Loading this315 skill alongside any of them is the recommended default.