add-entity

Add Domain Entity

When the user asks to add a new entity, scaffold following the project's domain-driven design patterns.

If the entity involves non-trivial EF Core configuration (owned types, complex value conversions, table splitting), use context7 to look up the current EF Core docs for the specific pattern before writing the configuration.

Arguments

• {Entity} -- Entity name in PascalCase (e.g., Customer, Order)
• {Service} -- Target microservice that owns this entity. Ask if ambiguous.

Configuration

Read cloudstack.json from the project root at the start of execution. Extract:

• NAMESPACE = project.namespace (default: detect from *.sln name or first *.csproj root namespace)
• DOMAIN_PATH = backend.sharedDomainPath (default: find directory matching **/Domain/ containing Entities/)
• INFRA_PATH = backend.sharedInfraPath (default: find directory matching **/Shared.*Infrastructure/)
• SERVICES = backend.services[] (default: discover from src/*/ directories containing .Application/ subfolders)
• SOLUTION = backend.solutionPath (default: find *.sln in src/)

If cloudstack.json does not exist, auto-detect by scanning the project structure.

Prerequisites

• The target microservice must exist under src/ with Infrastructure and Host projects
• The shared Domain project must exist at {DOMAIN_PATH}
• EF Core tools must be installed (dotnet tool list -g | grep ef)

1. Value Object ID ({DOMAIN_PATH}/ValueObjects/{Entity}Id.cs)

namespace {Namespace}.Domain.ValueObjects;

public class {Entity}Id : ValueObject
{
    public Guid Value { get; init; }

    public {Entity}Id(Guid value)
    {
        if (value == Guid.Empty)
            throw new ArgumentException("{Entity}Id cannot be empty.", nameof(value));
        Value = value;
    }

    public static {Entity}Id New() => new(Guid.NewGuid());

    protected override IEnumerable<object?> GetEqualityComponents()
    {
        yield return Value;
    }
}