SIGIO could have gotten more attention, it get's a poor treatment because epoll/kqueue are better, but if you stop thinking about getting out of the signal handler as fast as possible and start thinking of it as a kernel-side queue you can save a couple syscalls on an IO-heavy application.
There's some neat tricks you can do with SIGURG as well, since it lets remote processes(!) send a signal ahead of the TCP buffer.
Another good thing worth mentioning is the trick of trapping SIGSEGV/SIGBUS to sbrk; something like this:
char*p=sbrk(0);
void h(int _){ sbrk(4096);signal(SIGSEGV,h); }
signal(SIGSEGV,h);
This allows you to manually manage memory without having to check how close you are to the end of memory[2] which can really simplify some programs, since you'll get a hardware trap that automatically extends the data segment when you write off the end of memory.SIGXFSZ can be dealt with similarly: So many programs try to track bytes copied (quotes, etc) when setrlimit and a signal is easier. More programs don't bother which is annoying.
Also not mentioned: The terminal. SIGWINCH[3] which is useful for getting updated when the window resizes, and SIGTSTP/SIGCONT is how you detect a console user putting you in the background.
[1]: https://cr.yp.to/docs/selfpipe.html
[2]: https://github.com/geocar/ed-v6/blob/master/ed.c.orig#L608
[3]: http://web.mit.edu/~mkgray/jik/sipbsrc/src/utree/tst/sigwinc...