I'd put everything except /home, /tmp and /var on the SSD. The other folders are only written to when installing or updating software, yet they keep nearly all the files required to start programs (binaries, libraries, configuration files). Therefore putting them on the SSD will yield greatly improved performance, while the low amount of writes will keep the wear on the SSD low. Also, mount all filesystems on the SSD with the noatime mount option to reduce write access (which would put unnecessary wear on the SSD and is much slower than read, causing worse performance). If you think you don't need a filesystem journal, use a non-journalling filesystem like ext2 on the SSD.

My partition layout suggestion:

• /boot: 2 GB on SSD, ext2


• /: rest of SSD, ext2 should be safe, but if you want faster disk checks, use ext4 or xfs. Corruption is highly unlikely, since only few writes are performed


• /tmp: tmpfs, 16 GB (you'll need swap of at least that size),
  OR, if you want to burn blu-rays: 200 GB on HDD


• swap: 32 GB on HDD (since /tmp is tmpfs, and you might also want hibernate). If you use a non-ramdrive /tmp, swap can be smaller, but at least the size of the RAM.


• /var: 5 GB on HDD (should never get that big, just to be on the safe side...)


• /home: rest of HDD

Since WINE is installing prefixes per default in the home folder, you then have plenty of space for games. Nevertheless, you can of course in addition create a folder on the SSD that is owned by your user (for instance in /opt), to which you can install your games by setting the WINEPREFIX environment variable. It is anyhow good practice to install each game in a different WINEPREFIX.