Prompt Motion
@AiMotionSiteS
Prompt library

UI motion

Production-quality SaaS landing page for a team workspace product

Production-quality SaaS landing page for a team workspace product is a 19-second Claude Opus motion design reference by @itsluneri, built around code. [Note: the creator shared a partial prompt. Copy this UI motion prompt, keep the creator's frame counts and palette, and adapt the subject for your own launch film.

@itsluneriView post

Prompt

[Note: the creator shared a partial prompt. Wording below is theirs.] GOAL: Build a complete, production-quality landing page for Nock, a project workspace for small product teams. MOTION: Nock combines projects, issues, owners, discussions, and ship dates in one place. Its core purpose is to let a team see what is being built and what ships next without jumping between a tracker, a doc, and another status meeting. Technical requirements Build the website using Next.js, React, and TypeScript. Use TSX components and a proper Next.js project structure. Do not create a plain HTML/CSS website. The implementation should be clean, componentized, responsive, and production-quality. Use modern CSS or Tailwind CSS for styling where appropriate. Do not merely describe the implementation. Build the complete working page. Visual reference Use the provided reference image as the primary art-direction reference. Match its overall visual character very closely: typography treatment, density, spacing philosophy, texture, contrast, borders, surface treatment, visual weight, image treatment, and general design atmosphere. However, do not copy the reference website or recreate its content. Do not copy its: branding text or copy logos illustrations exact layout individual components imagery proprietary visual assets Instead, understand the design language behind the reference and reinterpret it for Nock. For example, if the reference uses grain, paper texture, sharp borders, muted surfaces, unusual typography, dense layouts, editorial spacing, or a particular treatment of imagery, use those qualities as inspiration while creating an original design. The finished page should clearly belong to the same visual world as the reference while still being an original website. Page Include a navbar, page sections, and a footer. Design those yourself. The hero should immediately explain Nock and show a convincing view of the actual product. Throughout the page, create realistic Nock UI showing projects, issues, assignees, discussions, statuses, ship dates, and progress. Keep names, projects, dates, statuses, and other information consistent across different product previews. Include the sections that genuinely help sell the product, such as: Hero Product demonstration Core workflow Features Team use cases Integrations Customer proof Pricing FAQ Final CTA You may change, combine, reorder, or remove sections when doing so produces a stronger page. Design quality Avoid the stereotypical AI-generated SaaS aesthetic. No purple gradient hero. No glowing blobs. No glassmorphism. No giant collection of rounded cards. No endless 3-column feature grids. No random floating icons. No meaningless charts. No fake AI functionality. No excessive pills. No generic startup illustrations. No repetitive centered sections. Do not make every element a card or container. Use typography, composition, whitespace, texture, product UI, imagery, and hierarchy to create visual interest. The product UI itself should be detailed and believable. Copy should
Author original
Build a complete, production-quality landing page for Nock, a project workspace for small product teams. Nock combines projects, issues, owners, discussions, and ship dates in one place. Its core purpose is to let a team see what is being built and what ships next without jumping between a tracker, a doc, and another status meeting. Technical requirements Build the website using Next.js, React, and TypeScript. Use TSX components and a proper Next.js project structure. Do not create a plain HTML/CSS website. The implementation should be clean, componentized, responsive, and production-quality. Use modern CSS or Tailwind CSS for styling where appropriate. Do not merely describe the implementation. Build the complete working page. Visual reference Use the provided reference image as the primary art-direction reference. Match its overall visual character very closely: typography treatment, density, spacing philosophy, texture, contrast, borders, surface treatment, visual weight, image treatment, and general design atmosphere. However, do not copy the reference website or recreate its content. Do not copy its: branding text or copy logos illustrations exact layout individual components imagery proprietary visual assets Instead, understand the design language behind the reference and reinterpret it for Nock. For example, if the reference uses grain, paper texture, sharp borders, muted surfaces, unusual typography, dense layouts, editorial spacing, or a particular treatment of imagery, use those qualities as inspiration while creating an original design. The finished page should clearly belong to the same visual world as the reference while still being an original website. Page Include a navbar, page sections, and a footer. Design those yourself. The hero should immediately explain Nock and show a convincing view of the actual product. Throughout the page, create realistic Nock UI showing projects, issues, assignees, discussions, statuses, ship dates, and progress. Keep names, projects, dates, statuses, and other information consistent across different product previews. Include the sections that genuinely help sell the product, such as: Hero Product demonstration Core workflow Features Team use cases Integrations Customer proof Pricing FAQ Final CTA You may change, combine, reorder, or remove sections when doing so produces a stronger page. Design quality Avoid the stereotypical AI-generated SaaS aesthetic. No purple gradient hero. No glowing blobs. No glassmorphism. No giant collection of rounded cards. No endless 3-column feature grids. No random floating icons. No meaningless charts. No fake AI functionality. No excessive pills. No generic startup illustrations. No repetitive centered sections. Do not make every element a card or container. Use typography, composition, whitespace, texture, product UI, imagery, and hierarchy to create visual interest. The product UI itself should be detailed and believable. Copy should

Questions

What is this ui motion prompt for?

It is a Claude Opus motion design brief for “Production-quality SaaS landing page for a team workspace product”. Paste it into Claude and keep the timings already written in the prompt.

Where is the original film?

The creator is @itsluneri. Use View post to open the X video this prompt belongs to.

More ui motion prompts