Sails out of the box supports a framework to handle assets. It comes with a folder structure and pipeline configuration that loads those files from assets folders to sails runtime for browser consumption.
The top level folder should not contain anything more than these folders and files.
This helps sails understand where to pick an asset and in what order. This is a sample configuration snippet from tasks/pipeline.js.
Sails also takes care of automatically linking those assets in ejs files via custom code blocks. Example
That means i need not add js or css file location manually.
// we add a timestamp to the query param named v when the pipeline runs. <script src="%s?v='+new Date().getTime()+'"></script>