If you're writing nginx C modules, this is your guide for designing the configuration interface admins will actually use. It covers 46 rules across exposure decisions (what to make configurable vs hardcode), naming conventions, directive types, scope placement, defaults, and validation. The priority ranking is helpful: it puts the critical stuff like naming and exposure first, then works down to compatibility concerns. Think of it as the design phase counterpart to implementation skills like nginx-c-modules. The framework for deciding configurable vs hardcoded is solid, and the cross-module consistency rules will save you from inventing your own conventions poorly.
npx skills add https://github.com/pproenca/dot-skills --skill nginx-c-module-design