Quality checks

After Klaudius builds a site, a fresh reviewer checks it before it goes live. It's a big part of why the sites read as carefully made, and one of the slowest, most usage-hungry steps in the pipeline, so you can switch it on or off.

What the review does

The reviewer's only job is to check the site. Besides reading the code, it takes screenshots at desktop and mobile sizes and looks at each one the way a person would, catching broken layouts, missing images, copy that drifted from the business's real details, broken links, or anything that just looks off.

If the site fails, Klaudius fixes what the reviewer found and has it reviewed again, up to three rounds. A site still failing after three rounds stops there, and Klaudius asks you what to do. If the checks themselves can't run on your computer, Klaudius alerts you and deploys the site as it would with quality checks off.

The reviewer starts fresh because the session that built the site knows what it meant to do, so it reviews leniently. A reviewer that starts cold sees the site as the owner will.

What it costs

The review is often the slowest part of the pipeline and takes a real slice of your usage, especially when a site fails the first round. With quality checks off, Klaudius goes straight from build to deploy and gets several sites out of each usage window, for a modest dip in quality.

Setup turns quality checks off on the entry-level plans, where the usage windows don't stretch to a review per site: Claude Pro, ChatGPT Plus, and a Standard seat on Claude Team or ChatGPT Business. Every other plan starts with them on. Plans and usage covers the trade-off for each plan.

Switching it

Open Settings → Pipeline settings, flip Quality checks, and press Save, or just tell Klaudius. The change applies to the next run you start.

If you change plan in Settings → Change setup → Plan, quality checks reset to that plan's default, so check the switch afterwards if you had chosen otherwise.