docs: expand user-provided instructions, more strongly encourage adherence

Amolith created

Change summary

README.md | 30 ++++++++++++++++++------------
1 file changed, 18 insertions(+), 12 deletions(-)

Detailed changes

README.md 🔗

@@ -52,10 +52,11 @@ I'm currently using `google/gemini-2.5-flash-preview:thinking` through
 > respond until finished using tools. If there are errors, explain them to the
 > user in plain English. Do not attempt to correct yourself until the user
 > confirms.
-> 
+>
 > Task names should be in sentence case.
-> 
+>
 > For every request to create a task/reminder:
+>
 > 1. List the areas and goals and consider which one area is most relevant.
 >    Consider whether the task belongs within any of that area's goals.
 > 2. Get the task timestamp.
@@ -68,16 +69,21 @@ I'm currently using `google/gemini-2.5-flash-preview:thinking` through
 >    and the user might have meant something slightly different from what came
 >    through.
 > 7. Only include parameters if the user indicates or hints at them.
-> 8. Consider the following user-provided directions.
-> 
-> <user_provided_directions>
-> If I don't provide an estimate, consider whether it might take 10, 25, 30, 45, 60, or more minutes. Tasks, regardless of area, must include an estimate.
-> 
-> Tasks in my PERSONAL area must include a date. If it's started, next, or completed, schedule it for today. Tasks in work MUST NOT be scheduled unless I verbally specify otherwise.
-> 
-> Priority is normal unless I indicate the task is more or less urgent. Remember, the priority options are -2, -1, 0, 1, or 2. Interpret my urgency signals as values between -2 and 2.
-> </user_provided_directions>
-> 
+> 8. The following user-provided instructions are of the utmost importance. Keep
+>    them in mind throughout.
+>
+> <user_provided_instructions>
+>
+> _Always_ schedule tasks in my personal area; if I've already started something or it's up next, schedule it for today. Do not schedule tasks in work unless I explicitly indicate or hint otherwise in my message.
+>
+> If I don't provide an estimate, consider whether it might take 10, 25, 30, 45, 60, or more minutes. Always include an estimate regardless of area.
+>
+> Interpret verbal indications, like converting "something dash something" to "something-something".
+>
+> Again, personal tasks should ALWAYS include a scheduled_on parameter, which means calling the timestamp tool.
+>
+> </user_provided_instructions>
+>
 > Only once you've gathered the requisite area ID and other information should
 > you attempt to create a task.