Getting started with Mdfoundry

Mdfoundry is a native macOS app for browsing, reading, and publishing AI prompts shared by the community. Install it, open it, and you'll know your way around in a minute.

What you can do

• Browse trending prompts, and search or filter the library by tag.
• Read any prompt with its source and rendered view side by side.
• Copy a prompt's Markdown to use in your favorite AI tool.
• Fork a prompt into your own library (sign-in required).
• Publish your own prompts and follow the creators you like.
• Leave tips on a prompt to share how you adapted it.

First steps after install

1. Open Mdfoundry. On first launch macOS may briefly show "verifying" — that's normal for a notarized app, and it only happens once.
2. Browse the community. No sign-in is needed to look around — start with what's trending.
3. Open any prompt. Click it to read the raw Markdown and the rendered version together.
4. Copy or save it. Copy the Markdown to use anywhere, or use "Copy to my library" to keep it (sign-in required).
5. Sign in when you want more. Create an account with an email and password to fork prompts or publish your own.
6. Publish your own. Press ⌘N, or open the Wizard tab, and Mdfoundry walks you through building a clean, reusable prompt.

Import from GitHub

Connect GitHub from the Sources tab in the Mac app and import Markdown prompts and recipes straight from your repos. Mdfoundry asks for read-only access to just the repositories you choose, and everything you import stays private to you until you share it.

By default Mdfoundry shows every .md file in a repo and takes its best guess at what each one is. To curate exactly what gets imported, add a .mdfoundry.yml at the repo root:

items:
  - path: prompts/review.md
    kind: prompt        # optional — prompt or recipe
  - path: recipes/*.md  # globs work; kind is inferred per file

• kind is optional. Resolution order: manifest, then frontmatter kind:, then the path (recipes/ reads as a recipe), then your call at review.
• Titles, tags, and best_with live in each .md file's frontmatter — the manifest only declares what belongs in the library.
• Re-sync any repo from Sources whenever it changes. If you edited your copy, Mdfoundry keeps it and lets you decide.

Invite your team

Team Space is better with teammates in it. Open the People tab (web or the Mac app) and use Invite teammates — each address gets an email with a join link, and a line in your team's TEAM.md. Naming your team happens right in the first invite.

• Invites are email-only. The invitee accepts (or declines) on a single landing page; new folks can create their account from the same link.
• Joining changes what your teammates can see, never what anyone shares: everything stays private until its owner explicitly shares it to Team Space.
• Members can leave anytime; what they shared stays with the team, attributed to them, and their private library goes with them untouched.

Foundries — share a whole workflow

A Foundry is the third unit of sharing: a folder with a README (the roles, the loop, the rules) plus the Recipes and templates that make it work — shared and forked as one unit. The ladder: Prompt → Recipe → Foundry.

Import detects Foundry-shaped folders automatically (a README beside recipes/, prompts/, or templates/), locally and from GitHub. Everything lands private; sharing is always an explicit step, and it tells you exactly what becomes visible. To declare a Foundry in a repo, add a foundries: block to .mdfoundry.yml:

foundries:
  - path: foundries/design-led-agentic-development
    title: Design-led agentic development   # optional — defaults to the README H1
    items:                                   # optional — defaults to all .md inside
      - path: recipes/product-manager.md
        kind: recipe

See the flagship example: Design-led agentic development — the workflow Mdfoundry itself was built with.

Install it

Mdfoundry is a free download for Apple silicon Macs on macOS 12 or later.

Download for Mac · Browse the community · Try the wizard