Add the MacBase badge to my site

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.

Add the "Featured on MacBase" badge to this site. I'll paste the code from my MacBase listing's badge section under this prompt; if I haven't, use the code at macbase.app/badge and tell me to swap in my app's own.

Put it in the footer of every page, or on the home page near the download links if the footer is tiny. Keep the link as given: a plain <a> to my MacBase page, no rel="nofollow", not rendered by JavaScript only, and not inside a lazy wrapper, so a plain fetch of the page sees it. Use the light version on light backgrounds and the dark one on dark, switching with prefers-color-scheme or the site's own theme. Make it about 44 pixels tall with the alt text as given, and add no other link or badge.

When you're done, these should hold:
- `curl -s https://your-site/ | grep macbase.app` finds the link in the HTML as served.
- Both themes show the right version.
- Check my site on your listing turns it verified.

End your summary with the next step: "Press Check my site" (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/add-the-badge.md and do what it says.

What you get

What your project has afterwards

• The badge in the footer of every page, or by the download links
• The light version on light backgrounds and the dark one on dark
• The link as MacBase gave it: a plain, followed link to your listing, in the HTML as served
• About 44 pixels tall, with the alt text
• Nothing else added

Check

When the agent says it’s done

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

• curl -s https://your-site/ | grep macbase.app finds the link in the HTML as served.
• Both themes show the right version.
• Check my site on your listing turns it verified.

The result

A good result to look at

• The badge

  Both versions, and the code

Questions

What people ask

What does the badge do?

A link from your site to macbase.app verifies your listing: a check mark by the name, a place above the unverified apps in every list, a review ahead of the others, and a followed link back to your site. A weekly check keeps it so while the badge stays.

Why not render it with JavaScript?

The check reads your page as served first; it tries again after scripts run, but a plain link in the HTML is found every time, and crawlers see it too.

Can it go somewhere other than the footer?

Anywhere on a public page. The footer is on every page, which is why it’s first. The home page by the download links is next best: people deciding whether to download see it.

More

Other prompts

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