Blame Context
Hover any line and see why it was written, reconstructed from commits, PRs, and issues. Built for Pair Programmer's Apprentice — use lumen forge to build a tool for developers who are new to a codebase. Git history reconstruction and the hover card. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Blame Context — main view
Blame Context — result state
On the clock
What shipped, what didn't
Completed in time
Git history reconstruction and the hover card.
Unfinished / faked
Slow on repos over 10k commits — no caching layer.
Obstacles
Spent too long on the data model and had to build the interface in the last eight minutes.
Lessons learned
Test the demo path once at minute 25. I didn't, and it showed.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Blame Context data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Started from the official framework starter template, unmodified.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
Excellent use of the model — it is doing actual work here, not decorating a form. The failure case you showed earned you points rather than costing them.
Marcus Bell
Founder, Bellwether Studio
The scope discipline here is the whole story. One path, finished, demoed without a stumble. That is what a 30-minute build should look like.
Hana Kobayashi
Principal Research Engineer, Independent
Excellent use of the model — it is doing actual work here, not decorating a form. The failure case you showed earned you points rather than costing them.
Discussion
0 comments
No comments yet.