Files
SluijsensandClaude Opus 5.5 65c850e949 Adds the prerendering requirements, design and baseline
Records the requirements, execution plan, application design, the first unit's
functional design and code generation plan, and the baseline on master.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 17:41:12 +01:00

1.5 KiB

Application Design Plan: prerendering

Depth: standard. No question file was created: each open choice was settled by testing it in a spike or is purely technical, and the owner's decisions are in requirements.md. The design states its decisions and the consequences the owner should know. Business rules follow in Functional Design (units 1 and 2) and Infrastructure Design (unit 3).

Plan

  • Analyse context
    • Read requirements.md, execution-plan.md and the shared reverse-engineering artifacts
    • Read in code: main.tsx, __root.tsx, vite.config.ts, index.html, serverConfig.ts, securityHeaders.ts, lighthouserc.cjs, the CI workflow, Reveal, useReveal, useInView, DeferredImage, NavigationBar, MobileNav, NotFound, renderApp
  • Test the open technical choices in the spike
    • Hydration under the production script-src, with inline and with moved scripts
    • URLs without a trailing slash through autoSubfolderIndex: false
    • Three ways to build the 404 page
    • Search parameters during hydration
  • Generate components.md
  • Generate component-methods.md
  • Generate services.md
  • Generate component-dependency.md
  • Generate application-design.md
  • Validate design completeness and consistency
    • Every FR-PR and NFR-PR item has a home in a unit
    • Mermaid diagrams use classDef with color:#000, safe node ids and a text alternative
    • Security Baseline and PBT compliance summarised; no blocking findings