ai-2070

Use this skill when the user is integrating the Net library (`@net-mesh/sdk`, Rust `net-sdk`, Python `net-sdk`, Go `net` binding, or C `net.h`) as an event bus, for nRPC request/response over the mesh, or for the RedEX / CortEX / Dataforts persistence + folded-state + caching layers on top — anything involving publishing to or subscribing from a Net channel, wiring a producer/consumer/relay against the Net SDK, calling a service via `serve_rpc` / `call_typed` / `TypedMeshRpc`, opening a `RedexFile` for durable append-only logs, building a CortEX adapter / NetDB query surface over folded state, enabling greedy-LRU caching / data gravity / blob refs / read-your-writes, or migrating from Kafka/NATS/Redis Streams/Pulsar/gRPC. Also covers the **gang-claim scheduler** (atomically claiming a contended exclusive resource — a GPU island / accelerator slot / licensed seat — under competition, without double-booking across a partition) and the **task-lifecycle / workflow** layer on top. Triggers on imports of those pack

Use this skill when the user is integrating the Net Payments SDK (`net-payments` Rust crate, `net_payments` lib, or the Python/Node `CapabilityGateway` + `PaymentProvider` payment surface) — x402-native payments for the Net mesh. Covers pricing a capability at discovery (`net.pricing.terms@1`), issuing signed quotes (`net.payment.quote@1`), the provider-side lifecycle engine (`PaymentEngine`: quote → verify → settle → tiered verification → billing), the caller-side flow (`CallerPaymentFlow` / `ProviderChannel`: pricing → spend policy → payload → pay), facilitators (mock + the real HTTP `verify`/`settle` client, config packs, auth), tiered verification (`observed | confirmed(n) | final`) with the independent on-chain `ChainChecker`, reorg handling, the settlement signer seam (`SchemeSigner` / `ExternalSigner` / `ExternalSvmSigner` / `ExternalXrplSigner` — EIP-3009 exact-EVM, SPL exact-SVM `sign_svm_transfer`/`SvmTransferIntent`, and exact-XRPL `sign_xrpl_payment`/`XrplPaymentIntent`; keys never cross the bound

Use this skill when the user is integrating the Net library (`@net-mesh/sdk`, Rust `net-sdk`, Python `net-sdk`, Go `net` binding, or C `net.h`) as an event bus, for nRPC request/response over the mesh, or for the RedEX / CortEX / Dataforts persistence + folded-state + caching layers on top — anything involving publishing to or subscribing from a Net channel, wiring a producer/consumer/relay against the Net SDK, calling a service via `serve_rpc` / `call_typed` / `TypedMeshRpc`, opening a `RedexFile` for durable append-only logs, building a CortEX adapter / NetDB query surface over folded state, enabling greedy-LRU caching / data gravity / blob refs / read-your-writes, or migrating from Kafka/NATS/Redis Streams/Pulsar/gRPC. Also covers the **gang-claim scheduler** (atomically claiming a contended exclusive resource — a GPU island / accelerator slot / licensed seat — under competition, without double-booking across a partition) and the **task-lifecycle / workflow** layer on top. Triggers on imports of those pack

Use this skill when the user is integrating the Net Payments SDK (`net-payments` Rust crate, `net_payments` lib, or the Python/Node `CapabilityGateway` + `PaymentProvider` payment surface) — x402-native payments for the Net mesh. Covers pricing a capability at discovery (`net.pricing.terms@1`), issuing signed quotes (`net.payment.quote@1`), the provider-side lifecycle engine (`PaymentEngine`: quote → verify → settle → tiered verification → billing), the caller-side flow (`CallerPaymentFlow` / `ProviderChannel`: pricing → spend policy → payload → pay), facilitators (mock + the real HTTP `verify`/`settle` client, config packs, auth), tiered verification (`observed | confirmed(n) | final`) with the independent on-chain `ChainChecker`, reorg handling, the settlement signer seam (`SchemeSigner` / `ExternalSigner` / `ExternalSvmSigner` / `ExternalXrplSigner` — EIP-3009 exact-EVM, SPL exact-SVM `sign_svm_transfer`/`SvmTransferIntent`, and exact-XRPL `sign_xrpl_payment`/`XrplPaymentIntent`; keys never cross the bound

Build, debug, and review apps that use the L0 reliability layer (`reliable-ai-streams`). TRIGGER when: a file imports `reliable-ai-streams` or any subpath (`reliable-ai-streams/core`, `/structured`, `/consensus`, `/parallel`, `/pipeline`, `/window`, `/guardrails`, `/drift`, `/monitoring`, `/openai`, `/anthropic`, `/mastra`, `/zod`, `/adapters/helpers`, `/utils/chunking`); the user asks for L0 retry/guardrail/drift/structured/consensus/pipeline/parallel/race wiring; the user references L0 events, lifecycle callbacks (`onRetry`, `onFallback`, `onDrift`, `onCheckpoint`, `onViolation`, etc.), or `L0Event`/`L0State`/`L0Result` types. SKIP for unrelated AI SDK code that doesn't touch L0.

Build, integrate, and debug code that uses the MemEX memory-graph library (@ai2070/memex). Covers the three graphs (Memory / Intent / Task), typed commands, soft-failure semantics, retrieval & budget packing, transplant, and bulk replay. TRIGGER when: code imports `@ai2070/memex`; user asks about MemEX memory items, edges, contradictions, aliases, intents, tasks, smartRetrieve, exportSlice/importSlice, replayFromEnvelopes; user wires MemEX into an agent or daemon. SKIP for unrelated storage/vector DB work.

Use MemEX epistemic memory — record beliefs with trust/conviction/importance scores, recall them ranked, trace provenance, and keep contradictions and corrections as data instead of overwriting.