◇ Could this help me?
Yes, with the sourcing caution taken seriously. Deciding on a design direction before generating code is the right sequence and is the reason this combination works better than prompting for a page directly, so the underlying method is sound. The caution is specific: a skill from a community marketplace is executable instruction text and a copied component is executable code, so both deserve a look at the publisher and the contents first, especially for anything that handles input or makes network calls. This is a general practice.
Before writing any code for this landing page, establish the design direction. Research how strong products in the industry I name actually present themselves, then propose a specific direction covering palette with values, type pairing and scale, spacing rhythm, imagery treatment, and motion character, and explain why it fits this audience. Once I approve the direction, build to it. If you want to bring in an external component, show me its source and what it does before adding it.