technical-architecture-simplification
Choose and document the simplest reliable technical architecture for Exorex client work, AI automations, dashboards, apps, backend systems, and operational tools. Use when Codex needs to avoid overeng
SKILL.mdskills/technical-architecture-simplification/SKILL.md
GitHubTechnical Architecture Simplification
Use this skill to solve the business problem with the simplest system that works reliably.
Core Principle
Start simple, but do not build something careless.
Simple means appropriate: reliable enough, secure enough, maintainable, explainable, affordable, upgradeable, and aligned with the client's current stage.
Workflow
- Define the real business problem.
- Identify the business stage:
- early stage
- growing
- scaling
- high-scale or enterprise
- Choose the lowest architecture level that can solve the current problem reliably.
- Compare at least one simpler and one more advanced alternative.
- Explain trade-offs in business language.
- Define what should remain manual for safety.
- Define an upgrade path so the system can grow later.
- Document the decision using an architecture decision record.
Read references/architecture-decision-guide.md for architecture levels, decision guides, checklist, and ADR template.
Architecture Levels
Use the simplest viable level:
- Manual or spreadsheet-based system.
- No-code or low-code automation.
- Simple web dashboard.
- Custom app or full system.
- Scalable cloud architecture.
Do not jump to a higher level unless the current business need, risk, users, data volume, security, or reliability requirement justifies it.
Overengineering Warnings
Challenge the design if it includes:
- mobile app before workflow validation
- microservices for a small internal tool
- complex AI where simple rules are enough
- full CRM when lead tracking is enough
- advanced analytics before reliable data collection
- full automation where manual approval is safer
- custom backend before a form, sheet, Airtable, or n8n flow is tested
Output Contract
When using this skill, provide:
- Recommended architecture level.
- Why it fits the client's current stage.
- Alternatives considered.
- Trade-offs and accepted risks.
- What to build now and what not to build yet.
- Upgrade path.
- Architecture decision record draft when the decision is significant.