Summer 2026 events: Seattle and Japan
The tech events we're attending in Seattle and Japan from June through August 2026.
Introducing StyleOps
Developer Experience
Documentation products and services for hardware and software developers.
New product
StyleOps is here
StyleOps checks your documentation against the Developer Experience style guide, or a custom style guide, and drafts compliant docs, inside Claude Code, AI chat, or your build pipeline. Every finding cites a numbered rule with a severity and a rationale.
What's included
Documentation standards for engineers, technical writers, and AI agents
Each release ships the style guide as flat Markdown for AI chat, JSON rules for your tooling, doc templates, a Vale configuration, and a Claude Code plugin. It runs on your systems. Model calls use your Anthropic key, and your docs never reach Developer Experience.
For tech writers, engineers, and AI
Check existing docs, or generate new docs
Optimize reviews your documentation for style guide compliance and reports findings. Generate drafts compliant developer guides and API reference docs based on your notes, specifications, and source code. A build gate keeps pull requests compliant.
Style guide launched
The Developer Experience Style Guide is online
The style guide behind StyleOps is now published on our docs site, free to read and searchable. The rules are designed by expert technical writers based on documentation user research. The guide settles the editorial decisions that stall doc reviews: voice, grammar, punctuation, formatting, word choice, and API documentation. Every rule carries a stable ID, a severity, examples, and the reasoning, so a review ends in a decision instead of a debate.
docs.developerexperience.com/style-guide/audience/ai-language/
Style guide Audience AI language and punctuation
AI language and punctuation
The guide is written for the age of AI drafting: it identifies the patterns that make text sound generated, from em-dash splices and borrowed vocabulary to fabricated claims and exaggeration. Because technical writing is already highly structured and consistent, the impact of AI-generated language and punctuation tends to get amplified, so it's important to enforce these rules.
Each rule names a pattern, shows the fix, and explains the reason.
ai-004 · Avoid em dashes
✗ Caches the token — a local copy — so calls skip the network.
✓ Caches the token locally, so repeated calls skip the network.
Severity: should · Applies to: main, api, marketing, blogResearch
An AI embodied robot, documented end to end
We're building an embodied robot from developer-accessible parts: the D-Robotics RDK S100P for compute and perception, the SLAMTEC Aurora S for mapping, and the Booster K1 humanoid platform in later phases. Every phase ships as blog posts and developer documentation.
