Audit Reference Originality

Compare the shipped experience with the complete reference corpus. Treat the audit as an evidence exercise, not a vibe check.

When to use this skill

When a supplied reference corpus exists (manifests, prompt packs, capture packs, stills, MP4s, reference URLs, IMAGE_CREDITS.md) and a shipped site or experience must be checked against it for originality/plagiarism risk.
When you need to compare current or historical site output with references across text, brands, numbers, images, assets, videos, layout, motion, or code.
When red flags must be evidence-backed — each paired with exact current-site and reference-site locations, severity, and a proposed fix — rather than a subjective "vibe check".
When you need to distinguish common visual grammar (black backgrounds, large sans-serif type, standard fade-ins) from distinctive, provably-copied elements.
When copied material may have been renamed, recolored, cropped, or deleted, requiring git log/git show/git log -S history checks in addition to current files.
Not for making the actual replacement edits unless the user also asks for fixes (this skill audits and proposes fixes; it does not silently apply them), and not for general code review or security audits unrelated to originality — route those to standard review/fix workflows instead.