Three Manual Checks to Run Before Shipping AI-Generated Website Code

The author, who is building a local prototype tool for checking declared file scope and static HTML evidence, offers a free manual review method for AI-written code. The core idea is to define allowed files, protected files, and explicit acceptance criteria before an agent starts work. A test case showed a page with the right heading and button still failing a strict local-link rule, since the link used a bare href='#' instead of the declared anchor. The piece argues that a diff against a saved Git baseline, including untracked files, reveals which paths changed, though a scope pass only shows files were allowed, not that features work. It also recommends replacing subjective criteria with inspectable static checks, while noting that even those don't prove a browser interaction succeeds.