# Codexpiator Architecture

> Software architecture guidance - project structure conventions, design patterns catalog, API contracts and versioning, scalability trade-offs, and monolith vs microservices. Use when structuring a new project, deciding how to split code, or making a structural/scaling decision.

- Skill: `emanuelegreco29/codexpiator-architecture` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add emanuelegreco29/codexpiator-architecture`
- Raw SKILL.md: https://api.skillmd.com/api/skills/emanuelegreco29/codexpiator-architecture/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: emanuelegreco29 (https://skillmd.com/u/emanuelegreco29)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/emanuelegreco29/codexpiator-architecture

---


# Codexpiator Architecture

Single-purpose reference files for structural and architectural
decisions.

| File | Read this when... |
|---|---|
| `project-structure-conventions.md` | Laying out folders, monorepo vs polyrepo |
| `design-patterns-catalog.md` | Deciding whether a pattern (DI, repository, strategy, observer) fits |
| `api-contracts-and-versioning.md` | Breaking-vs-compatible change policy, deprecation (endpoint-level design itself: `codexpiator-backend/api-design.md`) |
| `scalability-and-tradeoffs.md` | Deciding if/how to scale, avoiding premature scaling |
| `monolith-vs-microservices.md` | Deciding whether to split a service |

## Ask when useful; suggest an audit after significant work

See `shared/collaboration-and-audit-practice.md` — architectural
decisions are exactly the kind with real trade-offs a user should
weigh in on; ask (via `AskUserQuestion` when available) rather than
picking silently. Suggest `/codexpiator-audit` after a significant
structural change.