Product launch
Tell the launch story around one release and one clear next step.
Customize the recipe
Prompt preview
# Product launch Tell the launch story around one release and one clear next step. ## Deliverable A launch page with launch-day states and a public signup, availability, or purchase destination. ## Stack and visual direction - Recommended starting stack: Next.js, TypeScript and semantic CSS. Use static content where it serves the brief. - Editorial: Use strong display typography, readable measure and deliberate placement of images and captions. Let the content determine the grid and pacing. Apply this direction to the website. - Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI. Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it. - [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure. [Official setup](https://nextjs.org/docs/app/getting-started/installation). - [Motion](https://github.com/motiondivision/motion) (Repository) — Document intentional transitions, including reduced-motion behavior and interruption. ## Workflow 1. Make the new product concrete with a launch headline, a product image or demo, the release timeline, and an accessible CTA. Set the timezone explicitly when using a release date. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] Preview before and after launch with a controlled clock. - [ ] Reduced-motion visitors can read every reveal and use the CTA. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Check mobile navigation and every key page at narrow and desktop widths. Remove horizontal document overflow and optimize images with stable dimensions and appropriate alternatives. - [ ] Check working buttons, links and footer destinations, clickable logo and contact paths where applicable, page titles, descriptions, favicon, a useful 404 and the current copyright year. Remove placeholder text and unused navigation. - [ ] Verify forms with both valid and invalid submissions and useful success and error feedback.
Recipe resources
Source, setup, and compatibility details.
Frontend Design
Plan distinct typography, composition and interaction details before building UI.
Upstream documents Claude Code.
License · See upstream skill license
Next.js
Use App Router conventions, server rendering, metadata and accessible route structure.
License · MIT
Setup guide for Next.jsMotion
Document intentional transitions, including reduced-motion behavior and interruption.
License · MIT
21st MCP
Find and compare component examples that fit the chosen visual direction.
An MCP-compatible agent and a 21st API key. Check source terms before reusing a component.
Setup guide for 21st MCPPlaywright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI