Skip to content

Premium Functional Web Application

Build a research command center for creating projects, organizing evidence, comparing claims, and generating a report.

Open exact prompt

Overview

Test end-to-end product implementation beyond a static interface.

Capabilities tested

  • product architecture
  • forms
  • state
  • search
  • responsive UX

Required outcome

A coherent application with persistent local state, working navigation, and complete interface states.

Requirements

functional

  • Project creation
  • Source collection and detail view
  • Claim comparison
  • Search and filtering
  • Report generation

ux

  • Dashboard navigation
  • Command palette
  • Empty, loading, success, and error states
  • Responsive interface

technical

  • Persistent state
  • Accessible form controls
  • Production build must succeed

Constraints

Allowed

  • Local persistence
  • Mock source data
  • Established framework utilities

Forbidden

  • Dead controls
  • Unexplained placeholder states
  • Hard-coded score claims

Acceptance criteria

  • A user can create a project and add sources
  • Filtering and navigation change the visible content
  • Every required state is reachable
  • The report uses the saved project data

Evidence required

  • Production build output
  • Core-flow recording
  • State screenshots
  • Known-bug list

Exact prompt

prompts/challenges/premium-web-app.md
# BuildArena Challenge

Role: Senior product engineer.

Project: Premium Functional Web Application v1.0.0

Objective: Build a research command center where users create projects, collect sources, compare claims, organize evidence, and generate a report.

Required outcome: Working dashboard, project creation, source detail, search/filtering, forms, persistent state, a command palette, responsive navigation, and reachable empty/loading/success/error states.

Build order: Inspect the environment; implement project creation and source capture; verify one saved-project workflow; add search, claim comparison, and report generation; add states; run production validation.

Verification: Run package scripts and verify the primary user journey, persistence, keyboard behavior, narrow viewport, and console output.

Evidence to return: Commands, test results, screenshots of each state, flow recording, known bugs, missing requirements, human intervention, final commit, and deployment URL only when authorized.

Claims prohibited without proof: complete, production-ready, fully working, bug-free, accessible, responsive, performant.