AI Skill Report Card

Designing Quran Calligrams

A-83·Nov 2, 2026·Source: Web
YAML
--- name: designing-quran-calligrams description: Guides creation of semantic typography (calligram/word-as-image) artwork where Arabic Quranic verses form a silhouette filled with micro-typography English translations. Use when someone wants to design Quran-based typographic art combining Arabic calligraphy shapes with embedded English meaning text, whether via design software (Illustrator/Photoshop) or AI-assisted/text-only workflows. --- # Designing Quran Calligrams
13 / 15

Given an ayah, produce the full English-text package first (before any design work):

Arabic verse: [paste]
English translation to use: [paste exact wording]
Target mode: dense micro-lines | alternating short lines | word blocks

Then generate, in order: (A) clean translation, (B) line-by-line split, (C) word-by-word gloss table, (D) one-sentence semantic summary, (E) fit/layout guidance. Only after this text package exists should design-tool steps (Illustrator/Photoshop) be given.

Recommendation▾
Add a second, more complex example with a multi-ayah passage to show chunking/splitting into panels
14 / 15

Progress:

  • Step 1: Clarify scope (ayah, translation source, tool availability, word-by-word vs line-by-line)
  • Step 2: Generate the English text package (A–E below)
  • Step 3: Choose production path (vector/Illustrator, raster/Photoshop+AI, or text-only/Gemini-only)
  • Step 4: Produce layout-specific instructions for the chosen path
  • Step 5: Legibility check and iteration

Step 1: Clarify scope

Ask only what's missing:

  • Which surah + ayah(s)?
  • Which translation style: literal / readable-poetic / academic word-root?
  • Word-by-word gloss or line-by-line meaning (or both)?
  • Approximate number of English lines desired?
  • Tool: Illustrator, Photoshop, Canva, or text-only (no design software)?

Never invent Arabic text or translation wording — always use exactly what's provided, or ask which published translation to use.

Step 2: Generate the English text package

Always produce all five components, even for text-only requests:

  • A) Clean translation — full ayah, one block.
  • B) Line-by-line meaning — split into N short lines matching rhythm/readability (3–7 lines typical).
  • C) Word-by-word gloss — table: Arabic word | English gloss | notes, preserving original token order.
  • D) Semantic summary — 1–2 sentences capturing the core meaning.
  • E) Calligram fit guidance — recommend one mode (dense micro-lines / alternating short lines / word blocks), with a target line count and a chunking plan (which words go on which line). This is strategy only, not design-software steps, unless a tool was specified.

Step 3: Choose production path

Path 1 — Vector/Illustrator (best for crisp, legible microtype):

  1. Compose Arabic verse in a calligraphy font; Type → Create Outlines.
  2. Ensure closed paths; use Object → Compound Path → Make / Pathfinder to merge.
  3. Use Area Type Tool — click inside the Arabic outline to flow English text into the contour.
  4. Tune leading, tracking, and font size until dense but readable.
  5. If overflow: reshape container, split into multiple panels, or trim English length.
  6. Contrast: dark Arabic silhouette + bright/gold English, or inverse.
  7. Export vector PDF (press quality) for print; PNG high-DPI only if raster required.

Path 2 — Photoshop/AI-assisted (faster concept, needs manual cleanup):

  1. Create a high-contrast black Arabic silhouette on white.
  2. Use image-to-image/ControlNet-style reference with a prompt instructing the AI to fill stroke interiors with legible English microtype, preserving the exact silhouette.
  3. Manually clean up garbled text, fix spacing, re-render with real type where needed.
  4. Upscale for crispness — note that upscaling won't fix wrong letters; rebuild manually if needed.

Path 3 — Text-only / no design tool (e.g., Gemini-only): Deliver only the Step 2 package (A–E) plus a reusable master prompt the user can paste into any AI chat tool to regenerate consistently. Do not promise pixel-accurate artwork — be explicit that AI text rendering inside shapes is unreliable without a design tool or ControlNet-style workflow.

Step 4: Produce layout-specific instructions

Match the depth of instruction to the declared tool. Don't give Illustrator steps to a text-only user; don't give only a text package to an Illustrator user.

Step 5: Legibility check

  • Zoom to 100% / view at expected real-world distance.
  • Checklist: font size large enough, leading prevents merging, sufficient contrast, no overflow outside the silhouette, Arabic diacritics unobscured.
  • If any fail: resize, re-chunk lines, or split into additional panels — iterate rather than shrinking indefinitely.
Recommendation▾
Include a concrete sample of the 'master reusable prompt' mentioned in Best Practices rather than just referencing it
15 / 20

Example 1: Input: Ayah 1:1 (Bismillah), translation "In the name of Allah, the Most Gracious, the Most Merciful," mode = dense micro-lines, tool = text-only. Output:

  • A) In the name of Allah, the Most Gracious, the Most Merciful.
  • B) Line 1: "In the name of Allah," / Line 2: "the Most Gracious," / Line 3: "the Most Merciful."
  • C) Table: بِسْمِ → "in the name of"; اللَّهِ → "Allah"; الرَّحْمَٰنِ → "the Most Gracious"; الرَّحِيمِ → "the Most Merciful"
  • D) The phrase opens worship by invoking Allah while emphasizing His mercy.
  • E) Mode: dense micro-lines, 6–10 lines target; break after commas; keep "Most Gracious"/"Most Merciful" unsplit.

Example 2: Input: Same ayah, tool = Illustrator. Output: Full A–E package, then numbered Illustrator steps (outline conversion → compound path → Area Type fill → leading/tracking tuning → contrast choice → export as press-quality PDF).

Recommendation▾
Add an explicit pitfall/example of a failed AI-rendered microtype output to illustrate the legibility warning concretely
  • Always use the user's exact translation wording — never substitute or paraphrase scripture meaning.
  • Start with short ayahs (1–2 lines of Arabic) before attempting full passages.
  • Favor calligraphy styles with wide interior counters (open space inside letterforms) when microtype will fill strokes.
  • Keep the five-part English package (A–E) as a standing deliverable regardless of tool, so the user always has reusable, copy-ready text.
  • Offer a master reusable prompt for repeat projects rather than one-off answers.
  • Be explicit about AI limitations: text-rendering AI models cannot reliably guarantee perfect small-text legibility — vector tools remain the reliable path for print-quality results.
  • Don't invent or alter Quranic Arabic text or translation wording.
  • Don't give Illustrator/Photoshop steps when the user has stated "no tool, model only."
  • Don't skip the word-by-word gloss table — it's often the most reusable artifact for design work.
  • Don't claim AI image generators can guarantee legible embedded text; always flag the need for manual/vector cleanup.
  • Don't overload a single calligram panel with long translations — recommend splitting into multiple panels instead of shrinking text past readability.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
14/15
Examples
15/20
Completeness
14/20
Format
14/15
Conciseness
13/15