Check what my app needs

Read my project before you change anything. Tell me what you found and what you'd do, as a short plan, and wait for my OK. Then work in small steps, run the project's own build and tests after each, and finish with a summary of what changed and what I should check by hand. Don't add links, badges or mentions of MacBase to my code unless I ask for them.

Read the Xcode project (or the Package.swift, Tauri or Electron configuration) and tell me, with the file and line for each:

- The minimum macOS: MACOSX_DEPLOYMENT_TARGET, or LSMinimumSystemVersion in the Info.plist.
- Whether release builds run natively on Apple silicon: ARCHS and EXCLUDED_ARCHS, and any dependency or binary that is x86_64 only.
- Whether release builds are signed with a Developer ID and notarized (hardened runtime on, a notarization step in the release script or CI), or go to the Mac App Store.
- The sandbox and the entitlements.
- The localizations: .lproj folders or an .xcstrings catalog.

Compare that with what the website and the App Store listing say, and list every mismatch. Fix only what I confirm: for example, add arm64 to the build, change the deployment target, or add a notarization step to the release script with notarytool. Write the facts to REQUIREMENTS.md in plain words, as they'd read on a listing: "macOS 13 or later. Apple silicon native. Notarized. In English, German and Japanese."

When you're done, these should hold:
- A release build runs on an Apple silicon Mac without Rosetta: `file` on the binary lists arm64.
- `spctl -a -vv` on the built app says it’s a notarized Developer ID app.
- The site says the same minimum macOS as the project.

End your summary with the next step: "Put the facts on your listing" (https://macbase.app/dashboard).

Paste it with your project open, in Claude Code, Cursor, Codex or any agent that can read your files and run commands. Add anything the agent should know about your app after it. The Markdown copy of this page has the same text.

One line

Or hand the agent a link

For an agent that can read a link. It fetches the whole prompt from the Markdown copy.

Read https://macbase.app/prompts/check-my-requirements.md and do what it says.

What you get

What your project has afterwards

• REQUIREMENTS.md with the facts in plain words, as they read on a listing
• The minimum macOS, with the setting that decides it
• Whether a release build runs natively on Apple silicon, and which dependency stops it if not
• Whether release builds are notarized, or go through the Mac App Store
• The sandbox and the entitlements, listed
• The localizations, as language names
• Every mismatch between the project and what the website or the App Store listing says

Check

When the agent says it’s done

The prompt ends with these; the agent should say how each holds.

• A release build runs on an Apple silicon Mac without Rosetta: file on the binary lists arm64.
• spctl -a -vv on the built app says it’s a notarized Developer ID app.
• The site says the same minimum macOS as the project.

The result

A good result to look at

• How the facts read on a listing

  macOS version, Apple silicon, notarized, languages

Questions

What people ask

Why does MacBase care about these?

Every listing shows the minimum macOS, whether the app is native on Apple silicon, whether it’s notarized, and its languages, and people filter by them. A wrong fact sends someone to an app that won’t run on their Mac.

Does it change my build?

Only what you confirm. The first pass reads and reports. Adding arm64, changing the deployment target or adding notarization to the release script are each offered, not done.

My app is Electron or Tauri. Does it work?

Yes. The agent reads the packager’s configuration instead of an Xcode project. The facts are the same, and so is the listing.

More

Other prompts

• Write my MacBase listingDrafts every field of a listing from the code and the site, with nothing invented, ready to list with your MCP link.
• Make my app’s site readable by AIA Markdown copy of every page, llms.txt, llms-full.txt, ai.txt and crawler rules, as macbase.app has.
• Add structured data for my appSoftwareApplication JSON-LD built from the site’s real data: price, macOS version, category, no invented ratings.
• Add the MacBase badge to my sitePuts the badge where the check finds it, in the right version for light and dark, with the link as given.
• Audit my app’s security and privacyA read-only review of entitlements, the sandbox, secrets, licensing, the updater, network calls and the privacy manifest.
• Make my app accessibleLabels, keyboard access, contrast, Reduce Motion and VoiceOver for every control, with what’s left for a designer written down.
• Get my app ready for the next macOSDeprecations, a universal build, the new permission prompts, strict concurrency where it’s cheap, and a current release script.
• Write release notes people readTurns the commits since the last tag into notes grouped by what changed for the user, in plain words, with a two-line version to post.