spm-to-tuist

Migrate an SPM project to Tuist by applying a stepwise process that introduces Tuist alongside the existing setup, validates the dependency graph, and preserves module boundaries before removing Package.swift.

An enum-driven Swift architecture uses enum cases to map to distinct modules, each with a single product and test target, establishing a meta-model that defines dependency direction rules and internal separation.

Yes, migrating SPM to Tuist can preserve architectural invariants by maintaining the modeling primitives, dependency directions, and folder conventions while ensuring each enum case becomes a distinct Tuist target.

Convert SPM enum cases to Tuist targets by mapping each enum case to a distinct Tuist target with a corresponding product and test target, validating the structural equivalence before removing the Package.swift file.

Remove Package.swift only after introducing Tuist alongside SPM, validating the dependency graph, and ensuring structural equivalence between the enum-driven modeling primitives and the new Tuist configuration.

Migrating to Tuist maintains module separation by preserving abstraction, utility, and internal boundaries, ensuring dependency direction rules defined in the original SPM architecture are kept intact during the transition.