# NFR Requirements Plan — frontend-shell Unit: **frontend-shell**. Builds on requirements NFR-01…NFR-06 and the approved functional design. NFR Design is skipped (execution plan); the patterns are small and go straight into this document and the code generation plan. ## Plan - [x] 1. Answer the questions below - [x] 2. Analyze answers for ambiguities (follow-up questions if needed) - [x] 3. Generate `nfr-requirements.md` — measurable NFRs per category: performance, accessibility, SEO, security, reliability, maintainability/testing, browser support; scalability/availability marked N/A with rationale - [x] 4. Generate `tech-stack-decisions.md` — test stack (PBT-09), linting, security headers/CSP, build plugins, dependency changes with rationale - [x] 5. Validate against Security Baseline (SECURITY-04, -09, -10, -13, -15) and PBT-09 ## Already decided (no question needed) - **Scalability and availability**: N/A for the shell. It is a static site without a server; availability depends on the future host (Operations). - **Test stack** (NFR-03, PBT-09): Vitest + React Testing Library + `@testing-library/user-event` + `jsdom` + fast-check. fast-check covers custom generators, shrinking and seed-based replay, and runs inside Vitest. The seed is printed on failure and can be passed back to replay a run. - **Security headers** (NFR-04): `X-Content-Type-Options: nosniff`, `X-Frame-Options: DENY`, `Referrer-Policy: strict-origin-when-cross-origin` and HSTS `max-age=31536000; includeSubDomains`. Browsers ignore HSTS over plain `http://localhost`, so locally it has no effect; it matters on the production host. - **CSP content for the production build**: `default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'`. - `style-src 'unsafe-inline'` is needed because Chakra/Emotion inject `