toolkit

What is the site actually built on?

Divi audit

Divi front-end audit that routes by major version (Divi 4 vs Divi 5) — confirms a page is built with Divi, then reads the rendered HTML to report the Divi module inventory and the Divi-specific performance and config signals visible from outside: inline-CSS weight (the classic Divi bloat), Google Fonts loading, the jQuery dependency, and per-breakpoint responsive tailoring.

What this capability does

Divi front-end audit that routes by major version (Divi 4 vs Divi 5) — confirms a page is built with Divi, then reads the rendered HTML to report the Divi module inventory and the Divi-specific performance and config signals visible from outside: inline-CSS weight (the classic Divi bloat), Google Fonts loading, the jQuery dependency, and per-breakpoint responsive tailoring.

How employees use it

Ask for the outcome in normal job language. The coding agent selects the approved implementation, records evidence, and returns a review-ready result.

“audit this Divi site — https://sherberandrad.com”

Where the technical instructions live

The detailed implementation guide stays inside the private Toolkit repository. Employee-facing pages intentionally use friendly capability names only.

Watch real OpenCode results in Toolkit in Action →