malky-domain-designer

Guide a DDD design conversation for a Rust API and generate a domain-model.md file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mmacphail/my-claude-rules --skill malky-domain-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: malky-domain-designer
Source: https://github.com/mmacphail/my-claude-rules/tree/main/malky-domain-designer
Command: npx skills add https://github.com/mmacphail/my-claude-rules --skill malky-domain-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides a structured Domain-Driven Design design conversation for a Rust API project and produces a domain-model.md file at the project root.

Core Features & Use Cases

  • Interactive, phase-based design sessions that validate aggregates, relationships, and invariants.
  • Generates a complete domain-model.md detailing aggregates, fields, JSONB schemas, statuses, transitions, capabilities, and invariants.
  • Enforces hard rules for aggregates and domain modeling while capturing decisions for downstream implementation.

Quick Start

Provide your API goal and a list of aggregates to begin an interactive DDD design session that generates domain-model.md.

Frequently Asked Questions about malky-domain-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a domain model for a Rust API using Domain-Driven Design?

To design a domain model for a Rust API using Domain-Driven Design, you can use a guided interactive session that helps shape aggregates, fields, and invariants into a structured domain-model.md file.

What is the best way to define aggregates and invariants for a Rust domain model?

Defining aggregates and invariants for a Rust domain model involves a phase-based design conversation that validates relationships and enforces hard rules, capturing all decisions for downstream implementation.

How do I generate a domain-model.md file for my API project?

You generate a domain-model.md file by providing your API goal and a list of aggregates to start an interactive design session, which outputs the complete domain model at your project root.

Can I use DDD design sessions to validate JSONB schemas and status transitions?

Yes, DDD design sessions can validate JSONB schemas, statuses, and transitions by enforcing hard domain modeling rules while detailing aggregates, fields, and capabilities during the interactive conversation.

Do I need to provide a list of aggregates before starting domain-driven design for my API?

Yes, you need to provide your API goal and an initial list of aggregates to begin the interactive DDD design session and effectively shape the domain model.

What are the limitations of using automated DDD sessions for Rust API architecture?

Automated DDD sessions focus specifically on modeling aggregates, fields, and invariants for Rust APIs, meaning they produce a domain-model.md blueprint rather than generating the actual API implementation code.