What problem does it solve? Extending the Go CMS admin interface often leads to tight coupling between backend modules and the Vue frontend, hard-coded menu items, and rebuilds for every configuration change. This Skill defines the architectural boundary so backend modules contribute navigation declaratively while the frontend renders it through plugins. ## Core Features & Use Cases - Backend-Driven Navigation: The backend owns module availability, menu structure, ordering, permissions, and semantic route/icon IDs, while the frontend owns Vue components, routes, and icons. - Module-Contributed Admin Items: Optional feature modules contribute admin UI through a generic capability provider, so adding a module never requires editing the admin shell. - Permission-Aware, Site-Scoped Menus: Navigation is filtered per actor and per site runtime, distinguishing global items from site-scoped ones without a mutable global registry. - Use Case: When adding a new forms module to the CMS, use this Skill to expose its menu entry and semantic route from the backend and register its screens in a frontend plugin, without rebuilding the frontend when the module is later enabled or disabled per site. ## Quick Start Ask the AI to add a new module-contributed admin navigation item with backend permission filtering and a corresponding frontend plugin route following the go-cms-admin-ui guidelines.
