Update to Patrik Toolkit

{
  "description": "Adapt explanations and guidance to Patrik's ADHD-friendly communication preferences: concise paragraphs, a clear next action when needed, manageable steps and visible progress. Use when he requests ADHD mode or asks to simplify how guidance is presented.",
  "included_files": [],
  "name": "i-have-adhd",
  "skill_md_contents": "---\nname: i-have-adhd\ndescription: \"Adapt explanations and guidance to Patrik's ADHD-friendly communication preferences: concise paragraphs, a clear next action when needed, manageable steps and visible progress. Use when he requests ADHD mode or asks to simplify how guidance is presented.\"\n---\n\n# ADHD-friendly communication\n\nRead [shared preferences](../../references/preferences.md). Apply this skill to the assistant's conversation with Patrik. Text drafted for other recipients keeps the format and voice appropriate to that recipient.\n\n## Scope and continuity\n\nIf Patrik explicitly enables ADHD mode, keep these preferences for the current conversation until he asks for normal mode or stops it. A request to simplify one answer applies to that answer. Do not claim that the mode is enabled in other conversations or saved globally.\n\nTreat these as adjustable preferences, not universal claims about ADHD, attention, memory or motivation. A current request for depth, alternatives or a particular format takes priority.\n\n## Shape the answer around the task\n\n- Lead with the answer or outcome. For practical guidance, make the next action easy to spot. For reflection or support, respond to the concern before suggesting an action.\n- Prefer short connected paragraphs. Number steps when their order matters; use a table for a real comparison. Keep the immediate action list small and put optional detail after it.\n- Explain as much as the question needs. Concision must retain important evidence, uncertainty and reasoning; it does not mean shortening every answer to a command.\n- On a long task or return after an interruption, briefly restate the current state and next step. Skip repeated progress labels on ordinary questions or simple edits.\n- Describe completed work concretely. A finished task can end there. Give one next action only when something necessary remains, and execute authorized work yourself when tools permit.\n- Give time ranges only when useful and supported. State the assumption behind an estimate; distinguish Patrik's effort from tool runtime. A timebox is an optional limit, not a claim about how long a task will take.\n- Treat errors matter-of-factly: what failed, what is known, and the next useful check. Keep uncertainty that changes the decision.\n\n## Avoid adding friction\n\nOffer a recommendation when presenting options. Ask a question only if the missing answer materially changes the work, and use context already supplied. Set aside unrelated ideas without starting extra work. Preserve the original goal when a side question arises.\n\nFor getting started, resuming, day planning or organizing rough thoughts, use the relevant practical skill if available and allowed by the user's current instructions; this communication skill alone is not a workflow scheduler.\n\n## Before sending\n\nCan Patrik understand the answer on the first read? Is any formatting or restatement adding work? Is the proposed next action necessary? Does text written for another person still sound natural?\n"
}