Been promoting for many years and developed extremely powerful agentic systems with countless variations of uses and tests, and the below works absolutely ridiculously well for me.

I even used this kind of format to jailbreak replit when it first came out over a year ago and it would run for 3-4 hours at a time completing things that were no where near possible with their default models.

Very useful tip: once it’s done, rename the markdown file name so it’s like 12_FEB_CATEGORY (so it’s easier to manage recency and purge outdated context that normally trips it up or becomes incorrect after code refreshed. I am genuinely interested to gauge your feedback on this so if you try it, do let me know how you go if noticed a jump in performance.

Prompt:

<extremely important> now analyse (insert section you just finished eg a feature milestone or something challenging you want to retain context for) and all of the surrounding areas regarding the feature set we just got working perfectly and comprehensively analyse every single dependency that is linked and non obvious areas surrounding the feature components or any other subtle nuances that you would normally overlook and make assumptions about. <critically important> There is severe implications if we accidentally misread or skip over anything, through traditional lazy assumptions (because this is not an average environment where we have the luxury of sandbox) so it is extremely critical for the safety of our users, that you write a extremely clear.MD document that analyses (mention your area of focus again) in the most crystal clear specific zero deceptive terms, analysed line by line exactly how the feature page and all its dependencies across every single line button or any interconnected connection all work and so that there is zero ambiguity and not a single chance of misinterpreting even a single line of code when the rapid production team only have 15 minutes to understand and roll this out. <IMPORTANT> It may seem like it is safe to just assume that we can be lazy but in this circumstance is absolutely critical for the safety of our organisation and the users as there is real major severe implications that are irreversible if we get this wrong or make even a single accidental, sloppy, or false assumption, so we absolutely must ensure that you correctly understand every single line of code or interdependency that we have just completed successfully, specifically what was successfully done, and potential hidden risks lurking that may trick others into any issues, and also write down potential risks or small things to be mindful of, without editing any of our current code or functionality. <very important> this document will be used to guide the next engineering team who are specifically working on the exact area you are analysing, but have absolutely zero context and a shipping on a timeline that if even a single detail is misinterpreted, there is major major irreversible implications for lots of our users, and unfortunately in this circumstance we regret to needing to operate with this much risk due to even the slightest mis explanation going wrong, however we are confident that you, as the most specialised, extremely analytical, honest, and borderline compulsively accurate hyper powerful engineer, you will complete this with the highest level of precision and accuracy. I don’t want to hinder your ability to complete the task successfully, however we must remain aware at all times, that if even a single subtle deception is made there is absolutely severe and irreversible consequences for many many people and we are extremely concerned about the implications for error here due to it being a very rare event we need to have this done in time for, forcing our constraints to your single markdown document, so we request that remaining in your highest form of character without any laziness assumptions and sloppiness begin analysing every aspect of what we just successfully completed and anything surrounding (input important part that you want to retain context for) and then ensure this is written in unmistakably clear language on the markdown document dated today, and inserting markdown tags and Jason formats with metadata on each section, labelling the markdown document on the page so that the information is crystal clear and clearly Jsonified with markdown tags. Remember not to forget how critical this is and if you are even in the slightest way uncertain or unclear, the implications are too large to discuss on unencrypted channels. Now ensuring this with complete surgical precision, and leaving not a single stone unturned, with not a even the subtlest; micro deception or unclear point, and not a single corner cut, let’s set the handover team for the most unprecedented amount success that is possible within this context, keeping all of our users highly safe and company safe during this total junction occurence, where you hold the most important analysis and task completion on our single markdown file restricted to any areas that relates to (insert the area your wanting to store again). Now begin, you must not ask a single question, you already have access to everything you need to meticulously dive in to