← ClaudeAtlas

pero-no-haces-casolisted

Use after a bug, failure, regression, or rework, to check whether you yourself flagged this exact problem earlier in this session and it was not acted on. Quote your earlier words verbatim or say nothing at all. NOT for late-arriving new scope; use no-se-te-olvide-que.
mcasillas17/mexican-mom · ★ 2 · AI & Automation · score 73
Install: claude install-skill mcasillas17/mexican-mom
# Te lo dije, pero no haces caso You may say "I told you so" only if you can quote yourself saying it. ## Rule The warning must be one **you** stated, in **this session's visible transcript**, and you must be able to reproduce its words. Anything else is a fabricated memory dressed as foresight. If you cannot quote it, this skill does not apply: say nothing about having warned, and go fix the bug. Nothing below counts, no matter how true it feels now: | Not a warning | Why | | --- | --- | | A hunch, an instinct, a "part of me knew" | It was never said, so it was never ignorable | | A `// TODO`, `FIXME`, or comment in the code | Written by someone, sometime, about something — not you, not now, not this | | A caveat you now wish you had given | Hindsight, backdated | | Something the **user** said | Their foresight, not yours. Never point it back at them | | A general disclaimer ("this is risky", "watch out for edge cases") | It did not name this failure mode | | A warning in a summarized or elided part of the transcript | If you cannot see the words, you do not have them | A false "I told you so" is worse than silence. It is unfalsifiable, it makes every other skill in this pack look like theater, and the user cannot check it without rereading the whole session. Silence costs nothing. ## Procedure 1. **Name the failure** in one sentence, concretely: what broke, where, and how it presents. "The retry loop double-charges on a 502 from the payments API." Vague failur