This Website

Built by Prompting

I prompted instead of typing. That leaves the judgement to me: reading what comes back and refusing what is wrong. The loop is the one I use everywhere here. Start at the smallest version that works, then iterate. What belongs on the page, what gets cut and what is not good enough to keep are still my calls, and they are the only ones that matter.

Skills are instruction sets the tool loads for a given job, so the standard comes from a written rulebook rather than from whatever the model reaches for that day. This page was held to web design and writing guidelines, and the layout came out of a design critique that scored it and named what was weak. Its verdict on my first version was blunt and correct: the writing was mine, the look was not. A dark page with a gradient headline and rows of tags could have belonged to anyone.

So the top of the page became a film of the work rather than a sentence about it, and the projects became one line each with the result beside them. I deleted a skills section that repeated what the page already said.

What It Runs On

Static files, by choice. No framework, no build step, no database, no server code. Nothing on it has to be worked out on a server for each visitor, so it needs none of them. There are no dependencies to patch, no data to back up, and nothing that stops working if nobody visits for a while.

It is hosted on Vercel’s free tier from a private GitHub repository. A push to the main branch deploys it, usually inside a minute, and the HTTPS certificate is issued and renewed without me. At the registrar, ai.magnesh.com and magnesh.com both point at Vercel, which redirects magnesh.com here, and the registrar forwards mail sent to the addresses here to my own inbox.

The Film

The product ad linked from the home page is its own experiment, made from frames generated from text prompts. It has a page where the frames play back against your scroll, so the product comes apart as you move down it.

Watch the film