{ "name": "get_conventions", "arguments": {} }

## Golden Rules

1. Zero runtime reflection — all discovery (handlers, policies, routes, idempotency) at compile time
2. Connection is always shared — setShared(true) on DBAL Connection; multiple = broken transactions
3. CommandBus owns the transaction — handlers NEVER call beginTransaction/commit/rollBack
4. Return the aggregate from handlers — bus calls pullDomainEvents(); void = events silently dropped
...

## Naming Conventions

| Concept        | Pattern                  | Example                   |
|--------------- |--------------------------|---------------------------|
| Aggregate      | PascalCase               | User, Order               |
| Aggregate ID   | {Aggregate}Id            | UserId, OrderId           |
| Domain Event   | {Noun}{Verb}Event        | UserRegisteredEvent       |
| Command        | {Verb}{Noun}             | RegisterUser              |
| Command Handler| {Command}Handler         | RegisterUserHandler       |
...

{ "name": "get_architecture", "arguments": {} }

## Layers

### Domain
Responsibilities:
- Aggregates, entities, value objects, domain events, domain exceptions
- Repository interfaces (not implementations)
Rules:
- NO framework imports (no Symfony, no Doctrine, no Vortos attributes)
- NO infrastructure dependencies
- Pure PHP only

### Application
Responsibilities:
- Commands, queries, handlers, projections, policies
Rules:
- May import framework contracts (CommandBusInterface, QueryBusInterface)
- NO database calls directly — only via repository interface
...

## Canonical Directory Structure

src/{Context}/
├── Domain/
│   ├── Entity/
│   ├── Event/
│   ├── Exception/
│   ├── Repository/        ← interfaces only
│   └── ValueObject/
├── Application/
│   ├── Command/
│   ├── EventHandler/
│   ├── Policy/
│   ├── Projection/
│   └── Query/
├── Infrastructure/
│   ├── Messaging/
│   └── Repository/        ← implementations
└── Presentation/
    ├── Controller/
    └── Request/

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "enum": ["performance", "security", "testing", "worker_mode", "kafka"],
      "description": "Filter to a specific topic. Omit to return all topics."
    }
  }
}

{ "name": "get_best_practices", "arguments": { "topic": "testing" } }
{ "name": "get_best_practices", "arguments": {} }

1. Creating multiple DBAL Connection instances
   ✗ Wrong:  new Connection($params)
   ✓ Right:  ConnectionFactory::fromDsn() — shared singleton via DI
   Why: Multiple connections break transactions; write and read sides would use different connections

2. Returning void from a command handler
   ✗ Wrong:  public function __invoke(RegisterUser $command): void
   ✓ Right:  Return the aggregate — bus calls pullDomainEvents() on return value
   Why: Domain events are silently dropped if the handler returns void or null

...

{ "name": "get_mistakes", "arguments": {} }

{
  "type": "object",
  "properties": {
    "module": {
      "type": "string",
      "description": "Module name. Omit to list all modules."
    }
  }
}

{ "name": "get_module_docs", "arguments": { "module": "messaging" } }
{ "name": "get_module_docs", "arguments": {} }

## Messaging

Kafka-backed event-driven messaging with outbox, retry, dead letter, and full consumer pipeline.

### Provides
- EventBusInterface — dispatch domain events
- #[MessagingConfig], #[RegisterTransport], #[RegisterProducer], #[RegisterConsumer]
- #[AsEventHandler] — register event handlers (class or method level)
- #[MessageId], #[CorrelationId], #[Timestamp], #[Header] — header injection attributes
- RetryPolicy::exponential(), RetryPolicy::fixed() — configurable retry backoff
- DeadLetterWriter — persists failed messages to vortos_failed_messages

### Configuration (config/messaging.php)
- dlq().table(string) — dead letter table name (default: vortos_failed_messages)
- idempotency defaults via VortosMessagingConfig

### Commands
- vortos:consume <name>
- vortos:dlq:replay
- vortos:outbox:relay
- vortos:outbox:replay
- vortos:consumers:list
- vortos:transports:list

Installed vortos/* packages:

Package                        Version              Type
────────────────────────────── ──────────────────── ──────
vortos/vortos-foundation        v1.0.0-alpha-35      prod
vortos/vortos-cache             v1.0.0-alpha-35      prod
vortos/vortos-messaging         v1.0.0-alpha-35      prod
vortos/vortos-cqrs              v1.0.0-alpha-35      prod
vortos/vortos-make              v1.0.0-alpha-35      dev
vortos/vortos-mcp               v1.0.0-alpha-35      dev

{
  "type": "object",
  "properties": {
    "file": {
      "type": "string",
      "description": "Config filename without .php extension. Omit to return all config files."
    }
  }
}

{ "name": "read_project_config", "arguments": { "file": "cache" } }
{ "name": "read_project_config", "arguments": {} }

## config/cache.php

```php
use Vortos\Cache\DependencyInjection\VortosCacheConfig;

return static function (VortosCacheConfig $config): void {
    $config->dsn(sprintf('redis://%s:%s', $_ENV['REDIS_HOST'], $_ENV['REDIS_PORT']));
    $config->prefix($_ENV['APP_ENV'] . '_myapp_');
    $config->defaultTtl(3600);
};

If no `config/` directory exists, the tool returns instructions for publishing config stubs with `vortos:config:publish`.

<Callout type="info" title="Project-Aware Context">
`list_project_modules` and `read_project_config` are the tools that give the AI assistant project-specific awareness. They let the assistant tailor its suggestions to what is actually installed and configured in your project, rather than guessing from generic framework knowledge.
</Callout>