Target Services

Procedure

Confirm the service purpose and whether it belongs on the command side, query side, or reactive processing side.
Create a focused .NET project with only the dependencies that support that responsibility.
Keep event contracts explicit and versionable.
Isolate infrastructure code for Cosmos DB, messaging, and external integrations.
Add configuration for local emulator and cloud deployment separately.
Define tests around business behavior, projection logic, and contract mapping.

Do not merge unrelated responsibilities into a single service just because the repo is small initially.
Keep the API Gateway thin; business workflows belong in domain or processing services.

Use this skill when creating the application structure described in the README.

Confirm the service purpose and whether it belongs on the command side, query side, or reactive processing side.
Create a focused .NET project with only the dependencies that support that responsibility.
Keep event contracts explicit and versionable.
Isolate infrastructure code for Cosmos DB, messaging, and external integrations.
Add configuration for local emulator and cloud deployment separately.
Define tests around business behavior, projection logic, and contract mapping.

Do not merge unrelated responsibilities into a single service just because the repo is small initially.
Keep the API Gateway thin; business workflows belong in domain or processing services.