What problem does it solve?
This Skill prevents authorization bugs when you add a new endpoint by ensuring the permission constant, server gate, and admin UI routing are kept in sync.
Core Features & Use Cases
- Adds a server-side permission constant to the correct module resource group and includes it in the module’s
All collection for registration.
- Gates a backend endpoint with
.RequirePermission(...) so unauthorized requests reliably receive a 403.
- Mirrors the permission in the admin app so the permissions catalog and role/route guard logic can recognize it.
- Updates admin test seeding so
RouteGuard passes on first paint in E2E scenarios.
- Use case: when a new admin-facing “create” action needs authorization, you add the matching permission and wire both the backend and admin UI to enforce it consistently.
Quick Start
Add the new permission constant to the module’s {X}Permissions All list, then gate the target endpoint with .RequirePermission(...) and mirror the permission in the admin app permission tree plus route guard.