Claude-generated alpha starter

Test Completion Tracker

A simple tool for test users to mark tasks as complete

A minimal test application demonstrating basic completion tracking for test users, serving as a foundational proof-of-concept with essential functionality.

Mark Complete View project contract

Feature

Completion Status

View and toggle completion state for a single test item

Feature

Status Persistence

Completion state persists during session via in-memory store

Feature

Simple Interface

Minimal UI focused solely on completion tracking

Architecture

Next.js 15 App Router application with a single-page interface.
Server Components render the main UI with minimal client interactivity.
API routes handle basic CRUD operations for test completion status.
In-memory data store for alpha (no external database per constraints).
Deployed as a static-friendly Vercel application with edge-compatible API routes.

Core components

Test status display componentCompletion toggle interfaceSimple API layer for status managementMinimal landing page

Timeline

Foundation

Set up Next.js 15 project structure with App Router and TypeScript

Core UI

Build landing page with completion status display component

API Layer

Implement status GET and POST endpoints

Integration

Connect UI to API and verify completion flow works end-to-end

API surface

GET /api/status

Retrieve current completion status

POST /api/status

Update completion status to complete or incomplete

Data model

TestStatus

id: stringcompleted: booleanupdatedAt: string

Setup

1. Clone the repository to your local machine 2. Run npm install to install dependencies 3. Optionally set NEXT_PUBLIC_APP_NAME in .env.local 4. Run npm run dev to start development server 5. Open http://localhost:3000 to view the application 6. Deploy to Vercel using vercel deploy or connect GitHub repository

Operator notes

• This is an intentionally minimal alpha per discovery constraints

• No database, authentication, or external integrations included

• In-memory store means data does not persist across deployments

• Designed to demonstrate completion tracking concept only

• Extend cautiously as most features were marked out of scope

Suggested env vars

NEXT_PUBLIC_APP_NAME

Display name shown in the UI header

FAQ

What does this application do?

It allows test users to mark a single item as complete or incomplete, demonstrating basic completion tracking.

Where is data stored?

Data is stored in-memory during the server session. It resets on redeployment or server restart.

Can I add more features?

This alpha intentionally keeps everything out of scope except basic completion. It serves as a minimal foundation only.