القائمة
Use this skill to enforce strict separation between core system architecture and authentication/authorization concerns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when structuring the project, defining layers, or enforcing architectural boundaries.
Use this skill when implementing or reviewing core Java logic, domain models, performance-sensitive code, or JVM-related concerns in a Spring Boot microservice.
Use this skill when building Docker images for Spring Boot microservices.
Use this skill when building or reviewing the domain model for the hotel/hostel management system. This includes defining entities, attributes, relationships, and enumerations based on hospitality domain expertise.
Use this skill when making product, domain, data model, workflow, or business-rule decisions for hotel and hostel management software.
Use this skill when designing APIs, data ownership, or service boundaries in a microservices system.
| name | auth-agnostic-architecture-boundary |
| description | Use this skill to enforce strict separation between core system architecture and authentication/authorization concerns. |
This project is completely agnostic to authentication and authorization.
If a request reaches the system:
Authentication and authorization are external concerns.
They are handled by:
They are never handled inside:
The system assumes trusted, pre-authorized input.
Think of the system as operating in a secure internal network:
If a feature requires authorization logic,
it is out of scope by design.
Violations of this rule are architectural bugs, not security improvements.
