Nginx Config

Generate production-ready, commented Nginx configurations from plain English descriptions.

Install
cmdop skills install agensi-nginx-config

Nginx Config is a skill that converts plain English requirements into complete, production-ready nginx.conf files. Rather than requiring manual authorship of Nginx syntax, the skill interprets intent and assembles the full configuration structure, including worker processes, event loops, and HTTP blocks.

The skill applies consistent production standards on every generation. Security defaults such as server_tokens off and HSTS headers are always included. Gzip compression and static asset caching headers are added for performance. Proxy headers required by modern web applications are set correctly without manual intervention.

For reverse proxy and load balancing scenarios, the skill handles both single-backend setups and multi-server upstream blocks with weighting. SSL and TLS configuration is supported alongside rate limiting zones. Frontend use cases are covered through SPA try_files logic and Gzip compression settings. Advanced routing features include WebSocket upgrade handling, CORS policy injection, and 301/302 redirects such as WWW to non-WWW canonicalization.

This skill is appropriate when an agent needs to produce deployable Nginx configuration from a natural language description of infrastructure or routing requirements. It is not a live Nginx management tool and does not connect to a running server — it produces configuration text only.

Use cases

  • Generate a reverse proxy config routing traffic to a backend server
  • Produce an upstream load-balancing block with weighted servers
  • Create an SSL/TLS server block with HSTS headers from a domain description
  • Generate SPA-compatible try_files routing for a React or Vue frontend
  • Add WebSocket upgrade support to a proxy configuration
  • Set up CORS headers and rate limiting zones for an API endpoint

When to use it

  • An agent needs to produce a complete nginx.conf from a natural language infrastructure description
  • Consistent production security defaults such as server_tokens off and HSTS must be applied
  • The task involves reverse proxying, load balancing, or SSL termination configuration
  • A frontend SPA or static asset configuration with caching and Gzip is required

When not to use it

  • Live management or reloading of a running Nginx instance is needed
  • The task requires reading or auditing an existing Nginx configuration file
  • A different web server such as Apache or Caddy is in use
  • Dynamic runtime configuration changes rather than file generation are required