using-tuist-generated-projects — Claude Code skill: how to install
Guides coding agents through Tuist-generated Xcode workspaces, optimizing xcodebuild testing routines, selective target generation, and buildable folder structures.
npx skills add tuist/agent-skills --skill using-tuist-generated-projects -a claude-code
npx skills add tuist/agent-skills --skill generated-projects -a claude-codeWhat using-tuist-generated-projects does
The skill steers coding agents through building and testing Xcode workspaces produced by Tuist. It enforces headless generation with --no-open so Xcode stays closed during terminal tasks. Projects use buildableFolders instead of glob patterns. Directories mirror the filesystem directly, which avoids constant workspace rebuilds.
Local testing runs through xcodebuild test rather than tuist test. The native Tuist test command recreates the entire workspace before executing suites. That slows iteration down. By tagging targets with labels like tag:feature:*, the agent generates only isolated slices of the application.
When generation fails on missing packages, the skill triggers tuist install. If Objective-C linking issues arise, adding -ObjC or -force_load to OTHER_LDFLAGS fixes the build. Product types remain static when feasible to preserve launch performance.
What it helps with
- run isolated test suites without full workspace regeneration
- replace static glob patterns with dynamic
buildableFolders - scope workspace generation using target metadata tags
- resolve Objective-C linking failures in consuming targets
Example prompts for the agent
- Generate the workspace for
tag:feature:paymentswithout opening Xcode - Run the single test suite
AppTests/MyTestSuiteusingxcodebuild - Configure the target to use
buildableFoldersinstead of source globs
How to install using-tuist-generated-projects
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill using-tuist-generated-projects -a claude-codenpx skills add tuist/agent-skills --skill generated-projects -a claude-code2Manually: put the files in place
~/.claude/skills/generated-projects/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/generated-projects/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill generated-projects -a codex2Manually: put the files in place
.agents/skills/generated-projects/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill generated-projects -a cursor2Manually: put the files in place
.cursor/skills/generated-projects/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tuist/agent-skills generated-projects2Manually: put the files in place
.github/skills/generated-projects/SKILL.md1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill generated-projects -a gemini-cli2Platform CLI
gemini skills install https://github.com/tuist/agent-skills --path skills/generated-projectsManually: put the files in place
.devin/skills/generated-projects/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill generated-projects -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 using-tuist-generated-projects
How to install using-tuist-generated-projects in Claude Code?
Run npx skills add tuist/agent-skills --skill using-tuist-generated-projects -a claude-code in your terminal.
Why does the skill prefer xcodebuild test over tuist test?
Running tuist test forces a project regeneration on every single invocation. Invoking xcodebuild test directly with --only-testing runs specific test suites without that overhead.
How to handle generation errors caused by missing dependencies?
Execute tuist install to resolve and fetch the required external dependencies, then run workspace generation again with --no-open.
