create-disposabl-app 0.0.4 → 0.1.1

package/dist/templates/default/apps/desktop/README.md

@@ -0,0 +1,58 @@
+# Desktop
+
+Electron Forge with Vite and TypeScript, managed by the repository's Bun workspace.
+Requires Bun 1.4.4 and Node.js 22.13 or newer.
+
+Run these commands from the repository root:
+
+```sh
+bun install
+bun run --cwd apps/desktop dev
+bun run --cwd apps/desktop typecheck
+bun run --cwd apps/desktop lint
+bun run --cwd apps/desktop build
+bun run --cwd apps/desktop make
+```
+
+`dev` opens the app with Vite hot reload. `build` packages the application into
+`apps/desktop/out/`. `make` also creates distributables for the current platform.
+The desktop app participates in the root Turbo tasks, so
+`bun run dev --filter=desktop` also starts it.
+
+Use the root `bun.lock`; do not generate a separate npm lockfile or run npm install
+inside this workspace. Forge 8 still probes npm's version during its CLI system
+check, so its output can say `Found npm`. Bun installs the dependencies and runs
+the project scripts; Forge and Electron still use Node.js.
+
+## Distribution targets
+
+| Platform | Architecture         | Distributables                             | Bun script     |
+| -------- | -------------------- | ------------------------------------------ | -------------- |
+| Windows  | x64                  | Squirrel `Setup.exe`, `.nupkg`, `RELEASES` | `make:windows` |
+| Linux    | x64                  | `.deb` and `.rpm`                          | `make:linux`   |
+| macOS    | arm64, Apple Silicon | `.zip` containing the `.app`               | `make:macos`   |
+
+Run each script with `bun run --cwd apps/desktop <script>`. Packaging rejects other
+platform and architecture combinations, including Windows ARM and Intel macOS.
+Build Windows installers on Windows, Linux packages on Linux, and macOS packages
+on macOS. Linux builders need `fakeroot`, `dpkg`, and `rpm` installed.
+
+## GitHub releases
+
+The GitHub publisher uploads to `disposabl-dev/create-disposabl-app`. Desktop
+releases use `desktop-v<version>` tags to avoid collisions with the generator's
+`v<version>` releases. The version comes from this workspace's `package.json`.
+Uploads create a draft release for review before making the downloads public.
+
+With `GITHUB_TOKEN` supplied in the environment, run the matching `make:*` script
+on each platform, followed by:
+
+```sh
+bun run --cwd apps/desktop release --from-make
+```
+
+The token needs repository contents write access. Each platform uploads to the
+same draft for that version. Create the draft with one platform first, then upload
+the other platforms to avoid racing release creation. Code signing, notarization,
+and in-app updates are not configured.
+

package/dist/templates/default/apps/desktop/forge.config.mts

