# Modular Hexagonal Domain-Driven Design — optional Core rules pack

| | |
| --- | --- |
| **Pack version** | `1.0.0-draft` |
| **Layer** | Core (framework-agnostic) |
| **Required by the architecture?** | **No** — AI-neutral standard |

Use this pack only if you want a portable Core rules slice for an AI coding assistant (any vendor) or as a short human checklist. The documentation site remains the source of truth.

## Contents

| File | Purpose |
| ---- | ------- |
| `SKILL.md` | Portable Core rules summary |
| `RULES.core.md` | Short entrypoint text for project AI rules (any tool) |
| `CHECKLIST.md` | Pre-merge boundary checklist |

## How to use

1. Copy `SKILL.md` / `RULES.core.md` into whatever layout your chosen tool (or none) expects.
2. Keep host-specific adapter rules separate from Core.
3. Use [CHECKLIST.md](CHECKLIST.md) in human or assisted reviews.

## Design test

> If the peer module is deleted and replaced by HTTP, does Application/Domain still compile?

## Examples

Use greenfield names only: `Ordering`, `Warehouse`, `Directory`, `Identity`.