Create marketing pages using PublicPage structure and website primitives.
npx skills add https://github.com/resend/design-skills --skill marketing-pages
Please help me install this Agent Skill. Skill: marketing-pages Source: https://github.com/resend/design-skills/tree/main/marketing-pages Command: npx skills add https://github.com/resend/design-skills --skill marketing-pages
Marketing pages in the Resend codebase often lack a unified structure, leading to inconsistent layouts and copy across pages. This skill provides a standardized framework for creating, updating, and deleting marketing/public pages using shared design system rules and public primitives.
Create or update marketing pages using the standard PublicPage structure and reusable primitives.
High-intent search queries and answers about installing and using this skill.
Standardizing marketing page layouts requires a centralized structure using reusable public primitives like PublicPage.Root, Header, Hero, Container, and Footer to enforce consistent UX and avoid duplication across pages.
The correct directory structure places marketing pages under src/app/(website)/your-page, with corresponding content and components sourced from src/components/website/ and src/components/public-page.tsx.
Separating website public primitives from product UI components requires enforcing distinct directory paths, routing public pages through src/app/(website)/ while isolating shared layouts in src/components/public-page.tsx.
Yes, composing a new marketing page uses reusable website primitives by applying a standard PublicPage structure that references shared layout and metadata components to ensure consistent design system rules.
A limitation of using a centralized structure for public pages is the strict separation between website primitives and product UI, requiring all marketing pages to conform to the src/app/(website)/ routing and component sourcing rules.
Handling SEO metadata when creating a marketing page is guided by the centralized framework, which provides a reference for page layout and metadata alongside the standard public page components to ensure correct configuration.
TIAN0517Transform UI design requirements into TypeScript frontend code with CSS variable tokens.
baasith6Integrate PostHog analytics into web applications for event tracking and feature flagging.
hieutrtrApply design tokens and UI primitives to React/TypeScript projects.
TheeCoderAhmedIntegrate headless CMS platforms and generate type-safe frontend fetchers.
