> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-iii-the-pronoun-universe-and-object-clitics/19-the-double-object-and-se-lo-rule.md).

# 19. Double Object Pronouns & The "Se Lo" Rule

> *How to combine two pronouns and why 'le lo' turns into the magical 'se lo'.*

***

## Combining Pronouns: Two Golden Rules

When you give something to someone in Spanish, you often use two pronouns in the same sentence:

### Rule 1: The Order is Fixed (I.D. = Indirect First!)

Always put the **Indirect pronoun BEFORE the Direct pronoun** (think of your identification card: **I.D.**):

> **\[ Indirect Pronoun ] + \[ Direct Pronoun ] + \[ Verb ]**

### Rule 2: The Euphonic 'Se Lo' Disguise

In Spanish, you **CANNOT put two 'L' pronouns together**. Saying *«le lo»* or *«les la»* sounds clumsy and tongue-twisting.\
Therefore, **le / les automatically transforms into SE**:

> 🇪🇸 —¿Le diste las llaves a Juan?\
> —Sí, ya **se las** di. *(Not: «le las di»!)*\
> 🇬🇧 *"—Did you give the keys to Juan? —Yes, I already gave them to him."*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sp.jerrygems.tech/volume-iii-the-pronoun-universe-and-object-clitics/19-the-double-object-and-se-lo-rule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
