Recently, a few friends and I got together for a few days to learn from our resident AI whisperer.

I had been playing with AI for a bit, but this was a little more “formal”. I won’t bore you with all the details, but this was one of the biggest takeaways -> I created a document to encompass some of the best practices (for me) at this time, to create a software project.

One of the issues I have had wrapping my head around AI mastery is that there are no hard and fast “right way” to do things. In HTML, if you want an H1, you wrap it in “<h1></h1>” tags. With AI, if you want a successful program, there are MANY ways to achieve your goals. And even more ways to not prompt effectively.

I know where I am, and where I want to go – it’s the proper wording of the directions to traverse the trail is where I get lost.

This process utilizes additional files (other than the instruction file) that I have created for the overall experience. These are based off some of the Claude code guidelines. They can be adapted and used to ways that are beneficial to you, if needed.

Here are links to the files I have installed in my .claude/commands/ folder… I made them .txt so WordPress would take them with no modifications. For Claude, rename them to <filename>.md -> init-project, log-decision, session-summary and update-status.

And here is the instruction document of how to use it in Claude Code. Also, should change the file extension to ‘.md’ after downloading.

This is an example of how I was able to get a grip on creating a project in Claude code. I am confident, much like cooking, everyone has a favorite recipe. And like a true chef, this recipe will change and evolve over time as well. This is a good starting point, and by the time you read this, it may be outdated…

Oh, yes… I neglected to mention that I employ agency agents to help with the software creation process.