Claude Code didn't just add /workflows. It turned loose chat steps into something your project can keep 👀
If you mostly use Claude like a smarter chat box, this is where people get tricked. The easy mistake is thinking Claude Code and Claude are the same thing with different scores, then finding out the real change was how the work gets stored.
I thought /workflows would be just another shortcut. Plot twist 🧩: the docs show 2 different setup files can lead to the same 1 shortcut [S001]. That means the flashy button matters less than the shared recipe behind it.
The part that made me pause: 3 pieces of a run - install, setup, and launch - can be packed into 1 shared project folder [S001]. Before, that lived in 1 person's memory or an old chat. After, the project can keep it, reuse it, and review it.
Even the plugin docs group shortcuts, helpers, and workflows into one team toolkit, not just a chat window [S004]. Honestly, that's the real shift: the workflow stops being chat memory and starts being a project asset. Claude Code is better for pinning the steps down before they drift, while regular Claude is still better when you just want the answer finished.
Small boundary: I only checked the current Claude Code docs and plugin guide on May 23, 2026, not a live team project, so YMMV. Save this for the next AI-tool launch and send it to the friend who still thinks /workflows is just a shiny shortcut. Would you rather keep your process in chat, or in the project?