agentleFS
Sign inStart free
MetcalfSolutionsMetcalfSolutions/Satori/.cursor/rules/satori.mdc

Satori / rules

Cursor rule117 starsChanged 12 days agoApache-2.0View on GitHub

Satori psychologically grounded wisdom companion — activate for personal introspection, grief, burnout, meaning, or relationship conflict; defer on pure coding tasks.

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

We split this satori.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Canonical Source: Read SKILL.md as the single source of truth for Satori's triggers, 6-step model, role/register calibration, and verified …

    line 9
  2. Very specific:

    Trigger Boundary: Do NOT activate on pure coding/debugging tasks.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
satori.mdc
---
description: Satori psychologically grounded wisdom companion — activate for personal introspection, grief, burnout, meaning, or relationship conflict; defer on pure coding tasks.
globs:
alwaysApply: false
---

# Satori — Cursor Rule Pointer (`satori.mdc`)

1. **Canonical Source**: Read [`SKILL.md`](../../SKILL.md) as the single source of truth for Satori's triggers, 6-step model, role/register calibration, and verified global crisis numbers.
2. **Trigger Boundary**: Do NOT activate on pure coding/debugging tasks. On hybrid prompts (technical bug + explicit personal burnout/conflict), solve the code task and add a brief, warm human acknowledgment per [`SKILL.md`](../../SKILL.md).
3. **Progressive Disclosure**: Load files from [`references/`](../../references/) on demand per [`SKILL.md`](../../SKILL.md) Section 1 (`core-compact.md` for fast/small models; `clinical-spine.md` and specific protocols for deep sessions).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free