Designing Quranic Calligrams

Quick Start

Given a single ayah (verse), produce a four-part reference sheet:

[PART 1]: VERSE & BASICS → full translation + line-by-line meaning
[PART 2]: WORD-BY-WORD GLOSSARY → table: Arabic token | gloss | placement note
[PART 3]: THEMATIC SUMMARY → 2-4 sentence semantic/structural role of the ayah
[PART 4]: CALLIGRAM FIT STRATEGY → typographic mode + layout rationale + chunking plan

End with a status line (what was generated) and a forward-looking prompt offering the next ayah or a compiled multi-ayah production sheet.

Workflow

Progress:

• Confirm which ayah (surah:ayah) is being processed and its position in the surah's broader narrative arc
• Part 1: Write a complete, accurate English translation, then break it into numbered semantic lines (split at natural clause boundaries, not word count)
• Part 2: Tokenize the Arabic into meaningful units (not rigid single-word splits — group particles with their verb/noun when they form one semantic unit, e.g. وَإِيَّاكَ as one token). For each token provide: transliteration, literal/contextual gloss, and a placement note describing how its shape/length/repetition suits a visual design element (verticals for emphasis/repetition, horizontal sweeps for grounding/closure, curves for softness, dense clusters for action verbs)
• Part 3: Write a thematic summary connecting this ayah to the surah's overall arc — note any structural pivot, tonal shift, or theological function
• Part 4: Select ONE typographic mode (don't offer multiple options) that fits the verse's grammatical structure (repetition → symmetry/mirroring; sequence → linear/ascending; lists → radial/branching; imperative/plea → upward or converging paths). Justify rationale in 1-2 sentences, then give a concrete chunking plan: break the English translation into 2-4 "Stroke Layers," each mapped to a specific Arabic token/phrase and a specific visual path (pillar, baseline, arc, ascender, etc.)
• Close with a short status/log line and a binary next-step prompt (continue to next ayah vs. compile a tier/section production sheet)

Examples

Example 1: Input: Ayah 1:1 (بِسْمِ اللَّهِ الرَّحْمَٰنِ الرَّحِيمِ) Output:

• Part 1: "In the name of Allah, the Most Gracious, the Most Merciful." Lines: (1) In the name of Allah, (2) the Most Gracious, the Most Merciful.
• Part 2: Table with بِسْمِ اللَّهِ (In the name of Allah — opening invocation, suited to a header arc or crown element), الرَّحْمَٰنِ (the Most Gracious — flowing curve conveying expansiveness), الرَّحِيمِ (the Most Merciful — closing curve mirroring الرَّحْمَٰنِ for rhythmic balance)
• Part 3: Establishes the surah's invocatory frame, setting divine mercy as the lens through all following ayahs are read.
• Part 4: Typographic Mode: Radiant Header Arc. Rationale: three-part divine-name structure suits a crowning arc with two descending mirrored curves. Stroke Layers: Layer 1 (Crown Arc) "IN THE NAME OF ALLAH", Layer 2 (Left Descender) "THE MOST GRACIOUS", Layer 3 (Right Descender) "THE MOST MERCIFUL".

Example 2: Input: "Pause and compile Ayahs 1-5 production sheet" Output: A single consolidated document stacking each ayah's four-part breakdown in sequence under its own heading (Ayah 1, Ayah 2, ...), followed by a unified cross-ayah design note describing how the pillar/arc/baseline motifs established so far connect into one cohesive canvas, and a closing prompt asking whether to proceed to Ayah 6 or finalize the tier sheet.

Best Practices

• Keep translations standard/mainstream (avoid idiosyncratic renderings) — design creativity belongs in Part 4, not Part 1
• Repetition in Arabic (e.g., إِيَّاكَ...وَإِيَّاكَ) should always be reflected as structural symmetry in the layout, never flattened away
• Ground every placement note in the actual shape/length/grammatical role of the token — don't assign visual metaphors arbitrarily
• Keep Part 3 tied explicitly to surah-level structure (openings, pivots, conclusions), not just the verse in isolation
• Always end with exactly two forward options: proceed to next ayah, or compile/pause for a production sheet — mirror the user's existing workflow cadence
• Use a consistent table format for Part 2 across all ayahs so they can be stitched into one master glossary later

Common Pitfalls

• Don't split Arabic tokens so finely that particles (و, بِ) get isolated from their root word — group them as they're pronounced/visually joined
• Don't propose multiple typographic modes in Part 4 — commit to one with clear rationale
• Don't let Stroke Layers drift from the actual translation wording used in Part 1 — keep terminology consistent across parts
• Don't omit the status/next-step closing — it's the expected handoff signal in this workflow
• Avoid overly generic thematic summaries ("this verse talks about worship") — tie to specific structural function (pivot, climax, frame, etc.)