What problem does it solve? Email templates produce complex HTML that is hard to assert with traditional unit tests, and small template changes can silently break rendering across email clients. This Skill provides patterns for snapshot testing email output so regressions surface as reviewable diffs instead of production bugs. ## Core Features & Use Cases - Snapshot Testing with Verify: Capture rendered email HTML as .verified.html baselines and fail tests when output changes unexpectedly. - Dynamic Value Scrubbing: Normalize timestamps, GUIDs, and tokens so snapshots remain stable across test runs. - Composer-Level Tests: Verify full email objects including subject, recipients, and HTML body, plus CI integration that fails on missing baselines. - Use Case: When refactoring an MJML welcome email template, run the snapshot tests to get a visual diff of the rendered HTML, review it in a browser or diff tool, and accept the change only after confirming the rendering is correct. ## Quick Start Write a snapshot test for my email template rendering using Verify.Xunit and show me how to scrub dynamic values like dates and GUIDs.