Write my MacBase listing

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 this project, and the app's website if it's in here or linked from the README, and draft my listing for MacBase (macbase.app), a directory of Mac apps. Write it to MACBASE_LISTING.md with these fields:

- Name: as the app calls itself, up to 40 characters.
- Tagline: one line of up to 60 characters saying what the app does. Plain words, no slogan.
- Description: 80 to 4000 characters in paragraphs. What it does, who it's for, and what sets it apart. No list of more than five features and no superlatives.
- Categories: the main one, and up to two more, from macbase.app/categories.md (read it if you can; otherwise name the closest ones).
- Alternatives: up to four well-known Mac apps people would use instead, by name.
- Price: free, free with paid features, one-time or subscription, with the amount, the billing period and any free trial, taken from the code (StoreKit, Paddle, Lemon Squeezy, RevenueCat) or the site.
- Requirements: the minimum macOS from the deployment target; Apple silicon native or Intel only from the build settings; notarized, or on the Mac App Store; open source, with the repository, if the license says so.
- Languages: the localizations in the project (.lproj folders or an .xcstrings catalog), as language names.
- Links: website, Mac App Store, direct download, GitHub, and the social accounts the site links to.
- Screenshots: the images in the project or on the site that show the app itself, at 16:10 (a Mac screen's shape) and at least 1280 pixels wide. No banners or share images. Say which three to six to use and in what order, the main window first.
- Video: a YouTube or Vimeo link, if there is one.

Write "unknown" for anything you can't find rather than guessing.

When you're done, these should hold:
- Every field has a source in the code or on the site; nothing is made up.
- The tagline fits 60 characters and says what the app does.
- The screenshots show the app, not a banner.

End your summary with the next step: "List it with your MCP link" (https://macbase.app/submit#mcp).

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/write-my-listing.md and do what it says.

What you get

What your project has afterwards

• MACBASE_LISTING.md in your project, with every field a listing has
• A tagline of 60 characters or fewer that says what the app does
• A description in paragraphs, 80 to 4000 characters, with no superlatives
• The price, billing and trial read from StoreKit, Paddle, Lemon Squeezy or RevenueCat
• The minimum macOS, Apple silicon and notarization read from the build settings
• The languages read from the .lproj folders or the strings catalog
• Three to six screenshots picked and put in order, the main window first
• “unknown” wherever the code doesn’t say, instead of a guess

Check

When the agent says it’s done

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

• Every field has a source in the code or on the site; nothing is made up.
• The tagline fits 60 characters and says what the app does.
• The screenshots show the app, not a banner.

The result

A good result to look at

• Vitals on MacBase

  A listing with every field filled

• The same listing as Markdown

  What an agent reads

Questions

What people ask

Does it list the app for me?

Not this prompt: it writes the draft to a file so you read it first. Listing takes your own MCP link, from Submit. Paste it into the same agent and say: List my app on MacBase from MACBASE_LISTING.md. The listing is then reviewed like any other.

My code is private. Does any of it leave my Mac?

The agent runs on your Mac with your project, and the draft is a file in it. Nothing reaches MacBase until you list the app, and then only the listing’s fields.

Where do the categories and alternatives come from?

The categories from macbase.app/categories.md, the live list, when the agent can read links; otherwise it names the closest ones and you pick on the form. Alternatives are well-known Mac apps by name, which MacBase matches to its list.

Why no superlatives?

A listing is reviewed before it goes live, and marketing copy is the usual reason one is sent back. Plain words about what the app does pass the first time.

More

Other prompts

• 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.
• 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.