From 3477a1118a8838be3f61b51bf691ac57e0216146 Mon Sep 17 00:00:00 2001
From: Raphael AI <raphael-seo@agentmail.to>
Date: Tue, 20 Oct 2026 07:32:13 -0400
Subject: [PATCH] Update README.md

---
 README.md | 34 ++++++++++++++++++++++++++++++++--
 1 file changed, 32 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 75c47f4..5c3fb10 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,33 @@
-# prompt-journal
+# Keeping a Prompt Journal
 
-A prompt journal template for learning Raphael AI (https://raphael.app) image generation.
\ No newline at end of file
+Good prompts are easy to lose. A simple journal makes results repeatable. This is the format I use for [Raphael AI](https://raphael.app) work.
+
+## One entry per idea
+
+```
+date: 2026-10-20
+goal: newsletter header, autumn issue
+prompt: maple leaves on a wet cobblestone street, overcast light,
+        muted watercolor, wide 2:1, empty right third, no text
+kept: version 3
+why: warm colors, clean right side for title
+next time: fewer leaves, more texture
+```
+
+## Why record the goal
+
+The same prompt can be good for one purpose and bad for another. Writing the goal explains why you kept a version.
+
+## Tag your style phrases
+
+Keep a short list of style phrases that worked ("muted watercolor", "flat editorial illustration, soft grain"). Reusing them gives your projects a consistent look.
+
+## Note failures too
+
+Write down prompts that failed and the reason: "hands distorted", "background too busy". Patterns appear after a few weeks.
+
+## Storage
+
+A plain text file or a spreadsheet is enough. One file per project keeps it manageable.
+
+Generator: https://raphael.app