Hook: Every dev on your team has their own pile of AI prompts and one-off scripts — which means every hard-won lesson stays trapped with the person who learned it, and the rest of the team keeps paying to learn it again. What if your team’s AI tooling lived in a versioned, reviewed, CI-enforced repo — the same way your plugins do? Take-away: a concrete starter pattern for a team-skills repo + the three policies that make it stick.
Did you attend this session? Leave feedback.
