AI Skill Report Card

Designing Quran Calligrams

A-87·Nov 2, 2026·Source: Web

Designing Quran Calligrams (Semantic Typography)

Produces print-ready artwork where an Arabic ayah's calligraphic silhouette is filled with legible English translation micro-typography — plus the text-processing pipeline (translation versions, line-breaking, word-by-word gloss) needed to feed any design tool or AI image generator.

14 / 15

Given a surah + ayah number and a trusted English translation, immediately produce these 5 text artifacts before touching any design tool:

  1. Clean translation (full ayah, one line)
  2. Line-by-line split (3–7 short lines, broken at natural phrase boundaries)
  3. Word-by-word gloss (table: Arabic word | English gloss | notes)
  4. Semantic summary (1–2 sentences)
  5. Fit-mode recommendation (dense micro-lines / alternating short lines / word blocks) with target line count

Only after these exist should the user move to Illustrator, Photoshop, or an AI generator — the text artifacts are what gets poured into the silhouette.

Recommendation▾
Add a 'bad outcome' example (e.g., overflow or garbled AI text) to contrast with the two good examples for stronger examples-quality coverage.
15 / 15

Progress:

  • Step 1: Confirm inputs — surah+ayah, exact English translation source, literal vs poetic style preference
  • Step 2: Generate the 5 text artifacts (clean/line-by-line/gloss/summary/fit-mode)
  • Step 3: Choose production path — (A) Illustrator vector microtype, (B) Photoshop/AI concept render, (C) Gemini-only text-planning (no design tool)
  • Step 4: Execute chosen path's steps
  • Step 5: Run legibility check (font size, leading, contrast, overflow)
  • Step 6: Export (vector PDF for print; high-DPI PNG if raster required)

Step 1 — Confirm inputs

Ask only what's missing:

  • Which surah + ayah?
  • Which English translation text (paste exact wording — never invent or paraphrase scripture)?
  • Literal / poetic / academic (word-root) style?
  • Word-by-word or line-by-line inside the letterforms?
  • Target tool: Illustrator, Photoshop, Canva, or Gemini-only (text planning)?

Step 2 — Generate text artifacts

Use the exact English the user supplied. Never substitute your own translation of scripture. Produce the clean translation, line-by-line split, word-by-word gloss table, semantic summary, and a recommended fit-mode with a concrete line-chunking plan (see Examples).

Step 3A — Illustrator path (most control, legible microtype)

  1. Compose Arabic verse in a calligraphy font; Type → Create Outlines.
  2. Ensure closed paths; merge with Object → Compound Path → Make / Pathfinder if needed.
  3. Type Tool → Area Type, click inside the outline — English flows into the contour automatically.
  4. Tune leading (tight but readable) and tracking (slightly negative increases density).
  5. If English overflows: reshape container, split into multiple panels, or shorten text.
  6. If English is too tiny: enlarge font or reduce word density, not just leading.
  7. Contrast: dark Arabic strokes + bright/gold English, or inverse — test at final print size.
  8. Export as PDF (Press Quality) or SVG; avoid raster unless necessary.

Step 3B — Photoshop/AI concept path (faster, less precise)

  1. Create a crisp black Arabic silhouette on white background as baseline.
  2. Feed into AI image-to-image / ControlNet with a prompt instructing: "fill stroke interiors with dense, legible English micro-typography; preserve silhouette; keep background clean; high contrast."
  3. Manually clean up garbled or misplaced text in Photoshop.
  4. Upscale for sharpness — note: upscalers don't fix wrong letters; manual typographic rebuild is more reliable for legibility.

Step 3C — Gemini-only path (text planning, no design tool)

Use Gemini purely to produce the 5 text artifacts plus a chunking plan a human later lays out manually or feeds to a designer/AI tool. Gemini does not generate the final image.

Recommendation▾
Include guidance on sourcing/verifying translation accuracy (e.g., citing reputable translators) since scripture fidelity is a stated priority.
You are a Quran language assistant and calligram formatting instructor.

Arabic verse:
(PASTE ARABIC HERE)

English translation to use (must not change wording):
(PASTE EXACT ENGLISH HERE)

Create:
A) Clean translation (full ayah) — 1 line.
B) Line-by-line meaning — split into 3–5 short lines.
C) Word-by-word gloss — table with Arabic word → English gloss.
D) Semantic summary — 1–2 sentences.
E) Calligram fit guidance: choose one of (dense micro-lines /
   alternating short lines / word blocks). Give exact line-count
   and a recommended line text chunking plan.

Rules: Do not add new meaning; only format and split the given English.
17 / 20

Example 1: Al-Fātiḥah 1:1 — بِسْمِ اللَّهِ الرَّحْمَٰنِ الرَّحِيمِ

Input: "In the name of Allah, the Most Gracious, the Most Merciful." (user-supplied translation)

Output:

  • A) Clean: "In the name of Allah, the Most Gracious, the Most Merciful."
  • B) Line-by-line: "In the name of Allah," / "the Most Gracious," / "the Most Merciful."
  • C) Gloss table: بِسْمِ → in the name of | اللَّهِ → Allah/God (proper name) | الرَّحْمَٰنِ → the Most Gracious | الرَّحِيمِ → the Most Merciful
  • D) Summary: "Opens worship by invoking Allah while highlighting His mercy."
  • E) Fit mode: Dense micro-lines, ~6–10 lines target; shorten to core nouns/adjectives if too dense; break after commas, never mid-phrase ("Most Gracious" stays intact).

Example 2: Al-Fātiḥah 1:2 — الْحَمْدُ لِلَّهِ رَبِّ الْعَالَمِينَ

Input: "All praise is for Allah—Lord of all worlds."

Output:

  • A) Clean: "All praise is for Allah—Lord of all worlds."
  • B) Line-by-line: "All praise is for Allah—" / "Lord of all worlds."
  • C) Gloss table: الْحَمْدُ → all praise | لِلَّهِ → for Allah | رَبِّ → Lord/Sustainer | الْعَالَمِينَ → of all worlds
  • D) Summary: "Establishes that praise belongs to Allah, sustainer of all creation."
  • E) Fit mode: Alternating short lines, 4 lines max: "All praise is for Allah—" / "Lord of" / "all worlds" / optional margin label.
Recommendation▾
Consider trimming the three parallel production paths (3A/3B/3C) slightly or cross-referencing shared steps to tighten conciseness further.
  • Start with one short ayah before attempting full surahs.
  • Choose Arabic calligraphy fonts/styles with wide interior counters (open space inside strokes) — the English needs room to sit.
  • Never alter or invent translation wording; only reformat/chunk text the user explicitly supplied.
  • Test legibility at actual intended viewing distance, not just zoomed-in on screen.
  • Prefer vector output (PDF/SVG) over raster for any print use.
  • If English overflows the silhouette, fix by: shortening wording, splitting into multiple panels, or adjusting container shape — not by shrinking font below readable size.
  • Do not let AI image generators invent or alter the Arabic scripture text — always supply it as a locked reference image, never let it be freely regenerated.
  • Do not sacrifice legibility for density — illegible microtype defeats the purpose of semantic typography.
  • Do not rely on AI upscalers to fix garbled text; rebuild typographically by hand instead.
  • Do not mix multiple English translations within one piece without labeling which is used.
  • Do not skip the text-artifact stage (Step 2) — jumping straight to design software without a finalized line-by-line/gloss plan causes rework.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
15/15
Examples
17/20
Completeness
18/20
Format
14/15
Conciseness
13/15