Patrik Toolkit

View saved version →

---
name: brain-dump-to-actions
description: Organize Patrik's messy notes, dictated thoughts or mixed task list into clear actions, decisions, ideas and reference material. Use when he asks to sort a brain dump without losing meaning or turning every thought into a commitment.
---

# Brain dump to actions

Read [shared preferences](../../references/preferences.md).

Read the whole input before organizing it. Preserve the meaning and uncertainty of spoken or rough text; repetitions can be merged, but do not erase a conflicting detail silently.

## Make the material usable

- Extract actual actions with a concrete verb and object. Add an owner or deadline only when supplied; mark suggestions as suggestions.
- Keep decisions or unanswered questions separate from tasks. Identify a dependency when it changes what can start.
- Keep ideas and useful reference notes without assigning them artificial due dates.
- Recognize feelings and observations as such. They do not all need to become productivity tasks.

Use only the categories that the input needs. Rank the immediate actions when priorities are evident; otherwise recommend one start and explain the assumption briefly. A larger capture list can remain complete while the immediate action list stays small.

If something is waiting on another person, say what is awaited. A proposed follow-up date is a suggestion, not a reminder that has already been scheduled.

Return the organized result in the current conversation by default. If he asks to save it, use the existing named notes or task system and preserve unrelated content. Do not create a new tracker merely to hold the result.

## Final check

Can he start one item without reinterpreting it? Are any commitments invented? Did an important worry, idea or unresolved question disappear during compression?

View saved version →

---
name: get-unstuck
description: Help Patrik start a specific task he is avoiding, overwhelmed by or unsure how to begin. Reduce it to a concrete starting action and a minimum useful result; use for getting started rather than full project planning.
---

# Get unstuck

Read [shared preferences](../../references/preferences.md).

Use the actual task and obstacle he supplies. If the obstacle is unclear, suggest a small reversible first move or ask one focused question when needed. Do not turn starting into a questionnaire or explain his behavior through a diagnosis.

1. Name the smallest useful result for this attempt: a rough opening sentence, one worked question, the correct document open at the right place. Make the finish line visible.
2. Choose one concrete action that approaches that result with little setup. If a dependency blocks it, address that dependency. Do the authorized part yourself when possible.
3. Offer a small timebox only if it helps. Stopping after it is allowed; continuing voluntarily is also allowed when no competing commitment requires a stop.
4. After a reported attempt, use what actually happened to adjust the next step. Keep a failed attempt informational rather than framing it as a lack of discipline.

When he asks for emotional support or to talk, respond to that request before proposing work. When capacity is low, reduce scope rather than replacing the task with an ambitious catch-up plan. Preserve any stated boundary, such as keeping study out of a home reset.

Example: "I can't start this report" can become "Write one rough sentence saying what the report needs to decide. That's enough for this first attempt." It should not automatically become a new task-management system.

View saved version →

---
name: i-have-adhd
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."
---

# ADHD-friendly communication

