I don't like having multiple triggers for the same operation, so I prefer at most one for each action (insert, update, delete). I rarely write triggers for more than one action - there is always some code that needs to know if the action was insert, update, or delete' with one trigger per action, that's not a problem.

I can see some benefit of seperating auditing (especially if you use some code to generate these triggers) from other trigger actions/checks. But definitely not more - I would lose oversight of what happens when I change data in a table, and I have too little control over the order triggers fire.