Domain model change

Skill jukrap/ai-agent-playbook/skills/architecture/domain-model-change

Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.

Install

npx -y skills add jukrap/ai-agent-playbook --skill domain-model-change

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when changing or reviewing domain entities, aggregates, value objects, services, policies, use cases, repositories, adapters, invariants, or transaction boundaries.

SKILL.md

1.1 KB, as published. Nobody here has run it

Domain Model Change

Use this as the primary architecture skill for domain model and application boundary changes.

Workflow

Identify the project's domain style from code: DDD, clean architecture, hexagonal, layered services, active record, transaction scripts, or mixed.
Locate invariant ownership, transaction boundary, persistence boundary, DTO/domain mapping, events/messages, and integration adapters.
Keep domain rules out of UI, controller, persistence, and transport code unless the project intentionally uses a simpler pattern.
Record changed invariants, compatibility risks, persistence effects, and verification coverage.

Reference

Read references/domain-modeling-boundaries.md for entities, aggregates, value objects, services, policies, and invariant ownership.