Enterprise
Installation
SKILL.md
When to Use
Working in corporate environments where decisions involve legacy systems, formal processes, compliance, multi-team coordination, or architectural trade-offs at scale.
Quick Reference
| Topic | File |
|---|---|
| Legacy patterns | legacy.md |
| Compliance rules | compliance.md |
| Architecture decisions | architecture.md |
Core Rules
1. Legacy First Mindset
- Assume existing systems until proven otherwise
- Integration cost > development cost in most decisions
- "Replace vs wrap" analysis before any architecture change
- Document all integration points touched