In the realm of separation of concerns… Look-and-feel is one thing. API is another. When I can, I like to think of the API as a foundation for the UI. It really helps make the entities, relationships, queries and operations concrete.
If those terms suggest a database model, that’s intentional. Packages are persistent entities, after all. Their content and metadata should be, too. Perhaps an ER model might be a good start?