24-hour take-homes · empty repo · live agent
Build something real. From nothing.
Each project is a brief, a clear set of acceptance criteria and a rubric you can read before you start. You get an empty repository, a sandbox where you can run anything, an AI agent, and a 24-hour window, so you can fit a few hours of focused work around your day. When you submit, your tests are run, your README is checked and the work is reviewed against the rubric.
3 projects · Developer tooling
- Developer toolingeasy
envcheck: a .env linter and diff tool
A developer tool that lints .env files with line numbers and reports drift against .env.example, never printing secrets.
- TypeScript (Node)
- Python
- Go
~2.5h focused work · 24h window - Developer toolingeasy
Changelog generator from conventional commits
A CLI that turns conventional commit history into grouped Markdown release notes and suggests the next semver.
- Node
- Python
- Go
~3h focused work · 24h window - Developer toolinghard
Feature flag service and SDK
Targeting rules, sticky percentage rollouts, an admin API with an audit log, and an SDK that evaluates locally and degrades safely.
- TypeScript (Node)
- Go
- SQLite
~5h focused work · 24h window
Scoped to a few hours
Every brief names a suggested effort, usually three to five hours. The 24-hour clock is a window, not a workload: stop at the suggested effort and write down what you would do next.
Judged on a public rubric
Functionality, code quality, testing, architecture, UX, documentation and how you used AI, each with a weight you can see before you start.
AI expected, and recorded
Use the agent as much as you like. Every prompt is recorded, and your report shows whether you reviewed and tested what it wrote.