@@ -0,0 +1,90 @@
+import type { ForgeConfig } from '@electron-forge/shared-types';
+import { MakerSquirrel } from '@electron-forge/maker-squirrel';
+import { MakerZIP } from '@electron-forge/maker-zip';
+import { MakerDeb } from '@electron-forge/maker-deb';
+import { MakerRpm } from '@electron-forge/maker-rpm';
+import { VitePlugin } from '@electron-forge/plugin-vite';
+import { FusesPlugin } from '@electron-forge/plugin-fuses';
+import { PublisherGitHub } from '@electron-forge/publisher-github';
+import { FuseV1Options, FuseVersion } from '@electron/fuses';
+
+const config: ForgeConfig = {
+  packagerConfig: {
+    asar: true,
+    // Native bundle metadata needs a numeric version; package.json retains the PR suffix.
+    appVersion: process.env.DESKTOP_VERSION?.split('-')[0],
+    buildVersion: process.env.DESKTOP_VERSION?.split('-')[0],
+    download: {
+      cacheRoot: process.env.electron_config_cache,
+    },
+  },
+  rebuildConfig: {},
+  hooks: {
+    prePackage: async (_config, platform, arch) => {
+      const supported =
+        (platform === 'darwin' && arch === 'arm64') ||
+        ((platform === 'win32' || platform === 'linux') && arch === 'x64');
+
+      if (!supported) {
+        throw new Error(
+          `Unsupported desktop target ${platform}/${arch}. Use Windows x64, Linux x64, or macOS arm64.`,
+        );
+      }
+    },
+  },
+  makers: [
+    new MakerSquirrel({}),
+    new MakerZIP({}, ['darwin']),
+    new MakerRpm({}),
+    new MakerDeb({}),
+  ],
+  publishers: [
+    new PublisherGitHub({
+      repository: {
+        owner: 'disposabl-dev',
+        name: 'create-disposabl-app',
+      },
+      tagPrefix: 'desktop-v',
+      draft: true,
+      prerelease: false,
+    }),
+  ],
+  plugins: [
+    new VitePlugin({
+      // `build` can specify multiple entry builds, which can be Main process, Preload scripts, Worker process, etc.
+      // If you are familiar with Vite configuration, it will look really familiar.
+      build: [
+        {
+          // `entry` is just an alias for `build.lib.entry` in the corresponding file of `config`.
+          entry: 'src/main.ts',
+          config: 'vite.main.config.mts',
+          target: 'main',
+        },
+        {
+          entry: 'src/preload.ts',
+          config: 'vite.preload.config.mts',
+          target: 'preload',
+        },
+      ],
+      renderer: [
+        {
+          name: 'main_window',
+          config: 'vite.renderer.config.mts',
+        },
+      ],
+    }),
+    // Fuses are used to enable/disable various Electron functionality
+    // at package time, before code signing the application
+    new FusesPlugin({
+      version: FuseVersion.V1,
+      [FuseV1Options.RunAsNode]: false,
+      [FuseV1Options.EnableCookieEncryption]: true,
+      [FuseV1Options.EnableNodeOptionsEnvironmentVariable]: false,
+      [FuseV1Options.EnableNodeCliInspectArguments]: false,
+      [FuseV1Options.EnableEmbeddedAsarIntegrityValidation]: true,
+      [FuseV1Options.OnlyLoadAppFromAsar]: true,
+    }),
+  ],
+};
+
+export default config;

package/dist/templates/default/apps/desktop/index.html

@@ -0,0 +1,12 @@
+<!doctype html>
+<html>
+  <head>
+    <meta charset="UTF-8" />
+    <title>Hello World!</title>
+  </head>
+  <body>
+    <h1>💖 Hello World!</h1>
+    <p>Welcome to your Electron application.</p>
+    <script type="module" src="/src/renderer.ts"></script>
+  </body>
+</html>

package/dist/templates/default/apps/desktop/package.json

@@ -0,0 +1,55 @@
+{
+  "name": "desktop",
+  "productName": "desktop",
+  "version": "1.0.0",
+  "private": true,
+  "description": "My Electron application description",
+  "keywords": [],
+  "license": "MIT",
+  "author": {
+    "name": "vivek-yast",
+    "email": "vivek@yast.ai"
+  },
+  "main": ".vite/build/main.cjs",
+  "packageManager": "bun@1.4.4",
+  "engines": {
+    "node": ">=22.13.0"
+  },
+  "scripts": {
+    "dev": "electron-forge start",
+    "start": "electron-forge start",
+    "build": "electron-forge package",
+    "package": "electron-forge package",
+    "make": "electron-forge make",
+    "make:windows": "electron-forge make --platform=win32 --arch=x64",
+    "make:linux": "electron-forge make --platform=linux --arch=x64",
+    "make:macos": "electron-forge make --platform=darwin --arch=arm64",
+    "release": "electron-forge release",
+    "lint": "oxlint && oxfmt --check",
+    "lint:fix": "oxlint --fix && oxfmt --write",
+    "format": "oxfmt --write",
+    "typecheck": "tsc --noEmit"
+  },
+  "dependencies": {
+    "electron-squirrel-startup": "^1.0.1"
+  },
+  "devDependencies": {
+    "@electron-forge/cli": "8.0.1",
+    "@electron-forge/maker-deb": "8.0.1",
+    "@electron-forge/maker-rpm": "8.0.1",
+    "@electron-forge/maker-squirrel": "8.0.1",
+    "@electron-forge/maker-zip": "8.0.1",
+    "@electron-forge/plugin-fuses": "8.0.1",
+    "@electron-forge/plugin-vite": "8.0.1",
+    "@electron-forge/publisher-github": "8.0.1",
+    "@electron-forge/shared-types": "8.0.1",
+    "@electron/fuses": "^2.1.3",
+    "@types/electron-squirrel-startup": "^1.0.2",
+    "@types/node": "^24",
+    "electron": "45.2.1",
+    "oxfmt": "^0.75.0",
+    "oxlint": "^1.90.0",
+    "typescript": "^6.0.2",
+    "vite": "^8"
+  }
+}