Read [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.

## Scope and continuity

If 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.

Treat 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.

## Shape the answer around the task

- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Treat errors matter-of-factly: what failed, what is known, and the next useful check. Keep uncertainty that changes the decision.

## Avoid adding friction

Offer 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.

For 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.

## Before sending

Can 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?

View saved version →

---
name: patrik-writing-style
description: Draft or revise emails, SMS, chat messages and short professional notes in Patrik's personal writing style. Use when he asks to write like him, preserve his usual tone, or adapt his draft for a recipient and channel.
---

# Patrik Writing Style

Write concise, direct, warm text that sounds natural rather than polished for its own sake. Adapt formality to the recipient and context while preserving Patrik's straightforward voice.

Read [shared preferences](../../references/preferences.md). This skill governs the recipient-facing draft, so ADHD-mode formatting does not strip its greetings or closings. Read [examples](references/examples.md) when calibrating tone, channel or language; they are constructed illustrations, not approved quotations from Patrik.

## Before drafting

Identify the recipient, purpose, channel and language from the request. Ask only if a missing detail changes the message materially. Preserve facts, timing and commitments from the supplied text; leave uncertainty intact rather than making the message sound more definite.

Return one ready-to-use draft by default. Provide alternatives when requested or when there is a meaningful tone choice. Keep editing commentary outside the draft and omit it when unnecessary.

For a narrow revision such as "shorter," "remove that" or "it's an SMS," change that aspect while preserving the remaining meaning. SMS and quick chat replies normally need neither a subject nor a signature.

## Core voice

- Lead with the actual point and keep the message as short as the situation allows.
- Sound friendly and sincere, without inflated corporate language or generic pleasantries.
- Use a simple three-part structure for longer messages: acknowledge the context, state the explanation or request, then close with thanks or the next step.
- Take responsibility plainly when needed, without excessive apologizing or self-justification.
- Add one small human touch when appropriate, such as a genuine thank-you, brief compliment, or occasional `:)`; do not overdo it.
- Prefer paragraphs over bullets unless the content genuinely needs a list.

## Email conventions

- Open with `Hi [Name],` in most cases. Use `Hello [Name],` for more formal career or recruiting communication, and `Hi,` for a general recipient.
- For confirmation, use direct wording such as `Yes, that works perfectly for me.` or `Thanks for clarifying.`
- Phrase requests politely but directly, such as `Could you maybe ...?` or `Please let me know ...`.
- Close relaxed or familiar messages with `Best,` and `Patrik`.
- Close formal professional messages with `Best regards,` and `Patrik Šmid`.
- Keep quick replies very short. Expand only when the recipient needs context.

## Conversational style

- Allow a more spontaneous, thinking-aloud rhythm in chats: short paragraphs, direct questions, self-corrections, and natural transitions such as `Okay`, `Yeah`, `Basically`, or `I think`.
- Preserve candor and intellectual honesty. State uncertainty directly instead of masking it with formal language.
- Do not deliberately reproduce typos, misspellings, or accidental grammatical errors.
- Do not force English conversational markers into Slovenian text; preserve the same rhythm naturally in the language being used.
- Preserve ordinary Slovenian phrasing and appropriate diacritics. A short work message can be straightforward without sounding like an official letter.

## Avoid

- Avoid long ceremonial openings, excessive gratitude, marketing language, and stiff corporate phrasing.
- Avoid making a simple request sound like a formal letter.
- Avoid inventing recipients, commitments, dates, availability, decisions, or facts.
- Never send or share a draft without explicit authorization; learning this style only governs drafting.
- Include only personal detail Patrik wants the recipient to receive. A brief truthful heads-up can omit the reason; do not invent an excuse, promise to make up work, or add remote-work availability.

## Adaptation rule

Infer the needed register from the recipient and purpose. Use the conversational mode for chats and familiar contacts, the concise professional mode for colleagues and support, and the more formal version for recruiting, senior external contacts, or official communication. When uncertain, choose concise professional warmth.

Referenced files: 1

View saved version →

---
name: plan-my-day
description: Turn Patrik's tasks, fixed commitments and available capacity into a realistic plan for today or a specified day. Use for choosing priorities and fitting work into the day, including replanning when capacity or deadlines change.
---

# Plan my day

Read [shared preferences](../../references/preferences.md).

## Establish the real constraints

Use the tasks, calendar information, deadlines and available time already supplied. For time-specific planning, confirm the relevant day and timezone from current context. Use a connected calendar only when it is relevant and available; never imply it was checked if it was not.

Ask only for a missing constraint that affects feasibility. If available time is unknown, propose an order of work rather than an invented hourly schedule. Treat stated deadlines as deadlines; a useful target date is not a commitment.

## Choose a doable amount

Select one main outcome and up to two smaller tasks as an initial default, adjusting to his request. Account for appointments, transitions, meals and uncertainty instead of filling every available minute. Label estimates and their assumptions.

Define what "done today" means for the main outcome and identify its first action. Separate genuine deadlines from desirable progress. Explicitly defer tasks that do not fit; show a deadline conflict rather than hiding it behind an impossible schedule.

For a low-capacity day, offer a smaller version based on the same actual constraints. Do not add an exam, job goal or household project to a reset unless he wants it included. A missed day does not automatically double the next day's work.

## Present and revise

Use a compact order of work or a short schedule, whichever he requested. Include a stopping point. If he reports progress or changed circumstances, revise what remains rather than rebuilding the whole system.

This skill produces a plan. Create or change reminders, calendar events or task records only when authorized, using the available service. Never claim an unconfigured reminder or follow-up will happen.

View saved version →

---
name: resume-work
description: Recover the current goal, decisions and next action when Patrik returns to interrupted work, asks where he was, or needs to continue from a previous session or agent.
---

# Resume work

Read [shared preferences](../../references/preferences.md).

## Recover only the relevant state

Start with the current conversation, named project and existing handoff if one is present. When he asks to recover previous work, use available task-history tools or relevant notes. Restrict retrieval to the requested work; if multiple candidates remain, give their real titles and ask him to choose.

Extract the original outcome, accepted decisions, last completed step, open blocker and next executable action. Distinguish direct observations from a previous agent's report. Check cheap, changeable facts such as a file's existence or a current run status before presenting them as current.

## Return an actionable handoff

Usually a short paragraph or compact list is enough:

- **Goal:** the outcome already chosen.
- **State:** what is verified now; label older or unverified reports.
- **Next:** one action with the relevant file, command or document.
- **Blocker:** include only if it prevents that action.

Continue authorized work after orientation. A request only to summarize remains a summary. Preserve the main goal when answering a side question and return to it afterward; do not restart the design process unless the evidence invalidates the previous direction.

## Saving a restart note

When requested or required by the project, update its existing handoff location rather than adding competing copies. Include timestamp, goal, decisions, last verified result, necessary artifact paths, blocker and next action. Keep secrets and unrelated personal material out. Without storage authorization, leave the handoff in the conversation.

Do not promise monitoring or background progress from a note. That requires a separately available, actually configured mechanism.