How to collect helpful prompts for AI tutors for coding bootcamp students in 2026

Learn how coding bootcamp students can collect helpful prompts for AI tutors, with steps, tool options, and common mistakes to avoid.

By SupaKeeper · 2026-10-22

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

To collect helpful prompts for AI tutors, save the prompts that worked, note the coding situation each one fits, and keep them somewhere you can search and reuse. Copilot AI Productivity Suite is one option for keeping prompts you can insert into a chat in VS Code. ^[1]

Option	What it can do	What to check
Copilot AI Productivity Suite	Inserts saved prompts into a VS Code chat, and can ask for values for blanks at insert time. ^[1] ^[1]	Free plan at $0 that allows 20 Copilot insertions a week ^[1]; Premium at $6.99 a month with unlimited insertions ^[1].
A shared notes file	Keeps prompts in one place that you can search, if the file format you use supports search.	Check whether it can be shared with classmates and kept current on each machine you use.
Saved-prompt features in your editor or AI tutor	Depends on the feature. Check what it stores and where it is kept.	Check whether the feature works with the editor and course tools you use.

What you need before you start

Before you start, have your editor and your AI tutor ready, and know which one you use for lessons, exercises, and debugging help.

Look back at the prompts that gave you useful answers, such as a request for a hint instead of a full solution, or a request to explain what an error message means. Sort them by the kind of work they helped with, for example a failing test, a confusing function, or a project setup problem.

Note the course, module, or project each prompt came from, so you can find it again during a later assignment. Decide whether the prompts will stay with you alone or also be shared with classmates, because that choice affects which tool fits.

Check that the editor you work in is supported by any tool you consider. Keep your notes short, so the collection stays useful rather than becoming a long pile of text.

Step by step

Gather the prompts you have already used. Include the ones from lessons, pair sessions, and project reviews, even if they were written in a hurry.

Keep only the prompts that produced an answer you could learn from. Remove the ones that gave a full solution with no explanation, since those teach less.

Give each prompt a short name that describes the task, such as 'hint for a loop bug' or 'explain a stack trace'. Clear names make the list easier to search.

Add one line under each prompt that says when to use it and what kind of answer it produces. This helps you pick the right prompt when a deadline is close.

Mark any part of a prompt that changes from one task to the next, such as the language name, the file name, or the error text. Leave those parts as blanks you fill in each time.

Group the prompts by course, module, or project. A group that matches your schedule is easier to return to than one long list.

Review the collection once a week. Remove prompts that no longer help and add the ones that worked on new material.

Share the finished set with classmates only if your bootcamp allows it, and check its rules about sharing course material first.

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]

Typing #copilotsuite followed by a saved prompt's ID inserts that exact saved text into the conversation. ^[1] A saved prompt can include blanks such as ${name} or ${name:default}, and the editor asks you for a value each time you insert it. ^[1]

Saved prompts can sit in nested folders, and several can be bundled into a group that is inserted all at once. ^[1] You can select several prompts to move, delete, or insert together. ^[1] You can pin up to five favorite prompts to the VS Code status bar. ^[1]

Signing in with a one-time code sent by email syncs your saved prompts, groups, and settings across your machines. ^[1] You can export prompts as JSON or make a share link, and teammates can import them. ^[1]

A bundled local server makes your saved prompts available to Claude Code, Codex CLI, and other MCP clients over stdio. ^[1] If you turn it on, each saved 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]

While VS Code telemetry is on, it sends anonymous usage statistics, but never prompt content. ^[1]

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]

Other approaches include a shared notes file or the saved-prompt features already in your editor or AI tutor. Compare what each one can store, whether it can be shared, and how it handles prompts across the machines you use before choosing.

Common mistakes to avoid

Avoid saving prompts without a note about the task they fit. A prompt with no context is hard to choose when a deadline is close.

Avoid collecting every prompt you have ever used. A short set that you actually reuse is more useful than a long one with weak answers.

Avoid vague names such as 'helpful prompt' or 'test'. A name should say what the prompt is for.

Avoid pasting code or private course material into a collection you plan to share. Check your bootcamp's rules first.

Avoid choosing a tool before you know what you need to reuse, sync, or share. Start from the job, then compare the options.

Frequently asked questions

How can coding bootcamp students collect helpful prompts for AI tutors?

Start by gathering prompts that gave you a useful explanation or hint, not a finished answer. Note the task each one fits, give it a clear name, and group the prompts by course or project. Review the set each week to remove weak prompts and add new ones. Keep the collection somewhere you can search, and check your bootcamp's rules before sharing anything with classmates.

What should bootcamp students check before choosing a tool for saved prompts?

Check which tasks the tool can help with, where prompts are stored, and whether you can share them. Confirm that it works in the editor you use and on each machine you work from. Look at how prompts are grouped and searched, since a long collection needs clear names. Finally, check whether the tool needs an account, and read its terms before saving any course material.

Is Copilot AI Productivity Suite free for bootcamp students?

Copilot AI Productivity Suite has 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] Whether either plan fits depends on how often you insert prompts, so count a typical week of work before deciding.

Can Copilot AI Productivity Suite share prompts with classmates?

Copilot AI Productivity Suite can export saved prompts as JSON or make a share link, and teammates can import them. ^[1] Check your bootcamp's rules on sharing course material before you send anything. It can also sync saved prompts across your machines after a sign-in with a one-time code sent by email. ^[1]

Does Copilot AI Productivity Suite send usage data?

While VS Code telemetry is on, Copilot AI Productivity Suite sends anonymous usage statistics, but never prompt content. ^[1] You can check your VS Code telemetry setting to see whether this applies to you. Review that setting in your editor before relying on it, since it is controlled there rather than in this extension.

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)