There is no doubt in my mind that he is personally pissed because Anthropic stood up to him.

Now I have a favorite in my bookmark bar for each project I am working on that shows me the docs.

I'm so happy.

The endpoint verifies that the destination specified by the POST is in my project folder. If it points at an existing file, it creates a version. It does not overwrite.

I added a CLI, watchFile, that blocks Claude until the file shows up.

And made a skill that tells Claude to respond nicely to "Make an interactive document that...".

Claude Code has basically made software functionality, "Your wishes come true".

I run a web server on my Mac. Consequently, I have an HTTP process available. I keep intending to make an endpoint that Claude can use. I would tell it to make a document for commenting (or put a list of options or whatever) and post it to, I guess, the planning folder we are working in. The endpoint would know how to do this because I wrote it.

When it gets there, I would, I wanted to keep it, tell Claude to integrate the results into the file as static HTML. Or, if I don't care about that, just read it and do whatever I said and leave it disconnected.. The goal isn't to make a website.

This supports interactive conversations with Claude via HTML.

BUT, I only do this as an easy way of referencing specific ideas and text in notes to instruct Claude. I say, "I have added notes. Read them and adjust the doc accordingly." Or, "Read the notes I added. Turn them into html."

It's an insanely productive pattern.

Generating markdown is faster so unlike our friend here, I still do use it for straightforward things.

BUT, in general, I tell Claude, "I think we should starting a project planning folder for this. Put (the stuff we just talked about) into an html doc. while you're at it, make an index.html and put relative link to the page with a little explanation of what we are up to."

Or, just yesterday Claude and I worked out the design for a substantial AI enabled database tool. I had it make an explanatory doc for my team. It was a single html file that navigated through forty scenes that demonstrated it. MAGIC.

If you aren't doing your collaboration with Claude in html, listen to this guy. Your life and work will be better.

In practice, most designers know what they are doing as well as you know your job. If yours doesn't, you hired a quack.

Here. Try this, in practice, most business owners don't know what they are doing. In practice, most programmers write shit. It's easy to bitch at artists because most people don't understand what they do. Don't be one of those people.

I am 100% supportive of it being used for training... AI, you, everyone.

It has basically eliminated surprises like that.

Hasn't happened in a long time. Opus 4.6 is a miracle improvement.

It has examples of all the parts of a web app written, over many years, to be my own ideal structure. When the LLM era arrived, I added a ton of comments explaining what, why and how.

It turns out to serves as a sort of seed crystal for decent code. Though, if I do not remind it to mimic that architecture, it sometimes doesn't and that's very weird.

Still, that's a tip I suggest. Give it examples of good code that are commented to explain why its good.

I suppose if you are doing something that truly can be decided based on a test but, I just don't see it, at least for anything I do.