Anthropic gives Claude developers a new home for engineering guides
Claude.dev gathers engineering posts, Claude Code and API guidance, and videos, including articles published months before Anthropic's announcement.
By Ryan Merket · Published
Primary source: X
Why it matters
Claude.dev gives Anthropic's developer writing a dedicated address. Its archive shows the publication effort predates the announcement, while the featured guides expose developers to Anthropic's own workflows and company-reported experiments.

Anthropic introduced claude.dev on September 30th as a home for developers building with Claude, bringing engineering deep dives, Claude Code and API guides, advice from Anthropic's teams, and easter eggs under one address. The announcement came from Anthropic's developer account on X.
https://x.com/ClaudeDevs/status/2105391694741119047
The hub is a publication, not a new model or developer API. Anthropic describes it as a place to share tips, tricks, and points of view from its developers. Its homepage organizes posts into categories including engineering, agents, playbooks, and skills, and lists videos alongside written articles. The materials are publicly viewable on the site.
The archive also makes clear that the September announcement introduced a destination for work that was already being published. The homepage dates its listed articles from May 20th through September 28th. They include posts on using Claude Code, working with Claude's API, and managing the cost and effort involved in model-assisted tasks. Anthropic's May article on using Claude Code to create HTML describes how members of the Claude Code team use the tool to produce richer, shareable outputs. A June post on dynamic workflows covers Claude Code's use in tasks beyond routine coding.
Two recent articles show the kind of first-party material Anthropic is putting in front of developers. In a September 23rd account of a two-week performance sprint, three Anthropic engineers said they used Claude to identify bottlenecks, build benchmarks, propose changes, and monitor deployments. They reported that, at the 75th percentile, the time to reach a typeable page on a fresh Claude.ai load fell from 3.1 seconds to 0.55 seconds. Starting a Claude Code session fell from 0.8 seconds to 0.3 seconds, while loading a Claude Cowork cloud session fell from 2.6 seconds to 0.73 seconds. Anthropic said it merged more than 3,000 changes during the sprint without a customer-facing incident or rollback. These are company-reported results from Anthropic's selected user journeys, not an independent performance test. The engineering account describes the measurements and process in detail.
A September 28th guide to automated evaluation design presents a different sort of developer resource: a workflow for creating evaluation sets and improving an application against them. The guide explains how to keep a held-out set of examples away from the optimization process to help detect overfitting. In one example, Anthropic used an internal customer-support benchmark of 44 tickets, with 30 tickets used during optimization and 14 held out. The company reported that its final setup scored 90.5% accuracy on the held-out tickets, compared with 78.6% for the starting configuration, at about one-fifth the cost. The sample was small and internal; the figures describe that experiment, not expected results for developers generally.
That article also points readers to Anthropic's claude-api skill, which includes commands for building evaluations and iterating against them in Claude Code. The guide's practical value is in the procedure it lays out, while the reported benchmark numbers remain Anthropic's own test results.
The site's videos extend the same mix of technical and practical material. Its homepage features sessions about how Anthropic's Claude Code team uses the product and how engineers at Ramp and DoorDash work with AI tools. The written posts, videos, and category filters give developers several ways into the material without making claude.dev a replacement for Anthropic's API documentation.
Anthropic's announcement describes a new home for this material, while the dates on the site show that the writing itself predates the announcement by months. The distinction keeps the news in proportion: Anthropic has given its developer-facing editorial work a dedicated address, and the announcement does not describe a new API, change to product access, or pricing update.