Get my app ready for the next macOS

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.

Prepare this app for the current macOS SDK and Apple silicon:

- Build with the latest Xcode and SDK, and fix every warning and deprecation that touches the app's behavior, replacing removed APIs with their modern equivalents.
- Make the build universal (arm64 and x86_64), or tell me why it can't be, and check that every dependency ships arm64.
- Adopt the current appearance (sidebar and toolbar styles, SF Symbols, the settings window's layout) only where it's a plain swap.
- Check the app against the recent permission prompts (screen recording, accessibility, local network, folders) so each one has a usage description and the user sees the reason.
- Replace private API use, or write down the risk.
- Move to Swift's strict concurrency where it's cheap, fixing the real data races and noting the rest.
- Update the release scripts to notarytool and the current signing flow.

Keep the deployment target where it is unless a change needs it, and tell me what raising it would gain.

When you're done, these should hold:
- A clean build has no warnings in the app’s own code.
- The app runs its main flow on the latest macOS beta.
- `lipo -info` on the binary lists both architectures, or you know why not.

End your summary with the next step: "Update the requirements 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/new-macos-ready.md and do what it says.

What you get

What your project has afterwards

• A clean build on the latest Xcode and SDK, with deprecated APIs replaced
• A universal binary, or a written reason it can’t be
• The current appearance where a swap is cheap
• A usage description and a visible reason for every permission prompt
• Private API use replaced, or written down
• Strict concurrency where it’s cheap, with the real data races fixed
• Release scripts on notarytool and the current signing flow
• A note on what raising the deployment target would gain

Check

When the agent says it’s done

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

• A clean build has no warnings in the app’s own code.
• The app runs its main flow on the latest macOS beta.
• lipo -info on the binary lists both architectures, or you know why not.

Questions

What people ask

When should I run this?

When a macOS beta is out: that’s when the deprecations and the new prompts land, and it leaves time before the release in the fall. It’s also a good first pass on an app that hasn’t been touched for a year.

Will it raise my deployment target?

Not on its own. The prompt keeps it where it is and tells you what raising it would buy, which APIs and which simplifications, so you decide with the numbers.

Electron, Tauri or Catalyst?

For Electron and Tauri, the equivalent is upgrading the framework and the packager and checking arm64, and the agent does that instead. Catalyst apps follow the same list as native ones.

More

Other prompts

• 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.
• 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.
• Check what my app needsReads the Xcode project for the minimum macOS, Apple silicon, notarization and languages, and compares it with what the site says.
• 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.
• 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.