In Scrum, User Stories or PBIs as they are called in this template (and some others) are supposed to be vertical slices of functionality. This means that they describe features or other tangible benefits that the system provides. An example for some such benefit would be something like In order to reduce the amount of spam sent from my system, as a service administrator, I want to limit access to the send mail to registered users only.
This describes a change in the system that is end to end. It will include all of the associated tasks: adding UI for signing in, adding a single-sign-on service, modifying the DB schema to support the feature, etc. When all of the tasks are completed, the user will have a complete new feature added to the app.
What you described is actually a horizontal slice of functionality. If all the (UI) tasks are completed, and the PBI is done, the user hasn't gained anything. There is no value to the user / customer.
Therefore you should try to think in "vertical" slices - functionality, rather than "horizontal" slices which are technical layers.
Hope this helps,