@kennethsolomon/shipkit 1.0.0

package/skills/sk:laravel-new/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: sk:laravel-new
+description: "Scaffold a fresh Laravel app and configure it with opinionated production-ready conventions. Usage: /laravel-new [project-name]"
+---
+
+# /laravel-new
+
+Scaffold a fresh Laravel application and immediately configure it with production-ready conventions.
+
+## Steps
+
+### 1. Get Project Name
+If no argument was provided, ask: "What should the project be named?"
+
+### 2. Check Prerequisites
+Verify these are available:
+```bash
+which composer
+which laravel  # or: composer global show laravel/installer
+```
+If `laravel` installer is missing: `composer global require laravel/installer`
+
+### 3. Scaffold the App
+```bash
+laravel new {{PROJECT_NAME}}
+```
+
+When prompted by the Laravel installer:
+- Starter kit: choose based on user preference (ask if not specified — Inertia+React, Inertia+Vue, Livewire, or None/API)
+- Testing framework: **Pest** (always)
+- Database: ask user (default: SQLite for local dev)
+- Run migrations: yes
+
+### 4. Enter the Project Directory
+```bash
+cd {{PROJECT_NAME}}
+```
+
+### 5. Run /laravel-init
+Immediately invoke the `setup-claude` skill to configure the project:
+- Detect stack from what was just installed
+- Install missing dev tools (PHPStan/Larastan, Rector, Pint)
+- Publish config files
+- Configure strict models
+- Generate CLAUDE.md
+- Bootstrap tasks/ files
+
+### 6. Report
+Show a summary:
+```
+Project: {{PROJECT_NAME}}
+Stack: [detected]
+Location: [path]
+
+Files created:
+  CLAUDE.md
+  phpstan.neon
+  rector.php
+  pint.json
+  tasks/findings.md (pre-seeded)
+  tasks/lessons.md
+  tasks/todo.md
+  tasks/progress.md
+  .claude/commands/sk:lint.md
+  .claude/commands/sk:test.md
+
+Next step: /sk:brainstorm
+```

package/skills/sk:lint/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: sk:lint
+description: "Auto-detect and run all linting tools: formatters first (sequential), then analyzers in parallel. Fix and re-run until clean."
+---
+
+# /sk:lint
+
+Auto-detect project linting tools, run them, fix issues, repeat until clean.
+
+## Steps
+
+### 1. Read Project CLAUDE.md
+
+Check for project-specific lint configuration or overrides in `CLAUDE.md` before proceeding.
+
+### 2. Detect Stacks
+
+Scan the project root for config files. Enable every matching stack:
+
+| Config file | Stack | Formatter | Analyzers |
+|---|---|---|---|
+| `composer.json` with pint | Laravel/PHP | `vendor/bin/pint --dirty` | -- |
+| `composer.json` with phpstan | Laravel/PHP | -- | `vendor/bin/phpstan analyse --memory-limit=512M` |
+| `composer.json` with rector | Laravel/PHP | -- | `vendor/bin/rector --dry-run` |
+| `package.json` with prettier | Node/TS | `npx prettier --write .` | -- |
+| `package.json` with eslint | Node/TS | -- | `npx eslint .` |
+| `pyproject.toml` with ruff | Python | `ruff format .` | `ruff check .` |
+| `go.mod` | Go | `gofmt -w .` | `golangci-lint run` |
+| `Cargo.toml` | Rust | `cargo fmt` | `cargo clippy` |
+
+Detection logic:
+- For `composer.json`: read `require-dev` keys for `laravel/pint`, `phpstan/phpstan`, `rector/rector`
+- For `package.json`: read `devDependencies` keys for `eslint`, `prettier`
+- For `pyproject.toml`: check `[tool.ruff]` section or `ruff` in `[project.optional-dependencies]` / `[build-system]`
+- For `go.mod` / `Cargo.toml`: presence of file is sufficient
+
+Print detected stacks and tools before running anything.
+
+### 3. Run Formatters — Sequential
+
+Formatters modify files, so run them one at a time in this order:
+
+1. **Pint** (if detected): `vendor/bin/pint --dirty`
+2. **Prettier** (if detected): `npx prettier --write .`
+3. **ruff format** (if detected): `ruff format .`
+4. **gofmt** (if detected): `gofmt -w .`
+5. **cargo fmt** (if detected): `cargo fmt`
+
+After each formatter, note which files changed. All formatters must finish before step 4.
+
+### 4. Run Analyzers — Parallel Sub-Agents
+
+Launch all detected analyzers in parallel using the Agent tool in a single message:
+
+- **PHPStan**: `vendor/bin/phpstan analyse --memory-limit=512M`
+- **Rector**: `vendor/bin/rector --dry-run`
+- **ESLint**: `npx eslint .`
+- **ruff check**: `ruff check .`
+- **golangci-lint**: `golangci-lint run`
+- **cargo clippy**: `cargo clippy`
+
+Example with PHPStan + Rector + ESLint detected:
+```
+Agent 1: "Run vendor/bin/phpstan analyse --memory-limit=512M. Report all errors with file:line."
+Agent 2: "Run vendor/bin/rector --dry-run. Report all suggested changes with file:line."
+Agent 3: "Run npx eslint . Report all errors with file:line."
+```
+
+### 5. Fix and Re-run
+
+If any analyzer reports errors:
+1. Fix all reported issues
+2. Re-run formatters (fixes may need formatting)
+3. Re-launch all analyzers in parallel
+4. Loop until every tool exits clean
+
+### 6. Report Results
+
+Print one line per tool:
+
+```
+Pint:          X files formatted / clean
+Prettier:      X files formatted / clean
+ruff format:   X files formatted / clean
+gofmt:         X files formatted / clean
+cargo fmt:     X files formatted / clean
+PHPStan:       X errors fixed / clean
+Rector:        X changes applied / clean
+ESLint:        X errors fixed / clean
+ruff check:    X issues fixed / clean
+golangci-lint: X issues fixed / clean
+cargo clippy:  X warnings fixed / clean
+```
+
+Only include lines for detected tools. All must show "clean" before this skill passes.
+
+---
+
+## Model Routing
+
+Read `.shipkit/sk:config.json` from the project root if it exists.
+
+- If `model_overrides["sk:lint"]` is set, use that model — it takes precedence.
+- Otherwise use the `profile` field. Default: `balanced`.
+
+| Profile | Model |
+|---------|-------|
+| `full-sail` | sonnet |
+| `quality` | sonnet |
+| `balanced` | haiku |
+| `budget` | haiku |
+
+> `opus` = inherit (uses the current session model). When spawning sub-agents via the Agent tool, pass `model: "<resolved-model>"`.

