What problem does it solve? Building the E3-M3 module of the EOS skincare app requires coordinating backend routes, database tables, role-based permissions, and admin frontend screens for aesthetic centers, and this Skill defines the exact contracts and boundaries so the module is implemented consistently. ## Core Features & Use Cases - Center CRUD with Soft Delete: Implements GET, POST, PATCH, and DELETE endpoints under /api/centers following the routes-controller-service-repository pattern. - Center-Scoped Permissions: Restricts access through the center_admins table so each admin only manages centers where a matching row exists, returning 403 or 404 with friendly messages otherwise. - Specialist Assignment and Dashboard: Assigns specialists to centers via specialist_profiles.center_id and exposes a basic dashboard with specialist and client counters. - Use Case: When developing the EOS Entrega 3 Module 3, use this Skill to generate the centers endpoints, permission checks, and dashboard query without accidentally implementing M4 audit or M5 reporting features. ## Quick Start Use the e3-centers-admin skill to implement the centers module endpoints and center-scoped admin permissions for the EOS backend.
