First and foremost, it is important to separate the server templating (EJS) from angular.
Although sails defaults to an EJS template engine, it does not mean that you cannot still include angular in your asset library and create an angular app. EJS is the default programming language that sails uses for building its templates on the server which are then delivered to the client. Angular templates are utilized by the client to display information and perform tasks.
Above all, ensure that these two components are separated.
For setting up your asset pipeline, consider using sails-generate-frontend. It helps in creating grunt tasks for copying image files and configuring javascript libraries such as ANGULAR.js and jQuery for your front-end purposes.
In some cases, it may be beneficial to have two projects - one for Sails API and another for the Angular app, especially if it is a single-page application (SPA).
If you only need to use angular in specific areas of your app (similar to how jQuery is used), generate-front-end can be employed to obtain the angular library from a source like bower_components and incorporate it into your assets when lifting your app. This tool also ensures that the library is available to be included in your app's HTML.
However, I personally prefer using sails templates (specifically Jade instead of EJS) to create and modify my angular templates on the server side before they reach the client. While this practice might be more advanced and somewhat confusing without understanding the distinction between generating HTML on the server versus the client, it suits my needs.
An alternative approach is to create the index page on the server, which includes the necessary CSS and scripts. This page could be the only one on your server, with all other pages being angular templates rendered on the client side via JSON calls. In such a scenario, SAILS (EJS, Jade, or any preferred template engine) is used solely for rendering the single page INDEX.js.
However, it's worth noting that Sails already includes these functionalities out of the box, so sails-generate-frontend is not necessarily required as it comes pre-packaged in a standard Sails app.