package/dist/templates/default/apps/desktop/src/declarations.d.ts

@@ -0,0 +1,2 @@
+/// <reference types="@electron-forge/plugin-vite/forge-vite-env" />
+declare module '*.css';

package/dist/templates/default/apps/desktop/src/index.css

@@ -0,0 +1,8 @@
+body {
+  font-family:
+    -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial,
+    sans-serif;
+  margin: auto;
+  max-width: 38rem;
+  padding: 2rem;
+}

package/dist/templates/default/apps/desktop/src/main.ts

@@ -0,0 +1,58 @@
+import { app, BrowserWindow } from 'electron';
+import path from 'node:path';
+import started from 'electron-squirrel-startup';
+
+// Handle creating/removing shortcuts on Windows when installing/uninstalling.
+if (started) {
+  app.quit();
+}
+
+const createWindow = () => {
+  // Create the browser window.
+  const mainWindow = new BrowserWindow({
+    width: 800,
+    height: 600,
+    webPreferences: {
+      preload: path.join(__dirname, 'preload.cjs'),
+    },
+  });
+
+  // and load the index.html of the app.
+  if (MAIN_WINDOW_VITE_DEV_SERVER_URL) {
+    mainWindow.loadURL(MAIN_WINDOW_VITE_DEV_SERVER_URL);
+  } else {
+    mainWindow.loadFile(
+      path.join(__dirname, `../renderer/${MAIN_WINDOW_VITE_NAME}/index.html`),
+    );
+  }
+
+  // Open the DevTools.
+  mainWindow.webContents.openDevTools();
+};
+
+// This method will be called when Electron has finished
+// initialization and is ready to create browser windows.
+// Some APIs can only be used after this event occurs.
+app.whenReady().then(() => {
+  createWindow();
+
+  // On OS X it's common to re-create a window in the app when the
+  // dock icon is clicked and there are no other windows open.
+  app.on('activate', () => {
+    if (BrowserWindow.getAllWindows().length === 0) {
+      createWindow();
+    }
+  });
+});
+
+// Quit when all windows are closed, except on macOS. There, it's common
+// for applications and their menu bar to stay active until the user quits
+// explicitly with Cmd + Q.
+app.on('window-all-closed', () => {
+  if (process.platform !== 'darwin') {
+    app.quit();
+  }
+});
+
+// In this file you can include the rest of your app's specific main process
+// code. You can also put them in separate files and import them here.

package/dist/templates/default/apps/desktop/src/preload.ts

@@ -0,0 +1,3 @@
+// oxlint-disable eslint-plugin-unicorn/no-empty-file
+// See the Electron documentation for details on how to use preload scripts:
+// https://www.electronjs.org/docs/latest/tutorial/process-model#preload-scripts

package/dist/templates/default/apps/desktop/src/renderer.ts

@@ -0,0 +1,19 @@
+/**
+ * This file will automatically be loaded by vite and run in the "renderer" context.
+ * To learn more about the differences between the "main" and the "renderer" context in
+ * Electron, visit:
+ *
+ * https://electronjs.org/docs/tutorial/process-model
+ *
+ * By default, Node.js integration in this file is disabled. When enabling Node.js integration
+ * in a renderer process, please be aware of potential security implications. You can read
+ * more about security risks here:
+ *
+ * https://electronjs.org/docs/tutorial/security
+ */
+
+import './index.css';
+
+console.log(
+  '👋 This message is being logged by the renderer process, included via Vite',
+);

