skills/angular/angular-ssr/SKILL.md
Implement Angular SSR with hydration, TransferState caching, and per-route render modes. Use when configuring Angular Universal SSR, client hydration, static prerendering, or preventing double-fetching.
npx skillsauth add hoangnguyen0403/agent-skills-standard angular-ssrInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
ng add @angular/ssr.provideClientHydration(withEventReplay()) to app.config.ts providers.See hydration examples for app config and hydration setup.
afterNextRender(() => { /* window access */ }) for one-time browser-only code.PLATFORM_ID and use isPlatformBrowser(platformId).withHttpTransferCacheOptions() or manual TransferState to cache server responses for client replay.Export ServerRoute[] in app.routes.server.ts:
@defer (hydrate on viewport).viewport, interaction, idle, timer(ms), immediate, never.withEventReplay() to capture user events before hydration completes.afterNextRender() or PLATFORM_ID check.withHttpTransferCacheOptions() or TransferState.RenderMode.Client for authenticated dashboards.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.