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>
1.8 KiB
1.8 KiB
Functional Design Plan - Unit 1: Start migration and script step
Feature: prerendering. Unit: 1 "Start migration and script step" (see execution-plan.md § Units of Work). Owner decision on the e-mail address: start-migration-fd-questions.md (Q1 = A). Artifacts: functional-design/.
Steps
- Step 1: Analyse unit context (requirements, execution plan, application design, spike evidence, owner answer on the e-mail address)
- Step 2: Verify in
web/srcandweb/configevery component a rule is written for (hooks, routes, Footer, contact components,lib/, Sentry and Umami, sitemap plugin, test setup) and innode_moduleshow Chakra'suseMediaQueryanduseBreakpointValuebehave - Step 3: Search
web/srcfor further differences between prerender and first browser render (browser globals in render, time and random values,useId,windowordocumentin initialisers) - Step 4: Create this plan
- Step 5:
business-logic-model.md(build flow, page load phases, script step algorithm, runner, e-mail, search, 404, preview server, measurement, testable properties) - Step 6:
business-rules.md(numbered rules BR-BLD, BR-ENT, BR-HYD, BR-MAIL, BR-404, BR-LZY, BR-MON, BR-SCR, BR-SEC, BR-SRV, BR-TST, BR-MEA; to verify in code generation) - Step 7:
domain-entities.md(script step entities, hydration inventory, e-mail slot, request resolution) - Step 8:
frontend-components.md(component hierarchy, first-render contract per component, new hooks, document shell) - Step 9: Check diagrams against the Mermaid standards and the content validation rules
- Step 10: Report to the orchestrator (no questions needed; the open choices are listed in the report)