docs.dev vs Preseason

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

We track which developer tools AI models pick across a frozen panel of vibe-coding prompts at every level, from beginners to expert engineers.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Preseason

We track which developer tools AI models pick across a frozen panel of vibe-coding prompts at every level, from beginners to expert engineers. Define data-model boundaries, asynchronous processing for long-running work, observability, and a deployment and migration strategy that supports schema evolution without downtime. Enforce role-based separation between shoppers, support agents, and operations staff. Add observability for prompt, retrieval, latency, and failure traces, plus evaluation pipelines that score groundedness, escalation correctness, and regression risk before prompt or model changes are shipped.