Claude Academy is now available on the web and in the desktop app, covering everything from casual exploration to team-level rollouts. It is positioned as the canonical learning resource for working with and building on Claude.
Claude Academy launched on both the web and Claude desktop app, offering learning paths for new users, developers, and teams rolling out Claude at scale.
Fable is a new set of enterprise safeguards that give companies control over where their data lives and who can access it. Developed alongside roughly 100 companies, it's targeting a broader rollout in the fall.
A tweet circulating claimed Claude was over-using a particular output style pattern. An Anthropic team member confirmed it happens far too often and said it's being tuned back; the behavior stems from how output styles used to work by default.
The /eli5 command, popular internally at Anthropic, generates HTML artifact explainers with big pictures and minimal words. It is being shared publicly as a community plugin, with an official plugin status still under consideration.
Follow-up to the /eli5 announcement with exact install commands for the community plugin. Two commands pull it from the anthropics/claude-plugins-community marketplace.
A user argued that /eli5 is just a workaround for Claude's excessive verbosity and that fixing the default would make the command unnecessary. The team acknowledged the critique and confirmed that reducing verbosity is actively being worked on, while still defending the command's value for concept explainers.
A user complained that /eli5 produces overly dumbed-down analogies and prefers prompting for simplicity without losing technical precision. The team member pushed back, saying the skill generally meets users at their level.
Responding to a question about best practices with /code-review, bcherny suggested that as models improve, the slash command may become unnecessary altogether.
Responding to skepticism about the "coding is solved" framing, bcherny drew a distinction: coding may be solved, but eliminating bugs is a separate problem with a fix on the way.
Pushing back on the argument that bugs disprove "coding is solved," bcherny noted that human-written code was never bug-free either.
