SupaKeeper Plain comparisons of AI coding tools

How to share prompt templates with developer advocates in 2026

Learn how developer advocates can share prompt templates with a community, what to prepare, and which tools help with sharing and reuse.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, the makers of AgentHydra, Copilot AI Productivity Suite, Codex Forecast and Model Odds, which are compared here alongside other tools.

To share prompt templates with a community, prepare clear templates with marked fields, choose a place to hand them out, and set up a simple routine for updates.

OptionWhat it doesWhat to check
Copilot AI Productivity SuiteYou can export templates as JSON or make a share link, and teammates can import them. [1]Check that your editor is a VS Code-family editor, and whether the proprietary licence suits how you share.
Shared repositoryNo published details cover how a shared repository handles access or edits.Check how members get access, how changes are proposed, and whether readers can copy the files.
Shared folderNo published details cover how a shared folder handles access or edits.Check who can edit, how files are named, and how new members find the set.
Separate prompt library toolNo published details cover what a separate prompt library tool supports.Check which assistants it supports, how templates are shared, and what it costs.

What you need before you start

Before you share prompt templates with a community, have the templates themselves ready. Each one should state its purpose in a line, and any part that changes from person to person should be marked as a field the reader fills in, such as a name or a product name. A template that is clear to its author can still confuse a newcomer, so read each one as a reader who has never seen it would.

Decide who the community is and what they are allowed to do with the templates. Some groups want to copy and edit, while others only want to read. Know where the templates will live, and who will keep them current when models or tools change.

Gather example outputs that show what a good result looks like. Readers learn faster when they can compare a template with a sample answer. Also keep a short note on which tools each template was written for, since a prompt that works in one assistant may need changes in another.

Finally, decide how feedback will reach you. A simple place to collect questions and fixes keeps the templates useful after they are shared.

Step by step

  1. Pick a small set of templates that each solve one clear task. Remove any that depend on private data or unfinished work.
  1. Write a title and a one-sentence purpose for each template. Readers should know what it does before they open it.
  1. Mark every part that changes, such as a name, a file or a product, so it is easy to spot and replace.
  1. Add one example input and one example output to each template. This shows the expected result and makes mistakes easier to notice.
  1. Ask someone outside your team to try each template, and note where they get stuck. Edit the wording until the steps are clear without extra explanation.
  1. Choose where the set will be shared. This can be a shared folder, a repository, a tool built for prompt libraries, or an editor extension that can export and import saved templates.
  1. Put a short note at the top of the set that explains how to use it, who maintains it, and how to report a problem.
  1. Set a regular time to review the set. Remove templates that no longer work and add new ones that readers ask for.
  1. Credit authors clearly. Community members share more when their work is visible.

Tools that can do it

Copilot AI Productivity Suite is made by the team that publishes this site. It is a VS Code extension that needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. [1] You install it from the VS Code Marketplace as LunarWerx.copilot-suite. [1]

Saved prompt templates can sit in folders inside other folders, and you can bundle several together so they are referenced all at once. [1] Fields you fill in, such as a name or a product name, ask for a value at the moment a template is inserted. [1] Typing a slash command with a template's ID in Copilot Chat inserts that exact saved text into the conversation. [1]

To share, you can export templates as JSON or make a share link, and teammates can import them. [1] Signing in with an account, using an emailed one-time code, keeps templates, bundles and settings in sync across your machines. [1] The extension uses a proprietary licence, and the software is proprietary and confidential to LunarWerx. [1]

The Free plan costs $0 and allows 20 insertions a week with its Copilot feature. [1] Premium costs $6.99 a month and has unlimited Copilot insertions. [1]

Other approaches include a shared repository, a shared folder, or a separate prompt library tool. The facts available for this page do not describe what those options support, so compare each one on the sharing, access and import points in the table.

Common mistakes to avoid

Avoid sharing templates that depend on private data, such as internal names, keys or customer details. Remove them before publishing the set.

Avoid unclear placeholders. A reader who sees a bare word in brackets may not know what to replace it with.

Avoid sharing a set that has no owner. A set nobody updates will drift out of date as tools change.

Avoid assuming one tool fits every reader. Community members may use different assistants or editors, so check what each template expects.

Avoid skipping examples. A template without a sample output leaves readers guessing about what a good result looks like.

Frequently asked questions

How can developer advocates share prompt templates with a community?

Developer advocates can share prompt templates by preparing clear templates with marked fields, placing them in a shared location, and explaining how to use each one. The sharing method matters less than keeping the set readable and current. Start with a few templates, add an example output to each, and review the set on a regular schedule so readers can rely on it.

What should be ready before sharing prompt templates with a community?

Have each template's purpose, its fields to fill in, and at least one example output written down. Decide who the community is, what they may copy or change, and who will maintain the set. A short note on which tools each template was written for helps readers avoid surprises. Remove anything that exposes private data before the set is shared.

Can Copilot AI Productivity Suite share templates with teammates?

Copilot AI Productivity Suite can export templates as JSON or make a share link, and teammates can import them. [1] Templates can also sit in nested folders and be bundled into groups, which helps keep a shared set organized. [1] Check whether the sharing method fits how your community reads and edits the files.

Does Copilot AI Productivity Suite cost money?

The Free plan costs $0 and allows 20 insertions a week with the Copilot feature of Copilot AI Productivity Suite. [1] Premium costs $6.99 a month and has unlimited Copilot insertions. [1] Check which plan covers the number of insertions your community needs before you choose.

Does Copilot AI Productivity Suite send usage data?

While VS Code telemetry is on, Copilot AI Productivity Suite sends anonymous usage statistics, but never the content of your templates. [1] Whether usage statistics are sent therefore depends on your VS Code telemetry setting. Check that setting before asking community members to install the extension.

There is a Free plan at $0 that allows 20 Copilot insertions a week. [1]

Try Copilot AI Productivity Suite

Sources

  1. Copilot AI Productivity Suite's own description of itself (the product of this site's publisher)

Related comparisons