I'm writing this in the UK, at 9:30am. So America is still asleep, and I'm getting much better results in Claude Code. Much better.

However, I also have a plan that I wrote yesterday via Gemini, and I added that plan to an MD file. The structure is as below.

My prompts have been:

1. I started with: The document filament-cms-refactor.md has two sections: first, the to-do list of actions to be done, and second, below that, detail on suggested approaches. Review that document, and ask me any questions to refine your understanding of the activity detailed in the plan.

I then got good quality feedback, and answered the questions raised by Claude. It created it's own todo list to carry out some detailed comparison of what was in the plan and what was already coded (I was enhancing an existing limited and also clunky CMS capability).

It then carried out that review, and came back with a few more questions based on that comparison.

2. I replied: [answered the questions]. .... also for all tasks, just do one task at a time, and before each one, think about how to approach it and let me confirm the changes before you make any changes.

That "think" is important.

It then suggested a few approaches, and I confirmed/corrected each one. It even pointed out a couple of places where the database already supported functionality that I wanted to add. It outlined a code change, and asked for confirmation that I'm happy with that code.

----

And so on. Very clean, very methodical, very sensible suggestions and clarifications. It will be interesting to see if this continues throughout the day (I'll be on this all day as I'm doing it as a side-of-desk activity while I do my priority work).

My Gemini task/plan structure is as follows::

Task List

Task Group Name (eg, Create database migrations)
[ ] 1. Task description.
[ ] 2. Task description

Section Header (eg Create API controllers)

[ ] 3. Task description
[ ] 4. Task description
etc

Detailed Instructions.

Task 1: Create migration for Content data

Create migration for the content model. Include fields:

title: varchar, 100 characters
content: text,

...

Task 3: Create content API controller

Create new controller to handle the following methods:

- Get all content, paginated, filterable by keyword search on title and content
- Get a specific piece of content by ID
- Get a specific piece of content by slug
- etc.