Init Xcode App logo

Init Xcode App

Community
glebis
init-xcode-app

Scaffold a standalone SwiftUI app via XcodeGen — pick macOS, iOS, or iOS+watchOS; ships house conventions, a Swift Testing target, swiftformat/swiftlint, optional CloudKit/CI/Release/Push modules, and optional JTBD product context. Use to "init an xcode project", "scaffold a swiftui app", "new mac/ios app".

Overview

Publisherglebis
Repositoryclaude-skills
Skill nameinit-xcode-app
Stars
379
Forks
56
Bundled files
39
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 39 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by glebis on GitHub. Read the source before you install it.

Installation

Install the Init Xcode App AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/glebis/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/init-xcode-app .claude/skills/init-xcode-app
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Init Xcode App in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Init Xcode App on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Init Xcode App is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

init-xcode-app

Scaffolds a native SwiftUI app with XcodeGen (project.yml → generated, committed .xcodeproj), pre-loaded with the conventions and loop-closer toolchain (xcsift, the Xcode MCP, swiftformat/lint). The lighter native sibling of init-tauri-app.

When to use

  • "init an xcode project", "scaffold a swiftui app", "new macOS/iOS app".

Prerequisites (verify before scaffolding)

  • xcodegen on PATH (xcodegen --version; brew install xcodegen if missing).
  • Xcode + CLT (xcodebuild -version).

Procedure

1. Gather inputs (AskUserQuestion)

  • App name (PascalCase, e.g. Tidepool) → <Name>; lowercase → <name>.
  • Bundle-id prefix (default com.glebkalinin) → <bundlePrefix>.
  • DEVELOPMENT_TEAM (optional — blank allowed) → <TEAM>.
  • Target shape: ios | macos | ios-watchos.
  • Modules (multi-select): CloudKit · CI · Release · Push.
  • JTBD artifact (optional): path to a jtbd.json (else auto-discover ./jtbd.json, ~/jtbd/<name>/jtbd.json). See 1.5.
  • Target directory (default ~/ai_projects/<name>). Abort if non-empty.

1.5 Ingest JTBD (optional, additive)

Identical contract to init-tauri-app: resolve (explicit → ./jtbd.json~/jtbd/<name>/jtbd.json), confirm via hook, validate (render-jtbd.sh exits 3 → skip), pre-fill name. Artifacts written in Step 3.

2. Render core

Copy assets/core/common/* into the project (renames: gitignore.gitignore, swiftformat.swiftformat, CLAUDE.md.claude/CLAUDE.md). Copy assets/core/shapes/<shape>/* into the project root. For macos, also copy assets/core/shapes/ios/Sources + Tests (macos reuses the same SwiftUI sources). Substitute <Name>/<name>/<bundlePrefix>/<TEAM> in every copied file. Blank <TEAM> → leave the placeholder line DEVELOPMENT_TEAM: "".

If a JTBD artifact was confirmed: render assets/jtbd/PRODUCT.md.templatedocs/PRODUCT.md, guardrails-check.md.templatedocs/internal/guardrails-check.md, insert agents-product-section.md.template into AGENTS.md after the first heading, copy the artifact to project-root jtbd.json. See assets/jtbd/jtbd-map.md.

3. Compose selected modules

For each selected module open assets/modules/<m>/INSERT.md and follow it: it lists source files to copy and a project-fragment.yml to merge into project.yml (merge into the existing targets.<Name> and entitlements: maps — never overwrite). CloudKit + Push both extend the same entitlements: map.

4. Generate + verify (the gate)

bash
xcodegen generate

Then the unsigned build gate by shape:

  • ios / ios-watchos: xcodebuild build -scheme <Name> -destination 'generic/platform=iOS Simulator'
  • macos: xcodebuild build -scheme <Name> -destination 'platform=macOS' CODE_SIGNING_ALLOWED=NO

Then xcodebuild test against the same destination for the test target. Both must pass.

5. Handoff

Offer git init && git add -A && git commit. Print summary: shape, modules, signing note (device/release signing is a human step), next command (open <Name>.xcodeproj).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Init Xcode App AI skill do?

Scaffold a standalone SwiftUI app via XcodeGen — pick macOS, iOS, or iOS+watchOS; ships house conventions, a Swift Testing target, swiftformat/swiftlint, optional CloudKit/CI/Release/Push modules, and optional JTBD product context. Use to "init an xcode project", "scaffold a swiftui app", "new mac/ios app".

Why use Init Xcode App on TypingMind?

Because you install it once and use it with any model. Init Xcode App is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Init Xcode App in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/glebis/claude-skills/tree/main/init-xcode-app. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Init Xcode App?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Init Xcode App?

As many as you like. As long as a model supports skills, you can use Init Xcode App with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Init Xcode App AI skill free?

Yes. It is published on GitHub by glebis under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