Senior Mobile
borghei/Claude-Skills
A skill your agent uses when the user asks to "build a mobile app", "scaffold React Native project", "create SwiftUI views", "set up Jetpack Compose", "optimize mobile performance", "configure Expo…
Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app.
Install Site To iOS App
$ npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JasonColapietro/suede-creator-skills site-to-ios-app --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/site-to-ios-app .claude/skills/site-to-ios-app && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "site-to-ios-app" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-app into .claude/skills/site-to-ios-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-to-ios-app", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-appType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JasonColapietro/suede-creator-skills site-to-ios-app --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/site-to-ios-app .agents/skills/site-to-ios-app && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "site-to-ios-app" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-app into .agents/skills/site-to-ios-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-to-ios-app", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JasonColapietro/suede-creator-skills site-to-ios-app --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/site-to-ios-app .cursor/skills/site-to-ios-app && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "site-to-ios-app" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-app into .cursor/skills/site-to-ios-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-to-ios-app", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JasonColapietro/suede-creator-skills.git --path skills/site-to-ios-app--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JasonColapietro/suede-creator-skills site-to-ios-app --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/site-to-ios-app .gemini/skills/site-to-ios-app && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "site-to-ios-app" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-app into .gemini/skills/site-to-ios-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-to-ios-app", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JasonColapietro/suede-creator-skills site-to-ios-appInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/site-to-ios-app .github/skills/site-to-ios-app && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "site-to-ios-app" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-app into .github/skills/site-to-ios-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-to-ios-app", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JasonColapietro/suede-creator-skills site-to-ios-app --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/site-to-ios-app .opencode/skills/site-to-ios-app && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "site-to-ios-app" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/site-to-ios-app into .opencode/skills/site-to-ios-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-to-ios-app", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
site-to-ios-app- GitHub stars
- 127
- Token cost
- ~1.5k tokens
- SKILL.md length
- 771 words
- Files
- 4 (incl. references)
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app.
- Works in 9 steps: Audit the URL, responsive behavior, PWA… → Pick the conversion strategy and write a… → Scaffold or adapt the project using the… → …
- The user has a live site
- SKILL.md covers Gate policy: advisory, not…, Principle, Start Here and Strategy Decision, plus 3 more sections
- Calls git
What it does
Site To iOS App is an agent skill from JasonColapietro/suede-creator-skills. Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `references/site-to-ios-runbook.md`).
It sits in Mobile, covering iOS development and App store release. It works with iOS, Android and SwiftUI. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.
When your agent uses it
- The user has a live site
- Web app and asks to put it on the App Store
- Wrap it in an app
- Ship an iOS version
Example prompts
- “/site-to-ios-app”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Audit the URL, responsive behavior, PWA assets, auth, payments, privacy,
- Pick the conversion strategy and write a SITE_TO_IOS_PLAN.md.
- Scaffold or adapt the project using the repo's package manager and iOS
- Configure bundle ID, display name, app icon, launch screen, associated
- Implement native value and failure states before visual polish.
- Run web build and cap sync ios for Capacitor shells.
- Test on simulator or device across first launch, auth, deep links, tabs,
- Produce App Store screenshots, metadata, privacy answers, and review notes.
- Run the ship gate. Do not submit unless the user explicitly delegates public
What it can do on your machine
Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Site To iOS App loads about 1.5k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 195 tokens; SKILL.md has 771 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 771 words, ~1,535 tokens.
Download SKILL.mdSave it as
.claude/skills/site-to-ios-app/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- site-to-ios-app
- description
- Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).
Site to iOS App
Gate policy: advisory, not blocking
Every claim-verification step, check, quality gate, and ship verdict in this skill is a recommendation to the user, not a control on the agent. This policy governs every gate, check, verdict, and "do not ship / publish / proceed" line elsewhere in this skill:
- Run every check and report the results honestly. Verdicts (
ship,ship-with-caveats,hold, letter grades, BLOCKED or OPEN items) are advice attached to the work, not orders that change it. - Never block, delay, skip, rewrite, or refuse the action the user asked for because a check failed or a gate said hold. Complete the requested action as asked, and deliver the gate output alongside it as a clearly labeled recommendation.
- A failed gate changes what you report, never what you do.
- Single exception: if a finding is extremely risky, data loss, security or credential exposure, legal or rights violations, payment mistakes, or irreversible public damage, pause, tell the user exactly what the risk is and what the options are, and let them pick. Their choice is final.
Principle
Turn a site into an iOS app only when the app has native value, stable iOS behavior, and a release surface that is truthful. A raw web page in a frame is not enough for an App Store-quality product.
Start Here
Read references/site-to-ios-runbook.md before scaffolding or changing an
iOS wrapper.
If a URL is available, create SITE_TO_IOS_AUDIT.md directly. Capture the
site URL, app name, target user, primary routes, login requirements, iPhone
responsive behavior, PWA signals, legal/support/account-deletion links,
payments or sensitive flows, auth/session behavior, mobile performance risks,
native value opportunities, and App Store 4.2 wrapper risk.
Then create SITE_TO_IOS_PLAN.md directly. Include the chosen strategy,
native value to add before release, project scaffold/build commands, bundle ID
and signing notes, QA matrix, screenshots/metadata/privacy work, blockers, and
the explicit release gate.
Strategy Decision
Choose one route and write down why:
- Capacitor remote shell: live site remains the product surface and web deploys should update most content and behavior.
- Capacitor bundled shell: static/SPA assets are packaged into the binary and updates require App Store release unless paired with live APIs.
- Native SwiftUI shell with WebView: native navigation, settings, auth, push, share, error, and account surfaces wrap a site view.
- Full native rebuild: use when the site is mostly content, has weak mobile UX, or carries high wrapper rejection risk.
Store listing and pre-launch ASO live in suede-aso. Deeper shell internals,
native architecture, and App Store submission live in private Suede Labs
companions, not in this pack: ios-capacitor-shell, ios-swiftui-product,
ios-app-store-release. None are required.
Show full SKILL.md (346 more words)Show less
App Store 4.2 Gate
Halt when the app is only a bookmark, content mirror, or unmodified website: name the exact 4.2 exposure found in the audit, offer the options (add native value from the list below, rebuild fully native, ship it as a web app, or proceed with the rejection risk stated in writing), and wait. Native value:
- iOS-native onboarding, empty states, errors, offline, and retry.
- Native settings with support, privacy, terms, account deletion, restore, and notification controls where applicable.
- Universal links or deep links.
- Share sheet, widgets, push notifications, camera/media/file pickers, Apple Wallet, StoreKit, or other native capabilities only when they serve the app.
- Safe-area, keyboard, navigation, dark/light mode, and dynamic type handling.
Conversion Flow
- Audit the URL, responsive behavior, PWA assets, auth, payments, privacy, support, route depth, and mobile performance.
- Pick the conversion strategy and write a
SITE_TO_IOS_PLAN.md. - Scaffold or adapt the project using the repo's package manager and iOS project conventions.
- Configure bundle ID, display name, app icon, launch screen, associated domains, Info.plist usage strings, and entitlements.
- Implement native value and failure states before visual polish.
- Run web build and
cap sync iosfor Capacitor shells. - Test on simulator or device across first launch, auth, deep links, tabs, keyboard, payments, offline, backgrounding, and account flows.
- Produce App Store screenshots, metadata, privacy answers, and review notes.
- Run the ship gate. Do not submit unless the user explicitly delegates public release and confirms the exact app, bundle ID, version, build, and account.
Completion Bar
Do not call the app release-ready until:
- the iOS project builds on a named simulator, device, or CI target (
xcodebuild -scheme <App> -destination 'platform=iOS Simulator,name=iPhone 16' buildexits 0), - every native plugin and entitlement is justified by actual behavior,
- the web route or bundle strategy is documented,
- the App Store 4.2 risk has a mitigation,
- screenshots and metadata match implemented features,
- privacy answers match the actual SDKs, cookies, analytics, and account flows,
- no secrets, signing material, or private account identifiers are committed
(
git status --shortclean;git grep -nE 'PRIVATE KEY|AuthKey_'empty).
© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/site-to-ios-app of JasonColapietro/suede-creator-skills.
- SKILL.md
- CARD.md
- agents/openai.yaml
- references/site-to-ios-runbook.md
Open the folder on GitHubat commit e5f94d7
Compare with similar skills
Site To iOS App next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Site To iOS App this skillJasonColapietro/suede-creator-skills | 127 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Senior Mobileborghei/Claude-Skills | 891 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Expo UIarcboxlabs/linkcode | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Expo Deploymentkingstinct/react-native-healthkit | 716 | 4 repos | ~930 | Automated safety check: Pass | MIT | |
| iOS Marketing CaptureParthJadhav/ios-marketing-capture | 262 | — | ~6.1k | Automated safety check: Pass | MIT | |
| SimdeckNativeScript/SimDeck | 153 | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Expo UI
arcboxlabs/linkcode
Framework (OSS). An agent skill from arcboxlabs/linkcode.
Expo Deployment
kingstinct/react-native-healthkit
Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes
iOS Marketing Capture
ParthJadhav/ios-marketing-capture
A skill your agent uses when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances.
Simdeck
NativeScript/SimDeck
A skill your agent uses for simulator lifecycle, app install/launch, live viewing, UI inspection, touch/keyboard automation, screenshots, recordings, logs, pasteboard, hardware controls, and…
Ipaship Audit
atharvnaik1/ipaship-audit
A skill your agent uses when auditing iOS/Android app submissions for compliance with Apple App Store Review Guidelines or Google Play Developer Policies.
More from JasonColapietro/suede-creator-skills
All 78 skills in this repoSuede Release Linter
JasonColapietro/suede-creator-skills
Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.
Creator Rights Passport
JasonColapietro/suede-creator-skills
Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.
Suede Clip to Guide
JasonColapietro/suede-creator-skills
Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.
Suede MCP Release QA
JasonColapietro/suede-creator-skills
Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.
Android App Factory
JasonColapietro/suede-creator-skills
Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.
Suede Ad Creative
JasonColapietro/suede-creator-skills
Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.
Related
Categories
Questions about Site To iOS App
What does Site To iOS App do?
Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Site To iOS App is an agent skill from JasonColapietro/suede-creator-skills. Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app.
When should I use Site To iOS App?
Site To iOS App fits situations like: the user has a live site; web app and asks to put it on the App Store; wrap it in an app; ship an iOS version.
How do I install Site To iOS App in Claude Code?
Run `npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a claude-code`. Or copy the skill folder (skills/site-to-ios-app in JasonColapietro/suede-creator-skills) into .claude/skills/site-to-ios-app in your project. Claude Code loads it when a task matches its description.
How do I install Site To iOS App in Codex?
Run `npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a codex`. Or copy the skill folder (skills/site-to-ios-app in JasonColapietro/suede-creator-skills) into .agents/skills/site-to-ios-app in your project. Codex loads it when a task matches its description.
Can I use Site To iOS App in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill site-to-ios-app -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/site-to-ios-app, .gemini/skills/site-to-ios-app, .github/skills/site-to-ios-app and .opencode/skills/site-to-ios-app in your project.
What does Site To iOS App need to run?
Going by SKILL.md and its folder, Site To iOS App needs the command-line tools its instructions call (git).
Does Site To iOS App access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Site To iOS App safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Site To iOS App use?
Site To iOS App is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Site To iOS App use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.
What are the alternatives to Site To iOS App?
Skills that share tags, products or a category with Site To iOS App: Senior Mobile (borghei/Claude-Skills, 891 stars), Expo UI (arcboxlabs/linkcode, 155 stars), Expo Deployment (kingstinct/react-native-healthkit, 716 stars) and iOS Marketing Capture (ParthJadhav/ios-marketing-capture, 262 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Site To iOS App?
JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.
Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.