ClawHub

SwiftUI Empty App Init

v1.0.0

Initialize a minimal SwiftUI iOS app in the current directory by generating a single `.xcodeproj` with XcodeGen (no workspaces, packages, or tests unless explicitly requested).

⭐ 2· 2.3k·5 current·5 all-time
by@ignaciocervino

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for ignaciocervino/swiftui-empty-app-init.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "SwiftUI Empty App Init" (ignaciocervino/swiftui-empty-app-init) from ClawHub.
Skill page: https://clawhub.ai/ignaciocervino/swiftui-empty-app-init
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install ignaciocervino/swiftui-empty-app-init

ClawHub CLI

Package manager switcher

npx clawhub@latest install swiftui-empty-app-init
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the instructions: the skill expects Xcode and XcodeGen and only generates a minimal single-target SwiftUI .xcodeproj. No unrelated binaries, credentials, or installs are requested.
ℹ
Instruction Scope
Instructions are narrowly focused on creating a project.yml and running XcodeGen. They explicitly forbid auto-installation and avoid building or launching simulators. Two operational notes: (1) the skill directs writing files into the current directory and does not instruct checking for or avoiding overwriting existing files — users should run it in an empty/isolated directory or back up first; (2) it instructs the agent to 'proceed immediately' once inputs are provided (minimal confirmation), which is a behavior choice but not a security red flag by itself.
✓
Install Mechanism
This is an instruction-only skill with no install spec and no code files — nothing is written to disk by the skill bundle itself and no third-party downloads are specified.
✓
Credentials
The skill requests no environment variables, credentials, or configuration paths beyond requiring Xcode/XcodeGen to be present; requested access is proportional to its purpose.
✓
Persistence & Privilege
always is false, the skill does not request persistent or elevated platform privileges, and it does not modify other skills or global agent settings.
Assessment
This skill appears coherent for initializing a minimal SwiftUI project, but before using it: (1) ensure Xcode is selected (xcode-select) and XcodeGen is on PATH; (2) run it in an empty or backed-up directory to avoid accidental file overwrite (it will create project.yml, a .xcodeproj, and source files in CWD); (3) double-check the provided project name and bundle identifier because the skill is configured to 'proceed immediately' without extra confirmations; (4) note the skill will not auto-install prerequisites — if XcodeGen is missing it will stop and report what’s missing. If you need additional scaffolding (icons, tests, packages), explicitly request those options because the skill intentionally omits them.

Like a lobster shell, security has layers — review code before you run it.

latestvk974dqcr7m2pk43a9zk02xgzbn7z7cgh
2.3kdownloads
2stars
1versions
Updated 2mo ago
v1.0.0
MIT-0
@ignaciocervino
latest
Download

SwiftUI Empty App Init

Overview

Initialize a clean, single-target SwiftUI iOS app in the current directory. The project is generated using XcodeGen to produce a single .xcodeproj, leaving developers ready to start adding features immediately.

Prerequisites

  • Xcode installed and selected via xcode-select
  • XcodeGen available on PATH

If any prerequisite is missing:

  • Stop execution
  • Tell the user exactly what is missing
  • Do not attempt alternative scaffolding or auto-installation

Inputs

  • Project name (required)
  • Minimum iOS deployment target
  • Optional bundle identifier (or use default)

Defaults (use without extra confirmation)

  • Bundle identifier default: com.example.<ProjectName>
  • Proceed immediately once required inputs are provided (do not ask extra confirmations)

Core Requirements

The resulting project must:

  • Be generated via XcodeGen (do not hand-author project.pbxproj)
  • Use a single .xcodeproj (no .xcworkspace)
  • Contain exactly one app target
  • Use the SwiftUI @main App lifecycle
  • Contain a minimal ContentView placeholder
  • Contain a minimal Info.plist (avoid unnecessary scene or delegate keys)
  • Contain no Swift packages
  • Contain no test targets unless explicitly requested

Generation

  • Create a minimal project.yml using the provided inputs
  • Generate YourApp.xcodeproj using XcodeGen
  • Ensure the output matches all Core Requirements

Expected Structure

  • project.yml
  • YourApp.xcodeproj
  • YourApp/ (app target source files)
  • Optional config files only

No additional folders, packages, workspaces, scripts, or assets should be present.

Minimal Verification (fast)

  • Confirm YourApp.xcodeproj is generated successfully by XcodeGen.
  • Confirm the default scheme exists (e.g., via a lightweight scheme listing).
  • Do not boot simulators, build, install, or launch unless explicitly requested.

Notes

  • Keep the project minimal and unopinionated
  • Do not add icons/scripts, packages, workspaces, or architecture scaffolding
  • This skill is for app initialization only, not feature scaffolding

Comments

Loading comments...