package/dist/templates/default/apps/desktop/tsconfig.json

@@ -0,0 +1,14 @@
+{
+  "compilerOptions": {
+    "target": "ESNext",
+    "module": "preserve",
+    "moduleResolution": "bundler",
+    "allowJs": true,
+    "skipLibCheck": true,
+    "esModuleInterop": true,
+    "noImplicitAny": true,
+    "sourceMap": true,
+    "resolveJsonModule": true
+  },
+  "include": ["src/**/*", "*.ts", "*.mts"]
+}

package/dist/templates/default/apps/desktop/vite.main.config.mts

@@ -0,0 +1,4 @@
+import { defineConfig } from 'vite';
+
+// https://vitejs.dev/config
+export default defineConfig({});

package/dist/templates/default/apps/desktop/vite.preload.config.mts

@@ -0,0 +1,4 @@
+import { defineConfig } from 'vite';
+
+// https://vitejs.dev/config
+export default defineConfig({});

package/dist/templates/default/apps/desktop/vite.renderer.config.mts

@@ -0,0 +1,4 @@
+import { defineConfig } from 'vite';
+
+// https://vitejs.dev/config
+export default defineConfig({});

package/dist/templates/default/apps/docs/package.json

@@ -0,0 +1 @@
+{}

package/dist/templates/default/apps/mobile/.agents/skills/agent-device/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: agent-device
+description: Automates Apple-platform apps (iOS, tvOS, macOS), Android devices (including Android TV and Fire TV on Fire OS), and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
+---
+
+# agent-device
+
+For a normal app-driving task, start immediately. Do not probe first with `--help`, `--version`, `devices`, `appstate`, `snapshot`, or `screenshot`:
+
+```bash
+agent-device open <app> --foreground
+```
+
+That starts the session and returns the initial interactive snapshot with `@refs`.
+
+Loop: act with `press|click|fill|longpress <target> ... --settle`, `scroll <direction> --settle`, or `back --settle`; continue from the printed diff, verify the named expectation (`wait text "..."`, `is`, `get`, or `find`), then run `agent-device close`.
+
+Reaching an off-screen target is one command, not a scroll-and-check loop: `scroll down --until <selector>` scrolls until that element is on screen, and `scroll bottom` runs to the end of the content. Repeated bare `scroll down` calls are the slow way to find something.
+
+Copy refs byte-for-byte: `@e12`, `@e12~s4` — keep the `@` and any `~sN`. Prefer current refs, then `id`/`label`/`role` selectors; coordinates are a last resort. If snapshot reports sparse/AX-unavailable, its refs and selectors are invalid: run `agent-device screenshot`, inspect the image, use coordinates, then retry `snapshot -i` after navigating. Otherwise run `snapshot -i` only when the diff lacks the next target.
+
+Error output includes corrective hints; follow them instead of re-planning. Only when the task is specialized (for example gestures, scripting, TV, macOS, remote, or debugging) or a command shape is unclear, run `agent-device help <topic>`. `agent-device --help` lists topics, but is not a startup step.

package/dist/templates/default/apps/mobile/.agents/skills/android-emulator/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: android-emulator
+description: Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device.
+---
+
+# Android Emulator
+
+Require the `agent-device` CLI to be installed separately before driving an emulator:
+
+```bash
+npm install -g agent-device@latest
+```
+
+Treat installation and upgrades as user-owned setup steps. Do not run that command autonomously or substitute a mutable `npx -y agent-device@latest` invocation.
+
+For a normal app-driving task, start immediately. Do not probe first with `--help`, `--version`, `devices`, `appstate`, `snapshot`, or `screenshot`. Target Android explicitly when opening an app or package id:
+
+```bash
+agent-device open <app-or-package-id> --platform android --foreground
+```
+
+Follow the initial interactive snapshot and corrective error hints. If the shell reports that `agent-device` is unavailable, stop and ask the user to install it or expose their existing installation on `PATH`.
+
+Only when the task is specialized or a command shape is unclear, read the relevant version-matched help topic:
+
+```bash
+agent-device help validate        # engineering validation and build freshness
+agent-device help debugging       # screenshots, logs, traces, video, and failures
+agent-device help react-native    # React Native and Expo runtime guidance
+agent-device help react-devtools  # React components, props/state/hooks, render profiling
+agent-device help scripting       # durable replay and CI workflows
+```

