◇ Could this help me?
Yes on the workflow, provided the install steps get real scrutiny. Building a design reference file and a site structure file first and then generating page by page is genuinely better than asking for a whole site at once, because each page is built against a fixed reference instead of drifting. The part to slow down on is exactly the part the video moves through quickly: installing skills from a public repository and granting a connector server access is the same category of action that gets warned about elsewhere in this library, so confirm the publisher and read what the skills actually instruct before installing. This is a general practice.
I want to build a multi-page site from a design brief without generating it all at once. First, turn my brief into two reference files: a design definition covering palette, typography, spacing, and component style, and a site structure defining every page and its purpose. Then build the home page alone against those files and stop for my review. After I approve it, build the remaining pages one at a time, each checked against the same reference files. Before adding any external skill or connector, tell me exactly what it is, who publishes it, and what access it needs so I can approve it separately.