Skip to content

JasonColapietro/suede-creator-skills / skills/site-to-ios-app

site-to-ios-app

Verified

Suede Site to iOS App Skills. Use when asked to "turn this site into an iOS app" or convert a PWA: inspect the URL, choose shell or native strategy, then deliver an audit, build plan and release evidence. NOT FOR: Android builds (android-app-factory), Play rollout (suede-play-release), store listing strategy (suede-aso), or a native iOS app with no website.

FileKindSize
CARD.mdmarkdown4.5 KB
SKILL.mdskill md7.0 KB
agents/openai.yamlconfig278 B
references/app-store-requirements.mdmarkdown5.3 KB
references/site-to-ios-runbook.mdmarkdown4.5 KB
references/worked-contract.mdmarkdown2.0 KB
references/worked-example.mdmarkdown4.7 KB

references/site-to-ios-runbook.md

View on GitHub
# Site-to-iOS Runbook

## 1. URL Audit

Start with facts about the site:

- URL, app name, target user, and core job.
- Primary routes and whether they require login.
- Responsive behavior on iPhone widths.
- PWA signals: manifest, theme color, apple touch icon, service worker.
- Legal links: privacy, terms, support, contact, account deletion if accounts
  exist.
- Sensitive flows: payments, subscriptions, user-generated content, messaging,
  uploads, camera, microphone, location, health, finance, or minors. Any
  audience under 13 triggers the kids rules in `SKILL.md`.
- Auth behavior: OAuth redirects, the Guideline 4.8 login-option need, cookies,
  session persistence, same-site restrictions, universal links.
- Search footprint: which routes rank or get cited today. An app does not
  replace them, so keep the web pages indexable and link them to the App Store
  listing (`suede-aso` covers the listing side).

When a URL is reachable, write `SITE_TO_IOS_AUDIT.md` directly from current
evidence. Include the URL checked, route map, auth and payment behavior, PWA
signals, legal/support/account-deletion links, responsive findings at iPhone
widths, performance risks, sensitive permissions, native value opportunities,
and App Store 4.2 wrapper-risk notes.

## 2. Strategy Matrix

| Site Type | Default Strategy | Notes |
| --- | --- | --- |
| Existing SaaS or dashboard | Capacitor remote shell | Add native settings, deep links, offline/error states, and auth stability. |
| Static marketing or content site | Full native rebuild or native content app | A thin wrapper is high risk under App Store 4.2. |
| PWA with strong mobile UX | Capacitor bundled or remote shell | Keep update route explicit and preserve PWA assets. |
| Marketplace or commerce site | Capacitor remote plus native account/support | Verify payments policy, Stripe web checkout, account deletion, and support. |
| Media or creator app | Native shell or SwiftUI rebuild | Add media pickers, share, library, notifications, or offline where useful. |

## 3. Native Value Requirements

The required native value is the blocking gate and lives in one place: see
"App Store 4.2 Gate" in `SKILL.md`. Build against that list, not a copy.

## 4. Capacitor Scaffold

Use the repo's locked package manager. For a new shell, the common shape is:

```bash
pnpm create vite site-ios --template react-ts
cd site-ios
pnpm add @capacitor/core @capacitor/ios
pnpm exec cap init
pnpm build
pnpm exec cap add ios
pnpm exec cap sync ios
```

For a remote web app, configure the server URL only when the release policy
accepts remote-delivered behavior. For a bundled app, build local assets and
ship updates through binary releases unless using a governed live-update
system.

## 5. Native Configuration

Check these before release:

- `capacitor.config.*` app ID, display name, webDir, and server routing.
- Xcode bundle identifier, version, build number, signing team, and deployment
  target.
- App icon, launch screen, status bar, orientation, and safe areas.
- Associated domains and universal links.
- Info.plist usage descriptions for every native permission.
- Entitlements for Sign in with Apple, push, associated domains, iCloud, or
  Apple Pay only when implemented.
- `PrivacyInfo.xcprivacy` for the app, plus a manifest from every bundled SDK
  that Apple lists (see `app-store-requirements.md`).
- Xcode and SDK version on the build machine or CI runner meet Apple's current
  upload minimum.

## 6. QA Matrix

Run on a named simulator or device:

- first launch and return launch,
- login, logout, expired session, OAuth redirect,
- primary route navigation,
- keyboard forms and scroll-to-focused-field behavior,
- network offline, slow network, API failure, retry,
- file/media permission denial and later approval,
- deep link from cold and warm start,
- dark/light mode,
- background/foreground,
- payment or subscription flow if present,
- account deletion/support/privacy/terms links.

## 7. Release Gate

Produce:

- `SITE_TO_IOS_AUDIT.md`
- `SITE_TO_IOS_PLAN.md` with strategy, native value, build/run commands, QA
  matrix, screenshots/metadata/privacy work, blockers, and release gate
- build command output or CI link
- simulator/device QA notes
- screenshots and metadata (listing strategy from `suede-aso`)
- privacy questionnaire inputs and age rating answers
- reviewer notes, including demo credentials for gated routes

Recommend `hold` if the site cannot pass the wrapper-risk gate, if privacy/legal
links are missing, if payments violate policy, if the app does not build, or if
the user has not explicitly delegated public submission.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall