migrating-to-tuist-generated-projects — Claude Code skill for Xcode migration
This skill moves an existing Xcode project to a Tuist-generated workspace and checks its build and simulator launch. Use it when adopting Tuist for an app.
npx skills add tuist/agent-skills --skill migrating-to-tuist-generated-projects -a claude-code
npx skills add tuist/agent-skills --skill migrate -a claude-codeWhat migrating-to-tuist-generated-projects does
The skill helps describe an existing app’s targets, build settings, resources, scripts, and dependencies in Tuist manifests. It can separate shared settings into .xcconfig files and map external packages. First, it records a successful build of the original project so the generated workspace has a baseline.
After generation, the workflow rebuilds the app and launches it on a simulator. The skill covers common migration snags such as missing source files, SDK frameworks, resource bundles, and bundle identifiers. A clean build alone is not the finish line; runtime validation is part of the process.
The migration produces Tuist manifests, dependency configuration, and notes on build and runtime checks. Keep deployment targets and bundle identifiers aligned with the original project, or the app may behave differently when launched.
What it helps with
- move an existing Xcode project to Tuist
- define targets and dependencies in Tuist manifests
- separate shared build settings into
.xcconfigfiles - track down missing files or frameworks after generation
- check that the app launches on a simulator
Example prompts for the agent
- Migrate this Xcode project to Tuist and verify its build.
- Create Tuist manifests for every target and external dependency in this app.
- Build the generated workspace and test the app launch on a simulator.
How to install migrating-to-tuist-generated-projects
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill migrating-to-tuist-generated-projects -a claude-codenpx skills add tuist/agent-skills --skill migrate -a claude-code2Manually: put the files in place
~/.claude/skills/migrate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/migrate/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill migrate -a codex2Manually: put the files in place
.agents/skills/migrate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill migrate -a cursor2Manually: put the files in place
.cursor/skills/migrate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tuist/agent-skills migrate2Manually: put the files in place
.github/skills/migrate/SKILL.md1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill migrate -a gemini-cli2Platform CLI
gemini skills install https://github.com/tuist/agent-skills --path skills/migrateManually: put the files in place
.devin/skills/migrate/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill migrate -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about migrating-to-tuist-generated-projects
How do I install migrating-to-tuist-generated-projects in Claude Code?
Run npx skills add tuist/agent-skills --skill migrating-to-tuist-generated-projects -a claude-code. The skill is installed at ~/.claude/skills/migrate/SKILL.md.
What does migrating-to-tuist-generated-projects do?
It guides the conversion of an existing Xcode project into a Tuist-generated workspace, then checks the build and app launch on a simulator.
What should I validate after generating a Tuist workspace?
Build the workspace and launch the app on a simulator. Check that targets, extensions, and settings still match the original project.
