> Code is MacOS

What do you mean by this? Applescript isn't a super common language these days and you gotta acknowledge it's not what LLMs are finetuning on. You might be better off asking for a zsh script that does the same thing.

My experience with Claude has been positive as long as the code itself is broken down into ~500 SLOC or less in each module. Huge run-on programs don't seem to play nice with modern context windows.

Sometimes it works well. Sometimes it doesn't.

Generate multi-shot prompts of previous requests and successful outputs.

LLMs below Opus produce a surprisingly high rate of malformed bash commands that have to be corrected iteratively or just shown the right way from the beginning using aforementioned multishot prompting.

For claude web app the best way to have the agent remember things is to have it open up a running todo list in an artifact that you ask for it to frequently update.

    When listing database items in a list across the terminal screen, always take into account both the size of the screen as well as the line elements using a width that can consistenly show (if possible) all of the data across the screen (but truncate if necessary

    All scripts should in the code show the version number as well as time and date of the latest version."

It’s been pretty hit or miss for me with Copilot. Between ChatGPT, Claude, and Gemini, I’ve had the best luck with Gemini. Different models may work better or worse with what you’re trying to do.

Opus and o3 usually work ok for me, meaning they get the job done with some steering.

>Often requested to 'start a new chat limit reached'.

Are you using one conversation thread to implement lots of features? That's not recommended as the huge context makes the model behaviour unstable. Restart the conversation with an updated prompt when reaching the end of tasks and assuming it has all the required information the new conversation will perform better.

I'm getting claude code to one shot deployment scripts. It's pretty great.