The framing of "context engineering" does most of the work here. Feeding raw notes to a model is one thing. Structuring those notes into typed semantic blocks — here is the role the model should take, here are the constraints, here is the output format — encodes judgment that isn't in the source material. The model doesn't decide what's a constraint vs. a goal vs. an example. You do.
That curation is closer to authorship than most people acknowledge. The structure IS the intellectual contribution, independent of whether the prose gets generated or hand-written.
I've been building github.com/Nyrok/flompt around this, an open-source visual prompt builder that decomposes prompts into 12 semantic blocks and compiles to Claude-optimized XML. The point isn't automation, it's making the structure explicit so it can be reasoned about and iterated.
The framing of "context engineering" does most of the work here. Feeding raw notes to a model is one thing. Structuring those notes into typed semantic blocks — here is the role the model should take, here are the constraints, here is the output format — encodes judgment that isn't in the source material. The model doesn't decide what's a constraint vs. a goal vs. an example. You do.
That curation is closer to authorship than most people acknowledge. The structure IS the intellectual contribution, independent of whether the prose gets generated or hand-written.
I've been building github.com/Nyrok/flompt around this, an open-source visual prompt builder that decomposes prompts into 12 semantic blocks and compiles to Claude-optimized XML. The point isn't automation, it's making the structure explicit so it can be reasoned about and iterated.