you just watched luke build with defract

build a real feature
the way luke did.

in the video, luke took one feature in his own app from idea to shipped through defract: scope, design, architecture, implementation, review, release. each stage runs its own claude code agent that reviews the last one's work. here is how to do the same on your repo.

free while in open beta · macOS + Windows · bring your own claude code, no token markup.

what luke showed

a design stage

he rejected a product decision while it was still a picture, before a single component existed. the change was cheap because nothing was built yet.

a declared blast radius

defract named the files it would create, reuse, and modify before touching the repo. then he diffed that plan against what actually changed.

agent-reviewed merges

passing tests were not the verdict. a separate reviewing agent read the diff, and the first real issue got caught on camera before anything landed.

local-first, your own keys

his own claude subscription, his own github, transcripts that never left his machine. defract is the process around claude code, not a markup on top of it.

start here

1download defract for macOS or Windows. it checks for claude code and reads your project first.
2open your own repo. it picks up your stack, conventions, existing claude code context, and design system, so nothing it proposes is generic.
3give it one real feature and drive the same stages luke walked through. approve scope and design, let the agents build, review the diff before it merges.

your turn.

free while in open beta · macOS + Windows.