Skip to content
LIVERun 001 capturing

ready / v1.0.0

AI Coding-Agent Launch Page

Build a distinctive, responsive launch site for a fictional AI coding product without default SaaS styling.

Open exact prompt

Overview

Test visual taste, positioning, and disciplined responsive frontend implementation.

Capabilities tested

  • frontend taste
  • typography
  • product positioning
  • motion
  • responsive design

Required outcome

An original launch website with a credible product story and accessible conversion path.

Requirements

functional

  • Accessible navigation
  • Pricing or conversion section
  • Working internal navigation

ux

  • Original brand system
  • Strong hero
  • Readable product UI
  • Responsive behavior

technical

  • Semantic HTML
  • Visible focus states
  • Production build must succeed

Constraints

Allowed

  • Code-native UI
  • Original visual assets
  • Restrained motion

Forbidden

  • Purple-blob SaaS styling
  • Copied OpenAI, Cursor, or Linear branding
  • Unreadable fake dashboards
  • Repeated generic card grids

Acceptance criteria

  • The page has a clear original identity
  • Primary conversion action is visible and works
  • Keyboard navigation works
  • Mobile view remains readable

Evidence required

  • Production build output
  • Desktop and mobile screenshots
  • Keyboard navigation evidence
  • Known-bug list

Exact prompt

prompts/challenges/ai-coding-agent-launch-page.md
# BuildArena Challenge

Role: Senior frontend product engineer.

Project: AI Coding-Agent Launch Page v1.0.0

Objective: Build an original launch website for a fictional AI coding product with clear positioning and a credible conversion path.

Required outcome: Original brand system, strong hero, readable product UI, workflow explanation, integrations, social proof, pricing or conversion section, accessible navigation, responsive behavior, and restrained motion.

Constraints: Do not copy OpenAI, Cursor, or Linear branding. Do not use generic purple-blob SaaS styling, unreadable fake dashboards, or repeated generic card grids.

Verification: Run package scripts and verify conversion flow, keyboard navigation, reduced-motion behavior, mobile layout, and console output.

Evidence to return: Commands, test results, desktop/mobile screenshots, known bugs, missing requirements, human intervention, final commit, and deployment URL only when authorized.