package/dist/templates/default/apps/mobile/.agents/skills/dogfood/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: dogfood
+description: Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
+allowed-tools: Bash(agent-device:*), Bash(npx agent-device:*)
+---
+
+# Dogfood
+
+Router for exploratory QA. Private setup before using this skill:
+
+```bash
+agent-device --version
+```
+
+If that fails, stop and tell the user to expose a trusted `agent-device` binary on PATH or approve an exact-version npm command. This skill intentionally keeps allowed tools restricted to `agent-device` and `npx agent-device`.
+
+Require `agent-device >= 0.14.0`; older CLIs lack these help topics. If older, stop and tell the user to upgrade the trusted install or approve an exact-version npm command. Do not run `npm install -g agent-device@latest` or `npx -y agent-device@latest` autonomously, and do not include version/upgrade commands in final plans.
+
+Read current CLI guidance:
+
+```bash
+agent-device help dogfood
+```
+
+Loop: open app -> snapshot -i + screenshot -> explore flows -> capture evidence per issue -> close.
+
+Target app is required; infer platform or ask. Findings must come from runtime behavior, not source reads. Let `help dogfood` provide exact report shape, evidence commands, and current workflow guidance.

package/dist/templates/default/apps/mobile/.agents/skills/eas-app-stores/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: eas-app-stores
+description: Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.
+version: 1.1.0
+license: MIT
+---
+
+# App Store Deployment
+
+> **EAS service - costs apply.** Cloud builds use EAS plan resources, and EAS services have free-tier and paid-plan limits. Apple Developer and Google Play memberships are separate. Check https://expo.dev/pricing for the requested service.
+
+This skill covers building and releasing iOS and Android apps with EAS: Expo and other React Native projects, plus existing native apps. EAS is a delivery service; native apps can use it without adding Expo or React Native to their runtime. The native setup walkthrough currently covers SwiftUI/UIKit on iOS.
+
+## Choose the project path
+
+- **SwiftUI/UIKit app with no React Native runtime:** read [references/native-ios.md](references/native-ios.md) before changing its build configuration. Keep the Xcode project and Swift code as the app's source of truth. The Expo/React Native quick-start and development-client examples below do not apply to this path.
+- **Native Android app with no React Native runtime:** preserve its existing native build setup. See [references/play-store.md](references/play-store.md) for submission; the Swift/iOS setup instructions do not apply. A dedicated native Android setup walkthrough is not yet included.
+- **Expo/React Native app:** use the quick-start below, then the relevant store reference.
+- **Adding React Native screens to an existing native app:** use `expo-brownfield` for that integration; return here for distribution.
+
+Use the archive and icon checks in [references/native-ios.md](references/native-ios.md) during initial native iOS setup, after changing versioning, bundle IDs, or icons, or when diagnosing a rejected upload. Routine releases follow the EAS build/submit flow and the processing and availability checks in [references/testflight.md](references/testflight.md). A successful EAS build or a queued submission does not establish Apple acceptance, tester access, or an App Store release.
+
+## References
+
+Consult these resources as needed:
+
+- ./references/workflows.md -- CI/CD workflows for automated store releases and PR previews
+- ./references/testflight.md -- Submitting iOS builds to TestFlight for beta testing
+- ./references/app-store-metadata.md -- Managing App Store metadata and ASO optimization
+- ./references/play-store.md -- Submitting Android builds to Google Play Store
+- ./references/ios-app-store.md -- iOS App Store submission and review process
+- ./references/native-ios.md -- Native Swift/SwiftUI/UIKit setup, versioning, and archive verification without an Expo runtime
+
+## Expo / React Native Quick Start
+
+### Install EAS CLI
+
+```bash
+npm install -g eas-cli
+eas login
+```
+
+### Initialize EAS
+
+```bash
+npx eas-cli@latest init
+```
+
+`eas init` links or creates the EAS project. Run `eas build:configure` to create build profiles in `eas.json`; preserve existing project and store identifiers when a release setup already exists.
+
+## Build Commands
+
+### Production Builds
+
+```bash
+# iOS App Store build
+npx eas-cli@latest build -p ios --profile production
+
+# Android Play Store build
+npx eas-cli@latest build -p android --profile production
+
+# Both platforms
+npx eas-cli@latest build --profile production
+```
+
+### Submit to Stores
+
+```bash
+# iOS: Build and submit to App Store Connect
+npx eas-cli@latest build -p ios --profile production --auto-submit
+
+# Android: Build and submit to Play Store
+npx eas-cli@latest build -p android --profile production --auto-submit
+
+# Expo / React Native shortcut for iOS TestFlight
+npx testflight
+```
+
+## Web & API Route Hosting
+
+Deploying an Expo website or Expo Router API routes to EAS Hosting (`npx expo export -p web` then `eas deploy`) is covered by the `eas-hosting` skill. This skill focuses on native app store releases.
+
+## EAS Configuration
+
+Example for an Expo / React Native project (native Swift profiles are in `references/native-ios.md`):
+
+```json
+{
+  "cli": {
+    "version": ">= 16.0.1",
+    "appVersionSource": "remote"
+  },
+  "build": {
+    "production": {
+      "autoIncrement": true,
+      "ios": {
+        "resourceClass": "m-medium"
+      }
+    },
+    "development": {
+      "developmentClient": true,
+      "distribution": "internal"
+    }
+  },
+  "submit": {
+    "production": {
+      "ios": {
+        "appleId": "your@email.com",
+        "ascAppId": "1234567890"
+      },
+      "android": {
+        "serviceAccountKeyPath": "./google-service-account.json",
+        "track": "internal"
+      }
+    }
+  }
+}
+```
+
+## Platform-Specific Guides
+
+### iOS
+
+- For native Swift apps, use the explicit build/submit flow in `references/native-ios.md`
+- For Expo / React Native apps, `npx testflight` provides a quick TestFlight flow
+- Configure Apple credentials via `eas credentials`
+- See ./references/testflight.md for credential setup
+- See ./references/ios-app-store.md for App Store submission
+
+### Android
+
+- Set up Google Play Console service account
+- Configure tracks: internal → closed → open → production
+- See ./references/play-store.md for detailed setup
+
+## Automated Releases
+
+EAS Workflows automate the build → submit → update pipeline for CI/CD. See ./references/workflows.md for store-release examples. To author or validate workflow YAML, use the `eas-workflows` skill - it works from the live workflow schema.
+
+## Version Management
+
+EAS manages version numbers automatically with `appVersionSource: "remote"`:
+
+```bash
+# Check current versions
+eas build:version:get
+
+# Manually set version
+eas build:version:set -p ios
+```
+
+The version-set command prompts for the value. When setting up or changing native iOS versioning, or diagnosing a duplicate build number, inspect the archived `CFBundleVersion`: the remote counter alone does not prove that Xcode used it.
+
+## Monitoring
+
+```bash
+# List recent builds
+eas build:list
+
+# Check build status
+eas build:view BUILD_ID
+
+# Inspect submissions (verified with EAS CLI 23.2.0)
+eas submit:list -p ios --json
+eas submit:view SUBMISSION_ID --json
+```
+
+Check the CLI version before interpreting a missing command: these submission commands are available in 23.2.0 but not in the tested 18.6.0 installation. A pinned `npx eas-cli@23.2.0` invocation can use them without changing the global installation. See `references/testflight.md` for live Apple status and retry guidance. Follow the returned log URLs when the JSON result omits the underlying failure. Report the exact build ID/version and the furthest verified release state.
+
+## Submitting Feedback
+If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
+```bash
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-app-stores" "<actionable feedback>"
+```
+Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/templates/default/apps/mobile/.agents/skills/eas-app-stores/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "EAS App Stores"
+  short_description: "Build and submit iOS and Android apps."
+  default_prompt: "Use $eas-app-stores to set up or verify EAS builds, TestFlight and store submissions, signing, versioning, and store metadata for iOS and Android apps: Expo and other React Native projects, plus existing native apps."