Team-specific prompts
Turn what one engineer worked out into something the team runs by name, and keep it working.
4 lessons. 1 quiz.
Read in order, or jump to what you need.
Why team-specific prompts beat general ones
By the end of this lesson, you will be able to argue for team-specific prompts over general ones, design a prompt with the five required components, and recognize when a prompt is genuinely team-specific.
Building reusable prompts (skills)
By the end of this lesson, you will be able to write a reusable prompt as a Claude Code skill, parametrize it for variation across teams or time windows, and choose the right sharing mode for your team.
Sharing skills across the team
By the end of this lesson, you will be able to choose the right sharing mode, set quality gates for shared skills, and execute a migration from personal skills to a shared library.
Versioning and maintaining skills
By the end of this lesson, you will be able to version a shared skill with metadata + changelog, run a quarterly skill review, and execute a graceful deprecation when a skill becomes obsolete.
Module quiz.
Take it once the lessons are done.