If you mostly use Claude as a chat box and coding helper, and every big release makes you wonder whether you just gained something or quietly lost something, this is the part worth watching. The easy mistake is to treat Claude Code and Claude as the same tool and assume the higher-scoring one is the better fit. If you only read the upgrade pitch, you can think you bought a stronger version when the first thing you actually hit is a tighter boundary.
The interesting signal here is not just that Claude Code dropped /workflows. It is what seems to have replaced that idea. You came in looking for whether the model got better, but the real story is the tradeoff that was not front-and-center: workflows are not being framed like chat history anymore. They are being pushed toward project files. Workflows are not chat logs. They are repo assets, meaning project files your team can keep. The most discussable part of any release is never that the model got stronger. It is why the strongest thing was not put on the table directly.
The cleanest proof sits in the current Claude Code docs. Anthropic says custom commands are folded into skills, and the docs show that .claude/commands/deploy.md and .claude/skills/deploy/SKILL.md can both create the same /deploy action [S001]. That matters because it turns a repeat task from 'the shortcut I keep in one conversation' into 'the setup my project can keep on disk.' Same action, two file paths, one clear direction.
The same docs describe /run-skill-generator writing install, environment, and launch recipes into .claude/skills/run-<name>/ [S001]. That is not a nicer prompt. That is a project-level recipe. Once a workflow lives there, it can be committed, reused, reviewed, and handed to the next person without asking them to reconstruct your favorite chat thread. That is the real change hiding behind 'Claude Code dropped /workflows.'
That is also why I would not collapse Claude Code and Claude into one bucket. Claude Code is better for helping you inspect the problem first, while Claude is better for carrying the rest to completion. If your work repeats across setup, deploy, or run steps, read this release as a boundary shift, not just a UI change. Share it with the person who still treats repeat work like a personal prompt stash. The durable part now looks like the folder, not the chat.