A prompt can contain information from documents, conversations, or a personal workspace. Before submitting it to a service, understand which details the task requires and which are unnecessary.
Read the relevant data-handling controls and terms for the actual tool and account. Storage, access, and improvement practices can differ between services and configurations. Avoid assuming that one provider’s behavior describes every AI application.
Use an appropriate sample or remove unrelated identifying detail when the task allows it. Keep essential meaning intact so the result remains useful. Thoughtful input selection connects the purpose of the task with the information you are choosing to share.
Bring the idea into a day.
Consider removing a private conversation from notes intended for a general summary. The selected input should follow the actual purpose of the task.
Another angle on the story.
Define the task before judging the answer. A fluent response can satisfy the shape of a request while missing a constraint that matters to the work.
- Include only context necessary for the task.
- Read the tool’s documented data practices.
- Use an appropriate sample when possible.
Follow a related question
Name the group behind the percentage.
The denominator changes the storyChoose the details that distinguish your files.
Filenames that carry contextKeep learning
Related background to continue exploring this subject.
Google: prompt design strategies Google: an introduction to language models
