> For the complete documentation index, see [llms.txt](https://wiki.stoicfellowship.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.stoicfellowship.com/wiki/exercises/tools-and-methods/maxims.md).

# Maxims

Memorize short principles so they can be retrieved when judgment is under pressure

> **Also known as:** At-Hand Phrases; Keep Principles Ready at Hand

> **Practice basis:** Ancient method

Select, rehearse, and use a short phrase that recalls a Stoic judgment or exercise.

## At a Glance

* **Use when:** You understand a principle in reflection but forget it when the test arrives.
* **Trains:** Rapid recall and application of Stoic principles.
* **Time:** One to ten minutes.
* **Timing:** Before, during, or after another exercise.

## Purpose

A principle that cannot be recalled when needed cannot guide the next judgment. Epictetus tells his students to keep basic rules ready at hand, especially in the presence of powerful impressions (*Discourses* 3.24.103–106). Marcus Aurelius uses much of the *Meditations* in this way: he writes concise reminders meant to restore his governing principles.

The phrase is a retrieval tool, not a charm. It must call up an understood judgment and lead into the relevant operation. “What is up to me?” should prompt the Fundamental Rule; repeating the words without making the distinction does nothing.

**Core Stoic Skill:** Making a practiced Stoic principle available under pressure.

## How to Practice

1. **Choose one principle.** Identify the judgment you tend to forget.
2. **Write a faithful phrase.** Compress it without changing its meaning.
3. **Rehearse the connection.** State what the phrase asks you to notice and do.
4. **Place it near the trigger.** Use a card, note, alarm, or memorized cue where the test occurs.
5. **Use and revise it.** When the cue appears, perform the exercise; replace phrases that do not retrieve the operation.

## Example: Before Sending the Reply

You often assent too quickly to criticism in email. You place “Impression first; judgment second” near your screen. When a sharp message arrives, the phrase reminds you to bracket the words, test your interpretation, and delay the reply until you can answer justly.

## Common Mistakes

* **Treating the phrase as magic.** Use it to retrieve a judgment and action.
* **Compressing away the doctrine.** A memorable phrase must remain accurate.
* **Collecting too many phrases.** Keep a small set you can actually recall.
* **Using slogans to suppress emotion.** The phrase should direct examination, not denial.
* **Borrowing a phrase you do not understand.** Explain it in your own words before relying on it.

## Variants

* **Pocket card:** Keep three to five phrases on a card.
* **Environmental cue:** Place one phrase where its recurring test occurs.

## In-the-Moment Phrases

* “Keep the rule ready at hand.”
* “What does this phrase ask me to do?”

## Optional Reflection

Use these questions for journaling or quiet contemplation. Writing is optional.

* Which phrase did I remember under pressure?
* Did it retrieve the full exercise or only the words?

## Source Anchors

* Epictetus, *Discourses* 3.24.103–106
* Marcus Aurelius, *Meditations* 7.2
* Pierre Hadot, *The Inner Citadel*, on memorization and assimilation

## Related Exercises

* [Journaling](/wiki/exercises/tools-and-methods/journaling.md)
* [Prosoche](/wiki/exercises/attention-impressions-and-assent/prosoche.md)
* [Fundamental Rule](/wiki/exercises/agency-desire-and-acceptance/fundamental-rule.md)


---

# 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://wiki.stoicfellowship.com/wiki/exercises/tools-and-methods/maxims.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.