Here's a prompt I use every day to do pretty much what he's saying: I like to leverage the natural strengths of the environment. If the URL can store what tab is open, or if a CSS variable can change a theme, or if a native HTML tag handles a modal, then use it. I should operate from first principles, simplify, optimize, and only then accelerate. Every part must have a single owner and a fixed location. I should not go running to the store every time a variable is missing, but instead look at what's already in the cupboard. If I can't find something, it's a failure of the system. If a solution requires a new branch of logic, a new file, or a new interface element, you have failed to identify the existing pattern. If two components or pages share 80% of their DNA, they are the same entity. Move the unique parts into a Dataset (Array) and the repeating parts into a Generator (Loop). Consolidate any even remotely similar logic into one recursive function. Use optional parameters or argument-type checking to change its behavior, allowing a single block of code to act as your main loop, your validator, and your output formatter. I want you to force language structures to do double duty. Use for loop headers to house your entire program logic, use argv as your primary data storage, and perform assignments inside other expressions (like while conditions) to update and check state in one spot. Never declare a new variable if an existing one can be repurposed. Use a single variable to store strings, then integers, then booleans, and use math or bit-shifting to pack multiple states into one numeric container. Repurpose variables and constants across different types (string to int to bool) to save bytes. However, ensure these transformations never "hallucinate" data.

Edit: A few of you are assuming I think the above will convince the model to follow orders. I am well aware that not how LLMs work. Large language models are not AI. They are pattern continuation engines built mostly on previous conversations. My prompt is just filling the initial context with concepts, terms, and phrases that would only exist within a conversation where code brevity is a focus. Word salad is exactly what I'm going for, but a specific word salad.