What problem does it solve?
This skill provides a battle-tested blueprint to scaffold admin pages that are NOT backed by a datatable, ensuring a consistent route, page component, menu entry, i18n, and optional backend wiring across admin portals.
Core Features & Use Cases
- Route entry in frontend/admin/src/router.tsx with path and component.
- A page component in frontend/admin/src/pages/<Name>Page.tsx composed from @shared/components primitives.
- A menu entry in frontend/admin/src/config/side-menu.ts with permission gating.
- i18n keys in locales/<lang>/messages.json under a portal-specific namespace (admin.<name>.*).
- Optional backend: REST route in src/portals/admin/<name>_routes.rs, request/response DTOs, and a portal-less service function under src/domain/services/.
- The page is thin; route handlers call service functions; avoid duplicating business logic in the page.
Quick Start
Create a new admin-page scaffold and wire it into the router, menu, i18n, and optional backend following CLAUDE.md patterns.