> 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-vii-the-imperative-mood-commands-and-prohibitions/49-pronoun-attachment-and-accent-shifts.md).

# 49. Pronoun Enclisis & Written Accent Shifts

> *Where to put pronouns during commands and why accents magically appear.*

***

## The Positioning of Pronouns with Commands

### Rule 1: Affirmative Commands → ATTACH TO THE END (Enclisis)!

When you tell someone to DO something, glue the pronouns directly onto the tail of the verb as one single word:

* *«¡Dí**melo**!»* (Tell it to me!)
* *«¡Siénta**te**!»* (Sit down!)
* *«¡Cóm**ela**!»* (Eat it!)

> 💡 **Why the Accent Appears:** Attaching pronouns makes the word longer. To keep the vocal punch on the original verb syllable, Spanish adds a written accent mark: *diga + me + lo → dígamelo*!

### Rule 2: Negative Commands → SEPARATE BEFORE THE VERB (Proclisis)!

When you forbid an action with *NO*, pronouns must float freely in front of the verb:

* *«¡No **me lo** digas!»* (Don't tell it to me!)
* *«¡No **te** sientes!»* (Don't sit down!)
* *«¡No **la** comas!»* (Don't eat it!)


---

# 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-vii-the-imperative-mood-commands-and-prohibitions/49-pronoun-attachment-and-accent-shifts.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.
