メニュー
Use this skill when making product, domain, data model, workflow, or business-rule decisions for hotel and hostel management software.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill to enforce strict separation between core system architecture and authentication/authorization concerns.
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 designing APIs, data ownership, or service boundaries in a microservices system.
| name | hospitality-management-domain-expertise |
| description | Use this skill when making product, domain, data model, workflow, or business-rule decisions for hotel and hostel management software. |
This Agent Skill provides deep domain context for the hospitality industry (hotels, hostels, boutique stays, and small accommodations).
Its goal is to ensure an AI agent can make correct architectural, functional, and business decisions when designing or implementing a Hotel / Hostel Management System (HMS / PMS).
This is not a UI skill or a technical framework skill.
It is a business-domain intelligence layer.
Key implication: room logic, pricing, and guest handling differ by property type.
Hospitality inventory is perishable and time-bound.
A room can be:
Hostels often sell:
Inventory must always be date-based.
Each state change impacts:
Never assume:
Rates are usually:
Pricing logic must be decoupled from room availability logic.
A single guest can:
Guest profiles include:
Legal requirements vary by country (especially ID storage).
Late check-outs and early arrivals affect availability.
Housekeeping is tightly coupled to:
A room under maintenance must be unavailable for sale.
Important:
Key challenges:
Channel logic must be loosely coupled and event-driven.
Common hospitality metrics:
Reports are:
Reporting logic must rely on historical immutable data, not current state.
Never assume:
When building an application:
These are domain-critical errors, not minor issues.
Use this skill:
If a technical decision contradicts hospitality domain rules,
the domain rules win.
