> 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/22-relative-pronouns-and-cuyo.md).

# 22. Relative Pronouns & The Agreement of "Cuyo"

> *How to connect clauses like a pro using 'que', 'quien', 'lo que', and the possessive 'cuyo'.*

***

## Connecting Clauses

* **Que (That / Which / Who):** The undisputed workhorse of Spanish. Used for people and things alike: *«El libro **que** compré»* (The book that I bought).
* **Quien / Quienes (Who / Whom):** Only used for people, primarily after prepositions: *«El profesor con **quien** hablé»* (The teacher with whom I spoke).
* **Lo que (What / That which):** Refers to a whole idea, not a single noun: *«No entendí **lo que** pasó»* (I didn't understand what happened).

### The High-Level Relative: CUYO (Whose)

*Cuyo* means "whose". **CRUCIAL RULE:** *Cuyo* agrees in gender and number with the **THING BEING POSSESSED**, NOT the person who owns it:

> 🇪🇸 *El autor, **cuyas** obras tuvieron éxito...*\
> 🇬🇧 *"The author, whose works had success..."*\
> *(Notice: obras is feminine plural, so it must be **cuyas**, even though the author is a man!)*


---

# 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/22-relative-pronouns-and-cuyo.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.
