SupaKeeper Plain comparisons of AI coding tools

How software architects organize prompts for system design

Learn how software architects can keep system design prompts organized, and what to check before choosing a tool that helps with it.

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 organize prompts for system design, gather the prompts you already reuse, group them by the design job each one serves, and keep the set in one place your team can open and search.

OptionWhat it doesWhat to check
Copilot AI Productivity SuiteTyping #copilotsuite followed by a prompt's id inserts that exact saved prompt into the conversation. [1]Check that your VS Code version is 1.116.0 or newer. [1]
Notes files or existing toolsWhatever notes files or views your team already has for prompts.Check how the layout and search handle the prompts you reuse most.

What you need before you start

Before you organize prompts for system design, gather the prompts you already use. Most architects reuse a small set for tasks such as drafting a context section, listing quality attributes, comparing two candidate designs, or breaking a system into components. Collect them from chat history, notes, and the documents where your team keeps design work.

Decide which design jobs the prompts serve. A group named for the job, such as capacity review or service boundaries, is easier to find later than one named after a tool or a date. Know which systems the prompts touch, so you can tell which ones belong to a single system and which apply across the whole organization.

Have a place your team can open. If others will use the prompts, agree on who may change them and how changes are shared. Finally, note the editor and version your team uses, since that decides which tools can hold the prompts you collect.

Step by step

Work through these steps in order, and repeat step 6 as often as your designs change.

  1. Collect the prompts you reuse. Pull them from your recent design work, skip the one-off requests, and keep the ones that produce useful output for your team.
  1. Name each prompt for its job. Use names such as "trade-off comparison" or "failure mode review" so the list reads like a checklist you can scan quickly.
  1. Group prompts by design job. Put prompts for the same kind of decision together, so you can open one group before a design review without searching through everything.
  1. Mark the parts that change. Note where a prompt needs the system name, the expected load, or the constraints, and write those spots as clear placeholders that are easy to fill in each time.
  1. Choose one home for the set. Keep the prompts in a single place that you and your team can reach, rather than scattering them across chats and documents.
  1. Check the list against real work. Run a prompt on a current design question, then note what needs changing in the wording or the placeholders before you save it.
  1. Review and retire prompts on a regular schedule. Remove prompts that no longer match how your team designs systems, and add new ones when a repeated task appears in your work.

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 prompt's id inserts that exact saved prompt into the conversation. [1]

Prompts can sit in nested folders, and you can bundle several into a group that is referenced all at once. [1]

Placeholders like ${name} or ${name:default} in a prompt ask you for a value when the prompt is inserted. [1]

You can select several prompts and move them, delete them or insert all their references at once. [1]

You can pin up to five favorite prompts to the VS Code status bar. [1]

You can export prompts as JSON or make a share link, and teammates can import it. [1]

If you turn it on, each prompt is written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. [1]

The extension includes a local server that lets Claude Code and Codex CLI use your prompts and groups. [1]

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

If you sign in with an account, which uses an emailed one-time code, your prompts, groups and settings sync across your machines. [1]

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

While VS Code telemetry is on, the extension sends anonymous usage statistics, but never saved prompt content. [1]

Other approaches include the notes files and views your team already has, or a separate tool. Compare each option against the job of organizing system design prompts, and check how it handles the prompts you reuse most.

Common mistakes to avoid

Avoid collecting every prompt you have ever written. A long list with no grouping is harder to search than a short set of prompts for the design jobs you repeat.

Avoid vague names. A prompt called "new prompt 2" does not tell you when to use it, so name each one for the job it does.

Avoid skipping placeholders. A prompt that hard codes one system's name will give poor output when used on another, so mark the parts that change.

Avoid keeping the set in one personal place when others need it. Agree on a shared home and on who can change the prompts.

Avoid choosing a tool without checking your editor and version. A tool that does not run in your environment will not help with the set you have built.

Avoid never reviewing the list. Prompts that fit one design approach may not fit the way your team works now.

Frequently asked questions

How do software architects organize prompts for system design?

Start by collecting the prompts you already reuse, such as requirement reviews, trade-off comparisons and component breakdowns. Group them by the design job they serve, give each one a name that says its purpose, and keep the groups in one place your team can open. Review the set from time to time so that outdated prompts do not spread through the team's design work.

Does Copilot AI Productivity Suite work in VS Code?

Copilot AI Productivity Suite is a VS Code extension that needs VS Code 1.116.0 or newer. [1] It is also on Open VSX for Cursor, Windsurf and VSCodium. [1] Saved prompts can be inserted into the conversation by typing #copilotsuite followed by the prompt's id. [1] Check that your editor and version match before you start.

Is Copilot AI Productivity Suite free to use?

The Free plan costs $0 and allows 20 Copilot insertions a week. [1] Premium costs $6.99 a month and has unlimited Copilot insertions. [1] Consider how many prompts you insert in a typical week before you decide which option suits your work.

Does Copilot AI Productivity Suite keep saved prompts in sync across machines?

If you sign in with an account, which uses an emailed one-time code, your prompts, groups and settings sync across your machines. [1] The extension also includes a local server that lets Claude Code and Codex CLI use your prompts and groups. [1] If you want sync, check that you are comfortable signing in before you rely on it.

What telemetry does Copilot AI Productivity Suite send?

While VS Code telemetry is on, the extension sends anonymous usage statistics, but never saved prompt content. [1] Review your VS Code telemetry setting if you want to control what is shared from your editor.

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