Codex .NET Architecture for Modular Boundaries and Dependencies
Choose an architecture using business ownership and change frequency. Compare modular monoliths, vertical slices, and other shapes against operational needs.
中文Install in Codex
Codex with a .NET checkout, current modules and constraints, and the bundled architecture references.
- Copy the entire pinned `.codex/skills/architecture/` directory to `.agents/skills/architecture/` in the target checkout.
- Open Codex in that checkout and invoke `$architecture` with the example task and desired output.
Example task
Give `$architecture` a local library catalog exercise. Map catalog, loans, and reporting ownership and explain how to verify dependency direction.What to check
The proposal states responsibilities, data ownership, cross-module entrypoints, and an actionable dependency check.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should modules become separate services?
Look for team autonomy, scale, or independent deployment needs, and account for the resulting operational cost.