landing-page-design

To design a domain-appropriate landing page, this workflow routes planning by industry—medical, SaaS, agency, e-commerce, or restaurant—adapting section lists, content anatomy, and component choices to match specific brand intent and user expectations.

The landing page design workflow progresses phase-by-phase from domain selection to single vs multi-page decisions, section listing, content anatomy mapping, component scoping, design token definition, and concluding with build and deployment handoff.

Design tokens ensure visual consistency across multiple component libraries by establishing a coherence-first token system before installing any components, creating a unified visual language that governs all subsequent multi-library styling decisions.

Yes, you can use shadcn-compatible libraries while maintaining a custom design system by using live registry discovery to source current libraries, then enforcing your predefined design tokens to ensure visual coherence across all installed components.

Yes, the landing page workflow automatically generates an llms.txt file during the handoff phase, providing it alongside deployment and SEO guidance to ensure AI agents can process and continue the project seamlessly.

You choose a single-page or multi-page landing page structure during the early phase-by-phase workflow, right after domain selection, which then routes subsequent section list, content anatomy, and component scoping steps to match your project scope.