Feature
Task Creation
Add new tasks with a title via a simple form interface
Claude-generated alpha starter
Track What Matters
A simple task tracker to help you focus on completion, not complexity.
A minimal task completion tracker that allows users to create, view, and mark tasks as complete. Designed as a lightweight proof-of-concept demonstrating core CRUD patterns.
Feature
Task Listing
View all tasks in a clean, scannable list
Feature
Completion Toggle
Mark tasks complete or incomplete with a single click
Feature
Task Deletion
Remove tasks you no longer need to track
Architecture
Next.js 15 App Router application with server components for the main UI and API routes for data operations. Uses in-memory storage for the alpha (no external database required). The architecture follows a simple pattern: pages render server components that fetch from internal API routes, while client components handle interactive state like form submissions and task toggling.
Core components
TaskList server componentTaskForm client componentTaskItem client component with completion toggleAPI routes for CRUD operationsIn-memory task store module
Timeline
Foundation
Project setup with Next.js 15, TypeScript config, and base layout
Data Layer
In-memory store module and API route implementation
UI Components
TaskList, TaskForm, and TaskItem components with styling
Integration
Connect UI to API, add loading states, deploy to Vercel
API surface
GET /api/tasks
Retrieve all tasks from the store
POST /api/tasks
Create a new task with provided title
PATCH /api/tasks/[id]
Update task completion status
DELETE /api/tasks/[id]
Remove a task from the store
Data model
Task
id: stringtitle: stringcompleted: booleancreatedAt: string
Setup
1. Clone the repository and navigate to the project directory 2. Run npm install to install dependencies 3. Run npm run dev to start the development server 4. Open http://localhost:3000 in your browser 5. For production deployment, push to a GitHub repository connected to Vercel
Operator notes
• In-memory storage means data resets on cold starts - acceptable for alpha demonstration
• No authentication implemented per scope constraints
• Consider adding optimistic UI updates for better UX in future iterations
• Tailwind CSS used for styling to keep bundle lightweight
Suggested env vars
NEXT_PUBLIC_APP_URL
Base URL for the application, used for metadata and potential API calls from client
FAQ
Will my tasks persist after redeployment?
No. This alpha uses in-memory storage which resets on each deployment or serverless cold start. A database integration would be needed for persistence.
Can multiple users share tasks?
This version has no authentication. All users see the same task list. User-specific tasks would require auth integration.