How do I install the Nats Principal Engineer skill?

Run npx skillmds@latest add modra40/nats-principal-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nats Principal Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nats Principal Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nats Principal Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nats Principal Engineer?

modra40 (@modra40) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nats Principal Engineer by modra40 — Agent Skill

Name: Nats Principal Engineer
Author: modra40

Nats Principal Engineer

Principal/Senior-level NATS playbook for subject design, request/reply, JetStream durability, consumer semantics, multi-tenant messaging, and operating lightweight event platforms at scale. Use when: designing evented systems with NATS, reviewing JetStream usage, tuning subjects and consumers, or operating NATS in production.

modra40 ed5ddd8 9 files · 9.1 KB Updated Sep 17, 2026

File contents

NATS Mastery (Senior → Principal)

Operate

Start from messaging semantics: ephemeral pub/sub, request/reply, durable streams, or control-plane signaling.
Treat subject design, consumer semantics, retention, and topology as first-class architecture concerns.
Prefer simple subject hierarchies and explicit delivery semantics.
Design for debuggability and operator clarity before chasing messaging cleverness.

Default Standards

Subject naming should encode bounded, meaningful routing intent.
JetStream retention and ack behavior must match business semantics.
Consumers must be idempotent where durability and replay matter.
Multi-tenant usage needs policy before it needs scale.
Observability should reveal lag, redelivery, and cluster health clearly.

References

Subject design and routing semantics: references/subject-design-and-routing-semantics.md
Core NATS pub-sub and request-reply: references/core-nats-pub-sub-and-request-reply.md
JetStream durability and retention: references/jetstream-durability-and-retention.md
Consumer design, acking, and replay: references/consumer-design-acking-and-replay.md
Multi-tenant governance and security: references/multi-tenant-governance-and-security.md
Cluster topology and operations: references/cluster-topology-and-operations.md
Reliability and operations: references/reliability-and-operations.md
Incident runbooks: references/incident-runbooks.md

---name: nats-principal-engineerdescription: Principal/Senior-level NATS playbook for subject design, request/reply, JetStream durability, consumer semantics, multi-tenant messaging, and operating lightweight event platforms at scale. Use when: designing evented systems with NATS, reviewing JetStream usage, tuning subjects and consumers, or operating NATS in production.---# NATS Mastery (Senior → Principal)## Operate- Start from messaging semantics: ephemeral pub/sub, request/reply, durable streams, or control-plane signaling.- Treat subject design, consumer semantics, retention, and topology as first-class architecture concerns.- Prefer simple subject hierarchies and explicit delivery semantics.- Design for debuggability and operator clarity before chasing messaging cleverness.## Default Standards- Subject naming should encode bounded, meaningful routing intent.- JetStream retention and ack behavior must match business semantics.- Consumers must be idempotent where durability and replay matter.- Multi-tenant usage needs policy before it needs scale.- Observability should reveal lag, redelivery, and cluster health clearly.## References- Subject design and routing semantics: [references/subject-design-and-routing-semantics.md](references/subject-design-and-routing-semantics.md)- Core NATS pub-sub and request-reply: [references/core-nats-pub-sub-and-request-reply.md](references/core-nats-pub-sub-and-request-reply.md)- JetStream durability and retention: [references/jetstream-durability-and-retention.md](references/jetstream-durability-and-retention.md)- Consumer design, acking, and replay: [references/consumer-design-acking-and-replay.md](references/consumer-design-acking-and-replay.md)- Multi-tenant governance and security: [references/multi-tenant-governance-and-security.md](references/multi-tenant-governance-and-security.md)- Cluster topology and operations: [references/cluster-topology-and-operations.md](references/cluster-topology-and-operations.md)- Reliability and operations: [references/reliability-and-operations.md](references/reliability-and-operations.md)- Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)

Frequently asked questions