From crafting prompts to packaging them
The Prompt That Disappeared
You spend 45 minutes crafting the perfect code review prompt. Role, constraints, output format, severity rubric — it catches a SQL injection your team missed. Everyone is impressed.
Two weeks later, you need it again. You scroll through your chat history. Was it in the Thursday conversation? The one about the auth module? You find something close, but it's missing the severity rubric. You rewrite it from memory. This time it misses the injection.
The prompt was good. But it was ephemeral — it lived in one conversation and died there.
What if that prompt was a permanent tool — a slash command you could invoke anytime, share with your team, and refine over time? That's what skills are.