Skip to content
TrustedSkillsbeta
Back to all skills

Migrating To Tuist Generated Projects

Checked
tuist·vlatest·frontend

This skill automates the migration of existing Xcode projects to use Tuist-generated codebases for improved build performance and maintainability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tuist/agent-skills --skill migrating-to-tuist-generated-projects -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tuist

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tuist/agent-skills at 9a6ec783fe.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9a6ec783fe
Manifest
skills/migrate/SKILL.md
Scanned
1 file, 124 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to migrate existing iOS and macOS projects from CocoaPods or Carthage into Tuist-generated architectures. It automates the conversion of dependency graphs, schemes, and targets while preserving project structure and configuration settings.

When to use it

  • You are maintaining a legacy Objective-C or Swift codebase relying on CocoaPods or Carthage for dependency management.
  • Your team needs to unify multiple modules into a single, scalable build system with improved performance.
  • You require better IDE integration, faster build times, and more reliable dependency resolution than manual Xcode projects provide.
  • You want to transition from fragile Podfile configurations to a declarative Project.swift model managed by Tuist.

Key capabilities

  • Automatically converts existing CocoaPods or Carthage dependencies into Tuist-compatible targets.
  • Generates a complete Project.swift file that defines the entire project structure and build rules.
  • Preserves original source code, schemes, and configuration settings during migration.
  • Handles complex module hierarchies and framework integrations seamlessly.

Example prompts

  • "Migrate my existing iOS project from CocoaPods to Tuist while keeping all current dependencies."
  • "Convert this Carthage-based macOS application into a Tuist-generated project with updated schemes."
  • "Automate the migration of our multi-module Swift codebase to use Tuist instead of manual Xcode projects."

Tips & gotchas

Ensure your source project has a valid Podfile or Cartfile before initiating the migration, as these files are required for dependency analysis. After migration, verify that all build configurations and signing settings are correctly transferred to avoid runtime issues in production environments.