A skill tells an AI tool how to do a job. A prompt is how a person asks for it. When you share a project, the people who get it should not have to guess how to ask. Prompts in a project answer that: each one is written for a skill or an agent, and it travels with them.

What a project prompt is

A prompt in a project has a title, a short description of when to use it (the card and list show it), the AI it is written for (All, Claude, ChatGPT or Copilot) and the prompt itself, with {{variables}} for the parts that change. It is written for one skill or agent, or for the whole project when it is not about one of them.

Use the code-review skill to review {{pull request}}.
Report blocking problems first, then suggestions, and keep it under 300 words.

Add one

Open a project and look for Prompts in its files.

  1. Choose + next to Prompts, then New prompt. Or open the menu of a skill or agent and choose Add prompt: the new prompt already names that skill or agent.
  2. Write it. Promptor’s feedback is under the text: what is missing, and why it matters.
  3. Pick which skill or agent it is written for (or the whole project) and which AI.

Prompts are saved as you type, like the rest of the project. A prompt that holds something that looks like a real key is refused.

To start from one you already have, choose From the Library…. The project gets its own copy.

The Library and the project stay apart

A project’s prompt is a copy. Change it for this project and the Library prompt is untouched, and the other way round, so a prompt that suits one project never changes another one by surprise. When you want them to match, do it on purpose:

  • Update Library version puts this project’s wording into the Library prompt.
  • Reset from Library brings the Library wording back here.
  • Save to Library keeps a prompt that only the project has.

Several prompts for one skill

A skill often has a few: one to start, one to review, one to fix. They are grouped under the skill in the Prompts section, and a prompt’s menu has Move up and Move down to put the best one first. That order is the one used in lists and in the exported INDEX.md.

When the Library prompt changes

A Library prompt gets a new version when you choose Save as a new version while editing it (otherwise it is edited in place), and Version history in its menu shows the earlier ones and brings one back. A project that uses it keeps its own copy, so it does not change by itself. Instead the project’s Prompts section says “a newer Library version is available” and See what changed shows the title, description, AI and prompt text side by side (green added, red removed). You choose, for that project:

  • Update takes the new wording, when you have not changed the copy.
  • Use the Library version or Keep mine, when you changed the copy and the Library prompt changed too.
  • Update all unchanged takes every clean update in the project in one go.

Another project is asked separately, so a change made for one never reaches another by surprise.

Find them again

The Library’s Prompts tab lists the Library’s prompts and the ones only a project has. Filter by Project and Skill or agent to see what is written for a skill, sort them, and switch between cards and a list.

Share them

  • Zip export: a prompts/ folder with one file for each prompt and an INDEX.md that groups them by skill or agent and says how to use them. Untick Include prompts in the Export dialog to leave them out.
  • Project file: prompts are part of the project, so they are in the file. Importing it adds the prompts your Library does not have to your Library.
  • GitHub: a push writes the same prompts/ files and lists them in the repository’s README. A prompt you remove is removed from the repository on the next push. See Share your skills with GitHub.
  • Versions: prompts are saved, compared and restored with the project, so a version holds the prompts it had. In History, a prompt that changed shows as a file and can be put back on its own.

See them on the canvas

On the canvas, choose Show prompts (it starts hidden). Each prompt is a small card with a line to the skill or agent it is written for. Drag from a prompt’s dot to another skill or agent to change that, or remove the line to write it for the whole project.

Let your AI tool help

With Connect AI, your AI tool can read a project’s prompts, review one with /review-prompt and, after you confirm in the app, add, change or delete them. A change to a project is one step you can undo.

Keep them useful

  • Start with the task: “Review a pull request”, not “Prompt 1”.
  • Name the skill or agent in the prompt, so the AI tool picks it up.
  • Say in the description who it is for and what to have ready.
  • Keep each prompt short. If it grows steps and rules, it is a skill. See Prompts, skills, agents and instructions.