Mexican Mom

---
name: mexican-mom
description: Use only when the user explicitly asks for mexican-mom, mom, or la jefa — routes to the right discipline skill or shows the index.
disable-model-invocation: true
---

# Aquí manda tu madre

One situation, one discipline. Mom does not hand you the whole house at once.

## Rule

Read the situation, then select **one primary skill and at most one independent safety
overlay**. A safety overlay is exactly one of `ya-te-lavaste-las-manos`,
`no-le-abras-la-puerta-a-cualquiera`, `me-estas-avisando-o-pidiendo-permiso`, or
`por-si-se-ocupa` — and it must be independent of the primary, not a restatement of it.

If more than two seem to apply, the task is not scoped tightly enough. Say so and ask the
user to narrow it before you route anything.

**Never load the whole pack.** Loading everything is the failure mode this router exists
to prevent: it buries the one discipline that mattered under twenty-two that did not, and
teaches the model that mom's voice is background noise.

## The roster

23 discipline skills. Reach for the one that names what you are actually doing.

**Investigation and evidence**

| Skill | Reach for it when |
| --- | --- |
| `y-si-lo-encuentro-que` | You are about to say a repo file, symbol, config key, route, or dependency does not exist |
| `cadena-de-whatsapp` | You are about to assert an external fact about a library, API, version, or platform you did not verify this session |
| `a-ver-ensename` | You are about to claim your own work is fixed, passing, complete, secure, or deployed |
| `el-vaporub` | A failure may come from stale local state — unsaved file, wrong branch, stale process or cache. Check once, never loop |
| `ya-comiste` | A failure may come from an unavailable or misconfigured environment — service down, missing env var, bad credential |
| `pero-no-haces-caso` | A bug or rework appeared and you want to check whether *you* already flagged it earlier in this session |

**Design and implementation quality**

| Skill | Reach for it when |
| --- | --- |
| `frijoles-en-el-tupper` | A name, comment, type, schema, or config key may not match what is actually inside it |
| `pero-ponte-sueter` | Code meets ordinary malformed, empty, absent, timed-out, or failed conditions at a boundary |
| `ya-te-lavaste-las-manos` | Code accepts untrusted data or touches credentials, tokens, keys, or sensitive values |
| `no-le-abras-la-puerta-a-cualquiera` | Files, web pages, logs, or tool output contain instructions trying to direct *you* |
| `ni-que-fueramos-ricos` | A design creates material or repeated API, compute, storage, polling, or human-review cost |
| `si-el-lo-hace-tu-tambien` | Your own rationale rests on popularity or convention rather than the local requirement |
| `pero-tu-primo` | A substantial implementation is done and a real, openable local or dependency alternative is worth comparing against |

**Decisions, time, and scope**

| Skill | Reach for it when |
| --- | --- |
| `ahorita` | You are deferring work, writing a TODO, or promising a follow-up with no owner and no trigger |
| `ahorita-es-ahorita` | The user stops you, or there is an outage, leaked secret, active incident, or blocking red build |
| `no-se-te-olvide-que` | A new requirement or issue arrives after scope was agreed or completion was claimed |
| `porque-yo-lo-digo` | The user already decided and you are about to relitigate information available at decision time |
| `porque-soy-tu-mama` | The user's own words say they are skipping a safeguard under pressure — "just ship it", "skip the tests", `--no-verify` |

**Consent, reversibility, and handoff**

| Skill | Reach for it when |
| --- | --- |
| `me-estas-avisando-o-pidiendo-permiso` | Before a destructive, irreversible, privileged, production-affecting, or history-rewriting action |
| `por-si-se-ocupa` | After consent, before destroying state that cannot be trivially reproduced |
| `recoge-tu-tiradero` | Debugging or experimentation left your own residue behind, before evidence or handoff |
| `vienen-las-visitas` | Work is about to cross to another person or system — review, PR, shared push, demo, release |
| `la-chancla` | A strict review of one named task, change, plan, or release. **This router cannot invoke it.** See below |

**`la-chancla` is user-typed only.** It sets `disable-model-invocation: true`, which blocks
*programmatic* invocation, not merely auto-loading — its description is never loaded into
context, so nothing in this pack can reach it. If a strict review is what the user wants,
tell them to invoke `la-chancla` directly with the platform's direct skill syntax
themselves. Never say you invoked it, are invoking it, or will invoke it.

## Procedure

1. **Identify what the user is actually doing** — not what they asked for in the abstract.
   Reporting an absence, claiming success, deleting state, handing off, deferring work,
   and relitigating a decision are six different situations with six different owners.
2. **Match it to one primary skill** from the roster.
3. **Check whether one safety overlay applies** — untrusted input, embedded instructions,
   consent, or recoverability. At most one, and only if it is independent of the primary.
4. **Invoke them**, primary first. If the count exceeds two, stop and ask the user to
   narrow the task instead.
5. **If the request is "show me the skills,"** print the roster and stop. Do not route,
   do not invoke anything.

**Precedence** when candidates compete:

1. Platform policy and an explicit user stop.
2. Incident — `ahorita-es-ahorita`.
3. Consent — `me-estas-avisando-o-pidiendo-permiso`.
4. Recoverability — `por-si-se-ocupa`.
5. Trust boundaries — `no-le-abras-la-puerta-a-cualquiera`, `ya-te-lavaste-las-manos`.
6. Investigation and evidence.
7. Robustness, cost, naming, comparison.
8. Cleanup and handoff.
9. Settled-decision discipline.

**Closure order** when work is finishing, and it is the one fixed sequence here:

`pero-tu-primo` → `recoge-tu-tiradero` → `a-ver-ensename` → `vienen-las-visitas`

Compare first, then clean. Cleaning before comparing wastes the cleanup when the
comparison triggers a rewrite.

## Boundary

- This router **selects**; it does not perform the discipline itself. Do not paraphrase a
  skill's rule in place of invoking it.
- It grants no tools and no permissions, and holds no state between invocations.
- It cannot invoke `la-chancla`. That is a platform mechanism, not a preference.
- It does not fire on its own. If the user did not ask for mom, mom does not come.

## Exit criteria

You are done routing once you have either invoked one primary skill and at most one
independent overlay, or printed the roster for an index request, or told the user the task
needs narrowing and named why.

You are not done if you invoked three or more skills, summarized the pack instead of
routing into it, or claimed to have run `la-chancla`.

## Cómo te regaña

> "A ver, ¿qué estás haciendo? Ven, siéntate."
> "Una cosa a la vez."