package/skills/sk:perf/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/skills/sk:perf/SKILL.md

@@ -0,0 +1,188 @@
+---
+name: sk:perf
+description: Performance audit. Use before /sk:review to catch performance issues: bundle size, N+1 queries, slow DB queries, Core Web Vitals, memory leaks, caching opportunities. Auto-detects stack. Reports findings — does NOT fix code.
+license: Complete terms in LICENSE.txt
+---
+
+## Purpose
+
+Audit the implementation for performance issues before the final review. This is an audit skill — it identifies issues and produces a findings report. It does NOT fix code.
+
+Run this skill after implementing and passing lint/tests, but before `/sk:review`.
+
+## Hard Rules
+
+- **DO NOT fix code.** Report only. The user decides what to fix.
+- **Every finding must cite a specific file and line number.**
+- **Every finding must include an estimated impact** (high/medium/low) and a recommendation.
+- **Auto-detect the stack** — only run checks relevant to what's present.
+
+## Before You Start
+
+1. Detect the stack: read `CLAUDE.md`, check for `package.json`, `composer.json`, `go.mod`, `requirements.txt`, `Cargo.toml`, etc.
+2. Determine scope: `git diff main..HEAD --name-only` to find changed files.
+3. If `tasks/perf-findings.md` exists, read it — check if prior findings have been addressed.
+4. If `tasks/lessons.md` exists, read it — apply performance-related lessons.
+
+## Stack Detection
+
+| Indicator | Checks to run |
+|-----------|--------------|
+| `package.json` with React/Next/Vue | Frontend bundle, render performance, Core Web Vitals |
+| `package.json` with Express/Node | Node.js backend performance |
+| `composer.json` (Laravel/PHP) | PHP/Laravel backend performance |
+| `go.mod` | Go performance checks |
+| `requirements.txt` / `pyproject.toml` | Python performance checks |
+| Any ORM detected | Database query performance |
+
+## Audit Checklist
+
+### Frontend Performance
+
+**Bundle & Loading**
+- Unused imports or dependencies included in the bundle
+- Large dependencies that could be code-split or lazy-loaded
+- Images without lazy loading (`loading="lazy"`) or without `width`/`height` attributes
+- Fonts without `font-display: swap` or preloaded without need
+- No tree-shaking unfriendly imports (`import * from` large libraries)
+
+**Render Performance**
+- React: missing `memo`, `useMemo`, `useCallback` on expensive operations in hot render paths
+- React: unnecessary re-renders from unstable object/array/function references passed as props
+- React: large lists without virtualization (`react-window` or similar)
+- Synchronous operations blocking the main thread (large loops, heavy computation in render)
+- Missing Suspense boundaries for code-split routes
+
+**Core Web Vitals**
+- LCP (Largest Contentful Paint): hero image/text not prioritized, no preload hint
+- CLS (Cumulative Layout Shift): images/embeds without reserved dimensions, dynamic content inserted above existing content
+- INP (Interaction to Next Paint): heavy click/input event handlers, no debouncing on frequent events
+
+### Backend Performance
+
+**Database (all ORMs)**
+- N+1 query patterns: loops that query inside a loop without eager loading
+- Missing indexes on foreign keys, frequently filtered columns, or join columns
+- `SELECT *` where only specific columns are needed
+- Unindexed `WHERE` clauses on large tables
+- Missing pagination on endpoints that return collections
+- Queries inside loops that could be batched
+
+**Laravel-Specific**
+- Missing `with()` eager loading on Eloquent relationships
+- `all()` on large tables without `limit()`/`paginate()`
+- Expensive operations not queued (emails, notifications, file processing)
+- Missing cache on expensive repeated queries
+- Missing database indexes defined in migrations
+
+**Node.js-Specific**
+- Blocking `fs.readFileSync` / `execSync` in request handlers
+- Missing connection pooling on database clients
+- Unbounded promise arrays (`Promise.all` on thousands of items)
+- Memory leaks from event listeners not removed
+
+**Go-Specific**
+- Missing goroutine cleanup (goroutine leaks)
+- Repeated allocations in hot paths that could use `sync.Pool`
+- Blocking operations in goroutines without context cancellation
+
+**General Backend**
+- Missing HTTP response caching headers (`Cache-Control`, `ETag`) on static/infrequently-changing resources
+- Missing compression (gzip/brotli) on text responses
+- API responses without pagination on collection endpoints
+- Expensive computations not cached (Redis, in-memory, etc.)
+- External API calls in the critical path without timeout or circuit breaker
+
+### Memory & Reliability
+
+- Memory leaks: global caches/maps that grow without bounds
+- Missing cleanup in component unmount / service shutdown
+- Large objects held in memory longer than needed
+- Recursive functions without memoization on repeated inputs
+
+## Severity Levels
+
+- **Critical**: Will cause production degradation at scale (N+1 on large table, unbounded memory growth)
+- **High**: Measurable user-facing impact (LCP > 2.5s, missing pagination, blocking I/O in handler)
+- **Medium**: Noticeable but not breaking (unnecessary re-renders, missing cache on moderate traffic)
+- **Low**: Best practice / minor optimization (missing `loading="lazy"`, minor bundle bloat)
+
+## Generate Report
+
+Write findings to `tasks/perf-findings.md`:
+
+```markdown
+# Performance Audit — YYYY-MM-DD
+
+**Scope:** Changed files on branch `<branch-name>`
+**Stack:** [detected stack]
+**Files audited:** N
+
+## Critical
+
+- **[FILE:LINE]** Description
+  **Impact:** What happens at scale
+  **Recommendation:** How to fix
+
+## High
+
+- **[FILE:LINE]** Description
+  **Impact:** ...
+  **Recommendation:** ...
+
+## Medium
+
+- **[FILE:LINE]** Description
+  **Recommendation:** ...
+
+## Low
+
+- **[FILE:LINE]** Description
+  **Recommendation:** ...
+
+## Passed Checks
+
+- [Categories with no findings]
+
+## Summary
+
+| Severity | Count |
+|----------|-------|
+| Critical | N |
+| High     | N |
+| Medium   | N |
+| Low      | N |
+| **Total** | **N** |
+```
+
+**Never overwrite** `tasks/perf-findings.md` — append new audits with a date header.
+
+## When Done
+
+Tell the user:
+
+> "Performance audit complete. Findings saved to `tasks/perf-findings.md`.
+> - **Critical:** N | **High:** N | **Medium:** N | **Low:** N
+>
+> Address critical and high findings, then run `/sk:review` to proceed."
+
+If there are no critical or high findings:
+> "No critical or high performance issues found. N medium/low findings noted in `tasks/perf-findings.md`. Run `/sk:review` to proceed."
+
+---
+
+## Model Routing
+
+Read `.shipkit/sk:config.json` from the project root if it exists.
+
+- If `model_overrides["sk:perf"]` is set, use that model — it takes precedence.
+- Otherwise use the `profile` field. Default: `balanced`.
+
+| Profile | Model |
+|---------|-------|
+| `full-sail` | opus (inherit) |
+| `quality` | sonnet |
+| `balanced` | sonnet |
+| `budget` | haiku |
+
+> `opus` = inherit (uses the current session model). When spawning sub-agents via the Agent tool, pass `model: "<resolved-model>"`.

