This page is yours.

the book continues below ⌄

GRIMOIRE

A spellbook for the
age of intelligence

Sour Labs · MMXXVI

GRIMOIRE

a spellbook for the age of intelligence

Every great work starts with the right words.

Keep yours in a book that belongs to you.

First edition · bound by Sour Labs

Table of Spells

ISummon Clarity2

IIBanish Jargon4

IIIScry the Codebase6

✦The Blank Page9

More spells are written every week. Most of them by you.

1 Grimoire

Spell the First

Summon Clarity

For first drafts that read like third drafts. This spell does not make you sound smarter. It makes you sound like you — on your best day, saying the thing you actually mean.

Cast upon — memos, essays, announcements

Side effects — shorter sentences, braver claims

The Incantation

You are a ruthless but kind editor.
Here is my draft: [DRAFT]

1. Tell me what this piece is actually
   saying, in one sentence.
2. Cut everything that doesn't serve it.
   Show me the cuts.
3. Rewrite the opening so a busy
   stranger keeps reading.
4. Find three places I hedge.
   Offer the braver line for each.

Keep my voice. No corporate polish.

Spell the Second

Banish Jargon

Corporate fog is a spell too — one that gets cast on you. This is the counter-curse. It trades impressive noise for plain truth, and it is merciless about the difference.

Cast upon — anything that says “leverage synergies”

Side effects — meaning; occasional embarrassment

The Incantation

Rewrite this so a smart twelve-year-old
could explain it back to me: [TEXT]

Rules:
· No buzzwords. No acronym without
  its full name, once.
· Every abstract claim gets one
  concrete example.
· If a sentence sounds impressive
  but says nothing, delete it — and
  tell me it said nothing.

Then: one line for a sign,
one paragraph for a human.

Spell the Third

Scry the Codebase

For inherited code and foggy repositories. Sees past comment-lies and dead directories to the load-bearing walls beneath. It draws the map you wish you'd been handed.

Cast upon — legacy repos, new jobs, your own code from last year

Side effects — humility, then velocity

The Incantation

You are a senior engineer meeting
this codebase for the first time:
[REPO]

1. Name the five load-bearing modules
   and what each one really does.
2. Trace the data: where it enters,
   where it turns, where it leaves.
3. Point at the three places most
   likely to break under change. Why?
4. Write the README the authors
   should have written.

Assume the comments are wishes.
Trust only the code.

The Last Rule

Your spells are yours.

No platform. No harvest.
Just your craft, bound and kept.

Grimoire lives on your machine. It syncs nowhere by default, shows your work to no one, and answers only to its author. A book, not a funnel.

Scroll to open the book

Scroll — the binding comes loose

Every great work starts with the right words.

Keep yours in a book that belongs to you.

Spell I · the first

Summon Clarity

For first drafts that read like third drafts. This spell does not make you sound smarter. It makes you sound like you — on your best day, saying the thing you actually mean.

Cast upon — memos, essays, announcements

Side effects — shorter sentences, braver claims

You are a ruthless but kind
editor. Here is my draft:
[DRAFT]

1. Tell me what this piece is
   actually saying, in one
   sentence.
2. Cut everything that doesn't
   serve it. Show me the cuts.
3. Rewrite the opening so a
   busy stranger keeps reading.
4. Find three places I hedge.
   Offer the braver line for
   each.

Keep my voice.
No corporate polish.

Spell II · the second

Banish Jargon

Corporate fog is a spell too — one that gets cast on you. This is the counter-curse. It trades impressive noise for plain truth, and it is merciless about the difference.

Cast upon — anything that says “leverage synergies”

Side effects — meaning; occasional embarrassment

Rewrite this so a smart
twelve-year-old could explain
it back to me: [TEXT]

Rules:
· No buzzwords. No acronym
  without its full name, once.
· Every abstract claim gets
  one concrete example.
· If a sentence sounds
  impressive but says nothing,
  delete it — and tell me it
  said nothing.

Then: one line for a sign,
one paragraph for a human.

Spell III · the third

Scry the Codebase

For inherited code and foggy repositories. Sees past comment-lies and dead directories to the load-bearing walls beneath. It draws the map you wish you'd been handed.

Cast upon — legacy repos, new jobs, your own code from last year

Side effects — humility, then velocity

You are a senior engineer
meeting this codebase for the
first time: [REPO]

1. Name the five load-bearing
   modules and what each one
   really does.
2. Trace the data: where it
   enters, turns, and leaves.
3. Point at the three places
   most likely to break under
   change. Why?
4. Write the README the
   authors should have written.

Assume the comments are
wishes. Trust only the code.

This page is yours.

the book continues below ⌄

The Last Rule

Your spells are yours.

No platform. No harvest. Just your craft, bound and kept.

Prompts are craft. Yours took years to sharpen — every phrasing, every hard-won constraint, every trick that finally worked. Most tools quietly harvest that craft into somebody else's training set. Grimoire is a book, not a funnel: your spells live on your machine, leave only when you hand them over, and answer to no landlord.

Kept, not harvested

Your spellbook lives on your machine, in files you can open with your own hands. The cloud is other people's weather.

Shared like recipes

Hand a spell to a friend as a file, a gist, a note passed in class. On your terms, with your name still on it.

Bound forever

No subscription can expire your own words. A grimoire never rents itself back to its author.

Colophon

Every great work starts with the right words.

Keep yours in a book that belongs to you.

press the seal · grimoire.life

Set in Fraunces, Crimson Pro & DM Mono

Bound in a single HTML file · illuminated by candlelight

No cookies · no trackers · no harvest