# Prompts for your coding agent

Canonical page: https://macbase.app/prompts

Tasks to paste into Claude Code, Cursor or Codex with a Mac app’s project open. Each one’s Markdown copy carries the whole prompt, so an agent can be told: read this link and do what it says.

Every prompt starts the same way: “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.”

## Your listing

So the listing is right without typing it.

- [Write my MacBase listing](https://macbase.app/prompts/write-my-listing.md): Drafts 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 needs](https://macbase.app/prompts/check-my-requirements.md): Reads the Xcode project for the minimum macOS, Apple silicon, notarization and languages, and compares it with what the site says.

## Your website

Readable by AI, structured data, and the badge.

- [Make my app’s site readable by AI](https://macbase.app/prompts/ai-readable-site.md): A Markdown copy of every page, llms.txt, llms-full.txt, ai.txt and crawler rules, as macbase.app has.
- [Add structured data for my app](https://macbase.app/prompts/app-structured-data.md): SoftwareApplication JSON-LD built from the site’s real data: price, macOS version, category, no invented ratings.
- [Add the MacBase badge to my site](https://macbase.app/prompts/add-the-badge.md): Puts the badge where the check finds it, in the right version for light and dark, with the link as given.

## Your app

Security and privacy, accessibility, and the next macOS.

- [Audit my app’s security and privacy](https://macbase.app/prompts/security-and-privacy-audit.md): A read-only review of entitlements, the sandbox, secrets, licensing, the updater, network calls and the privacy manifest.
- [Make my app accessible](https://macbase.app/prompts/accessibility-pass.md): Labels, 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 macOS](https://macbase.app/prompts/new-macos-ready.md): Deprecations, a universal build, the new permission prompts, strict concurrency where it’s cheap, and a current release script.

## Your release

Release notes people read.

- [Write release notes people read](https://macbase.app/prompts/release-notes.md): Turns 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.

## Questions

**What are these?**

Tasks for a coding agent, written out. You paste one into Claude Code, Cursor, Codex or any agent that can read your files and run commands, with your Mac app’s project open. The agent reads the project, shows a plan, waits for your OK, and then does the work in your code.

**Are they free?**

Yes, and there’s nothing to sign in to. Copy one, use it, keep the result.

**Do they put MacBase links in my code?**

No. Every prompt tells the agent not to add links, badges or mentions of MacBase unless you ask. The badge prompt is the one exception, and that’s the whole point of it.

**Where do they come from?**

Each one is something MacBase does on its own site (the AI-readable pages, the structured data), asks of a listing (the facts, the screenshots, the badge), or that makes a Mac app better. Where a live example exists, the prompt’s page links to it.

Makers list their apps with their own MCP link, from [Submit](https://macbase.app/submit); assistants look apps up through the [public MCP](https://macbase.app/mcp).
