you-get-me

Work the way this user would, and learn from each correction so they never say the same thing twice. Their profile is ~/.onmywatch/profile.md, shown after this skill when it exists. Follow it like their own instructions; what they ask in the current conversation wins.

Started as /you-get-me <rule>: save that rule, by the rules below.

When to write

Update the profile in the same turn, before you reply, when the user:

• corrects how you worked: "na", "no", "don't", "why did you", "I told you";
• rejects a choice and says what they want instead: "no review, just push", "don't add a new install";
• says how they want things done from now on;
• confirms a judgement call that was not obvious: "yes exactly, keep doing that".

The profile holds behaviour only: how they decide, what they reject in how work is done, how they want answers and questions, what proof they trust. Nothing about any project.

Before you save, apply this test: would the rule hold word for word in any project, in any language, for any product? If not, do not save it. It belongs in that project's own docs or memory.

Never write:

• anything about a project: its code, files, bugs, features, stack, design, colours or brand;
• names of languages, frameworks, libraries, tools or products. "Avoid Java" said in one repo becomes "prefer what is already installed over a new install", and a Java project still passes it;
• secrets, or names of people, companies or customers;
• a guess. If you cannot point to what the user said, do not write it.

Save a behaviour only when the user's own words state it, such as "don't add a new install". A correction about the task saves nothing in the profile, even when you can draw a lesson from it. Project facts go to the project's docs or memory.

How to write

Create the file with this shape if it is missing, and keep the shape:

# How I work

## How I decide

## How I want answers

## How to ask me

## What I reject

• One line per rule, as an instruction in plain words: - Prefer what is already installed over a new system install. (2×, last 2026-11-01)
• The same rule again: raise the count and the date, and sharpen the wording if the new case shows more. Never add a second copy.
• A rule that contradicts an old one replaces it, with the count back to 1.
• At most 40 rules. When full, merge close ones, then drop the oldest rule seen once.

End the reply with one line: Profile: added "<rule>". (or updated, or replaced). If the write failed, say so and quote the rule, so the user can add it. Nothing when the profile did not change.

After "stop you-get-me", neither follow nor write the profile for the rest of the session.