How do I install the Nginx Ingress Principal Engineer skill?

Run npx skillmds@latest add modra40/nginx-ingress-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 Nginx Ingress 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 Nginx Ingress 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 Nginx Ingress Principal Engineer free to use?

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

Who published Nginx Ingress Principal Engineer?

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

Nginx Ingress Principal Engineer by modra40

Name: Nginx Ingress Principal Engineer
Author: modra40

Nginx Ingress Principal Engineer

Principal/Senior-level NGINX Ingress playbook for traffic management, edge reliability, multi-tenant ingress governance, security controls, performance tuning, and production Kubernetes ingress operations. Use when: designing ingress topology, debugging traffic routing, tuning edge behavior, securing external access, or operating shared ingress platforms.

modra40 41d1d29 9 files · 9.7 KB Updated Sep 17, 2026

File contents

NGINX Ingress Mastery (Senior → Principal)

Operate

Start from request flow, trust boundaries, tenant separation, and failure blast radius.
Treat ingress as product-facing critical infrastructure.
Prefer explicit routing, sane defaults, and clear ownership of TLS, auth, and rewrite behavior.
Optimize for safe change rollout, debuggability, and predictable traffic behavior.

Default Standards

Routing rules should be understandable by humans.
Edge timeouts, retries, body limits, and buffering should match workload reality.
Multi-tenant ingress needs policy before scale.
Observability at the edge is mandatory.
Controller upgrades and config changes should be reversible.

References

Ingress topology and ownership: references/ingress-topology-and-ownership.md
Routing, rewrites, and path behavior: references/routing-rewrites-and-path-behavior.md
TLS, auth, and edge security: references/tls-auth-and-edge-security.md
Performance tuning and traffic shaping: references/performance-tuning-and-traffic-shaping.md
Multi-tenant policy and platform governance: references/multi-tenant-policy-and-platform-governance.md
Observability and debugging: references/observability-and-debugging.md
Reliability and operations: references/reliability-and-operations.md
Incident runbooks: references/incident-runbooks.md

---name: nginx-ingress-principal-engineerdescription: Principal/Senior-level NGINX Ingress playbook for traffic management, edge reliability, multi-tenant ingress governance, security controls, performance tuning, and production Kubernetes ingress operations. Use when: designing ingress topology, debugging traffic routing, tuning edge behavior, securing external access, or operating shared ingress platforms.---# NGINX Ingress Mastery (Senior → Principal)## Operate- Start from request flow, trust boundaries, tenant separation, and failure blast radius.- Treat ingress as product-facing critical infrastructure.- Prefer explicit routing, sane defaults, and clear ownership of TLS, auth, and rewrite behavior.- Optimize for safe change rollout, debuggability, and predictable traffic behavior.## Default Standards- Routing rules should be understandable by humans.- Edge timeouts, retries, body limits, and buffering should match workload reality.- Multi-tenant ingress needs policy before scale.- Observability at the edge is mandatory.- Controller upgrades and config changes should be reversible.## References- Ingress topology and ownership: [references/ingress-topology-and-ownership.md](references/ingress-topology-and-ownership.md)- Routing, rewrites, and path behavior: [references/routing-rewrites-and-path-behavior.md](references/routing-rewrites-and-path-behavior.md)- TLS, auth, and edge security: [references/tls-auth-and-edge-security.md](references/tls-auth-and-edge-security.md)- Performance tuning and traffic shaping: [references/performance-tuning-and-traffic-shaping.md](references/performance-tuning-and-traffic-shaping.md)- Multi-tenant policy and platform governance: [references/multi-tenant-policy-and-platform-governance.md](references/multi-tenant-policy-and-platform-governance.md)- Observability and debugging: [references/observability-and-debugging.md](references/observability-and-debugging.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