Well, it is an example in itself. Dependencies are in /public/javascript/lib, and the core in /public/javascript/src/base.
The main page is in /public/templates/index.html, and inside that .html every route starts with /assets/ because I use it with Play framework. You can change the routes to /public/ or whatever.
In /public/javascript/src/screens you can find two basic screens which point to each other, and in /public/templates/ there are 2 .haml files corresponding to each screen. In /public/locals are the locals for each screen.
Some example code/tutorials/howto or common use cases would be really useful to understand what your project is used for...
And saying it is an example in itself, clearly isn't helping us understand it.
Who needs it? Why is it useful? What are the features? A screen system is about as descriptive as a 'javascript framework'.
You could simply publish those files in a way that we can open with our browsers without having to download the project, and link it in the readme. This would be worth a thousand words :)
And don't suppose that everybody know what a "Screen system" is...