All SPI device libraries I deal with manage their own slave selects once the SPI devices are started. The low level library functions pull the slave select LOW, do the read/write, and set it HIGH again when finished. There is no need for you to do that in your code.
The only no-no I know of is do not read or write to a SPI device during an interrupt. (edit: Meaning not in the ISR function itself.)