The idea would be to follows XDG Base Directory Specification standard.

Instead of only looking at ~/.config/nuclei/config.yaml, nuclei would resolve $XDG_CONFIG_HOME and try global config too. So with default value, for example, it could look for (in order):

1. $XDG_CONFIG_HOME/nuclei/config.yaml (in most cases would resolve to ~/.config/nuclei/config.yaml) to look for user-defined config
2. /etc/nuclei/config.yml (system, global, for all users, default config)
3. Hardcoded ~/.config/nuclei/config.yaml fallback

Same for templates, instead of dumping them at ~/nuclei-templates, it would look at:

1. $XDG_DATA_HOME/nuclei/templates/ (in most cases would resolve to $HOME/.local/share/nuclei/templates/)
2. $XDG_DATA_DIRS/nuclei/templates/ 1st value (in most cases would resolve to /usr/local/share/nuclei/templates/)
3. $XDG_DATA_DIRS/nuclei/templates/ 2nd value (in most cases would resolve to /usr/share/nuclei/templates/)
4. Hardcoded ~/nuclei-templates fallback

That would help to comply with standard paths, ensure to respect users custom structures, ease distribution packaging, unmess the root of user home directory.

Related issues on BlackArch Linux for packaging nuclei

• nuclei-templates not used by nuclei package BlackArch/blackarch#3382
• nuclei: add nuclei-template support BlackArch/blackarch#4357
• https://github.com/BlackArch/blackarch/blob/master/packages/nuclei/config.yaml
• nuclei: remove forced -config flag. BlackArch/blackarch#4723
• nuclei: revert s7x change BlackArch/blackarch#4726
• https://wiki.archlinux.org/title/XDG_Base_Directory