What problem does it solve? Code changes to AEM Edge Delivery Services blocks, scripts, and styles can ship with rendering bugs, console errors, responsive breakdowns, and type errors that linting alone misses. This Skill provides a structured pre-PR testing workflow that catches these issues before they reach review. ## Core Features & Use Cases - Lint and TypeScript validation: Runs npm run lint and npm run build first to surface code quality and type errors, accounting for this project's noEmit TypeScript setup. - Browser validation with Playwright or MCP browser tools: Guides viewport testing (mobile, tablet, desktop), console error checks, and screenshot capture as proof of testing. - Selective unit testing with Vitest: Helps decide when unit tests are worth writing (logic-heavy utilities, data transformations) versus when browser testing suffices, including full Vitest setup instructions. - Use Case: After modifying a hero block in src/blocks/hero/, follow the workflow to lint, load the draft page at http://localhost:3000/drafts/hero, capture screenshots at three viewports, and confirm zero console errors before opening the pull request. ## Quick Start Test my recent block changes by running lint, validating the block in a browser at multiple viewports, and confirming no console errors before I open a pull request.