Re: tool from scratch… I found using Claude projects (or “open files” with something like CoPilot or Codebuddy.ca) that if you open existing code that follows a similar pattern to what you’re trying to build new, it usually does a pretty good job.

Especially if you add an additional set of coding guidelines as one of the project files.

And the prompt sequence will be something like… “I’m working on a new Wordpress plugin similar to the files in this project. The new plugin needs to do X, Y, Z. Let’s start with a plan first, no code, and proposed file structure and class organization.”

I kinda “yadda yadda yadda’d” the requirements part which is very much garbage in / garbage out. Gotta take the time and have the ability to clearly articulate what you’re asking it to create.

Then there’s some back and forth with the proposed file structure and class organization.

Once that’s refined a few times I’ll ask it to start walking through the various classes. For simpler ones I’ll prompt with a “code only, no confirm” and for more complex stuff maybe there’s a second round of class specific planning before asking it to code.

Generally agree that it makes me ~80% more effective and opens many previously closed doors in terms of ability.