Use buildableFolders instead of sources and resources globs. Buildable folders stay synchronized with the file system, so adding or removing files does not require regeneration.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionusing-tuist-generated-projectsExecute the skills CLI command in your project's root directory to begin installation:
Fetches using-tuist-generated-projects from tuist/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate using-tuist-generated-projects. Access via /using-tuist-generated-projects in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
28
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28
stars
# Generate workspace without opening Xcode
tuist generate --no-open
# Build a scheme with xcodebuild
xcodebuild build -workspace App.xcworkspace -scheme App
# Run tests with xcodebuild
xcodebuild test -workspace App.xcworkspace -scheme AppTests -only-testing AppTests/MyTestCase
Use buildableFolders instead of sources and resources globs. Buildable folders stay synchronized with the file system, so adding or removing files does not require regeneration.
let target = Target(
name: "App",
buildableFolders: [
"App/Sources",
"App/Resources",
]
)
Use target tags to group areas of the project, for example:
tag:team:*tag:feature:*tag:layer:*These tags make it easier to scope generation and testing later.
Example target metadata with tags:
let target = Target(
name: "PaymentsUI",
metadata: .metadata(tags: [
"tag:team:commerce",
"tag:feature:payments",
"tag:layer:ui",
])
)
When working on a focused area, generate only what you need:
tuist generate tag:feature:payments
tuist generate PaymentsUI PaymentsTests
Keep build configurations aligned between the project and external dependencies. Use PackageSettings(settings: .settings(configurations: [])) to mirror project configurations; mismatches emit warnings.
tuist generate --no-open in automation and scripts to avoid launching Xcode.tuist install to resolve dependencies and retry.Use xcodebuild build against the generated workspace and scheme.
xcodebuild build \
-workspace App.xcworkspace \
-scheme App \
-destination "generic/platform=iOS Simulator"
Use xcodebuild test for running tests locally. Prefer it over tuist test because tuist test regenerates the project on each invocation, which slows down iteration.
To optimize test run time:
--only-testing to run only the specific test suite or test case you are working on, instead of the full target.# Run a specific test suite
xcodebuild test \
-workspace App.xcworkspace \
-scheme AppTests \
-only-testing AppTests/MyTestSuite
# Run a single test case
xcodebuild test \
-workspace App.xcworkspace \
-scheme AppTests \
-only-testing AppTests/MyTestSuite/testMyFunction
buildableFolders paths aligned to the target's real file system layout.buildableFolders with sources or resources globs in the same target.tuist generate --no-open.Static side effects warnings: adjust product types deliberately. Use Target.product for local targets and PackageSettings(productTypes:) for external products. Making everything dynamic with .framework can compile and run, but it may hurt launch time. Prefer static products (static frameworks or libraries) when possible and when they do not introduce side effects.
Objective-C dependency crashes: add -ObjC or -force_load via OTHER_LDFLAGS on consuming targets as needed. Reference: https://tuist.dev/en/docs/guides/features/projects/dependencies#objectivec-dependencies.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
leonxlnx/taste-skill
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
using-tuist-generated-projects reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: using-tuist-generated-projects is focused, and the summary matches what you get after install.
We added using-tuist-generated-projects from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
using-tuist-generated-projects fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
using-tuist-generated-projects is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
using-tuist-generated-projects has been reliable in day-to-day use. Documentation quality is above average for community skills.
using-tuist-generated-projects reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added using-tuist-generated-projects from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
using-tuist-generated-projects has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: using-tuist-generated-projects is focused, and the summary matches what you get after install.
showing 1-10 of 46