How to keep demo code snippets handy for developer advocates

Learn how developer advocates can keep demo code snippets ready to insert, and compare tools that help with snippet reuse.

By SupaKeeper · 2026-10-25

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

To keep demo code snippets handy, save each demo's code as a named snippet, replace the values that change with placeholders, and group the snippets for each product feature. Store the group where every presenter can reach it, and check that the tool you choose works in the editor and AI chat you already use.

Option	What it can do	What to check
Copilot AI Productivity Suite	Inserts saved snippets into the Copilot conversation by typing #copilotsuite followed by a snippet ID. ^[1]	Check that VS Code is 1.116.0 or newer, or that your editor is Cursor, Windsurf or VSCodium. ^[1]
Snippet file kept in your project	Check its own documentation for what it stores and inserts.	Check how the file is shared with your team and how you insert it into your chat.
Shared team notes page	Check its own documentation for how code is formatted and inserted.	Check who can edit the page and whether it stays current before demos.
Snippet feature in your editor	Check its own documentation for what it can insert.	Check whether it reaches your AI chat and how it works across machines.

What you need before you start

Before you start, know which demos you give most often and the code each one depends on. A developer advocate usually works across a laptop, a sample project, a live coding session and a shared chat, so the snippets need to reach all of them.

Have the editor you use for demos set up on every machine you present from. Keep a short list of the setup commands, sample inputs and expected outputs for each demo, since those are the parts that tend to break first on stage or on a call.

Decide where the snippets will live. A personal file, a shared team notes page and a snippet feature in your editor each suit a different kind of sharing, so pick the one your team already reads.

Mark which values change from one demo to the next, such as a project name, a region or a sample user. Those values are the ones a reusable snippet should ask for when you insert it.

Finally, set aside any keys, tokens or private data. Snippets are easy to copy and share, so keep secrets out of the text you plan to store.

Step by step

Work through these steps in order. Each one applies whichever tool you choose.

List the demos you present most often, and note the code each one needs.

Copy each demo's code into its own snippet, with a clear name you can find by typing a few letters.

Replace the changing values with placeholders, and write a sensible default for each one where you can.

Group related snippets together, such as all the snippets for one product feature.

Choose where each group will live, and make sure every presenter can reach it.

Run each snippet once in a clean project, following its steps from start to finish, so you know it works as written.

Share each group with your team using an export or a link, then check that a teammate can open it and insert the code.

Review the list before each event. Remove snippets for demos that have changed, and rename any that no longer match the feature they show.

Tools that can do it

Copilot AI Productivity Suite is made by the team that publishes this site.

Copilot AI Productivity Suite 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]

Typing #copilotsuite followed by a snippet's ID inserts the exact saved snippet template into the conversation. ^[1] Placeholders like ${name} or ${name:default} in a snippet ask you for a value when the snippet is inserted. ^[1]

Snippets can sit in nested folders, and you can bundle several into a group that is referenced all at once. ^[1] You can select several snippets and move them, delete them or insert all their references at once. ^[1] You can pin up to five favorite snippets to the VS Code status bar. ^[1]

You can export snippets as JSON or make a share link, and teammates can import it. ^[1] If you sign in with an account that uses an emailed one-time code, your snippets, groups and settings sync across your machines. ^[1]

A bundled local MCP server makes your snippets and groups available to Claude Code, Codex CLI and other MCP clients over stdio. ^[1] If you turn it on, each snippet is written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. ^[1]

You can also create and edit Copilot toolsets, custom agents, instruction files and prompt files from the sidebar. ^[1]

Other options include a snippet file kept in your project, a shared notes page, or the snippet feature already in your editor. Check what each one stores, how it inserts code into your chat, and how your team would share it. Compare each option against the job of keeping demo code handy during real presentations.

Common mistakes to avoid

Avoid saving snippets that contain real keys or private data. Copying and sharing spread that text further than you intend, so keep secrets in your own environment instead.

Avoid vague snippet names. A name like 'new code' or 'test' makes it hard to find the right code on stage, so name each snippet after the feature it shows.

Avoid skipping placeholders. A snippet with fixed names and regions forces you to edit code mid-demo, which is a common place for errors.

Avoid sharing a tool's snippets outside your team without reading its licence first. The Copilot AI Productivity Suite extension uses a proprietary licence, and the software is proprietary and confidential to LunarWerx. ^[1]

Avoid relying on a free plan for heavy use. If you use the Free plan, it allows 20 Copilot insertions a week. ^[1] Count how many insertions your demos need before you depend on it.

Avoid leaving a snippet group unreviewed. Check your saved snippets before each event so the code still matches the current version of the demo.

Frequently asked questions

How can developer advocates keep demo code snippets handy?

Save each demo's code as a named snippet, replace the values that change with placeholders, and group the snippets for each product feature. Store the group where every presenter can reach it, and run each snippet once in a clean project so you know it works as written. Review the group before each event, since demo code tends to change between events. These steps apply to any snippet tool, so the choice of tool can follow the steps rather than come first.

Does Copilot AI Productivity Suite keep demo code snippets handy in VS Code?

Copilot AI Productivity Suite is a VS Code extension that needs VS Code 1.116.0 or newer. ^[1] Typing #copilotsuite followed by a snippet's ID inserts the exact saved snippet template into the conversation. ^[1] Snippets can sit in nested folders, and you can bundle several into a group. ^[1] You can also pin up to five favorite snippets to the VS Code status bar. ^[1]

Can Copilot AI Productivity Suite sync demo snippets between machines?

If you sign in with an account that uses an emailed one-time code, your snippets, groups and settings sync across your machines. ^[1] Sign in on each machine you present from, so the same demo code is ready wherever you are. You can also export snippets as JSON or make a share link, and teammates can import it. ^[1] That gives you a second way to share a group with people who are not signed in to the same account.

Is Copilot AI Productivity Suite free for developer advocates?

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1] To choose between them, estimate how many snippets you expect to insert in a typical week, then compare that number with the weekly limit on the Free plan. Heavier presenting weeks may point toward the paid plan.

Does Copilot AI Productivity Suite send usage data from VS Code?

While VS Code telemetry is on, the extension sends anonymous usage statistics, but never snippet content. ^[1] Your VS Code settings control whether telemetry is on, so check those settings if you want to decide what is shared. The extension uses a proprietary licence, and the software is proprietary and confidential to LunarWerx, so read the licence before sharing its output outside your team. ^[1]

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

Try Copilot AI Productivity Suite

Sources

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