القائمة
Rules for defining ports in hexagonal architecture. Use this when creating or modifying or reviewing an interface or abstract type that acts as a boundary between the application and its adapters.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ports |
| description | Rules for defining ports in hexagonal architecture. Use this when creating or modifying or reviewing an interface or abstract type that acts as a boundary between the application and its adapters. |
A port is an interface (or abstract type) that defines how the application communicates with the outside world.
UserRepository, EmailSender). Ports SHOULD refer to the needs of a single usecase.Rules for writing domain objects in hexagonal architecture. Use this when creating or modifying or reviewing entities, value objects, aggregates, or domain services.
Core rules for developing code with hexagonal architecture. Use this whenever writing, reviewing, or refactoring any codebase that follows hexagonal architecture or making any recommendations about hexagonal architecture. References the other hex-arch skills for specifics.
Rules for writing inbound adapters (also called presenters, controllers, or primary adapters) in hexagonal architecture. Use this when creating or modifying or reviewing any code that receives input from the outside world (HTTP handlers, CLI commands, queue consumers, event listeners, etc.).
Rules for writing outbound adapters (also called secondary adapters or infrastructure adapters) in hexagonal architecture. Use this when creating or modifying or reviewing any code that talks to the outside world on behalf of the application (databases, external APIs, file systems, message brokers, etc.).
Rules for writing use cases in hexagonal architecture. Use this when creating or modifying or reviewing a use case / application service class or function.