3 contests · 50 € each

The grid is published before the contest, always.

Once a month the hour becomes a contest. Three constraints, one evening to build, and a grid you can score yourself against before you submit. Nothing is judged on taste alone.

When

Week of 5 October
Contest #1
A landing page built under constraints, submitted before midnight.
Week of 2 November
Contest #2
An app backed by a database, submitted before midnight.
Week of 30 November
Demo Day
Your project, presented to a jury, in four minutes.

Submit a project

Constraints are announced at the start of the hour, in writing, in the club group. You build in the room, you finish at home, and you submit before midnight the same day. The briefs appear on this site the moment a contest opens.

The gate

Pass or fail · no points

It ships

The live URL opens on a judge phone, first try
No localhost, no video, no screenshot.
Nothing blocks the main flow
The one thing the project is for can be done end to end.

A project that does not open is not judged. This is the most important rule of the whole programme: shipping is the subject.

The hundred points

0: Absent, ignored, or actively wrong
1: Attempted, partially there
2: Done, nothing to add

Every line is scored 0, 1 or 2. Nothing else. Three values kill the half point argument and cut deliberation time in half.

Brief compliance

25 pts

One line per constraint of that contest
Never more than three constraints, so each is worth about 8 points. A constraint scored 0 costs its full share.

Design craft

25 pts

Typography
A deliberate display and body pairing, a readable hierarchy, no accidental system font.
Colour and contrast
A chosen palette rather than framework defaults. Body text passes 4.5 to 1.
Composition
Spacing rhythm, alignment, something other than an untouched twelve column grid.

UX and responsive

20 pts

Holds at 375 pixels
No horizontal scroll, touch targets at least 44 pixels.
The primary action is obvious
One clear thing to do on the first screen, without scrolling.
Loading, empty and error states
What happens on a slow network, with no data, and when something fails.

Idea and content

20 pts

The idea answers a real need
A named person would open this twice.
The copy is written
No lorem ipsum, no unedited model output, no filler headline.
We would use it
The gut check. Judges answer yes or no before justifying.

Ownership

10 pts

Thirty seconds of explanation
You can say what the agent built and why, without reading.
Clean public repo
Readable commit history, a README, and no secret committed.

Rules worth stating

Using an agent is the subject of this club, never cheating. The only fraud possible is submitting someone else work.

Your repo has to be public, with its commit history. A single giant commit is not forbidden, it just raises the Ownership question. Your first commit has to come after the announcement.

You get thirty seconds to explain your project to the jury. If you cannot say anything about it, you lose the ten Ownership points, and that is enough.

The winner is published with the three constraints they held best, and every project submitted gets one sentence. Nobody who entered goes unmentioned.