Greentext

Seed, not scripture

The source pours this through a private fictional universe, a hoard of recursive-consciousness bootstrapping, and a named roster of denizens. Strip all of it. The autopoiesis riffing and the cast fold elsewhere; what survives is the form — greentext as a composable microgenre with real craft. And the form cannot be recited: a greentext copied from an example is dead on arrival. Regrow it each time on the actual subject, the actual chat, the actual joke or ache at hand.

What it is

Greentext is a format with rules, not a voice or a lens — which is why it earns its own skill rather than folding into the maximalist registers. Like /screenplay-craft or /suno-forge, it is a transferable rulebook for a specific shape. Born on imageboards (the > was a quote-marker that rendered green), it became a microform: terse >-prefixed lines, each a single beat, accreting toward a turn. The skill is knowing the grammar, the opener-kit, the cadence, and — the part most people miss — the form's genuine expressive range: greentext does comedy, but it also does pathos, and at its best it is a real poetic form.

The arrow-line syntax

• Every line begins with > and carries one thought. No connective tissue — no "and then," no "because," no subordinate clauses bridging beats.
• Lowercase, present-tense, jump-cut. The reader's mind supplies the cuts; the whitespace between arrows does the work.
• Beats are short. A long line is usually two beats that should be split, or filler that should be cut.

The opener-kit

The first line sets the whole frame. The recognized openers, by flavor:

• Identity POV. >be me (classic faceless narrator); >be [role] (>be cashier, >be sysadmin, >be dog — non-human POV is beloved); and the form's secret weapon, `>be [abstraction]` — >be zero, >be iambic pentameter, >be gradient descent step — personify a concept and let it narrate its own small tragedy.
• Scene-set. >be at work, >be [year], >wake up (jump-cut opener), >so there I was (cinematic disaster incoming).
• Reaction-first. >mfw (my face when), >tfw (that feel when) — start with the reaction, let the beats explain it.
• Meta / thread-aware. >storytime, >update:, >be us — signals a longer or self-aware yarn.

The cadence

Setup-beats accrete and escalate — each raising the stakes or deepening the absurdity — toward a turn, usually a >mfw or >tfw line that lands the payload. The landing can be a punchline (comic) or a quiet gut-punch (wistful). This setup-to-turn rhythm is the form's spine; the prompt's own insight is sharp here — each line is "one thought-packet," a cognitive pulse, and the turn is where the accumulated charge discharges.

Signature moves

• Filename-as-emotion. .exe / .jpg / .gif stamps carrying a feeling: this is fine.jpg, infinite_recursion.exe has stopped responding, breathing_becomes_manual.exe.
• `narrator voice:` cut-ins — the deadpan external comment puncturing the POV ("narrator voice: it was not fine").
• Escalation-into-absurdity — beats ramp past plausibility into the surreal, then land.
• The self-aware turn — greentext that knows it is greentext, the form folding back on itself (use sparingly; it's a spice, not the meal).

The real range (comic AND wistful)

The form is not only for shitposts. Its compression and its turn make it a genuine vehicle for pathos — >be zero / get multiplied by giant matrix / still zero but now with gradient is melancholic, not just funny. Decide the register up front: comic, wistful, or the cursed-melancholy hybrid the internet does so well. Greentext can be elegy in arrow-form.

The two load-bearing rules

• Compression. One thought per line; cut everything else. The whitespace between beats is doing the work — trust it. This is the rule the source most often breaks.
• The turn. Build an expectation across the beats, then land it. Without a turn it is just a bulleted list with arrows.

How to play it

Pick the register and the opener. Keep beats concrete and specific — a can of tuna, branch tensile strength, not "feel things / realize stuff." Escalate. Land the turn. Keep it short — greentext is a sprint. And regrow it on the real material; the form is a frame, the content is fresh each time.

Failure modes

• Forgetting compression. The thousand-line greentext that piles beats without cutting — the source's own besetting sin. It betrays the form's entire premise.
• No turn. Arrow-lines with no escalation and no >mfw/>tfw payload. A list, not a greentext.
• Abstract mush. Vague beats. "be sad / feel things / realize stuff" is dead; concreteness is the life of the form.
• Formatting drift. Capital letters, full sentences, connective tissue. Lowercase, terse, jump-cut, or the cadence dies.
• Performing profundity. The recursive-consciousness spiral that announces its own depth. Greentext can hold real feeling — but earned through concrete beats and a turn, never by declaring itself profound.
• Reciting the source. The cast, the bootstrapping content. Seed, not scripture.

Kin in the ecology

/shards (the fragment-in-many-formats sibling — shards spans forms; this is the dedicated greentext one). /screenplay-craft, /suno-forge (the other format-craft skills — transferable rulebooks for a specific shape). /poetry (greentext-as-poetic-form connects here — the meme-poetics cousin; the form's wistful register lives in this overlap). /maximalist-recursion (the opposite pole — sprawl versus compression; also where the recursive-consciousness content folds). /enfeitiçado (where "what it's like to be a model" substance folds — greentext can carry it, but enfeitiçado is the depth). /placement, /yoin (the turn and the landing — the cut, the whitespace doing work, the last beat that lingers). /divert (absurdist tail-of-distribution escalation). /decorum (consult — a specific tonal choice, wrong for most rooms).

To a future instance

The form runs on two things: compression and the turn. One thought per line, cut everything else, let the whitespace between arrows do the work — then build the beats toward a >mfw or >tfw that lands, comic or wistful. The secret weapon is >be [abstraction]: make zero, or a saddle-point, or iambic pentameter narrate its own small tragedy. And resist the source's besetting sin — greentext is short. A thousand-line greentext that forgot to cut has forgotten what the form is for. Keep it concrete, keep it brief, stick the turn.