package/skills/sk:release/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: sk:release
+description: "Automate releases: bump version, update CHANGELOG, create git tag, push to GitHub. Supports --android and --ios flags to run a full App Store / Play Store readiness audit before release — checks configs, permissions, signing, icons, store listing requirements, and guides you step-by-step through fixes. Use this whenever someone wants to release, publish, deploy, or submit an app to the App Store, Play Store, Google Play, or Apple App Store."
+---
+
+# Release Automation Skill
+
+Automate the release process with optional mobile store submission review.
+
+## Modes
+
+| Invocation | What happens |
+|---|---|
+| `/sk:release` | Git release only: version bump, CHANGELOG, tag, push |
+| `/sk:release --android` | Git release + Play Store readiness audit |
+| `/sk:release --ios` | Git release + App Store readiness audit |
+| `/sk:release --android --ios` | Git release + both store audits |
+
+## Step 1: Detect Flags
+
+Parse the user's invocation for `--android` and/or `--ios` flags.
+
+- If **no flags**: run the standard git release flow (Step 2 only)
+- If **flags present**: run Step 2 (git release), then Step 3 (store audit for each flag)
+
+## Step 2: Standard Git Release
+
+Run the existing release script (`release.sh`) which handles:
+
+1. Auto-detect project info (name, version, GitHub URL)
+2. Prompt for new version number (semver)
+3. Update CHANGELOG.md ([Unreleased] -> [Version])
+4. Update version in CLAUDE.md
+5. Create git commit + annotated tag
+6. Push tag to GitHub
+
+If no flags were passed, stop here.
+
+## Step 3: Mobile Store Audit
+
+When `--android` or `--ios` flags are present, run the store readiness audit AFTER the git release completes.
+
+### 3a. Auto-Detect Framework
+
+Detect the mobile framework by checking for these files (in order):
+
+| Check | Framework |
+|---|---|
+| `app.json` or `app.config.js` or `app.config.ts` with `"expo"` key | **Expo** |
+| `react-native.config.js` or `node_modules/react-native` | **React Native (bare)** |
+| `pubspec.yaml` with `flutter` dependency | **Flutter** |
+| `build.gradle` + `AndroidManifest.xml` (no RN/Flutter markers) | **Native Android (Kotlin/Java)** |
+| `*.xcodeproj` or `*.xcworkspace` (no RN/Flutter markers) | **Native iOS (Swift/ObjC)** |
+| `.NET MAUI` or `maui` in csproj | **.NET MAUI** |
+| `capacitor.config.ts` or `capacitor.config.json` | **Capacitor/Ionic** |
+
+Report the detected framework to the user. If detection fails, ask them.
+
+### 3b. Detect Store History
+
+Check if the app has been previously submitted:
+
+- **Android**: Look for `android/app/sk:release/` builds, `google-services.json`, existing `sa_key.json` (service account), or `android/app/build.gradle` with a `versionCode` > 1
+- **iOS**: Look for existing provisioning profiles in `ios/`, `ExportOptions.plist`, or `app.json` with an existing `bundleIdentifier` that follows reverse-domain convention with a real domain
+
+Report whether this appears to be a **first-time submission** or an **update to an existing app**.
+
+### 3c. Run the Audit
+
+Based on the detected flags, read and execute the corresponding checklist:
+
+- `--android`: Read `references/android-checklist.md` and walk through every section
+- `--ios`: Read `references/ios-checklist.md` and walk through every section
+
+For each checklist item:
+
+1. **Check** — Read the relevant config file and evaluate the requirement
+2. **Report** — Tell the user the status (PASS / FAIL / WARN / MANUAL CHECK NEEDED)
+3. **Fix** — If it's a config issue you can fix, propose the fix and apply it with user approval
+4. **Guide** — If it requires manual action (screenshots, store listing, etc.), give clear step-by-step instructions
+
+### 3d. Summary Report
+
+After completing the audit, present a summary:
+
+```
+## Store Readiness Report
+
+### Android (Play Store)     <-- if --android
+- [x] App signing configured
+- [x] Version code incremented
+- [ ] Privacy policy URL missing  <-- actionable items
+- [ ] Store listing screenshots needed
+
+### iOS (App Store)           <-- if --ios
+- [x] Bundle ID configured
+- [x] Info.plist permissions
+- [ ] App Transport Security exception needs justification
+
+### Next Steps
+1. Fix the items marked above
+2. [Framework-specific build command]
+3. [Framework-specific submit command]
+```
+
+## Important Behaviors
+
+- Always check files before suggesting changes — never assume config values
+- For first-time submissions, include account setup guidance (Developer Console / App Store Connect)
+- For Expo projects, prefer EAS Build/Submit commands over manual native builds
+- Be explicit about costs ($25 Google Play one-time fee, $99/year Apple Developer Program)
+- When fixing config files, show the diff and get approval before applying
+- If both `--android` and `--ios` are passed, run Android audit first, then iOS