Module Boundary Check

5. Type Safety

• Require: Strict TypeScript
• Forbid: any types

Import Rule Validation

Valid Patterns

• Feature → Shared utilities
• Feature → Core services
• Screens → Components (same feature)
• Feature A → Core → Feature B (via core)

Invalid Patterns

• Component → Screen (reverse)
• Feature A → Feature B (direct cross-feature)
• Shared → Platform-specific
• Data → UI (reverse layer)

Validation Process

1. Dependency Graph Analysis: Parse imports, build graph
2. Circular Detection: Detect all cycle types
3. Layer Validation: Verify inward-only imports
4. Import Rule Check: Enforce valid patterns
5. Public API Check: Verify only public imports

Common Violations & Fixes

Guardrails

• Reject boundary violations (FAIL)
• Enforce layer separation (FAIL if reversed)
• No external imports in shared (FAIL)
• Proper dependency direction (FAIL if reversed)
• No circular dependencies (FAIL)
• Type safety (WARN on any)

Triggers

Use when:

• PR changes module imports
• New dependencies added
• Module structure refactored
• Cross-module refactor needed
• Architecture review required