---
name: website-evidence-review
description: Review a workshop business website against its brief and return testable findings with file or browser evidence. Use for pre-deployment quality review of a company, rental, or product website.
---

# Website evidence review

Read the project's brief, package scripts, server configuration and applicable infrastructure rules. Identify the requested business flow and the running environment before choosing checks. Existing user authorization controls which actions may run; this skill grants no additional permissions.

Inspect the full flow from its visible control through the API and persistence boundary. Read only the source files needed to trace that flow. Use the project's existing commands; inspect what each command does before running tests that write data. Use isolated local data for mutation tests. When no browser or runtime is available, report a static review and identify the missing evidence.

For a company form, check input validation, submission failures and truthful success feedback. For rentals, check date semantics, stale availability and simultaneous capacity enforcement. For product pages, check reduced motion, keyboard access and server-owned pricing. The relevant business branch defines the checks; other branches need not be loaded or tested.

For each finding, provide severity, concrete trigger, affected file or route, expected behavior, observed evidence and a minimal repair suggestion. Separate verified failures from plausible concerns. Include which acceptance criteria passed and which remain unverified. A rendered page or a successful build alone does not prove database writes, access control or deployment.

Finish with the smallest set of unresolved issues that would change the release decision. Stop after reporting; this review workflow does not edit the application or publish a deployment unless the user has separately requested that follow-up work.