This website uses cookies

Read our Privacy policy and Terms of use for more information.

I’ve built more than 35 apps. Only one passed app review on the first try.

Most of my rejections came from small things. The reviewer could not log in. A privacy answer did not match the app. A screenshot showed something that was not ready. The app worked, but the submission missed one detail.

Then I had to fix it, upload a new build, and wait again.

This free App Store Compliance Playbook checks your project before you send it to Apple or Google. You do not need to understand the code inside the repository. Codex or Claude Code can read it and guide you.

Start with the easiest option

Run a one-time check before you install anything. This works in Codex and Claude Code.

Step 1: Open your app project

Open the folder for the app you want to submit in Codex or Claude Code.

You do not need to find a special file. Open the same project folder you use when you build the app.

Step 2: Paste this prompt

Use the free App Store Compliance Playbook from this repository:
https://github.com/mjmirza/app-store-compliance

Check the app project I have open for Apple App Store and Google Play
rejection risks.

Do not change any files yet. Explain every problem in beginner language.
Sort the results into:

1. Fix before submitting
2. Check by hand
3. Looks okay

Tell me the first problem I should fix and why.

The tool will read the repository, look through your app, and give you a short list. You can stop here if you only need one check.

Step 3: Fix the first problem

Paste this next:

Fix the first item under "Fix before submitting."

Show me what you plan to change before you edit anything. Make one fix,
test it, and stop. Explain the result in beginner language.

Work through one problem at a time. Small steps make the changes easier to review.

Step 4: Run the check again

Run the App Store Compliance Playbook check again.

Show me what was fixed, what still needs work, and anything I must check
inside App Store Connect or Google Play Console.

Install it in Codex

Use this setup if you want the playbook available for future app projects.

Open Codex and paste:

Install the App Store Compliance Playbook for Codex from:
https://github.com/mjmirza/app-store-compliance

Clone the repository into ~/repositories/app-store-compliance.
Install its audit skill in ~/.codex/skills/app-store-compliance using the
files and folders listed in the repository README.

Keep the cloned repository so Codex can run its pre-submission guard against
my projects. Do not install Claude Code hooks. Do not submit an app or take
any action on my GitHub account.

Show me what you plan to install first. After I approve it, install it and
run a read-only check on the app project I have open. Explain the results in
beginner language.

After that, open any app project in Codex and paste:

Run the App Store Compliance Playbook against this project.
Start with a read-only check and explain the results in beginner language.

Install it in Claude Code

The repository includes a skill and an automatic pre-submission guard for Claude Code.

Open Claude Code inside your app project and paste:

Set up the App Store Compliance Playbook from:
https://github.com/mjmirza/app-store-compliance

Follow the Claude Code setup instructions in the repository README.
Clone it into ~/repositories/app-store-compliance, install the audit skill,
and install the pre-submission guard.

Show me any change you want to make to my Claude Code settings before you
write it. Do not submit my app and do not take any action on my GitHub account.

After setup, run the first audit on the app project I have open. Explain the
results in beginner language and tell me the first problem I should fix.

After installation, open an app project and type:

/app-store-audit

Claude Code will run the same check again. The guard can also warn you before common app-submission commands.

Reading your results

  • Critical: Stop and fix it before you submit.

  • High: Ask Codex or Claude Code to explain it and show the file involved.

  • Medium: Review it. The tool may need information it cannot see.

Ask the tool to show a source for each warning. The playbook can find risks, but it cannot promise Apple or Google will approve the app.

Five checks you still need to make

  1. Reviewer login: Give the reviewer a working demo account.

  2. Live app services: Make sure the backend and database stay online.

  3. Privacy answers: Match the store privacy forms to the data your app uses.

  4. Account deletion: Test the delete-account button if users can create accounts.

  5. Screenshots and description: Show features that exist in the submitted build.

Codex and Claude Code cannot see every setting in App Store Connect or Play Console. Ask them to walk through these five checks with you before you press Submit.

The bottom line

You do not need to memorize app-store rules. Open your project, share the repository with Codex or Claude Code, and let it show you what to fix.

Start with the one-time prompt. Install the playbook after it earns a place in your toolkit.

If you want help building your first app and getting it ready to launch, join us inside AI Builders. We help non-technical founders turn an idea into a product people can use.

Sources