What problem does it solve? Angular single-page apps render entirely in the browser, which hurts SEO, slows first paint, and breaks when code touches browser-only APIs on the server. This Skill guides you through adding SSR, hydration, and prerendering to an Angular v20+ project so pages render on the server without hydration mismatches. ## Core Features & Use Cases - SSR Setup & Configuration: Add @angular/ssr to an existing project, configure app.config.server.ts, and define per-route render modes (Prerender, Server, Client). - Hydration Strategies: Apply incremental hydration with @defer triggers (viewport, interaction, idle, timer), enable event replay, and debug hydration mismatches. - Browser-Only API Handling: Guard window, document, and localStorage access using PLATFORM_ID, afterNextRender, and injection tokens so code runs safely on both server and client. - Use Case: You have an e-commerce Angular app where product pages need SEO-friendly static HTML, but the dashboard must stay client-only. Use this Skill to prerender product routes with getPrerenderParams, SSR dynamic pages, and mark authenticated routes as RenderMode.Client. ## Quick Start Add server-side rendering to my Angular project and configure the product detail route to prerender at build time.