Inspector overview

QA & production readiness — detect and report before you ship. Honest scope, not auto-fix.

Note

Creytix Inspector is one of the eight Creytix departments — QA and production readiness for everything you ship through Creytix.

Overview

Inspector's job is to catch problems before a deploy, not after. It runs the checks a careful reviewer would run — is the SEO metadata right, does this page meet accessibility basics, did this change break something a screenshot diff would catch — and reports what it finds. It does not silently rewrite your content or your code to fix what it finds; that stays a deliberate choice you make.

Creytix tool	Replaces
Creytix Inspector	Manual QA spreadsheets

How it works

Protect runs deterministic checks — SEO, schema, accessibility, and recipe rules — fast, rule-based, no judgment calls.
The CI gate blocks a deploy when those checks fail, instead of relying on someone remembering to look.
Playwright smoke and journeys exercise real pages in a browser to catch what static rule checks can't.

Steps

•
Wire Protect into your workflow
Run Protect's rule checks against a page or a batch of pages before you consider them ready.
•
Let the CI gate hold the line
Connect the gate to your deploy flow so a failing check blocks the release instead of a person having to catch it manually.
•
Add browser-level smoke checks
Layer in Playwright journeys for the flows that matter most — the ones a rule check can't see.
•
Review what Inspector reports
Inspector tells you what it found. Deciding what to do about it — fix, accept, or override — stays yours.

Capabilities

Protect — deterministic SEO, schema, accessibility, and recipe checks, rule-only and fast.
CI chain & review gate — a pre-ship gate that blocks a deploy on failing checks.
Playwright smoke & journeys (building) — browser-level smoke checks on public templates.
Inspector MCP server (building) — expose Inspector's checks as tools an AI agent can call directly.

Limits & honest scope

Inspector detects and reports. It is deliberately not an auto-fix tool.

It flags what's wrong; it does not rewrite your content, code, or markup to resolve findings.
Rule-based checks catch what they're written to catch — they are not a substitute for human review of judgment calls like tone, brand fit, or legal review.
Playwright smoke and the MCP server are still being built — today's browser coverage and agent tool exposure are narrower than the target described on their pages. Check each page's tier badge.