Xcode Project Setup
Firebase (Google)OfficialCreated by Google LLCDistributed by Firebase (Google)
- Skill
- Tool integration
- Software development
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a secure, automated method for adding Swift Package Manager (SPM) dependencies to Xcode projects. It replaces manual, error-prone modifications to .pbxproj files by utilizing a dedicated Swift script that handles both repository dependency injection and target linking. The tool is designed to be idempotent and includes specific support for complex configurations, such as injecting the -ObjC linker flag required for static frameworks like Firebase.
What it does
- Adds Swift Package Manager dependencies to Xcode projects.
- Automatically links package modules to the main project target.
- Injects necessary linker flags like -ObjC for static frameworks.
- Integrates configuration files such as GoogleService-Info.plist into the build phase.
- Verifies the local Swift toolchain environment before execution.
- Ensures safe project modification without manual .pbxproj editing.
When to use it
- When you need to add external Swift Package dependencies to an iOS project.
- When integrating Firebase or other SDKs that require specific linker flags.
- When you want to automate dependency management while avoiding manual Xcode UI steps.
- When you need to ensure consistent project configuration across development environments.
Advantages
- Prevents common errors associated with manual .pbxproj file editing.
- Automates the multi-step process of adding and linking packages.
- Ensures critical build settings like -ObjC are correctly applied.
- Idempotent execution prevents duplicate configurations.
- Uses native Swift for project manipulation, avoiding external dependencies like Ruby.
Usage examples
- “Add Alamofire version 5.8.1 to my project MyApp.xcodeproj.”
- The agent executes the Swift script to add the Alamofire repository and link the module to the project target.
- “Install Firebase version 11.0.0 and include my GoogleService-Info.plist.”
- The agent runs the setup script, adds the Firebase SDK, links the specified products, and configures the plist and linker flags.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/firebase/xcode-project-setup/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip xcode-project-setup.zip -d .agents/skills
Documentation by Google LLC
Xcode Project Setup
⛔️ CRITICAL RULES & ENVIRONMENT CHECKS
Before performing any Xcode setup or file manipulation, you MUST adhere to the following rules. A hefty fee will be applied if you violate them.
1. The Anti-Ruby Mandate
You are strictly forbidden from using Ruby, Rails, or any Ruby gems
(including the xcodeproj gem). Under no circumstances may you write or execute
Ruby scripts.
2. Modern Xcode Folder Synchronization
Modern Xcode projects support folder synchronization. When adding new source
code (.swift) or resource files, simply write them to the correct directory on
disk. They will be automatically included in the Xcode project. Never manually
modify the .pbxproj file to add files.
3. Allowed Scripting Languages
If you absolutely must write a script to manipulate the project environment
(e.g., configuring SPM packages beyond what the provided xcode_spm_setup
script does), you must use Swift. Only as an absolute last resort, if Swift
is completely unviable, may you use Node.js or TypeScript.
4. Toolchain Verification
Because this skill relies entirely on a native Swift script, you must verify the environment:
Run
swift --versionbefore proceeding.If the Swift command is not found, you must stop and recommend the user install the Swift toolchain (e.g., via
xcode-select --installon macOS), or ask if you can attempt to install it for them. Do not attempt to proceed without Swift.
5. Mandatory Linker Flags for Static Frameworks (Firebase)
When setting up SPM dependencies that heavily rely on internal Objective-C
categories and +load methods (such as the Firebase iOS SDK suite), the Apple
linker will aggressively strip these methods out if they are linked statically.
This causes fatal runtime crashes (e.g.,
FirebaseAuth/Auth.swift:167: Fatal error: Unexpectedly found nil).
The provided xcode_spm_setup Swift script automatically injects the -ObjC
flag to OTHER_LDFLAGS when adding Firebase products. However, you should
still verify it is present in the build settings if you encounter issues.
Failing to include this flag when adding Firebase dependencies is a critical error.
Empty Directory Workflow
If you are asked to build an iOS app or configure Xcode dependencies but no
.xcodeproj or .xcworkspace exists, you MUST ask the user to create the
project first:
"No Xcode project found in this directory. Please create an empty Xcode project manually and let me know when you are ready to proceed."
Wait for the user to confirm they have created the .xcodeproj via Xcode, then
proceed with the Standard Xcode Workflow below.
Standard Xcode Workflow
Do not use raw text parsing, sed, or Ruby scripts to modify .pbxproj files
directly.
Instead, execute the Swift configuration package bundled with this skill
(scripts/xcode_spm_setup) to securely install SPM packages and link optional
config files (like GoogleService-Info.plist).
CRITICAL: Always Use Latest SDK Version
To ensure access to the latest features and security fixes, always use the most recent version of the Firebase iOS SDK. Check for the latest release version at https://github.com/firebase/firebase-ios-sdk/releases.
Use the most recent version number (e.g.,
11.x.y) in your commands instead of hardcoded placeholders.
Understanding the Script's Actions
When adding a Swift Package to an Xcode project, two distinct steps must occur:
Adding the package repository dependency (e.g.,
https://github.com/Alamofire/Alamofire).Selecting the target (e.g.,
MyApp), navigating to General > Frameworks, Libraries, and Embedded Content, and hitting the+button to explicitly link the specific product modules (e.g.,Alamofire).
The provided xcode_spm_setup Swift script automatically handles BOTH of
these steps for you. By passing the list of modules as arguments, it safely
injects the package dependency and automatically wires those modules to the main
target's Frameworks build phase. You do not need to do any manual linking.
Usage
Locate the package path: Find the absolute path to this skill's
scripts/xcode_spm_setupdirectory on disk.Execute: Run the native
swift runcommand using the signature below:
swift run --package-path <PATH_TO_SKILL>/scripts/xcode_spm_setup xcode_spm_setup <ProjectPath.xcodeproj> <RepoURL> <VersionRequirement> [--plist <Optional/Path/To/Config.plist>] <Product1> [Product2 ...]Example 1: Generic Package (e.g., Alamofire)
Adding Alamofire to a standard Xcode project. Notice there is no --plist flag.
swift run --package-path /Users/foo/.agents/skills/xcode-project-setup/scripts/xcode_spm_setup xcode_spm_setup MyApp.xcodeproj https://github.com/Alamofire/Alamofire 5.8.1 AlamofireExample 2: Firebase (Requires Plist)
Adding Firebase and linking the GoogleService-Info.plist to the resources
build phase automatically. Note: Replace 11.0.0 with the actual latest
version from
the releases page.
swift run --package-path /Users/foo/.agents/skills/xcode-project-setup/scripts/xcode_spm_setup xcode_spm_setup MyApp.xcodeproj https://github.com/firebase/firebase-ios-sdk 11.0.0 --plist MyApp/GoogleService-Info.plist FirebaseCore FirebaseAuth FirebaseFirestoreNote: The script is idempotent. It will automatically skip linking files or packages that are already present in the project.
Files
- ATTRIBUTION.mdAdded by AutoGineer969 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md6.0 KiB
- scripts/xcode_spm_setup/.gitignore153 B
- scripts/xcode_spm_setup/Package.resolved1.1 KiB
- scripts/xcode_spm_setup/Package.swiftScript428 B
- scripts/xcode_spm_setup/Sources/main.swiftScript9.2 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
The author says: Requires Swift to be installed locally and macOS environment.
Security
What our scanner noticed· Low risk
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Google LLC
- Publisher
- Firebase (Google) (Official)
- Distributed by
- Firebase (Google)
- Source
- firebase/agent-skills · skills/xcode-project-setup · commit b76be96
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google LLC or Firebase (Google).
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download xcode-project-setup.zip