Coding with AI tools

Stage 3 · Lesson 6 of 7

Saving prompts that work

Prompting for code: small tasks, clear specs

When a prompt works well several times, save it in the so you and your team can run it by name. In , a is a folder in .claude/skills/ with a SKILL.md file, run with a slash and its name, such as /review-pr. In Cursor, skills appear in the / menu in the Agent, and a skill can be kept on as a Custom Mode so it stays active every turn.

In Copilot, prompt files are .prompt.md files in .github/prompts/, run with a slash in chat, and /create-prompt drafts one. Good candidates are review checklists, "write tests first" workflows and release steps.

Common trapsaving a prompt after it worked once: keep it only after it has worked on several different tasks.

A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it

Resources for this stage

Start with· follow one of these

Keep handy

Also worth your time

Mark this stage as not done?