By this point in the course you have two personalisation layers already working for you. Your context document, built in Module 3, tells the tool who you are, how you write, who your clients are, and what your standing preferences are. Your project instructions, built in Module 9, tell the tool what this specific piece of work is about: the client, the destination, the documents, the requirements.
This module adds the third layer: platform-level custom instructions that sit between the context document and the project. They control how the tool behaves by default, across all your work, in ways that are more specific than your context document can handle and more persistent than what belongs in a project instruction.
Think of it as the difference between telling someone what you do and telling them how you prefer to work. Your context document says: I am a travel advisor who works with high-end leisure clients across Southern Africa. Custom instructions say: when I ask you to draft an email, always write in prose, never use bullet points in client communications, keep the length under two hundred words unless I specify otherwise, and never open with a greeting that includes an exclamation mark.
That level of specificity removes an entire category of editing from your workflow. Instead of correcting the same default behaviours in every output, you set the preference once and it applies everywhere. The cumulative time saving is significant, and more importantly, the output starts closer to what you actually want every time.
