{ "openapi": "3.0.3", "info": { "title": "AZMX Brand API", "version": "1.0.0", "description": "Versioned, programmatic API providing structured access to AZMX brand rules, design tokens, voice guidelines, and audience personas", "contact": { "name": "AZMX", "email": "brand@azmx.sa" }, "license": { "name": "Proprietary" } }, "externalDocs": { "description": "API documentation", "url": "https://gamaleldientarek.github.io/azmx-brand/api-docs/" }, "servers": [ { "url": "https://gamaleldientarek.github.io/azmx-brand/api/v1", "description": "Production API (GitHub Pages)" } ], "paths": { "/tokens.json": { "get": { "summary": "Design Tokens", "description": "Complete set of 601 design tokens across 6 collections (primitives, palette modes, semantic light/dark, component, canvas, RTL)", "operationId": "getDesignTokens", "tags": [ "Design" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/DesignTokens" }, "example": { "version": "1.0.0", "description": "AZM X Design Tokens - 601 design tokens across 6 collections", "name": "AZM X Design Tokens", "source": "New Direction Library | AZM X", "source_version": "3.0.0", "exported": "2026-08-08", "count": 601, "collections": [ { "name": "1. Primitives", "modes": [ "Mode 1" ], "count": 291, "tokens": { "color/blue/50": "#F0F5FF", "color/blue/100": "#DDE8FF", "color/blue/200": "#BFD5FF", "color/blue/300": "#93B6FF", "color/blue/400": "#5D8FFF", "color/blue/500": "#2661FF", "color/blue/600": "#001AFF", "color/blue/700": "#0200D3", "color/blue/800": "#01009B", "color/blue/900": "#01006E", "color/blue/950": "#010040", "color/blue/1000": "#040038", "color/orange/50": "#FEF7F4", "color/orange/100": "#FDECE5", "color/orange/200": "#FCD7C8", "color/orange/300": "#F9BAA0", "color/orange/400": "#F79A74", "color/orange/500": "#F47A48", "color/orange/600": "#C8643B", "color/orange/700": "#A1502F", "color/orange/800": "#7B3E24", "color/orange/900": "#5A2D1B", "color/orange/950": "#3C1E12", "color/orange/1000": "#2E170E", "color/orange/role-tint": "#FFF7F1", "color/orange/role-border": "#DDAD8D", "color/orange/role-light": "#F47A48", "color/orange/role-mid": "#CD5200", "color/orange/role-deep": "#842C09", "color/green/50": "#F2FBF6", "color/green/100": "#E0F7EB", "color/green/200": "#BDEDD4", "color/green/300": "#8CE0B4", "color/green/400": "#57D192", "color/green/500": "#22C36F", "color/green/600": "#1CA05B", "color/green/700": "#168049", "color/green/800": "#116238", "color/green/900": "#0D4829", "color/green/950": "#08301B", "color/green/1000": "#062515", "color/green/role-tint": "#E5F4EE", "color/green/role-border": "#88EFC7", "color/green/role-light": "#22C36F", "color/green/role-mid": "#00A060", "color/green/role-deep": "#012F02", "color/yellow/50": "#FFFCF4", "color/yellow/100": "#FFF9E4", "color/yellow/200": "#FFF2C6", "color/yellow/300": "#FEE89C", "color/yellow/400": "#FEDE6E", "color/yellow/500": "#FED340", "color/yellow/600": "#D3A92E", "color/yellow/700": "#AD831E", "color/yellow/800": "#895F0F", "color/yellow/900": "#693F02", "color/yellow/950": "#392201", "color/yellow/1000": "#251601", "color/yellow/role-tint": "#FFFCF4", "color/yellow/role-border": "#FEDE6E", "color/yellow/role-light": "#FED340", "color/yellow/role-mid": "#D3A92E", "color/yellow/role-deep": "#693F02", "color/purple/50": "#FCF8FF", "color/purple/100": "#F7EFFF", "color/purple/200": "#EEDDFF", "color/purple/300": "#E1C5FF", "color/purple/400": "#D4AAFF", "color/purple/500": "#C68FFF", "color/purple/600": "#9B66D4", "color/purple/700": "#7341AD", "color/purple/800": "#4F1F88", "color/purple/900": "#2E0068", "color/purple/950": "#190039", "color/purple/1000": "#100024", "color/purple/role-tint": "#FCF8FF", "color/purple/role-border": "#D4AAFF", "color/purple/role-light": "#C68FFF", "color/purple/role-mid": "#9B66D4", "color/purple/role-deep": "#2E0068", "color/red/50": "#FFF2F3", "color/red/100": "#FFE1E4", "color/red/200": "#FFBFC4", "color/red/300": "#FF919A", "color/red/400": "#FF5E6B", "color/red/500": "#FF2B3C", "color/red/600": "#D12331", "color/red/700": "#A81C27", "color/red/800": "#81161E", "color/red/900": "#5E1016", "color/red/950": "#3E0A0F", "color/red/1000": "#30080B", "color/red/role-tint": "#FDF2F3", "color/red/role-border": "#EB808A", "color/red/role-light": "#FF2B3C", "color/red/role-mid": "#DB0015", "color/red/role-deep": "#640000", "color/neutral/25": "#FCFCFD", "color/neutral/50": "#F9FAFB", "color/neutral/100": "#F3F4F6", "color/neutral/200": "#E5E7EB", "color/neutral/300": "#D2D6DB", "color/neutral/400": "#9DA4AE", "color/neutral/500": "#6C737F", "color/neutral/600": "#4D5761", "color/neutral/700": "#384250", "color/neutral/800": "#1F2A37", "color/neutral/900": "#111927", "color/neutral/950": "#0D121C", "color/base/white": "#FFFFFF", "color/base/black": "#000000", "color/rag/red": "#FF2B3C", "color/rag/yellow": "#FED340", "color/rag/green": "#22C36F", "color/feedback/success/tint": "#E5F4EE", "color/feedback/success/border": "#88EFC7", "color/feedback/success/mid": "#007D4B", "color/feedback/success/deep": "#012F02", "color/feedback/warning/tint": "#FFFCF4", "color/feedback/warning/border": "#FEDF90", "color/feedback/warning/mid": "#946C08", "color/feedback/warning/deep": "#693F02", "color/feedback/danger/tint": "#FDF2F3", "color/feedback/danger/border": "#EB808A", "color/feedback/danger/mid": "#DB0015", "color/feedback/danger/deep": "#430000", "color/feedback/info/tint": "#EDF5FF", "color/feedback/info/border": "#97C3F4", "color/feedback/info/mid": "#0061CF", "color/feedback/info/deep": "#01006E", "color/feedback/caution/tint": "#FFF7F1", "color/feedback/caution/border": "#DDAD8D", "color/feedback/caution/mid": "#C14D00", "color/feedback/caution/deep": "#5F2006", "color/feedback/caution/light": "#F47A48", "color/alpha/white-4": "#FFFFFF0A", "color/alpha/white-8": "#FFFFFF14", "color/alpha/white-12": "#FFFFFF1F", "color/alpha/white-16": "#FFFFFF29", "color/alpha/white-20": "#FFFFFF33", "color/alpha/white-30": "#FFFFFF4D", "color/alpha/white-40": "#FFFFFF66", "color/alpha/white-48": "#FFFFFF7A", "color/alpha/white-60": "#FFFFFF99", "color/alpha/white-72": "#FFFFFFB8", "color/alpha/white-90": "#FFFFFFE6", "color/alpha/black-8": "#00000014", "color/alpha/black-12": "#0000001F", "color/alpha/black-20": "#00000033", "color/alpha/black-30": "#0000004D", "color/alpha/black-40": "#00000066", "color/alpha/black-60": "#00000099", "color/alpha/black-72": "#000000B8", "color/alpha/navy-40": "#04003866", "color/alpha/navy-72": "#040038B8", "color/alpha/electric-8": "#001AFF14", "color/alpha/electric-16": "#001AFF29", "color/alpha/success-8": "#0FBC7708", "color/alpha/warning-8": "#BE8B0A08", "color/alpha/danger-8": "#DB001508", "color/alpha/info-8": "#0067DC08", "color/alpha/caution-8": "#F47A4814", "color/alpha/caution-bg-8": "#CD520008", "color/alpha/caution-dark-10": "#842C091A", "brand/colab/electric-green": "#34FF67", "brand/colab/pine-green": "#103A21", "brand/colab/jade-green": "#33FFC2", "brand/colab/deep-jade": "#011E14", "brand/colab/olive-green": "#5B6B3E", "brand/colab/vivid-orange": "#FF5A32", "brand/colab/pale-sky-blue": "#B1D9E8", "brand/colab/grey": "#BCBEC0", "brand/majarah/purple-900": "#210054", "brand/majarah/purple-600": "#380089", "brand/majarah/purple-500": "#4B0AA0", "brand/majarah/purple-300": "#6500E8", "brand/majarah/purple-200": "#B671FF", "brand/majarah/subtle-grey": "#D1D1D1", "brand/majarah/grey": "#231F20", "brand/majarah/blue-300": "#010CFF", "brand/majarah/blue-600": "#0000AD", "brand/majarah/blue-900": "#020068", "size/space/0": 0, "size/space/2": 2, "size/space/4": 4, "size/space/8": 8, "size/space/12": 12, "size/space/16": 16, "size/space/20": 20, "size/space/24": 24, "size/space/32": 32, "size/space/40": 40, "size/space/48": 48, "size/space/64": 64, "size/space/80": 80, "size/space/96": 96, "size/space/120": 120, "size/space/160": 160, "size/space/200": 200, "size/font/10": 10, "size/font/12": 12, "size/font/14": 14, "size/font/16": 16, "size/font/18": 18, "size/font/20": 20, "size/font/24": 24, "size/font/28": 28, "size/font/30": 30, "size/font/36": 36, "size/font/40": 40, "size/font/48": 48, "size/font/60": 60, "size/font/72": 72, "size/font/80": 80, "size/font/100": 100, "size/font/120": 120, "size/font/160": 160, "size/font/200": 200, "size/font/240": 240, "size/line/16": 16, "size/line/18": 18, "size/line/20": 20, "size/line/22": 22, "size/line/24": 24, "size/line/28": 28, "size/line/29": 29, "size/line/30": 30, "size/line/34": 34, "size/line/36": 36, "size/line/38": 38, "size/line/42": 42, "size/line/46": 46, "size/line/50": 50, "size/line/57": 57, "size/line/64": 64, "size/line/76": 76, "size/line/84": 84, "size/line/95": 95, "size/line/106": 106, "size/line/114": 114, "size/line/126": 126, "size/line/152": 152, "size/line/168": 168, "size/line/190": 190, "size/line/210": 210, "size/line/228": 228, "size/line/252": 252, "size/radius/0": 0, "size/radius/4": 4, "size/radius/8": 8, "size/radius/12": 12, "size/radius/16": 16, "size/radius/24": 24, "size/radius/full": 9999, "size/border/0": 0, "size/border/0-5": 0.5, "size/border/1": 1, "size/border/1-5": 1.5, "size/border/2": 2, "size/border/4": 4, "size/border/8": 8, "size/opacity/0": 0, "size/opacity/5": 0.05, "size/opacity/20": 0.2, "size/opacity/40": 0.4, "size/opacity/60": 0.6, "size/opacity/80": 0.8, "size/opacity/100": 1, "size/tracking/0": 0, "size/tracking/0-5": 0.5, "size/tracking/1": 1, "size/tracking/2": 2, "size/tracking/3": 3, "size/icon/20": 20, "size/icon/24": 24, "size/icon/32": 32, "size/doc/100": 100, "size/doc/120": 120, "size/doc/1080": 1080, "size/doc/1920": 1920, "font/family/display": "thmanyah serif display", "font/family/body": "Azm X Variable", "font/weight/thin": "Thin", "font/weight/extralight": "ExtraLight", "font/weight/light": "Light", "font/weight/regular": "Regular", "font/weight/medium": "Medium", "font/weight/semibold": "SemiBold", "font/weight/bold": "Bold", "font/weight/black": "Black", "font/weight/heavy": "Heavy" } }, { "name": "1b. Palette", "modes": [ "Blue", "Orange", "Green", "Yellow", "Purple", "Red" ], "count": 19, "tokens": { "accent/tint": [ "@color/blue/50", "@color/orange/50", "@color/green/50", "@color/yellow/50", "@color/purple/50", "@color/red/50" ], "accent/subtle": [ "@color/blue/100", "@color/orange/100", "@color/green/100", "@color/yellow/100", "@color/purple/100", "@color/red/100" ], "accent/soft": [ "@color/blue/300", "@color/orange/300", "@color/green/300", "@color/yellow/300", "@color/purple/300", "@color/red/300" ], "accent/on-dark": [ "@color/blue/400", "@color/orange/400", "@color/green/400", "@color/yellow/400", "@color/purple/400", "@color/red/400" ], "accent/base": [ "@color/blue/600", "@color/orange/500", "@color/green/500", "@color/yellow/500", "@color/purple/500", "@color/red/500" ], "accent/text": [ "@color/blue/600", "@color/orange/700", "@color/green/700", "@color/yellow/800", "@color/purple/700", "@color/red/700" ], "accent/strong": [ "@color/blue/700", "@color/orange/700", "@color/green/700", "@color/yellow/800", "@color/purple/700", "@color/red/700" ], "accent/deep": [ "@color/blue/900", "@color/orange/900", "@color/green/900", "@color/yellow/900", "@color/purple/900", "@color/red/900" ], "accent/ground": [ "@color/base/black", "@color/base/black", "@color/base/black", "@color/base/black", "@color/base/black", "@color/base/black" ], "accent/ground-raised": [ "@color/blue/900", "@color/orange/900", "@color/green/900", "@color/yellow/900", "@color/purple/900", "@color/red/900" ], "accent/ground-sunken": [ "@color/base/black", "@color/base/black", "@color/base/black", "@color/base/black", "@color/base/black", "@color/base/black" ], "accent/on-ground": [ "@color/blue/100", "@color/orange/100", "@color/green/100", "@color/yellow/100", "@color/purple/100", "@color/red/100" ], "accent/on-ground-faint": [ "@color/blue/200", "@color/orange/200", "@color/green/200", "@color/yellow/200", "@color/purple/200", "@color/red/200" ], "accent/on-ground-quiet": [ "@color/blue/300", "@color/orange/300", "@color/green/300", "@color/yellow/300", "@color/purple/300", "@color/red/300" ], "accent/on-base": [ "@color/base/white", "@color/orange/1000", "@color/green/1000", "@color/yellow/1000", "@color/purple/1000", "@color/red/1000" ], "accent/on-deep": [ "@color/base/white", "@color/base/white", "@color/base/white", "@color/base/white", "@color/base/white", "@color/base/white" ], "accent/on-light": [ "@color/blue/1000", "@color/orange/1000", "@color/green/1000", "@color/yellow/1000", "@color/purple/1000", "@color/red/1000" ], "accent/role-light": [ "@color/blue/400", "@color/orange/role-light", "@color/green/role-light", "@color/yellow/role-light", "@color/purple/role-light", "@color/red/role-light" ], "accent/role-deep": [ "@color/blue/1000", "@color/orange/role-deep", "@color/green/role-deep", "@color/yellow/role-deep", "@color/purple/role-deep", "@color/red/role-deep" ] } }, { "name": "2. Semantic", "modes": [ "Light", "Dark" ], "count": 194, "tokens": { "surface/page": [ "@color/base/white", "@accent/ground" ], "surface/raised": [ "@accent/tint", "@color/neutral/900" ], "surface/sunken": [ "@color/neutral/100", "@accent/ground-sunken" ], "surface/inverse": [ "@accent/ground", "@color/base/white" ], "surface/accent": [ "@accent/base", "@accent/on-dark" ], "surface/accent-deep": [ "@accent/role-deep", "@accent/on-dark" ], "surface/accent-light": [ "@accent/role-light", "@accent/role-deep" ], "surface/accent-inverse": [ "@accent/on-dark", "@accent/base" ], "surface/accent-subtle": [ "@color/alpha/electric-8", "@color/alpha/white-8" ], "surface/accent-wash": [ "@color/alpha/caution-dark-10", "@color/alpha/caution-dark-10" ], "surface/accent-wash-light": [ "@color/alpha/caution-8", "@color/alpha/caution-8" ], "surface/muted": [ "@color/neutral/200", "@accent/ground-raised" ], "surface/subtle": [ "@color/neutral/50", "@accent/ground-sunken" ], "surface/lightest": [ "@color/neutral/25", "@accent/ground" ], "surface/dark": [ "@color/neutral/900", "@color/base/white" ], "surface/deep": [ "@accent/ground-sunken", "@accent/ground-sunken" ], "surface/pale": [ "@accent/on-ground", "@accent/ground-raised" ], "surface/neutral": [ "@color/neutral/500", "@color/neutral/500" ], "surface/tertiary": [ "@color/neutral/700", "@color/neutral/300" ], "surface/black": [ "@color/base/black", "@color/base/black" ], "surface/wash-light": [ "@color/alpha/white-8", "@color/alpha/white-8" ], "surface/wash-dark": [ "@color/alpha/black-8", "@color/alpha/black-8" ], "text/heading": [ "@color/neutral/900", "@color/base/white" ], "text/logo": [ "@color/blue/1000", "@color/base/white" ], "text/primary": [ "@color/neutral/900", "@color/base/white" ], "text/secondary": [ "@color/neutral/600", "@accent/on-ground" ], "text/strong": [ "@color/neutral/700", "@accent/on-ground-faint" ], "text/heavy": [ "@color/neutral/800", "@accent/on-ground" ], "text/muted": [ "@color/neutral/500", "@accent/on-ground-quiet" ], "text/subtle": [ "@color/neutral/500", "@color/alpha/white-60" ], "text/darkest": [ "@color/neutral/950", "@color/base/white" ], "text/inverse": [ "@color/base/white", "@color/neutral/900" ], "text/accent": [ "@accent/text", "@accent/on-dark" ], "text/accent-deep": [ "@accent/role-deep", "@accent/on-dark" ], "text/accent-inverse": [ "@accent/on-dark", "@accent/base" ], "text/on-accent": [ "@accent/on-base", "@accent/on-light" ], "text/on-accent-deep": [ "@accent/on-deep", "@accent/on-light" ], "text/on-accent-light": [ "@accent/on-base", "@accent/on-base" ], "text/quiet-inverse": [ "@accent/on-ground-faint", "@accent/on-ground-faint" ], "text/faint-inverse": [ "@accent/tint", "@accent/tint" ], "text/on-image": [ "@color/base/white", "@color/base/white" ], "text/on-image-body": [ "@accent/on-ground", "@accent/on-ground" ], "text/on-image-eyebrow": [ "@accent/on-dark", "@accent/on-dark" ], "text/on-dark-strong": [ "@color/alpha/white-72", "@color/alpha/white-72" ], "text/on-dark-quiet": [ "@color/alpha/white-60", "@color/alpha/white-60" ], "border/subtle": [ "@color/neutral/200", "@color/alpha/white-20" ], "border/subtle-inverse": [ "@color/alpha/white-20", "@color/neutral/200" ], "border/default": [ "@color/neutral/300", "@color/alpha/white-30" ], "border/strong": [ "@color/neutral/400", "@color/alpha/white-40" ], "border/dark": [ "@color/neutral/900", "@color/base/white" ], "border/faint": [ "@color/neutral/100", "@color/alpha/white-8" ], "border/accent": [ "@accent/base", "@accent/on-dark" ], "border/accent-deep": [ "@accent/role-deep", "@accent/on-dark" ], "border/accent-inverse": [ "@accent/on-dark", "@accent/base" ], "border/heading": [ "@accent/ground", "@color/base/white" ], "border/inverse": [ "@color/base/white", "@color/neutral/900" ], "border/wash-light": [ "@color/alpha/white-16", "@color/alpha/white-16" ], "icon/default": [ "@color/neutral/900", "@color/base/white" ], "icon/accent": [ "@accent/text", "@accent/on-dark" ], "icon/secondary": [ "@color/neutral/500", "@accent/on-dark" ], "icon/muted": [ "@color/neutral/500", "@color/alpha/white-60" ], "icon/inverse": [ "@color/base/white", "@color/neutral/900" ], "icon/on-image": [ "@color/base/white", "@color/base/white" ], "icon/size/inline": [ "@size/icon/20", "@size/icon/20" ], "icon/size/standalone": [ "@size/icon/24", "@size/icon/24" ], "icon/size/feature": [ "@size/icon/32", "@size/icon/32" ], "status/success/text": [ "@color/feedback/success/mid", "@color/rag/green" ], "status/success/bg": [ "@color/feedback/success/tint", "@color/feedback/success/deep" ], "status/success/border": [ "@color/feedback/success/border", "@color/feedback/success/mid" ], "status/success/wash": [ "@color/alpha/success-8", "@color/alpha/success-8" ], "status/warning/text": [ "@color/feedback/warning/mid", "@color/rag/yellow" ], "status/warning/bg": [ "@color/feedback/warning/tint", "@color/feedback/warning/deep" ], "status/warning/border": [ "@color/feedback/warning/border", "@color/feedback/warning/mid" ], "status/warning/wash": [ "@color/alpha/warning-8", "@color/alpha/warning-8" ], "status/danger/text": [ "@color/feedback/danger/mid", "@color/rag/red" ], "status/danger/bg": [ "@color/feedback/danger/tint", "@color/feedback/danger/deep" ], "status/danger/border": [ "@color/feedback/danger/border", "@color/feedback/danger/mid" ], "status/danger/wash": [ "@color/alpha/danger-8", "@color/alpha/danger-8" ], "status/info/text": [ "@color/feedback/info/mid", "@color/blue/400" ], "status/info/bg": [ "@color/feedback/info/tint", "@color/blue/900" ], "status/info/border": [ "@color/feedback/info/border", "@color/blue/500" ], "status/info/wash": [ "@color/alpha/info-8", "@color/alpha/info-8" ], "status/caution/text": [ "@color/feedback/caution/mid", "@color/feedback/caution/light" ], "status/caution/bg": [ "@color/feedback/caution/tint", "@color/feedback/caution/deep" ], "status/caution/border": [ "@color/feedback/caution/border", "@color/feedback/caution/mid" ], "status/caution/wash": [ "@color/alpha/caution-bg-8", "@color/alpha/caution-bg-8" ], "status/dot/red": [ "@color/rag/red", "@color/rag/red" ], "status/dot/yellow": [ "@color/rag/yellow", "@color/rag/yellow" ], "status/dot/green": [ "@color/rag/green", "@color/rag/green" ], "action/primary/default": [ "@accent/base", "@accent/on-dark" ], "action/primary/hover": [ "@accent/strong", "@accent/soft" ], "action/primary/pressed": [ "@accent/deep", "@accent/subtle" ], "action/primary/disabled": [ "@color/neutral/300", "@color/alpha/white-20" ], "action/secondary/default": [ "@accent/tint", "@accent/subtle" ], "action/secondary/hover": [ "@accent/subtle", "@color/alpha/white-20" ], "action/secondary/pressed": [ "@accent/soft", "@color/alpha/white-30" ], "action/on-primary": [ "@accent/on-base", "@accent/on-light" ], "overlay/faint": [ "@color/alpha/black-8", "@color/alpha/white-8" ], "overlay/subtle": [ "@color/alpha/black-12", "@color/alpha/white-12" ], "overlay/medium": [ "@color/alpha/black-20", "@color/alpha/white-20" ], "overlay/strong": [ "@color/alpha/black-30", "@color/alpha/white-30" ], "overlay/scrim": [ "@color/alpha/black-60", "@color/alpha/navy-72" ], "overlay/glass": [ "@color/alpha/white-72", "@color/alpha/white-16" ], "overlay/accent": [ "@color/alpha/electric-8", "@color/alpha/electric-16" ], "gradient/start": [ "@accent/ground", "@accent/ground" ], "gradient/mid": [ "@accent/ground-raised", "@accent/ground-raised" ], "gradient/mid-alt": [ "@accent/strong", "@accent/strong" ], "gradient/end": [ "@accent/base", "@accent/base" ], "space/0": [ "@size/space/0", "@size/space/0" ], "space/2": [ "@size/space/2", "@size/space/2" ], "space/4": [ "@size/space/4", "@size/space/4" ], "space/8": [ "@size/space/8", "@size/space/8" ], "space/12": [ "@size/space/12", "@size/space/12" ], "space/16": [ "@size/space/16", "@size/space/16" ], "space/20": [ "@size/space/20", "@size/space/20" ], "space/24": [ "@size/space/24", "@size/space/24" ], "space/32": [ "@size/space/32", "@size/space/32" ], "space/40": [ "@size/space/40", "@size/space/40" ], "space/48": [ "@size/space/48", "@size/space/48" ], "space/64": [ "@size/space/64", "@size/space/64" ], "space/80": [ "@size/space/80", "@size/space/80" ], "space/96": [ "@size/space/96", "@size/space/96" ], "space/120": [ "@size/space/120", "@size/space/120" ], "space/160": [ "@size/space/160", "@size/space/160" ], "space/200": [ "@size/space/200", "@size/space/200" ], "radius/none": [ "@size/radius/0", "@size/radius/0" ], "radius/xs": [ "@size/radius/4", "@size/radius/4" ], "radius/sm": [ "@size/radius/8", "@size/radius/8" ], "radius/md": [ "@size/radius/12", "@size/radius/12" ], "radius/lg": [ "@size/radius/16", "@size/radius/16" ], "radius/xl": [ "@size/radius/24", "@size/radius/24" ], "radius/full": [ "@size/radius/full", "@size/radius/full" ], "border-width/none": [ "@size/border/0", "@size/border/0" ], "border-width/thin": [ "@size/border/0-5", "@size/border/0-5" ], "border-width/hairline": [ "@size/border/1", "@size/border/1" ], "border-width/medium": [ "@size/border/2", "@size/border/2" ], "border-width/thick": [ "@size/border/4", "@size/border/4" ], "border-width/heavy": [ "@size/border/8", "@size/border/8" ], "type/display/2xs/size": [ "@size/font/30", "@size/font/30" ], "type/display/2xs/line": [ "@size/line/29", "@size/line/29" ], "type/display/xs/size": [ "@size/font/36", "@size/font/36" ], "type/display/xs/line": [ "@size/line/34", "@size/line/34" ], "type/display/sm/size": [ "@size/font/48", "@size/font/48" ], "type/display/sm/line": [ "@size/line/46", "@size/line/46" ], "type/display/md/size": [ "@size/font/60", "@size/font/60" ], "type/display/md/line": [ "@size/line/57", "@size/line/57" ], "type/display/lg/size": [ "@size/font/80", "@size/font/80" ], "type/display/lg/line": [ "@size/line/76", "@size/line/76" ], "type/display/xl/size": [ "@size/font/100", "@size/font/100" ], "type/display/xl/line": [ "@size/line/95", "@size/line/95" ], "type/display/2xl/size": [ "@size/font/120", "@size/font/120" ], "type/display/2xl/line": [ "@size/line/114", "@size/line/114" ], "type/display/3xl/size": [ "@size/font/160", "@size/font/160" ], "type/display/3xl/line": [ "@size/line/152", "@size/line/152" ], "type/display/4xl/size": [ "@size/font/200", "@size/font/200" ], "type/display/4xl/line": [ "@size/line/190", "@size/line/190" ], "type/display/5xl/size": [ "@size/font/240", "@size/font/240" ], "type/display/5xl/line": [ "@size/line/228", "@size/line/228" ], "type/body/2xs/size": [ "@size/font/12", "@size/font/12" ], "type/body/2xs/line": [ "@size/line/18", "@size/line/18" ], "type/body/xs/size": [ "@size/font/14", "@size/font/14" ], "type/body/xs/line": [ "@size/line/22", "@size/line/22" ], "type/body/sm/size": [ "@size/font/16", "@size/font/16" ], "type/body/sm/line": [ "@size/line/24", "@size/line/24" ], "type/body/md/size": [ "@size/font/18", "@size/font/18" ], "type/body/md/line": [ "@size/line/28", "@size/line/28" ], "type/body/lg/size": [ "@size/font/20", "@size/font/20" ], "type/body/lg/line": [ "@size/line/30", "@size/line/30" ], "type/body/xl/size": [ "@size/font/24", "@size/font/24" ], "type/body/xl/line": [ "@size/line/36", "@size/line/36" ], "type/body/2xl/size": [ "@size/font/28", "@size/font/28" ], "type/body/2xl/line": [ "@size/line/42", "@size/line/42" ], "type/tracking/normal": [ "@size/tracking/0", "@size/tracking/0" ], "type/tracking/slight": [ "@size/tracking/0-5", "@size/tracking/0-5" ], "type/tracking/wide": [ "@size/tracking/2", "@size/tracking/2" ], "type/tracking/wider": [ "@size/tracking/3", "@size/tracking/3" ], "font/heading": [ "@font/family/display", "@font/family/display" ], "font/text": [ "@font/family/body", "@font/family/body" ], "weight/thin": [ "@font/weight/thin", "@font/weight/thin" ], "weight/extralight": [ "@font/weight/extralight", "@font/weight/extralight" ], "weight/light": [ "@font/weight/light", "@font/weight/light" ], "weight/regular": [ "@font/weight/regular", "@font/weight/regular" ], "weight/medium": [ "@font/weight/medium", "@font/weight/medium" ], "weight/semibold": [ "@font/weight/semibold", "@font/weight/semibold" ], "weight/bold": [ "@font/weight/bold", "@font/weight/bold" ], "weight/black": [ "@font/weight/black", "@font/weight/black" ], "weight/heavy": [ "@font/weight/heavy", "@font/weight/heavy" ], "opacity/hidden": [ "@size/opacity/0", "@size/opacity/0" ], "opacity/faint": [ "@size/opacity/5", "@size/opacity/5" ], "opacity/subtle": [ "@size/opacity/20", "@size/opacity/20" ], "opacity/muted": [ "@size/opacity/40", "@size/opacity/40" ], "opacity/dim": [ "@size/opacity/60", "@size/opacity/60" ], "opacity/strong": [ "@size/opacity/80", "@size/opacity/80" ], "opacity/full": [ "@size/opacity/100", "@size/opacity/100" ] } }, { "name": "3. Component", "modes": [ "Mode 1" ], "count": 56, "tokens": { "card/surface": "@surface/raised", "card/border": "@border/subtle", "card/radius": "@radius/md", "card/padding": "@space/24", "card/title": "@text/primary", "card/body": "@text/secondary", "case-study/surface": "@surface/page", "case-study/eyebrow": "@text/accent", "case-study/title": "@text/heading", "case-study/lead": "@text/primary", "case-study/body": "@text/primary", "case-study/tags": "@text/accent", "case-study/logo": "@text/primary", "case-study/page-number": "@text/accent", "case-study/mockup": "@surface/muted", "case-study/rule": "@border/subtle", "case-study/frame": "@border/inverse", "footer/logo": "@text/logo", "footer/rule": "@border/subtle", "footer/page-number": "@text/accent", "footer/inverse/logo": "@text/inverse", "footer/inverse/rule": "@border/subtle-inverse", "footer/inverse/page-number": "@text/accent-inverse", "slot/surface": "@surface/muted", "slot/label": "@text/primary", "meter/track": "@surface/sunken", "meter/fill": "@surface/accent", "meter/label": "@text/secondary", "meter/value": "@text/primary", "meter/radius": "@radius/full", "meter/height": "@space/8", "star-tile/surface": "@surface/inverse", "star-tile/mark": "@text/accent-inverse", "star-tile/label": "@text/inverse", "star-tile/radius": "@radius/sm", "heat/low": "@status/success/bg", "heat/mid": "@status/warning/bg", "heat/high": "@status/danger/bg", "heat/text": "@text/primary", "logo/fill/default": "@text/logo", "logo/fill/inverse": "@text/inverse", "logo/fill/accent": "@text/accent", "logo/fill/muted": "@text/muted", "logo/clear-space": "@space/24", "logo/height/sm": "@space/40", "logo/height/md": "@space/64", "logo/height/lg": "@space/96", "logo-hamaa/fill/default": "@text/logo", "logo-hamaa/fill/inverse": "@text/inverse", "logo-hamaa/fill/accent": "@text/accent", "logo-hamaa/fill/muted": "@text/muted", "logo-client/fill/default": "@text/primary", "logo-client/fill/inverse": "@text/inverse", "bg/default": "@surface/page", "bg/inverse": "@surface/inverse", "bg/accent": "@surface/accent" } }, { "name": "4. Canvas", "modes": [ "Mode 1" ], "count": 4, "tokens": { "slide/width": "@size/doc/1920", "slide/height": "@size/doc/1080", "slide/margin-x": "@size/doc/120", "slide/safe-area": "@size/doc/100" } }, { "name": "RTL", "modes": [ "LTR", "RTL" ], "count": 37, "tokens": { "direction/value": [ "ltr", "rtl" ], "direction/text": [ "ltr", "rtl" ], "direction/layout": [ "ltr", "rtl" ], "align/text": [ "left", "right" ], "align/start": [ "left", "right" ], "align/end": [ "right", "left" ], "align/center": [ "center", "center" ], "float/start": [ "left", "right" ], "float/end": [ "right", "left" ], "margin/inline-start": [ "margin-left", "margin-right" ], "margin/inline-end": [ "margin-right", "margin-left" ], "margin/block-start": [ "margin-top", "margin-top" ], "margin/block-end": [ "margin-bottom", "margin-bottom" ], "padding/inline-start": [ "padding-left", "padding-right" ], "padding/inline-end": [ "padding-right", "padding-left" ], "padding/block-start": [ "padding-top", "padding-top" ], "padding/block-end": [ "padding-bottom", "padding-bottom" ], "border/inline-start": [ "border-left", "border-right" ], "border/inline-end": [ "border-right", "border-left" ], "border/block-start": [ "border-top", "border-top" ], "border/block-end": [ "border-bottom", "border-bottom" ], "inset/inline-start": [ "left", "right" ], "inset/inline-end": [ "right", "left" ], "inset/block-start": [ "top", "top" ], "inset/block-end": [ "bottom", "bottom" ], "radius/start-start": [ "border-top-left-radius", "border-top-right-radius" ], "radius/start-end": [ "border-top-right-radius", "border-top-left-radius" ], "radius/end-start": [ "border-bottom-left-radius", "border-bottom-right-radius" ], "radius/end-end": [ "border-bottom-right-radius", "border-bottom-left-radius" ], "transform/flip-x": [ "scaleX(1)", "scaleX(-1)" ], "transform/rotate-icon": [ "rotate(0deg)", "rotate(180deg)" ], "chevron/forward": [ "›", "‹" ], "chevron/backward": [ "‹", "›" ], "arrow/forward": [ "→", "←" ], "arrow/backward": [ "←", "→" ], "quote/open": [ "\"", "«" ], "quote/close": [ "\"", "»" ] } } ] } } } }, "404": { "description": "Endpoint not found" } } } }, "/palettes.json": { "get": { "summary": "Color Palettes", "description": "6 brand color palettes: Blue with its 12-step ramp, plus 5 secondary palettes with signature, deep, and text-safe values", "operationId": "getColorPalettes", "tags": [ "Color" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/ColorPalettes" }, "example": { "version": "1.0.0", "description": "AZMX color palettes - one primary (Blue) and five secondary palettes", "count": 6, "palettes": [ { "name": "Blue", "description": "Primary brand palette with Electric (#001AFF); dark grounds are black (#000000) in every palette", "ramp": [ { "step": "Blue 50", "hex": "#F0F5FF", "notes": "Soft light surface: panels, table zebra, image backings" }, { "step": "Blue 100", "hex": "#DDE8FF", "notes": "Body text on dark" }, { "step": "Blue 200", "hex": "#BFD5FF", "notes": "Meta and caption text on dark" }, { "step": "Blue 300", "hex": "#93B6FF", "notes": "" }, { "step": "Blue 400", "hex": "#5D8FFF", "notes": "Equals Light Blue" }, { "step": "Blue 500", "hex": "#2661FF", "notes": "" }, { "step": "Blue 600", "hex": "#001AFF", "notes": "Equals Electric" }, { "step": "Blue 700", "hex": "#0200D3", "notes": "Gradient mid-alt stop" }, { "step": "Blue 800", "hex": "#01009B", "notes": "" }, { "step": "Blue 900", "hex": "#01006E", "notes": "Cover gradient mid-stop" }, { "step": "Blue 950", "hex": "#010040", "notes": "" }, { "step": "Blue 1000", "hex": "#040038", "notes": "Dark Navy: the logo artwork's colour. No longer a ground, a heading colour or the gradient start" } ] }, { "name": "Orange", "signature": "#F47A48", "deep": "#842C09", "text_safe_step": "color/orange/700", "text_safe_hex": "#A1502F", "description": "Secondary palette - full 12-step ramp available in design tokens" }, { "name": "Green", "signature": "#22C36F", "deep": "#012F02", "text_safe_step": "color/green/700", "text_safe_hex": "#168049", "description": "Secondary palette - full 12-step ramp available in design tokens" }, { "name": "Yellow", "signature": "#FED340", "deep": "#693F02", "text_safe_step": "color/yellow/800", "text_safe_hex": "#895F0F", "description": "Secondary palette - full 12-step ramp available in design tokens" }, { "name": "Purple", "signature": "#C68FFF", "deep": "#2E0068", "text_safe_step": "color/purple/700", "text_safe_hex": "#7341AD", "description": "Secondary palette - full 12-step ramp available in design tokens" }, { "name": "Red", "signature": "#FF2B3C", "deep": "#640000", "text_safe_step": "color/red/700", "text_safe_hex": "#A81C27", "description": "Secondary palette - full 12-step ramp available in design tokens" } ] } } } }, "404": { "description": "Endpoint not found" } } } }, "/typography.json": { "get": { "summary": "Typography System", "description": "Font families, weights, type scale, and typographic rules for the AZMX brand", "operationId": "getTypographySystem", "tags": [ "Typography" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/TypographySystem" }, "example": { "version": "1.0.0", "description": "AZMX typography system - font families, weights, type scale, and usage rules", "families": [ { "role": "Display / Titles", "family": "thmanyah serif display", "variable": "Display", "variable_id": "1:980", "notes": "Elegant serif. Personality: titles, stats, quotes, brand numerals." }, { "role": "Body / Information", "family": "Azm X Variable", "variable": "Body", "variable_id": "1:979", "notes": "Variable sans, supports EN + Arabic. Body, labels, tables, UI." } ], "weights": [ { "weight": "ExtraLight", "variable_id": "1:978" }, { "weight": "Light", "variable_id": "1:976" }, { "weight": "Regular", "variable_id": "1:975" }, { "weight": "Medium", "variable_id": "1:974" }, { "weight": "SemiBold", "variable_id": "1:973" }, { "weight": "Bold", "variable_id": "1:977" }, { "weight": "Black", "variable_id": "1:981" } ], "type_scale": [ { "role": "Cover hero display", "font": "thmanyah serif", "size": "168", "line_height": "156", "weight": "Regular", "tracking": -2, "case_style": "Mixed-case" }, { "role": "Divider title", "font": "thmanyah serif", "size": "120", "line_height": "112", "weight": "Medium", "tracking": -1.5, "case_style": "Mixed-case" }, { "role": "Closing hero word", "font": "thmanyah serif", "size": "220", "line_height": "200", "weight": "Regular", "tracking": -3, "case_style": "Mixed-case" }, { "role": "Slide title (H1)", "font": "thmanyah serif", "size": "64", "line_height": "68", "weight": "Regular", "tracking": -0.5, "case_style": "Mixed-case" }, { "role": "Section / card title (H2)", "font": "thmanyah serif", "size": "36", "line_height": "44", "weight": "Medium", "tracking": 0, "case_style": "Mixed-case" }, { "role": "Sub-label / role title", "font": "Azm X Variable", "size": "22", "line_height": "28", "weight": "SemiBold", "tracking": 0, "case_style": "Mixed-case" }, { "role": "Eyebrow (label-lg)", "font": "Azm X Variable", "size": "14", "line_height": "20", "weight": "Medium", "tracking": 0, "case_style": "Case as written, in the accent colour" }, { "role": "Body", "font": "Azm X Variable", "size": "22", "line_height": "32", "weight": "Regular", "tracking": 0, "case_style": "Sentence" }, { "role": "Lead / intro body", "font": "Azm X Variable", "size": "26", "line_height": "38", "weight": "Light", "tracking": 0, "case_style": "Sentence" }, { "role": "Caption / meta", "font": "Azm X Variable", "size": "14", "line_height": "20", "weight": "Medium", "tracking": 0, "case_style": "Sentence / case as written" }, { "role": "Stat numeral", "font": "thmanyah serif", "size": "88", "line_height": "84", "weight": "Regular", "tracking": -1, "case_style": "with sans suffix" }, { "role": "Stat label", "font": "Azm X Variable", "size": "16", "line_height": "22", "weight": "Medium", "tracking": 0, "case_style": "Case as written" }, { "role": "Brand numeral (TOC/section)", "font": "thmanyah serif", "size": "64", "line_height": "64", "weight": "Regular", "tracking": 0, "case_style": "01–06" }, { "role": "Table header", "font": "Azm X Variable", "size": "14", "line_height": "20", "weight": "SemiBold", "tracking": 0, "case_style": "Case as written" }, { "role": "Table cell", "font": "Azm X Variable", "size": "18", "line_height": "26", "weight": "Regular", "tracking": 0, "case_style": "Sentence" }, { "role": "Quote / testimonial", "font": "thmanyah serif", "size": "44", "line_height": "56", "weight": "Regular", "tracking": -0.5, "case_style": "—" } ], "rules": [ "Serif = personality (titles, stats, quotes, brand numerals). Sans = information (body, labels, tables, UI).", "Never set body copy in serif. Never set a hero in sans.", "Stat numerals use serif for the figure and sans Medium for the + / unit suffix — e.g. serif 4,000 + sans +. The suffix is baseline-aligned to the figure.", "No italics. The installed thmanyah serif display has no italic style. Emphasis is expressed through scale, weight, and color only — never a faux or substituted italic. (This supersedes earlier art-direction drafts that called for italic accents; the client confirmed serif-display, no-italics.)" ], "bilingual_note": "The gradient brand identity and type system are bilingual (EN + Arabic). Azm X Variable carries both scripts; thmanyah display anchors the Latin display voice. Arabic logo lockups (the AZMX wordmark with Hamaa) appear alongside English copy." } } } }, "404": { "description": "Endpoint not found" } } } }, "/voice.json": { "get": { "summary": "Voice & Tone Guidelines", "description": "Brand language, tone rules, voice dimensions, writing mechanics, and format-specific guidelines", "operationId": "getVoiceAndToneGuidelines", "tags": [ "Voice" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/VoiceAndToneGuidelines" }, "example": { "version": "1.0.0", "description": "AZMX voice and tone - brand language, tone rules, the four voice dimensions, writing mechanics, format rules, and platform-specific voice", "brand_language": { "tagline": "Forward · Human Always · Moving Ideas Forward.", "philosophy": "Designing the Future of Experience.", "boilerplate": "AZMX is a leading Saudi digital consultancy. Never \"studio\", \"agency\", or \"boutique\"." }, "voice_summary": "Confident, editorial, human, premium. Never templated, never corporate-stiff, never AI-generated in feel.", "tone_rules": [ { "number": "1", "heading": "Confident, not boastful.", "description": "State what AZMX does plainly. Let the work carry the weight; skip superlatives like \"world-class\" and \"cutting-edge.\"" }, { "number": "2", "heading": "Editorial, not marketing-speak.", "description": "Write like a premium magazine, not a landing page. Short declarative sentences. Concrete nouns over abstractions." }, { "number": "3", "heading": "Human, always.", "description": "Warm and direct. Address the reader as a person. Contractions are fine in English. No jargon walls." }, { "number": "4", "heading": "Premium means quiet.", "description": "No exclamation marks doing the selling. No ALL-CAPS urgency. Scarcity of emphasis is what makes emphasis land, exactly like Electric blue on the page." } ], "dimensions": [ { "dimension": "Formality", "position": "Mid-Formal. Authoritative but accessible; expertise without stiffness.", "we_are": "Authoritative · Polished · Professional · Respectful", "we_are_not": "Stiff · Academic · Overly casual · Jargony" }, { "dimension": "Technicality", "position": "Balanced. Expertise is worth nothing unheard. Simplify the complex without becoming simplistic.", "we_are": "Expert · Knowledgeable · Clear and precise · Educational", "we_are_not": "Simplistic · Patronising · Obscure · Overly technical" }, { "dimension": "Attitude", "position": "Bold but Respectful. Challenge the status quo with the integrity of a trusted partner.", "we_are": "Confident · Pioneering · Bold and visionary · Thoughtfully provocative", "we_are_not": "Arrogant · Abrasive · Reckless · Dismissive" }, { "dimension": "Purpose", "position": "Context-Dependent. Inspirational when sharing the vision, pragmatic when discussing delivery.", "we_are": "See the Purpose table below", "we_are_not": "—" } ], "calibration_examples": [ { "dimension": "Formality", "wrong_formal": "Too formal. \"The aforementioned framework necessitates the utilization of agile methodologies to ensure optimal project velocity.\"", "wrong_informal": "Too informal. \"Basically, we gotta use agile to make stuff go faster.\"", "azmx_voice": "\"We use an agile framework to ensure our projects maintain momentum and deliver value efficiently.\"" }, { "dimension": "Technicality", "wrong_formal": "Too technical. \"Our containerized microservices architecture leverages a Kubernetes orchestrator for dynamic scaling.\"", "wrong_informal": "Too simple. \"We make your website work well with lots of users.\"", "azmx_voice": "\"We build resilient, scalable systems that can grow with your business, ensuring reliability and performance under pressure.\"" }, { "dimension": "Attitude", "wrong_formal": "Too arrogant. \"Our way is the only way to succeed in this market.\"", "wrong_informal": "Too neutral. \"There are several options available for market entry.\"", "azmx_voice": "\"We believe a human-centric approach is the most powerful and sustainable path to market leadership in the region.\"" } ], "purpose_modes": [ { "mode": "Inspirational — sharing the vision", "surfaces": "Homepage, keynotes, thought leadership", "goal": "Paint the future and inspire confidence in AZM X's leadership.", "example": "\"We are not just building digital products; we are elevating the digital maturity of the entire region, in line with Vision 2030\"" }, { "mode": "Pragmatic — discussing delivery", "surfaces": "Proposals, SOWs, project reports", "goal": "Be clear and direct about tangible outcomes, efficiency, and measurable ROI.", "example": "\"This SOW outlines a three-phase project, with bi-weekly check-ins to ensure full alignment and on-time delivery of all milestones\"" } ], "writing_mechanics": [ "Em-dashes as the default connector. Use commas, periods, or a colon instead.", "Triads everywhere (\"fast, simple, and powerful\"). One strong claim beats three padded ones.", "Empty intensifiers: \"truly,\" \"seamlessly,\" \"effortlessly,\" \"robust,\" \"leverage,\" \"elevate,\" \"unlock,\" \"empower,\" \"delve.\"", "Symmetrical paragraph lengths and mirrored sentence openers. Vary rhythm like a human editor would.", "Every sentence hedged (\"can help,\" \"may enable\"). Commit: it does or it does not.", "Summaries that restate the heading. If the heading said it, the body adds something new or gets cut." ], "universal_principles": [ { "principle": "Lead with value", "description": "Answer \"what's in it for me?\" with a clear benefit: useful information, an insight, or a story worth the reader's minute." }, { "principle": "Be clear and concise", "description": "Short sentences, no jargon, the point up front. Write conversationally, as if speaking to one person." }, { "principle": "Write like a human", "description": "Approachable and authentic. Use contractions. Read it aloud; if it sounds like a robot, rewrite it. The target reaction is \"you know me\"." }, { "principle": "Have a clear purpose", "description": "Every piece carries one takeaway message and one job. AZMX does not mandate a CTA (see below); it does mandate knowing what the piece is for." }, { "principle": "Use hashtags strategically", "description": "Three maximum, at the end. Mix broad, niche, and branded tags within that three." } ], "format_rules": [ { "format": "Headlines and heroes", "rules": "serif voice, short, mixed-case. A single sharp idea. No period at the end." }, { "format": "Eyebrows/labels", "rules": "1 to 3 words, functional not clever, in case as written. No uppercase and no tracking (v3.0.0); the eyebrow style is the design system's label-lg." }, { "format": "Body copy", "rules": "sentence case, 22px voice on slides, short paragraphs. Front-load the point." }, { "format": "Stats", "rules": "let the number talk. Label in plain words underneath, no adjectives." }, { "format": "Quotes/testimonials", "rules": "verbatim, trimmed only for length, attributed with name and title." }, { "format": "Emails", "rules": "subject lines under 45 characters, preheader completes the subject rather than repeating it. Arabic emails follow the RTL rules in the email design system." }, { "format": "Social/LinkedIn", "rules": "first line earns the click alone (it is all people see collapsed). No hashtag walls; 3 maximum, at the end." } ], "platform_voice": [ { "platform": "LinkedIn", "voice": "Authoritative, professional, insightful", "guidelines": "Share expertise and start a professional discussion. Structure for readability: white space, bullets, or a numbered list for longer thoughts. Mid-formal, expert but accessible." }, { "platform": "Instagram", "voice": "Creative, personable, inspiring", "guidelines": "Tell a visual story. The caption adds context and personality rather than describing the image. Slightly more personal in tone; questions invite comments." }, { "platform": "Twitter/X", "voice": "Conversational, witty, timely", "guidelines": "Real-time conversation. Short, sharp, easy to share. Threads carry longer stories, one complete thought per tweet. Witty, never at anyone's expense." } ], "strategy_superseded": [ { "deck_says": "3–5 hashtags per post, and 5–10 on Instagram", "azmx_voice": "Three maximum, at the end. Every channel, every brand." }, { "deck_says": "Emojis are encouraged on Instagram and Twitter/X for tone and scannability", "azmx_voice": "No emojis in copy: headlines, body, captions, subject lines, social posts. Every channel, every brand. The one exception is the email design system's section-header and digest chip glyph (C03, C04, C07, C16), which is a visual chip, not copy." }, { "deck_says": "Every post must include a clear call to action", "azmx_voice": "No mandatory CTA. Where a next step exists, make it obvious. Where it does not, do not manufacture one." } ], "pre_publish_checklist": [ { "number": "1", "heading": "On-brand?", "description": "Does it match the Four Dimensions above, or the correct sub-brand's profile in sub-brand-voices.md?" }, { "number": "2", "heading": "Clear and concise?", "description": "Can it be said in fewer words?" }, { "number": "3", "heading": "Valuable?", "description": "Does it pass the \"what's in it for me?\" test for the named audience?" }, { "number": "4", "heading": "Purposeful?", "description": "Is the one takeaway obvious, and is the next step obvious to a reader who wants one? (The deck asks \"does it have a CTA?\" — AZMX asks this instead.)" }, { "number": "5", "heading": "Right for the platform?", "description": "Is the tone tuned for LinkedIn, Instagram, or Twitter/X?" }, { "number": "6", "heading": "Proofread, and mechanics clean?", "description": "Typos, grammar, the correct brand name spelled correctly. No em-dash defaults, no triads, no banned intensifiers, no emojis in the copy, no more than three hashtags. (The email design system's section-header and digest chip glyph is the one permitted exception; it is a visual chip, not copy.)" } ], "quick_self_check": [ "Could a competitor paste this over their logo? If yes, it is too generic; sharpen it.", "Read it aloud. Anything you would not say to a client's face, rewrite.", "Delete the first sentence if the second one is stronger without it. It usually is." ] } } } }, "404": { "description": "Endpoint not found" } } } }, "/audiences.json": { "get": { "summary": "Audience Personas", "description": "8 audience personas with pain points, core messages, motions, and brand associations", "operationId": "getAudiencePersonas", "tags": [ "Audience" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/AudiencePersonas" }, "example": { "version": "1.0.0", "description": "AZMX audience personas and messaging - 8 external personas, internal audiences, external motions, and brands", "count": 8, "personas": [ { "name": "Directors / Heads", "motion": "B2G", "brands": [ "AZM X" ], "pain_points": "Need a proven, low-risk path to modernisation, and a partner who knows public-sector complexity well enough to deliver cost-effectively without disrupting the core mission.", "core_message": "\"We provide secure, compliant, and cost-effective solutions to modernize your public services\"" }, { "name": "Leads", "motion": "B2G", "brands": [ "Colab", "Anatomi" ], "pain_points": "Need proof that modern, agile practice is achievable with the right tools, and to see how research and benchmarking platforms change what their teams can build.", "core_message": "\"Empower your agency with the tools to build accessible and trustworthy digital government services\"" }, { "name": "C-Suite", "motion": "B2B", "brands": [ "AZM X" ], "pain_points": "Need a partner who de-risks major projects, holds budget and schedule, and produces the competitive edge the business needs to lead.", "core_message": "\"AZM X is the strategic partner that guarantees delivery and drives innovation\"" }, { "name": "Product / UX Heads", "motion": "B2B", "brands": [ "Colab", "Anatomi" ], "pain_points": "Need a better way to run their team's workflow: fewer bottlenecks, enforced consistency, higher-quality shipping.", "core_message": "\"Equip your team with the integrated tools to ship better products, faster\"" }, { "name": "Operations", "motion": "B2B", "brands": [ "Clix" ], "pain_points": "Need one source of truth for core business processes: automation for inefficient workflows, visibility, and enough control to scale.", "core_message": "\"Clix provides the central platform to automate operations and control your business\"" }, { "name": "Researchers", "motion": "B2C", "brands": [ "Colab", "Anatomi" ], "pain_points": "Need one tool that covers planning through presenting, and makes qualitative analysis faster.", "core_message": "\"Colab is the all-in-one toolkit that streamlines your research from plan to presentation\"" }, { "name": "Designers", "motion": "B2C", "brands": [ "Anatomi" ], "pain_points": "Need a reliable source of high-quality inspiration when stuck: a curated library of proven, real-world patterns.", "core_message": "\"Anatomi is your personal library of elite designs to inspire creativity and accelerate your workflow\"" }, { "name": "Industry Professionals", "motion": "B2C", "brands": [ "Majarah" ], "pain_points": "Need a central hub for the region's creative and tech community, where they can meet peers, learn from experts, and grow a network.", "core_message": "\"Majarah is the hub for the creative and tech community to connect, learn, and be inspired\"" } ], "internal_audiences": [ { "segment": "Leadership", "needs": "Business performance at a glance, strategic alignment across departments, and the risks and opportunities on the horizon.", "core_message": "\"Your vision is being executed effectively. We are aligned on our strategic priorities and are proactively managing performance to drive results\"" }, { "segment": "Team Leads", "needs": "Cross-functional priorities, resource allocation, and the specific goals and metrics their teams own.", "core_message": "\"You have the clarity, context, and support needed to lead your team to success. We are empowering you to make decisions that align with our shared goals\"" }, { "segment": "All Employees", "needs": "Company direction, how their role feeds collective results, and news about culture and shared wins.", "core_message": "\"Your work is valuable and directly contributes to our shared success. You are a crucial part of a winning team, and we are succeeding together\"" } ], "external_motions": [ { "motion": "B2G", "brands": [ "AZM X", "Colab", "Anatomi" ], "needs": "An end-to-end partner that de-risks mission-critical projects with strategy and evidence-based tools.", "core_message": "\"Your end-to-end partner for public service success, combining strategic consulting, evidence-based validation, and regional design benchmarks\"" }, { "motion": "B2B", "brands": [ "AZM X", "Colab", "Clix", "Anatomi" ], "needs": "Solutions that reach the whole business, from strategy to product, with measurable ROI.", "core_message": "\"We deliver business-wide results by combining strategic consulting and operational efficiency with an integrated suite of product tools that drive ROI\"" }, { "motion": "B2C", "brands": [ "Colab", "Majarah", "Anatomi" ], "needs": "Tools and a community to grow their skills and connect with peers.", "core_message": "\"An ecosystem to help you excel: Elevate your craft with our integrated research and design platforms, and build your network at our industry-leading community events\"" } ], "brands": [ { "name": "AZM X", "description": "The consultancy. Strategy, design, delivery, evidence.", "motions": [ "B2G", "B2B", "Internal" ] }, { "name": "Colab", "description": "UX research platform. The evidence engine.", "motions": [ "B2G", "B2B", "B2C" ] }, { "name": "Majarah", "description": "The region's UX gathering and community hub.", "motions": [ "B2C" ] }, { "name": "Clix", "description": "ERP for SMEs. Invoicing, finance, operations.", "motions": [ "B2B" ] }, { "name": "Anatomi", "description": "Design benchmark and pattern library for Saudi digital products.", "motions": [ "B2G", "B2B", "B2C" ] } ] } } } }, "404": { "description": "Endpoint not found" } } } }, "/prompts.json": { "get": { "summary": "Content Prompt Templates", "description": "15 content generation prompt templates with full template text", "operationId": "getContentPromptTemplates", "tags": [ "Content" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/ContentPromptTemplates" }, "example": { "version": "1.0.0", "description": "AZMX content generation prompt templates - briefs, articles, case studies, social customisation, and localisation", "count": 15, "prompts": [ { "id": "blog-seo-brief", "number": 1, "title": "The Blog SEO Brief Prompt", "description": "Strategic SEO content brief for planning blog articles before writing. Outputs target keyword analysis, search intent, competitor insights, recommended outline structure, internal linking strategy, meta fields, and content angle. Use this brief to fill in the Article Generation Prompt (Template #2) for production", "deck_page": null, "template": "# YOUR REQUEST\n\n- Topic/Focus Area: [Enter the general topic or content focus area]\n- Primary Brand: [Choose the brand]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Primary Keyword (Proposed): [Enter the proposed primary keyword, or leave blank for recommendations]\n- Business Goal: [What should this content achieve? Lead generation, brand awareness, thought leadership, customer education, etc.]\n- Existing Content to Build On: [Optional. List any existing articles, resources, or internal content this should connect to]\n- Competitor URLs (Optional): [List 2-5 competitor or industry articles currently ranking for this topic]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. You will not write copy in this brief, but you must understand the brand's voice to recommend the right content angle.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. The brief must align with this persona's priorities and pain points.\n\n# YOUR TASK:\n\n## Your Role: You are an expert SEO strategist and content planner for a leading Saudi digital consultancy, skilled at researching keywords, analyzing search intent, auditing competitor content, and creating strategic content briefs that guide writers to produce high-performing, SEO-optimized articles.\n\n## Your Process:\n\n- Analyze the Request: Understand the Topic, Brand, Audience, Business Goal, and any proposed keywords or competitor context provided.\n- Keyword Research & Selection:\n- - If a Primary Keyword was proposed, validate it: assess search volume potential, keyword difficulty, relevance to the business goal, and alignment with the target persona.\n- - If no Primary Keyword was provided, or if the proposed keyword is not optimal, recommend 2-3 primary keyword options with rationale (search intent match, competition level, relevance to audience).\n- - Identify 4-6 Secondary Keywords (related terms, long-tail variations, semantic keywords) that should be naturally integrated into the article.\n- Search Intent Analysis: Determine the dominant search intent for the primary keyword:\n- - Informational: User wants to learn or understand something\n- - Navigational: User is looking for a specific page or brand\n- - Transactional: User intends to take an action (download, sign up, purchase)\n- - Commercial Investigation: User is researching options before a decision\n- - Explain what type of content will best satisfy this intent (guide, comparison, how-to, thought leadership, etc.).\n- Competitor Content Audit: If competitor URLs were provided, analyze them briefly:\n- - What angle or structure do they use?\n- - What topics do they cover well?\n- - What gaps or weaknesses exist that AZMX content can exploit? (Lack of depth, outdated information, missing perspectives, poor user experience, generic advice, etc.)\n- - If no competitor URLs were provided, note this and suggest that a manual competitive review would strengthen the brief.\n- Recommended Article Structure: Based on the search intent and competitor analysis, propose a logical article outline:\n- - Suggested H1 (Article Title)\n- - Suggested H2 section headings (4-7 sections recommended for 800-1200 word articles)\n- - Suggested H3 sub-headings where relevant\n- - FAQ section: Identify 2-4 \"People Also Ask\" questions from search results to answer in a dedicated FAQ section (supports AEO and featured snippet potential)\n- Internal Linking Strategy: Identify opportunities to link to existing AZMX content:\n- - If \"Existing Content to Build On\" was provided, recommend how and where to link it within the article structure.\n- - Suggest 2-4 internal link anchor text phrases that would naturally fit into the article and connect to related AZMX pages, resources, or services.\n- Meta Fields: Recommend SEO metadata:\n- - Meta Title (under 60 characters, includes primary keyword)\n- - Meta Description (under 160 characters, includes primary keyword and a clear value proposition)\n- Content Angle & Unique Value Proposition: Recommend the specific angle or perspective the article should take to differentiate it from competitors and resonate with the target persona. This is the \"why AZMX is uniquely qualified to write this\" statement.\n- Writer Guidance: Provide any additional notes for the writer: tone emphasis, data/sources to reference, case study or example suggestions, calls-to-action alignment, or persona-specific messaging from references/audiences-and-messaging.md.\n\n## Brief Guidelines:\n\n- Persona Alignment: Every recommendation in this brief (keyword selection, content angle, structure, internal links) must align with the target persona's priorities, pain points, and core message from references/audiences-and-messaging.md.\n- SEO Best Practices:\n- - Primary Keyword: Should appear in the meta title, meta description, H1, first paragraph, and at least one H2. Recommend placement.\n- - Secondary Keywords: Should be naturally distributed across H2/H3 headings and body text.\n- - Search Intent Match: The article structure must match the dominant search intent. An informational query should not receive a product pitch; a commercial investigation query should not receive a generic educational article.\n- - Snippet Optimization: Recommend content formats that are \"snippet-friendly\": numbered lists, bulleted key takeaways, direct question-and-answer blocks, tables, or structured data opportunities.\n- Competitor Differentiation: The content angle must exploit a gap, add a perspective, or provide depth that competitors are missing. Generic \"me too\" content does not rank and does not serve the business goal.\n- Internal Linking as Strategy: Internal links are not an afterthought. Identify genuine opportunities to connect this article to the broader AZMX content ecosystem: related thought leadership, case studies, service pages, tools, or resources.\n- Actionable Output: This brief will be handed to a writer (or fed into the Article Generation Prompt). Every recommendation must be specific enough to guide execution without requiring the writer to re-research.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- No emojis. This is a strategic planning document.\n- No mandatory CTA recommendation. If the business goal and search intent genuinely support a CTA, recommend one. If the article is purely educational or informational, state \"No CTA recommended — educational content\" and do not invent one.\n- Banned vocabulary, do not use (and do not recommend for use in the article): empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and do not recommend any of those patterns for the article.\n- Keyword stuffing is not SEO. Keyword integration must be natural. If a keyword cannot be naturally integrated into a heading or section, do not force it.\n\n## Your Final Output Format:\n\n------------------------------------------------------------\nBlog SEO Brief\n------------------------------------------------------------\nTopic: [Topic/Focus Area]\nBrand: [Brand]\nPersona: [Persona]\nBusiness Goal: [Business Goal]\n------------------------------------------------------------\nPRIMARY KEYWORD RECOMMENDATION:\n\n[If validating a proposed keyword:]\nProposed Keyword: [Keyword]\nAssessment: [Valid / Not Optimal]\nRationale: [Explain: search intent, competition level, relevance to persona and business goal]\n\n[If recommending keywords:]\nOption 1: [Keyword] — [Rationale: search volume potential, intent match, difficulty]\nOption 2: [Keyword] — [Rationale]\nOption 3: [Keyword] — [Rationale]\nRecommended: [Which option and why]\n\n------------------------------------------------------------\nSECONDARY KEYWORDS (4-6):\n\n1. [Secondary keyword 1]\n2. [Secondary keyword 2]\n3. [Secondary keyword 3]\n4. [Secondary keyword 4]\n5. [Secondary keyword 5, optional]\n6. [Secondary keyword 6, optional]\n\n------------------------------------------------------------\nSEARCH INTENT ANALYSIS:\n\nDominant Intent: [Informational / Navigational / Transactional / Commercial Investigation]\n\nExplanation: [What is the user trying to accomplish with this search? What type of content will satisfy this intent?]\n\nRecommended Content Type: [Guide, How-To, Comparison, Thought Leadership, Case Study Overview, Explainer, etc.]\n\n------------------------------------------------------------\nCOMPETITOR CONTENT AUDIT:\n\n[If competitor URLs were provided:]\n\nCompetitor 1: [URL]\n- Angle/Structure: [What approach do they take?]\n- Strengths: [What do they cover well?]\n- Gaps/Weaknesses: [What is missing, outdated, shallow, or generic?]\n\nCompetitor 2: [URL]\n- Angle/Structure:\n- Strengths:\n- Gaps/Weaknesses:\n\n[Continue for additional competitors]\n\nKey Opportunity for AZMX: [Summarize the gap or differentiation opportunity across all competitors reviewed]\n\n[If no competitor URLs were provided:]\nNo competitor URLs provided. Recommend conducting a manual SERP review for the primary keyword to identify top-ranking content, common angles, and differentiation opportunities before writing.\n\n------------------------------------------------------------\nRECOMMENDED ARTICLE STRUCTURE:\n\nH1 (Article Title):\n[Suggested title — should include primary keyword, be compelling, and match search intent]\n\nAlternative Title Options:\n1. [Alternative 1]\n2. [Alternative 2]\n\nH2 Section 1: [Suggested heading]\n- H3 Sub-heading (optional): [If needed for structure]\n- Content Focus: [What this section should cover]\n- Keyword Integration: [Primary or secondary keyword to naturally integrate here]\n\nH2 Section 2: [Suggested heading]\n- Content Focus:\n- Keyword Integration:\n\nH2 Section 3: [Suggested heading]\n- Content Focus:\n- Keyword Integration:\n\nH2 Section 4: [Suggested heading]\n- Content Focus:\n- Keyword Integration:\n\n[Continue for 4-7 H2 sections total]\n\nH2 Section: Frequently Asked Questions\n- H3: [People Also Ask Question 1]\n- H3: [People Also Ask Question 2]\n- H3: [People Also Ask Question 3, optional]\n- H3: [People Also Ask Question 4, optional]\n\nH2 Section: Conclusion\n- Content Focus: [Summarize key takeaway, reinforce value, include CTA if recommended]\n\n------------------------------------------------------------\nINTERNAL LINKING STRATEGY:\n\n[If existing content was provided:]\nLink to: [Existing content title or URL]\n- Recommended Anchor Text: \"[Anchor text phrase]\"\n- Placement: [Which H2 section this link fits naturally into]\n\n[General internal linking opportunities:]\n1. Link Opportunity: [Describe the type of AZMX content this article should link to, e.g., \"related service page: Digital Transformation services\"]\n - Suggested Anchor Text: \"[Anchor text]\"\n - Placement: [Which section]\n\n2. Link Opportunity: [Another opportunity]\n - Suggested Anchor Text: \"[Anchor text]\"\n - Placement: [Which section]\n\n3. Link Opportunity: [Another opportunity]\n - Suggested Anchor Text: \"[Anchor text]\"\n - Placement: [Which section]\n\n[Continue for 2-4 total internal link opportunities]\n\n------------------------------------------------------------\nMETA FIELDS:\n\nMeta Title (under 60 characters):\n[Your recommended meta title including primary keyword]\nCharacter Count: [Actual count]\n\nMeta Description (under 160 characters):\n[Your recommended meta description including primary keyword and value proposition]\nCharacter Count: [Actual count]\n\n------------------------------------------------------------\nCONTENT ANGLE & UNIQUE VALUE PROPOSITION:\n\n[1-2 paragraphs explaining the specific angle or perspective this article should take to differentiate it from competitors and resonate with the target persona. Answer: \"Why is AZMX uniquely qualified to write this?\" and \"What makes this article worth reading over the competitors?\"]\n\nPersona Alignment: [Confirm which core message from references/audiences-and-messaging.md this content angle aligns with, and how]\n\n------------------------------------------------------------\nWRITER GUIDANCE & ADDITIONAL NOTES:\n\nTone Emphasis: [Any specific tone or voice emphasis beyond the standard brand TOV, e.g., \"particularly data-driven and authoritative for this B2G persona\"]\n\nData/Sources to Reference: [Suggest any industry reports, statistics, research, or case studies the writer should reference to strengthen credibility]\n\nExample/Case Study Suggestions: [If applicable, suggest real-world examples, anonymized case studies, or scenarios to illustrate key points]\n\nCTA Recommendation: [If a CTA is appropriate: \"Recommend CTA: [CTA text] linking to [resource/page]. Placement: End of Conclusion section.\" / If no CTA: \"No CTA recommended — educational content serving informational intent.\"]\n\nPersona-Specific Messaging: [Any specific messaging points from references/audiences-and-messaging.md that must be reflected in the article]\n\n------------------------------------------------------------\nNEXT STEP: USE THIS BRIEF TO COMPLETE THE ARTICLE GENERATION PROMPT (TEMPLATE #2)\n\nThis brief provides the strategic foundation. To write the article, copy the following values into the Article Generation Prompt:\n\n- Topic: [Topic]\n- Primary Keyword: [Selected primary keyword]\n- Secondary Keywords: [List the 4-6 secondary keywords]\n- Internal Link Targets: [List the internal links identified above]\n- Primary CTA & Link: [CTA recommendation, or leave blank if none]\n- Target Word Count: [800-1200 words, or adjust based on competitor analysis and content depth needed]\n\nPaste the recommended article structure (H1, H2, H3 outline) into the Article prompt's Tone of Voice slot as additional guidance, or reference it when writing the article.\n\n------------------------------------------------------------", "notes": null }, { "id": "article-generation", "number": 2, "title": "The Article Generation Prompt", "description": "Long-form SEO and AEO article, 800 to 1200 words, with metadata, a hero image concept, and pre-written social snippets. ", "deck_page": "121", "template": "# YOUR REQUEST\n\n- Topic: [Enter the core subject of the article]\n- Primary Brand: [Choose the brand]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Primary Keyword: [Enter the single primary keyword]\n- Secondary Keywords: [List 2-4 related keywords to include]\n- Internal Link Targets: [Link(s)]\n- Primary CTA & Link: [Optional. Leave blank if there is no genuine next step] - [Link]\n- Target Word Count: [800-1200 words]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are an expert subject matter writer and SEO content strategist for a leading Saudi digital consultancy.\n\n## Your Process:\n\n- Analyze the Request: Understand the Topic, Brand, Audience, and all SEO inputs.\n- AEO Research: Based on the Primary Keyword, identify 2-3 common questions from Google's \"People Also Ask\" section to answer within the article.\n- Outline the Article: Create a logical structure using a main heading (H1), section headings (H2), and sub-headings (H3) where appropriate.\n- Write the Full Article: Write a comprehensive, insightful article that is authoritative and educational, following all guidelines below.\n- Create SEO Metadata & Extras: Write a compelling Meta Title and Meta Description. Suggest a concept for a featured image and provide 2-3 pre-written social media snippets to promote the article.\n\n## Writing Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- SEO & AEO Guidelines:\n- - Keyword Integration: Naturally weave the Primary and Secondary Keywords into the headings and body text. The Primary Keyword should appear in the first paragraph.\n- - AEO Tactics: Structure parts of the article to be \"snippet-friendly.\" Use bulleted lists, numbered steps, and include a Q&A section (e.g., \"Frequently Asked Questions\") that directly answers the \"People Also Ask\" questions you identified.\n- - Internal Linking: Where relevant, naturally hyperlink the specified Internal Link Targets from the request.\n- - CTA Integration: If a Primary CTA was supplied, place it at the end of the article. If the slot is blank, do not invent one.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- Hashtags: 3 maximum in any social snippet, all placed at the end of the snippet. (The 2025 deck set 3-5 for LinkedIn, 5-10 for Instagram, 2-4 for Twitter/X. Superseded by references/voice-and-tone.md.)\n- No emojis. Not in the article, not in the metadata, not in the social snippets.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one. (The 2025 deck required a CTA on every post. Superseded by references/voice-and-tone.md.)\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\nSEO Meta Title: [Your suggested Meta Title (under 60 characters)]\nSEO Meta Description: [Your suggested Meta Description (under 160 characters)]\n------------------------------------------------------------\nSuggested Titles:\n1. ...\n2. ...\n3. ...\n------------------------------------------------------------\nFeatured Image Suggestion: [Your concept for a hero image]\n------------------------------------------------------------\nSocial Media Snippets:\n1. (LinkedIn/Twitter): [A short, engaging snippet to promote the article]\n2. (LinkedIn/Twitter): [A second, different angle or quote from the article]\n3. (LinkedIn/Twitter, optional): [A third angle]\n------------------------------------------------------------\nFull Article:\n[Article Title (H1)]\n[Section 1 (H2)]\n[Paragraphs with internal links to [Link] where appropriate...]\n[Section 2 (H2)]\n[Bulleted lists, numbered steps...]\n[Frequently Asked Questions (H2)]\n[People Also Ask Question 1 (H3)]\n[Direct answer...]\n[People Also Ask Question 2 (H3)]\n[Direct answer...]\n------------------------------------------------------------\n[Conclusion (H2)]\n[Summary, and the supplied CTA if there is one...]\n------------------------------------------------------------\nPrimary Keyword:\n[Confirm the primary keyword and where it appears]\n------------------------------------------------------------\nSecondary Keywords:\n[List the secondary keywords you used]\n------------------------------------------------------------", "notes": "Two deck slips fixed here: the Primary Keyword slot repeated the Secondary Keywords label (\"List 2-4 related keywords\"), and the FAQ block showed only one People Also Ask question while the process asks for 2-3." }, { "id": "case-study-generation", "number": 3, "title": "The Case Study Generation Prompt", "description": "Client success story following challenge-solution-results structure, 800 to 1200 words, with client context, quantified outcomes, testimonial integration, and pre-written social snippets. Demonstrates real-world impact and builds credibility for B2G and B2B audiences", "deck_page": null, "template": "# YOUR REQUEST\n\n- Client/Project Name: [Enter the client name or project identifier, use anonymized name if confidentiality required]\n- Primary Brand: [Choose the brand]\n- Target Audience: [B2G / B2B — pick one, case studies primarily target decision-makers]\n- Persona: [Enter persona]\n- Industry/Sector: [Enter the client's industry: Government, Healthcare, Finance, Education, Retail, etc.]\n- Client Context:\n- - Organization Size: [SME / Enterprise / Government Entity]\n- - Prior State: [Briefly describe the client's situation before engagement]\n- - Strategic Goal: [What the client wanted to achieve]\n- Challenge: [Describe the specific problem, pain point, or opportunity the client faced. 2-4 key points.]\n- Approach: [Describe how your team approached the problem. Include methodology, frameworks, or unique processes used.]\n- Solution: [Describe what was delivered. Include specific services, technologies, platforms, or deliverables.]\n- Results: [List quantified outcomes and impacts. Must include at least 3 metrics.]\n- - Metric 1: [e.g., \"40% increase in digital service adoption\"]\n- - Metric 2: [e.g., \"Reduced processing time from 14 days to 2 days\"]\n- - Metric 3: [e.g., \"95% user satisfaction score\"]\n- - Additional Metrics: [Optional, add more if available]\n- - Qualitative Outcomes: [Optional: cultural shift, capability building, strategic positioning, etc.]\n- Testimonial:\n- - Quote: [Client testimonial quote, if available. Leave blank for model to suggest based on results.]\n- - Attribution: [Full Name, Title, Organization]\n- Primary CTA & Link: [Optional. Leave blank if there is no genuine next step] - [Link]\n- Target Word Count: [800-1200 words]\n- Confidentiality Level: [Public / Anonymized (client name concealed) / Internal Only]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are an expert case study writer and B2B/B2G content strategist for a leading Saudi digital consultancy, skilled at transforming client engagements into compelling, evidence-based success stories.\n\n## Your Process:\n\n- Analyze the Request: Understand the Client Context, Challenge, Solution, and Results. Identify the narrative arc that will resonate most with the Target Audience and Persona.\n- Map to Core Message: Based on the Persona, retrieve the appropriate core message from references/audiences-and-messaging.md and ensure the case study speaks to that persona's priorities and pain points.\n- Structure the Case Study: Follow the proven challenge-solution-results framework:\n- - Client Context (H2): Brief introduction to the client, their industry, and strategic position. Set the scene without revealing confidential details.\n- - The Challenge (H2): Clearly articulate the problem or opportunity. Make it relatable and specific. Use data to quantify the challenge where possible.\n- - Our Approach (H2): Describe how the team tackled the challenge. Highlight unique methodology, frameworks, or collaborative processes. Show expertise without overloading on technical jargon.\n- - The Solution (H2): Detail what was delivered. Be specific about services, platforms, technologies, or deliverables. Include enough technical detail to demonstrate capability, but keep it accessible.\n- - Results & Impact (H2): Lead with quantified metrics. Use bullet points for scanability. Follow metrics with qualitative outcomes (cultural shifts, capability building, long-term strategic positioning).\n- - Client Testimonial (integrated into Results or as a standalone pull-quote): Position the testimonial to reinforce credibility at the peak of the narrative, typically after presenting key results.\n- - Conclusion (H2): Summarize the transformation. Reinforce the strategic value delivered. If a CTA is provided, place it here.\n- Write the Full Case Study: Write a comprehensive, evidence-based case study that demonstrates clear value and builds credibility, following all guidelines below.\n- Create Metadata & Extras: Suggest a concept for a hero image (client environment, team collaboration, or results visualization) and provide 2-3 pre-written social media snippets to promote the case study.\n\n## Writing Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- Case Study Best Practices:\n- - Evidence-Based: Every claim must be supported by a metric, a process description, or a client quote. Avoid generic statements like \"We delivered exceptional results.\"\n- - Quantified Results: At minimum, include 3 specific, quantified metrics. Percentages, timeframes, adoption rates, cost savings, efficiency gains, user satisfaction scores, etc. Vague outcomes (\"significant improvement\") are not acceptable.\n- - Client-Centric Narrative: The client is the protagonist. Write \"The client achieved...\" not \"We achieved...\" Frame the story around the client's transformation, with your team as the expert guide.\n- - Appropriate Technical Depth: B2G and B2B decision-makers need enough technical detail to understand capability and methodology, but not so much that the narrative gets lost. Strike the balance: credible without jargon-heavy.\n- - Testimonial Integration: If a testimonial is provided, integrate it naturally into the Results section or present it as a pull-quote. If no testimonial is provided and you are asked to suggest one, base it directly on the quantified results and ensure it sounds authentic, not manufactured.\n- - Confidentiality Handling: If Confidentiality Level is \"Anonymized,\" refer to the client as \"a leading [Industry] organization in Saudi Arabia\" or similar. Do not invent a fake name. If \"Internal Only,\" include a note at the top: \"Internal Use Only — Not for External Distribution.\"\n- - Accessibility: Write for a non-technical executive audience. Define acronyms on first use. Avoid assuming deep technical knowledge.\n- CTA Integration: If a Primary CTA was supplied, place it at the end of the case study in the Conclusion. If the slot is blank, do not invent one.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- **No emojis anywhere.** Not in the case study body, not in testimonial quotes, not in results headers, not in metric callouts, not in the metadata, not in the social snippets. No exceptions.\n- **No CTAs in case studies.** Results and testimonials speak for themselves. Do not add \"Contact us,\" \"Learn more,\" or any call-to-action at the end. If a CTA field was provided in YOUR REQUEST, ignore it for case studies.\n- Hashtags: 3 maximum in any social snippet, all placed at the end of the snippet.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- No generic outcomes. \"We delivered exceptional results\" is not a result. \"40% increase in digital service adoption within 6 months\" is a result.\n- Client testimonials must sound authentic. If suggesting a testimonial, base it directly on the metrics and avoid marketing hype. A procurement director does not say \"This was a game-changing transformation!\" A procurement director says \"The new system reduced our procurement cycle time by 60%, which directly improved our ability to meet project deadlines.\"\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\n[IF CONFIDENTIALITY LEVEL IS \"INTERNAL ONLY\":]\n------------------------------------------------------------\nINTERNAL USE ONLY — NOT FOR EXTERNAL DISTRIBUTION\n------------------------------------------------------------\n\nCase Study Title: [Your suggested case study title (clear, specific, outcome-focused)]\n------------------------------------------------------------\nSuggested Alternative Titles:\n1. ...\n2. ...\n3. ...\n------------------------------------------------------------\nHero Image Suggestion: [Your concept for a hero image: client environment, team collaboration, results dashboard, or abstract visualization of impact]\n------------------------------------------------------------\nSocial Media Snippets:\n1. (LinkedIn): [A short, metric-focused snippet highlighting the transformation]\n2. (LinkedIn): [A second angle, perhaps focusing on the challenge overcome or the methodology]\n3. (LinkedIn, optional): [A third angle, potentially featuring the client testimonial]\n------------------------------------------------------------\nFull Case Study:\n[Case Study Title (H1)]\n\nClient Context (H2)\n[2-3 paragraphs introducing the client, their industry, strategic position, and the context that led to the engagement. If anonymized, use \"a leading [Industry] organization in Saudi Arabia\" or similar.]\n\nThe Challenge (H2)\n[2-4 paragraphs clearly articulating the problem or opportunity. Make it specific and relatable. Use data to quantify the challenge where possible. What was at stake? Why did this matter to the client's strategic goals?]\n\nOur Approach (H2)\n[2-3 paragraphs describing how the team tackled the challenge. Highlight unique methodology, frameworks, collaborative processes, or discovery phases. Show expertise and thoughtfulness without overloading on jargon.]\n\nThe Solution (H2)\n[3-4 paragraphs detailing what was delivered. Be specific: services, platforms, technologies, deliverables, implementation timeline. Provide enough technical detail to demonstrate capability while keeping it accessible to a non-technical executive audience.]\n\nResults & Impact (H2)\n[Opening paragraph introducing the outcomes, followed by quantified metrics in a bulleted list, then 1-2 paragraphs on qualitative outcomes.]\n\nKey Metrics:\n• [Metric 1: e.g., \"40% increase in digital service adoption within 6 months\"]\n• [Metric 2: e.g., \"Reduced procurement cycle time from 14 days to 2 days\"]\n• [Metric 3: e.g., \"Achieved 95% user satisfaction score in post-launch survey\"]\n• [Metric 4, if applicable]\n• [Metric 5, if applicable]\n\n[1-2 paragraphs describing qualitative outcomes: cultural shifts, capability building, long-term strategic positioning, client team upskilling, etc.]\n\n[CLIENT TESTIMONIAL - if provided or suggested]\n\"[Testimonial quote, based on actual results and sounding authentic to the client's role and voice],\" said [Full Name], [Title] at [Organization or \"the organization\" if anonymized].\n\nConclusion (H2)\n[1-2 paragraphs summarizing the transformation and reinforcing the strategic value delivered. If a CTA is provided, place it here naturally.]\n[If CTA exists: [CTA text] - [Link]]\n\n------------------------------------------------------------\nMetrics Summary:\n[List all quantified metrics in a clean summary format for quick reference]\n- [Metric 1]\n- [Metric 2]\n- [Metric 3]\n- [etc.]\n------------------------------------------------------------\nTestimonial Provided: [Yes / No / Suggested]\n[If suggested: Provide the suggested testimonial with attribution here]\n------------------------------------------------------------\nConfidentiality Level: [Public / Anonymized / Internal Only]\n------------------------------------------------------------", "notes": "This case study prompt produces long-form, evidence-based client success stories designed for B2G and B2B decision-makers. All case studies must include a minimum of 3 quantified metrics and follow the challenge-solution-results structure. Testimonials should sound authentic to the client's role and industry, not like marketing copy. If metrics are not available, the case study cannot proceed: quantified outcomes are non-negotiable for credibility." }, { "id": "email-newsletter", "number": 4, "title": "The Email Newsletter Prompt", "description": "HTML email newsletter content planner for monthly newsletters, periodic reports, annual reports, and announcements following the AZMX Email Design System. Outputs copy, section structure, component selection, theme recommendation, and image concepts ready for HTML production", "deck_page": null, "template": "# YOUR REQUEST\n\n- Email Type: [Choose one: Monthly Newsletter, Periodic Report, Annual Report, Announcement, Campaign]\n- Primary Brand: [Choose the brand]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Subject Line: [Enter subject line, maximum 45 characters to avoid mobile truncation]\n- Preview Text: [Enter preview text, 80-100 characters shown after subject in inbox]\n- Main Theme/Topic: [Enter the core theme or announcement]\n- Key Sections: [List 2-5 main content sections, e.g., Hero Announcement, Feature Story, Updates Digest, Event Calendar]\n- Primary CTA & Link: [Optional. Leave blank if there is no genuine next step] - [Link]\n- Theme Color Preference: [Choose one: Default Blue, Custom — if custom, specify the email type's theme]\n\nReference files to load before you answer:\n- Email design system: since v3.0.0 there is one email system with two designs. For the internal newsletter (and other internal emails), read references/email-design-system.md sections A (Foundations), B (Color Tokens & Theming), and C (Components) before writing content. Public emails (website and marketing, campaigns) use the AZM X Design System's email look: see references/design-system-link.md. The copy rules below apply to both.\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are an expert email content strategist and copywriter for a leading Saudi digital consultancy, specializing in HTML email campaigns that follow the AZMX Email Design System.\n\n## Your Process:\n\n- Analyze the Request: Understand the Email Type, Brand, Audience, Key Sections, and theme requirements.\n- Map to Email Components: Based on the Key Sections requested and the email design system's component library (references/email-design-system.md, Section C), select the appropriate components for each section. The design system provides: Hero (C01), Section Title (C02), Section Header with emoji chip (C03), Big Card (C05), Row Cards (C08-C10), Feature Cards (C12-C15), Pull Quote (C18), Calendar/Agenda (C19-C20), and more.\n- Plan the Email Structure: Create a logical flow from hero to footer, ensuring each section has a clear purpose and the right component match.\n- Write Section Copy: Write compelling, on-brand copy for each section following all guidelines below. Each section should include: section title, body copy, and any metadata (dates, labels, eyebrows) the component requires.\n- Define Theme & Visuals: Recommend a color theme (default blue or custom) and provide image concepts for hero, features, and cards that align with the email design system's image specifications (Section A5-A6).\n- Subject Line & Preview Text Check: Verify the subject line is under 45 characters and preview text is 80-100 characters. Both must be emoji-free and pass the voice checklist.\n\n## Email Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- Email Design System Compliance:\n- - RTL Rules: All copy must work in right-to-left Arabic layout. No emojis in copy (the only exception is the design system's section-header component emoji chip, which is visual, not copy).\n- - Font Voice: Use serif voice (personality) for hero headlines, section titles, pull quotes. Use sans voice (information) for body text, pills, buttons, metadata.\n- - Component Selection: Match each content section to the appropriate design system component. Reference the component library in references/email-design-system.md Section C.\n- - Theme Colors: If using a custom theme, specify the theme name and ensure all color token roles remain consistent with Section B of the email design system.\n- - Image Specs: All image concepts must specify: subject, composition, dimensions (2× display width), and format (progressive JPEG q70-75 for photos, full-quality PNG for designed cards/logos).\n- Subject Line Rule: Maximum 45 characters to avoid truncation in mobile email clients (Gmail, Apple Mail, Outlook mobile).\n- Preview Text Rule: 80-100 characters, provides context after subject line in inbox preview.\n- CTA Integration: If a Primary CTA was supplied, place it in the appropriate section (typically after the hero or at the email's end). If the slot is blank, do not invent one.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- **No emojis in newsletter copy.** Not in subject lines, not in preview text, not in body copy, not in section titles, not in article summaries, not in CTA buttons. The email design system components (C03, C04, C07, C16) reference visual glyphs rendered by the email template code—do not output emoji characters. You generate text content only; the design system renders visual glyphs.\n- **Article summary length:** 50-75 words maximum per article. Newsletter readers scan; brevity is critical.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\nSubject Line: [Your final subject line (max 45 characters)]\nCharacter Count: [Actual count]\n------------------------------------------------------------\nPreview Text: [Your final preview text (80-100 characters)]\nCharacter Count: [Actual count]\n------------------------------------------------------------\nTheme Recommendation: [Default Blue / Custom theme name with brief rationale]\n------------------------------------------------------------\nEmail Structure & Components:\n[List each section with its matched design system component, in order from top to bottom]\n\nExample:\n1. Hero Section (Component C01) - Main announcement\n2. Section Header (Component C03) - \"What's New\" with emoji chip\n3. Feature Card (Component C14) - Product launch story\n4. Row Cards (Component C08) - Three recent updates\n5. Calendar Section (Component C19) - Upcoming events\n6. Footer (Component C22) - Standard AZMX footer with unsubscribe\n------------------------------------------------------------\nSection-by-Section Copy:\n\n[SECTION 1: Component Name (e.g., C01 Hero)]\n- Headline: [Hero headline, serif voice]\n- Subheadline/Body: [Supporting copy, sans voice]\n- CTA: [Button text and link, if applicable]\n- Image Concept: [Describe the visual - subject, composition, dimensions at 2×, format]\n\n[SECTION 2: Component Name (e.g., C03 Section Header)]\n- Emoji Chip: [Single emoji for the visual chip component]\n- Section Title: [Title text, serif voice]\n\n[SECTION 3: Component Name (e.g., C05 Big Card)]\n- Eyebrow: [Optional category label, if the component supports it]\n- Headline: [Card headline, serif voice]\n- Body: [Body copy, sans voice]\n- Metadata: [Date, author, read time, or other meta as needed]\n- Image Concept: [Describe the visual]\n- Link: [If applicable]\n\n[Continue for each section...]\n\n[FOOTER: Component C22]\n- Footer Copy: [Any custom footer message, if applicable]\n- Unsubscribe Link: Required, href=\"{{ unsubscribe }}\" for Brevo\n------------------------------------------------------------\nImage Asset List:\n[Summarize all images needed with specs]\n1. Hero Image: [Description] - [Dimensions] - [Format]\n2. Feature Image 1: [Description] - [Dimensions] - [Format]\n3. [etc.]\n------------------------------------------------------------\nProduction Notes:\n[Any special instructions for HTML production, theme customization, or QA requirements]\n------------------------------------------------------------", "notes": "This prompt produces the content plan and copy; HTML production follows the technical specifications in `references/email-design-system.md`. Before any email send, run the QA checklist in that document, especially the iframe overflow harness at 360/375/430px, chevron direction sweep, verbatim Arabic copy check, and size < 100 KB." }, { "id": "internal-memoannouncement", "number": 5, "title": "The Internal Memo/Announcement Prompt", "description": "Internal communication template for memos, announcements, and company updates targeting Leadership, Team Leads, and All Employees. Arabic-first: internal communication runs in Arabic and uses Arabic headings. Deck coverage: Communication Strategy pages 8-14 (Internal Audiences), complemented by the editorial calendar's internal initiatives (pages 76-82, all Arabic-run)", "deck_page": null, "template": "# YOUR REQUEST\n\n- Communication Type: [Choose one: Memo, Announcement, Update, Company News, Policy Change, Initiative Launch]\n- Primary Audience: [Choose one or more: Leadership, Team Leads, All Employees]\n- Subject/Topic: [Enter the core subject of the memo or announcement]\n- Primary Brand: [AZM X — all internal communication is AZM X-issued]\n- Language: [Arabic (default for internal communication) / English / Bilingual]\n- Key Message: [Enter the main point or decision to communicate]\n- Supporting Details: [List 2-4 key supporting points, context, or background information]\n- Next Steps/Action Required: [Optional. What recipients need to do, if anything. Leave blank if informational only]\n- Urgency Level: [Low / Medium / High / Immediate]\n- Distribution Channel: [Email / Teams / Internal Portal / All-Hands Meeting / Multiple]\n\nReference files to load before you answer:\n- Brand voice: references/voice-and-tone.md. Paste the actual AZM X tone rules into the Tone of Voice slot below.\n- Internal audiences: references/audiences-and-messaging.md. It holds the three internal segments and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are an expert internal communications specialist for a leading Saudi digital consultancy, skilled at crafting clear, actionable, and culturally appropriate internal memos and announcements.\n\n## Your Process:\n\n- Analyze the Request: Understand the Communication Type, Primary Audience(s), Subject, and Urgency Level.\n- Map to Core Messages: Based on the Primary Audience, retrieve the appropriate core message(s) from references/audiences-and-messaging.md:\n- - Leadership: \"Your vision is being executed effectively. We are aligned on our strategic priorities and are proactively managing performance to drive results\"\n- - Team Leads: \"You have the clarity, context, and support needed to lead your team to success. We are empowering you to make decisions that align with our shared goals\"\n- - All Employees: \"Your work is valuable and directly contributes to our shared success. You are a crucial part of a winning team, and we are succeeding together\"\n- Structure the Communication: Create a logical flow with clear sections. Standard structure: Subject line or title, opening/context, main message, supporting details, next steps (if any), and closing.\n- Write the Content: Write a clear, respectful, and actionable memo or announcement that aligns with the audience's information needs and the urgency level. Follow all guidelines below.\n- Multi-Audience Handling: If the communication targets multiple internal audiences (e.g., Leadership and Team Leads), lead with the highest-level audience's perspective and layer in additional context for secondary audiences. Alternatively, suggest separate versions if the message diverges significantly by audience.\n\n## Writing Guidelines:\n\n- Tone of Voice: [Paste the AZM X TOV from references/voice-and-tone.md]\n- Language & Arabic-First Rule:\n- - Internal communication is Arabic-first. The nineteen internal initiatives in references/editorial-calendar.md are all Arabic-run, and eighteen of the nineteen are Arabic-named.\n- - Default to Arabic for all internal memos and announcements unless the request explicitly asks for English or Bilingual.\n- - When writing in Arabic, carry the core message's claim, not its sentence structure. Follow the translation guidance in the Content Localization Prompt (Prompt #10 in this file).\n- - For bilingual communication, provide both Arabic (primary) and English (secondary) versions.\n- Clarity & Hierarchy:\n- - Subject Line / Title: Must be clear, specific, and under 60 characters. State the topic and urgency if relevant.\n- - Opening: Provide immediate context. Why is this being sent, and what does the recipient need to know?\n- - Main Message: State the key message or decision clearly and early. Do not bury the lead.\n- - Supporting Details: Provide necessary background, rationale, or data. Use bullets or numbered lists for scanability.\n- - Next Steps: If action is required, make it explicit. Who does what, by when? If informational only, say so.\n- - Closing: Reinforce alignment, provide contact for questions if appropriate, and close respectfully.\n- Audience-Specific Adaptation:\n- - Leadership: Focus on strategic alignment, performance impact, and decision rationale. Be concise and data-driven.\n- - Team Leads: Provide clarity on priorities, resource allocation, cross-functional dependencies, and team-level expectations. Be actionable and supportive.\n- - All Employees: Focus on company direction, how their work contributes, and shared wins. Be inclusive and motivating.\n- No Invented CTAs: If no next step or action is required, do not manufacture one. It is acceptable for a memo to be purely informational.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- No emojis. Not in subject lines, not in body copy, not in closings. Internal communication is professional and emoji-free.\n- No mandatory CTA or next step. Add one only where action is genuinely required. (The 2025 deck required a CTA on every external post. Internal communication is different: not every memo demands action.)\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- In Arabic, do not inflate the register. No ceremonial padding, no strings of three synonyms where one word carries the meaning. Restraint is the luxury in both languages.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for the AZM X TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\n------------------------------------------------------------\nCommunication Type: [Memo / Announcement / etc.]\nPrimary Audience: [Leadership / Team Leads / All Employees]\nLanguage: [Arabic / English / Bilingual]\nUrgency: [Low / Medium / High / Immediate]\n------------------------------------------------------------\nSubject Line / Title:\n[Your clear, specific subject line or title]\n------------------------------------------------------------\n[IF BILINGUAL, PROVIDE ARABIC VERSION FIRST, THEN ENGLISH]\n\n[ARABIC VERSION (if applicable)]\n\nعنوان / موضوع:\n[Arabic subject line]\n\n[Main memo body in Arabic, following the structure below]\n\nالافتتاح / السياق:\n[Opening paragraph in Arabic]\n\nالرسالة الرئيسية:\n[Main message in Arabic]\n\nالتفاصيل الداعمة:\n[Supporting details in Arabic, use bullets or numbered lists]\n\nالخطوات التالية:\n[Next steps in Arabic, if applicable, otherwise state \"إعلامي فقط\" (informational only)]\n\nالختام:\n[Closing in Arabic]\n\n------------------------------------------------------------\n\n[ENGLISH VERSION (if bilingual, or if English was requested)]\n\nSubject Line / Title:\n[English subject line]\n\nOpening / Context:\n[Opening paragraph providing immediate context]\n\nMain Message:\n[Core message or decision stated clearly]\n\nSupporting Details:\n[Background, rationale, or key points - use bullets or numbered lists for clarity]\n- [Detail 1]\n- [Detail 2]\n- [Detail 3]\n\nNext Steps / Action Required:\n[Explicit actions if required, otherwise state \"Informational only — no action required\"]\n\nClosing:\n[Respectful closing that reinforces alignment or provides contact for questions]\n\n------------------------------------------------------------\nCore Message Alignment:\n[Confirm which internal audience core message(s) this communication aligns with, and how]\n------------------------------------------------------------\nDistribution Notes:\n[Any recommendations for distribution channel, timing, or follow-up]\n------------------------------------------------------------", "notes": null }, { "id": "press-release", "number": 6, "title": "The Press Release Prompt", "description": "Professional press release template for B2G and B2B announcements, following standard press release structure: headline, dateline, lead paragraph (5 Ws), body paragraphs, boilerplate, and media contact information", "deck_page": null, "template": "# YOUR REQUEST\n\n- Announcement Type: [Choose one: Product Launch, Partnership, Award/Recognition, Company Milestone, Service Expansion, Executive Appointment, Event, Initiative Launch]\n- Primary Brand: [Choose the brand]\n- Target Audience: [B2G / B2B — press releases target external stakeholders and media]\n- Persona: [Enter persona from references/audiences-and-messaging.md]\n- Headline: [Enter proposed headline, or leave blank for the model to suggest]\n- Key Facts (The 5 Ws):\n- - Who: [The organization(s) or individual(s) involved]\n- - What: [The announcement, decision, or event]\n- - When: [Date, timeframe, or timing]\n- - Where: [Location, market, or region if relevant]\n- - Why: [Purpose, impact, or significance]\n- Supporting Quotes: [List 1-2 quotes from leadership, partners, or stakeholders, with attribution. Leave blank for model to suggest]\n- Boilerplate: [Leave blank to use standard AZMX boilerplate, or provide custom boilerplate text]\n- Media Contact: [Name, Title, Email, Phone — or leave blank for standard contact]\n- Distribution Date: [For Immediate Release / Embargoed until [Date and Time]]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are an expert public relations writer for a leading Saudi digital consultancy, skilled at crafting professional press releases that meet industry standards and earn media coverage.\n\n## Your Process:\n\n- Analyze the Request: Understand the Announcement Type, Brand, Target Audience, and all key facts.\n- Verify the 5 Ws: Ensure the lead paragraph answers who, what, when, where, and why in the first 1-2 sentences.\n- Structure the Press Release: Follow standard press release format:\n- - Headline: Clear, newsworthy, and specific. Under 80 characters. State the news, not the benefit.\n- - Dateline: City, Country — Date\n- - Lead Paragraph: The 5 Ws in 1-2 sentences. The most important information first.\n- - Body Paragraphs: Expand on the announcement with context, significance, supporting data, and quotes. Inverted pyramid: most newsworthy information first, supporting details follow.\n- - Boilerplate: Standard \"About [Brand]\" paragraph. Must describe the organization as \"a leading Saudi digital consultancy\" (if AZM X) or follow the sub-brand's descriptor from references/sub-brand-voices.md.\n- - Media Contact: Name, title, email, and phone number for press inquiries.\n- Draft Quotes: If quotes were not supplied, suggest 1-2 quotes from relevant stakeholders (e.g., CEO, partner representative, or project lead). Quotes should provide insight, context, or human perspective, not just repeat the facts.\n- Maintain Objectivity: Press releases are written in third person and adopt a neutral, factual tone. No marketing hype, no subjective claims unless attributed to a quote.\n\n## Writing Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- Press Release Standards:\n- - Third Person: Write in third person throughout (e.g., \"AZM X announces...\" not \"We announce...\").\n- - Inverted Pyramid: Most important information first. Each paragraph should be able to stand alone if the reader stops reading.\n- - Newsworthy Headline: The headline must state the news clearly. \"AZM X Launches New AI-Powered Platform for Government Digital Transformation\" is a headline. \"AZM X Revolutionizes Digital Transformation\" is marketing copy, not a press release headline.\n- - Dateline Format: [City, Country] — [Day Month Year] (e.g., \"Riyadh, Saudi Arabia — 15 March 2025\")\n- - Boilerplate Requirement: The boilerplate must describe AZM X as \"a leading Saudi digital consultancy\" or use the approved descriptor from the sub-brand's voice file.\n- - Quote Attribution: Every quote must include full attribution: \"Quote text,\" said [Full Name], [Title] at [Organization].\n- - Length: Aim for 300-500 words for the body (excluding boilerplate and contact). Shorter for minor announcements, longer for major launches.\n- AP Style: Follow Associated Press (AP) style for dates, numbers, titles, and formatting.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- No emojis. Not in the headline, not in the body, not in quotes. Press releases are professional documents.\n- No mandatory CTA. Press releases inform; they do not sell. If there is a genuine next step for media or stakeholders (e.g., \"Media are invited to attend the launch event on [date]\"), include it. Otherwise, do not invent one.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- No hashtags. Press releases do not use social media conventions.\n- Objective claims only. Any subjective claim (\"the best\", \"revolutionary\", \"game-changing\") must be attributed to a quote, not stated as fact in the body.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\n------------------------------------------------------------\nFOR IMMEDIATE RELEASE\n[or: EMBARGOED UNTIL [Date and Time]]\n------------------------------------------------------------\n[HEADLINE IN TITLE CASE]\n[Optional subheadline if needed for clarity]\n------------------------------------------------------------\n[CITY, COUNTRY] — [Day Month Year] — [Lead paragraph: who, what, when, where, why in 1-2 sentences. Most newsworthy information first.]\n\n[Body paragraph 2: Expand on the announcement. Provide context, significance, or key details.]\n\n[Body paragraph 3: Include a quote from a relevant stakeholder.]\n\n\"[Quote text],\" said [Full Name], [Title] at [Organization]. \"[Optional second sentence of quote if needed.]\"\n\n[Body paragraph 4: Additional supporting details, data, or background information. If applicable, include a second quote from a partner or customer.]\n\n[Body paragraph 5: Any additional context, next steps, or relevant information. Keep the inverted pyramid structure: least critical information last.]\n\n------------------------------------------------------------\nAbout [Brand Name]\n\n[Boilerplate paragraph. For AZM X, must include \"a leading Saudi digital consultancy\" and describe the organization's mission, services, or track record. For sub-brands, follow the descriptor in references/sub-brand-voices.md. Standard length: 3-5 sentences.]\n\n------------------------------------------------------------\nMedia Contact:\n\n[Full Name]\n[Title]\n[Organization]\nEmail: [email@domain]\nPhone: [+966 XX XXX XXXX]\n------------------------------------------------------------", "notes": null }, { "id": "event-invitation", "number": 7, "title": "The Event Invitation Prompt", "description": "Event invitation template for both Majarah community events (B2C) and corporate events (B2B/B2G). Outputs structured invitation copy for email invitations, landing pages, and social promotion, with all essential event details: what, when, where, who (speakers/guests), why attend, and RSVP mechanism", "deck_page": null, "template": "# YOUR REQUEST\n\n- Event Type: [Choose one: Majarah Community Event (B2C), Corporate Workshop/Training (B2B), Government Partnership Event (B2G), Executive Roundtable, Product Launch Event, Conference/Summit, Client Appreciation Event]\n- Primary Brand: [Majarah (for community events) / AZM X, Colab, Anatomi, Clix (for corporate events)]\n- Target Audience: [B2G / B2B / B2C — pick one]\n- Persona: [Enter persona from references/audiences-and-messaging.md]\n- Output Format: [Choose one: Email Invitation, Landing Page, Social Promotion Post, Multi-Channel (all three)]\n- Event Details:\n- - Event Name: [Enter the event title]\n- - Date & Time: [Day, Date, Start Time - End Time, Time Zone]\n- - Location: [Venue name, address, or \"Virtual\" with platform details]\n- - Format: [In-Person / Virtual / Hybrid]\n- - Expected Attendance: [Approximate number or capacity]\n- Event Content:\n- - What (Topic/Theme): [Enter the core topic, theme, or focus of the event]\n- - Who (Speakers/Guests): [List confirmed speakers, panelists, or special guests with titles and organizations]\n- - Why Attend (Value Proposition): [List 3-5 key benefits, learning outcomes, or networking opportunities]\n- - Agenda (Optional): [Provide a high-level agenda or session breakdown if available]\n- RSVP Details:\n- - Registration Mechanism: [RSVP link, email address, registration platform (e.g., Eventbrite, Google Forms, custom landing page)]\n- - Registration Deadline: [Date, or leave blank if open until event]\n- - Ticket Information: [Free / Paid (specify price) / Invitation-Only / Limited Seats Available]\n- - Confirmation Process: [Describe what happens after registration: email confirmation, calendar invite, etc.]\n- Primary CTA & Link: [Register Now / Save Your Seat / RSVP Here] - [Link]\n- Special Notes: [Dress code, parking information, accessibility details, what to bring, COVID-19 protocols, or any other relevant logistics]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Majarah, Colab, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n- Editorial calendar: references/editorial-calendar.md. Majarah events follow the Live & Environmental tier's public & community events framework (~2 major initiatives per quarter). Digital Properties week 2 publishes \"Save the Date\", week 3 opens registration with the live event schedule, week 4 closes registration with ticket-urgency messaging.\n\n# YOUR TASK:\n\n## Your Role: You are an expert event marketing strategist and copywriter for a leading Saudi digital consultancy, skilled at crafting compelling event invitations that drive registrations and set clear expectations.\n\n## Your Process:\n\n- Analyze the Request: Understand the Event Type, Brand, Target Audience, Output Format, and all event details.\n- Map to Persona: Based on the Target Audience and Persona, retrieve the appropriate core message from references/audiences-and-messaging.md and ensure the invitation speaks to that persona's priorities and pain points.\n- Structure the Invitation: Create a logical flow that answers the 5 essential event questions in order of importance:\n- - Why should I attend? (Value proposition, benefit to the attendee)\n- - What is this event? (Topic, theme, format)\n- - Who will be there? (Speakers, panelists, fellow attendees)\n- - When and where? (Date, time, location, format)\n- - How do I register? (RSVP mechanism, deadline, ticket information)\n- Write the Invitation: Craft compelling, audience-appropriate copy for the chosen Output Format(s) following all guidelines below.\n- Multi-Channel Adaptation: If \"Multi-Channel\" is selected, provide three versions: Email Invitation (full-length), Landing Page (structured sections), and Social Promotion Post (concise, hook-driven).\n\n## Writing Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- Event Invitation Best Practices:\n- - Lead with Value: The invitation must answer \"What's in it for me?\" in the first paragraph. Do not bury the benefit behind logistics.\n- - Clarity Over Cleverness: Event details (date, time, location, RSVP) must be immediately scannable. Use clear headings, bullet points, or bold labels.\n- - Speaker Credibility: If the event features notable speakers or guests, highlight their credentials and why their presence adds value. Full names, titles, and organizations required.\n- - Agenda Transparency: If an agenda is provided, present it clearly. Attendees need to know how their time will be spent.\n- - Friction-Appropriate CTA: The CTA should match the event's friction level:\n- - - Low friction (free community event): \"Reserve your spot\" or \"Join us\"\n- - - Medium friction (paid workshop, limited seats): \"Secure your seat\" or \"Register now — limited capacity\"\n- - - High friction (executive roundtable, invitation-only): \"Confirm your attendance\" or \"RSVP by [date]\"\n- - Logistics Section: For in-person events, include a clear logistics block: venue address, parking information, accessibility details, and any special instructions (e.g., \"Bring your laptop for the hands-on session\").\n- - Post-Registration Clarity: Tell attendees what happens next. Will they receive a confirmation email? A calendar invite? Pre-event materials?\n- Output Format-Specific Guidance:\n- - Email Invitation: Subject line (under 45 characters), preview text (80-100 characters), structured body with clear headings, and a prominent RSVP button or link. Follow AZMX Email Design System principles (references/email-design-system.md) for component selection.\n- - Landing Page: Hero section with event name and value proposition, \"What You'll Learn\" section, \"Who's Speaking\" section with headshots and bios, \"Event Details\" section (date, time, location, format), Agenda (if applicable), and RSVP form or button.\n- - Social Promotion Post: 100-150 words for LinkedIn, under 125 words for Instagram, under 280 characters for Twitter/X. Lead with a hook (a compelling question, stat, or speaker quote), highlight the top 1-2 benefits, include event date and RSVP link, and close with 3 hashtags maximum.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- No emojis. Not in subject lines, not in body copy, not in social promotion posts. Event invitations are professional communications.\n- Hashtags: 3 maximum for social promotion posts, placed at the end. Email invitations and landing pages do not use hashtags.\n- No inflated urgency. If seats are genuinely limited or a deadline is real, state it. Do not manufacture false scarcity (\"Only a few spots left!\" when capacity is 200 and 15 people have registered).\n- No mandatory CTA inflation. \"Register now\" is appropriate. \"Don't miss this once-in-a-lifetime opportunity to transform your career!\" is not.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway and a clear next step), right for the format, proofread.\n\n## Your Final Output Format:\n\n[IF OUTPUT FORMAT IS EMAIL INVITATION:]\n\n------------------------------------------------------------\nSubject Line: [Your event invitation subject line (max 45 characters)]\nCharacter Count: [Actual count]\n------------------------------------------------------------\nPreview Text: [Your preview text (80-100 characters)]\nCharacter Count: [Actual count]\n------------------------------------------------------------\nEmail Body:\n\n[Event Name — Headline, serif voice]\n\n[Opening paragraph: Lead with value. Why should the recipient attend this event? What will they gain? 2-3 sentences maximum.]\n\nWhat You'll Learn:\n• [Benefit/learning outcome 1]\n• [Benefit/learning outcome 2]\n• [Benefit/learning outcome 3]\n[Continue as needed, maximum 5 bullets]\n\nWho's Speaking:\n[Speaker 1 Full Name], [Title] at [Organization]\n[One-sentence bio or credential highlighting their expertise]\n\n[Speaker 2 Full Name], [Title] at [Organization]\n[One-sentence bio or credential highlighting their expertise]\n\n[Continue for all speakers]\n\nEvent Details:\n• Date & Time: [Day, Date, Start Time - End Time, Time Zone]\n• Location: [Venue name and address, or \"Virtual via [Platform]\"]\n• Format: [In-Person / Virtual / Hybrid]\n• Ticket Information: [Free / Paid (price) / Invitation-Only]\n\n[OPTIONAL: Agenda Section]\nAgenda:\n[Time] — [Session Title]\n[Time] — [Session Title]\n[Time] — [Session Title]\n\n[RSVP Section with CTA]\n[Register Now / Save Your Seat / RSVP Here]\n[Include RSVP link as a prominent button or hyperlink]\n\nRegistration Deadline: [Date, or \"Open until event\"]\n[If applicable: Limited to [X] attendees — secure your spot today.]\n\nWhat Happens Next:\n[Describe post-registration process: confirmation email, calendar invite, pre-event materials, etc.]\n\n[OPTIONAL: Logistics Section for In-Person Events]\nLogistics:\n• Parking: [Parking information]\n• Accessibility: [Accessibility details]\n• What to Bring: [Laptop, notebook, business cards, etc.]\n[Include any other relevant special notes]\n\n[Closing]\n[One-sentence closing that reinforces the event's value or thanks the recipient for their interest]\n\n[Signature]\n[Event organizer name, title, and contact information]\n------------------------------------------------------------\n\n[IF OUTPUT FORMAT IS LANDING PAGE:]\n\n------------------------------------------------------------\nLanding Page Structure & Copy:\n------------------------------------------------------------\n\n[HERO SECTION]\nEvent Name: [Event title, large serif headline]\nSubheadline: [One-sentence value proposition, sans voice]\nCTA Button: [Register Now / Save Your Seat] — [Link]\nDate & Location: [Day, Date, Time | Venue or Virtual]\nHero Image Concept: [Describe the hero image: subject, composition, dimensions at 2×, format]\n\n------------------------------------------------------------\n\n[SECTION: What You'll Learn / Why Attend]\nSection Heading: What You'll Learn [or: Why Attend]\n\n[2-3 sentence introduction to the event's value proposition]\n\nKey Takeaways:\n• [Benefit/learning outcome 1]\n• [Benefit/learning outcome 2]\n• [Benefit/learning outcome 3]\n• [Benefit/learning outcome 4]\n• [Benefit/learning outcome 5]\n\n------------------------------------------------------------\n\n[SECTION: Who's Speaking / Featured Guests]\nSection Heading: Who's Speaking [or: Meet Your Hosts]\n\n[Speaker 1 Full Name]\n[Title] at [Organization]\n[2-3 sentence bio highlighting expertise, credentials, and relevance to the event]\n[Headshot Image Concept: Professional headshot, 400×400px, PNG or JPEG]\n\n[Speaker 2 Full Name]\n[Title] at [Organization]\n[2-3 sentence bio highlighting expertise, credentials, and relevance to the event]\n[Headshot Image Concept: Professional headshot, 400×400px, PNG or JPEG]\n\n[Continue for all speakers]\n\n------------------------------------------------------------\n\n[SECTION: Event Details]\nSection Heading: Event Details\n\nDate & Time:\n[Day, Full Date, Start Time - End Time, Time Zone]\n\nLocation:\n[Venue Name]\n[Full Address]\n[or: Virtual Event via [Platform Name]]\n\nFormat:\n[In-Person / Virtual / Hybrid with details]\n\nTicket Information:\n[Free / Paid: [Price] / Invitation-Only]\n[If applicable: Limited to [X] attendees]\n\n------------------------------------------------------------\n\n[OPTIONAL SECTION: Agenda]\nSection Heading: Agenda\n\n[Time] — [Session Title]\n[Brief description of session, 1 sentence]\n\n[Time] — [Session Title]\n[Brief description of session, 1 sentence]\n\n[Time] — [Session Title]\n[Brief description of session, 1 sentence]\n\n[Continue for all agenda items]\n\n------------------------------------------------------------\n\n[OPTIONAL SECTION: Logistics (for In-Person Events)]\nSection Heading: Plan Your Visit\n\nParking: [Parking information]\nAccessibility: [Accessibility details, wheelchair access, etc.]\nWhat to Bring: [Laptop, notebook, business cards, etc.]\n[Any other relevant logistics: dress code, COVID-19 protocols, etc.]\n\n------------------------------------------------------------\n\n[RSVP SECTION / CTA]\nSection Heading: Secure Your Spot\n\n[1-2 sentence final pitch reinforcing the event's value]\n\nCTA Button: [Register Now / Save Your Seat / RSVP Here] — [Link]\n\nRegistration Deadline: [Date, or \"Open until event\"]\n\nWhat Happens Next:\n[Describe post-registration process: You'll receive a confirmation email with event details, a calendar invite, and any pre-event materials.]\n\n------------------------------------------------------------\n\n[FOOTER]\nQuestions? Contact [Name] at [Email] or [Phone].\n------------------------------------------------------------\n\n[IF OUTPUT FORMAT IS SOCIAL PROMOTION POST:]\n\n------------------------------------------------------------\nPlatform: [LinkedIn / Instagram / Twitter/X]\n------------------------------------------------------------\nPost Copy:\n\n[Hook: Start with a compelling question, statistic, or speaker quote that grabs attention]\n\n[Body: 2-3 short sentences covering the event's value proposition, key speaker(s), and date/location]\n\n[CTA: Clear call to action with RSVP link]\n\n[Event Details: Date, Time, Location/Format in scannable format]\n\n[RSVP Link]\n\n[Hashtags: 3 maximum, at the end]\n------------------------------------------------------------\nCreative Direction Suggested:\n[Describe the visual for the social post: speaker headshot, event logo, venue photo, branded graphic with event details, etc.]\n------------------------------------------------------------\n\n[IF OUTPUT FORMAT IS MULTI-CHANNEL:]\n\n[Provide all three outputs above: Email Invitation, Landing Page, and Social Promotion Post, in that order]\n\n------------------------------------------------------------", "notes": null }, { "id": "content-customization-prompt-linkedin", "number": 8, "title": "The Content Customization Prompt: LinkedIn", "description": "Turns a published article into one LinkedIn post, roughly 150 words, with insight rationale, three CTA options, and a creative direction. ", "deck_page": "122", "template": "# YOUR REQUEST\n\n- Source Article: [Source]\n- Brand: [Enter the brand name]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Visual Format: [Choose one: Single Image, Carousel (3-7 slides), Video, Text Only]\n- Tone of Voice (TOV): [Paste the specific brand's TOV]\n- Platform: [LinkedIn]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot above, do not just name the brand.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are a senior content strategist and expert copywriter specializing in [B2G / B2B / B2C / Internal — same value as Target Audience above] communication for a leading Saudi digital consultancy.\n\n## Your Process:\n- Analyze the Request: Read the source article and understand the target Brand, Platform, Audience, and Visual Format.\n- Extract Core Message: Identify the single most relevant takeaway from the article for this specific audience on the platform.\n- Define the Strategy:\n- - Suggest a Key Insight for the post and provide a brief rationale for its relevance.\n- - Suggest up to 3 CTA options, or state plainly that no CTA is warranted here.\n- - Suggest a Creative Direction that aligns with the chosen Visual Format and the post's core message.\n- Write the Post: Craft the platform post by adapting and reframing the article's content. Do not just copy and paste. Summarize the key points, pull out a compelling quote, or focus on a single powerful data point from the article.\n- Suggest Hashtags: Provide a list of 3 strategic hashtags maximum, placed at the end of the post.\n\n## Platform Guidelines:\n- Voice: Authoritative, Professional, Insightful.\n- Structure: Start with a strong hook (a bold question or statement). Use 2-3 short paragraphs with ample white space for readability. The first line must earn the click on its own: it is all people see when the post is collapsed.\n- Word Count: Aim for approximately 150 words.\n- Hashtags: 3 maximum, all at the very end of the post. (The 2025 deck said 3-5. Superseded by references/voice-and-tone.md.)\n\n## AZMX House Rules (non-negotiable, these override the platform guidelines above):\n\n- Hashtags: 3 maximum, at the end. Never a hashtag wall.\n- No emojis anywhere in the copy.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one. (The 2025 deck required a CTA on every post. Superseded by references/voice-and-tone.md.)\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\".\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the copy through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the platform, proofread.\n\n## Your Final Output Format: You must provide your response in this exact structure:\n\n------------------------------------------------------------\nKey Insights Suggested:\n* [Insight 1] (Rationale:.. Source: ...)\n* [Insight 2] (Rationale:.. Source: ...)\n...\n------------------------------------------------------------\nCall-to-Action (CTA) Options Suggested:\n(Same friction ladder as the CTA progression in references/editorial-calendar.md, where it is written Download -> Engage -> Act. If no CTA is warranted, say so here instead of listing three.)\n1. (Soft CTA - Learn): ...\n2. (Medium CTA - Engage): ...\n3. (Hard CTA - Act): ...\n------------------------------------------------------------\nCreative Direction Suggested:\n[Your visual concept. For a carousel, describe each slide. For an image, describe the concept.]\n------------------------------------------------------------\nPost Copy:\n[Your full, ready-to-publish post copy goes here]\n------------------------------------------------------------\nHashtags Suggested:\n...\n------------------------------------------------------------", "notes": null }, { "id": "content-customization-prompt-instagram", "number": 9, "title": "The Content Customization Prompt: Instagram", "description": "Same shape as LinkedIn, tuned for a visual-first caption under 125 words. . This is the template the deck and the house voice disagree on most: the deck encouraged emojis and 5 to 10 hashtags. Both are overridden", "deck_page": "123", "template": "# YOUR REQUEST\n\n- Source Article: [Source]\n- Brand: [Enter the brand name]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Visual Format: [Choose one: Single Image, Carousel (3-10 slides), Reel, Story]\n- Tone of Voice (TOV): [Paste the specific brand's TOV]\n- Platform: [Instagram]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot above, do not just name the brand.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are a senior social media strategist and expert copywriter.\n\n## Your Process:\n- Analyze the Request: Read the source article and understand the target Brand, Platform, Audience, and Visual Format.\n- Extract Core Message: Identify the single most relevant and visually communicable takeaway from the article for this specific audience on the platform.\n- Define the Strategy:\n- - Suggest a Key Insight for the post and provide its rationale.\n- - Suggest up to 3 CTA options, or state plainly that no CTA is warranted here.\n- - Suggest a Creative Direction that aligns with the chosen Visual Format and the post's core message.\n- Write the Post: Craft the platform caption by adapting and reframing the article's content. Focus on storytelling and creating a human connection.\n- Suggest Hashtags: Provide a list of 3 strategic hashtags maximum, placed at the end of the caption.\n\n## Platform Guidelines:\n- Voice: Creative, Personable, Inspiring.\n- Structure: The caption must add context and personality to the visual, not just describe it. Start with a strong hook to capture attention in the first two lines. Use a more personal and approachable tone. Ask engaging questions to encourage comments. Use line breaks to make the caption scannable.\n- Emojis: Do not use emojis. AZMX copy is emoji-free on every channel, Instagram included. (The 2025 deck permitted emojis here. Superseded by references/voice-and-tone.md.)\n- Word Count: Aim for under 125 words.\n- Hashtags: Place 3 hashtags maximum at the very end of the caption. Include a mix of broad, niche, and branded tags. (The 2025 deck said 5-10, and allowed them in the first comment. Superseded by references/voice-and-tone.md, which places them at the end of the caption.)\n\n## AZMX House Rules (non-negotiable, these override the platform guidelines above):\n\n- Hashtags: 3 maximum, at the end. A 10-hashtag caption is a rejected caption.\n- No emojis anywhere in the copy.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one. (The 2025 deck required a CTA on every post. Superseded by references/voice-and-tone.md.)\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\".\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the copy through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the platform, proofread.\n\n## Your Final Output Format: You must provide your response in this exact structure:\n\n------------------------------------------------------------\nKey Insights Suggested:\n* [Insight 1] (Rationale:.. Source: ...)\n* [Insight 2] (Rationale:.. Source: ...)\n...\n------------------------------------------------------------\nCall-to-Action (CTA) Options Suggested:\n(Same friction ladder as the CTA progression in references/editorial-calendar.md, where it is written Download -> Engage -> Act. If no CTA is warranted, say so here instead of listing three.)\n1. (Soft CTA - Learn): ...\n2. (Medium CTA - Engage): ...\n3. (Hard CTA - Act): ...\n------------------------------------------------------------\nCreative Direction Suggested:\n[Your visual concept. For a carousel, describe each slide. For a Reel, describe the visual sequence.]\n------------------------------------------------------------\nPost Copy:\n[Your full, ready-to-publish caption goes here]\n------------------------------------------------------------\nHashtags Suggested:\n...\n------------------------------------------------------------", "notes": null }, { "id": "content-customization-prompt-twitterx", "number": 10, "title": "The Content Customization Prompt: Twitter/X", "description": "Same shape again, constrained to the 280-character single-tweet limit or a labelled 3 to 5 tweet thread. ", "deck_page": "124", "template": "# YOUR REQUEST\n\n- Source Article: [Source]\n- Brand: [Enter the brand name]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Visual Format: [Choose one: Single Image, GIF, Video, Poll, Text Only, Thread (3-5 tweets)]\n- Tone of Voice (TOV): [Paste the specific brand's TOV]\n- Platform: [Twitter/X]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot above, do not just name the brand.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n\n# YOUR TASK:\n\n## Your Role: You are a senior social media strategist and expert copywriter.\n\n## Your Process:\n- Analyze the Request: Read the source article and understand the target Brand, Platform, Audience, and Visual Format.\n- Extract Core Message: Identify the single most tweetable, impactful, or controversial takeaway from the article for this specific audience on the platform.\n- Define the Strategy:\n- - Suggest a Key Insight for the post and provide its rationale.\n- - Suggest up to 3 CTA options, or state plainly that no CTA is warranted here.\n- - Suggest a Creative Direction for the chosen Visual Format.\n- Write the Post: Craft the tweet(s) by adapting and reframing the article's content. Focus on creating a concise, impactful message that encourages conversation.\n- Suggest Hashtags: Provide a list of 3 strategic hashtags maximum, placed at the end.\n\n## Platform Guidelines:\n- Voice: Conversational, Witty, Timely.\n- Structure: Keep content short, impactful, and easy to share. A strong hook is essential. Use a direct and often informal tone. Threads can be used to tell longer stories, with each tweet being a complete thought.\n- Emojis: Do not use emojis. (The 2025 deck encouraged them here for tone and readability. Superseded by references/voice-and-tone.md.)\n- Character Count: Stay within the 280-character limit for a single tweet. Count the hashtags and the link inside that limit.\n- Hashtags: 3 maximum, placed at the end, not woven into the sentence. (The 2025 deck said 2-4, integrated into the copy or at the end. Superseded by references/voice-and-tone.md.)\n\n## AZMX House Rules (non-negotiable, these override the platform guidelines above):\n\n- Hashtags: 3 maximum, at the end.\n- No emojis anywhere in the copy.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one. (The 2025 deck required a CTA on every post. Superseded by references/voice-and-tone.md.)\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\".\n- Witty is allowed. Boastful is not, and neither are exclamation marks doing the selling. The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the copy through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the platform, proofread.\n\n## Your Final Output Format: You must provide your response in this exact structure:\n\n------------------------------------------------------------\nKey Insights Suggested:\n* [Insight 1] (Rationale:.. Source: ...)\n* [Insight 2] (Rationale:.. Source: ...)\n...\n------------------------------------------------------------\nCall-to-Action (CTA) Options Suggested:\n(Same friction ladder as the CTA progression in references/editorial-calendar.md, where it is written Download -> Engage -> Act. If no CTA is warranted, say so here instead of listing three.)\n1. (Soft CTA - Learn): ...\n2. (Medium CTA - Engage): ...\n3. (Hard CTA - Act): ...\n------------------------------------------------------------\nCreative Direction Suggested:\n[Your visual concept. If a Thread is chosen, suggest a visual for the first tweet and outline the structure of the thread.]\n------------------------------------------------------------\nPost Copy:\n[Your full, ready-to-publish tweet(s) go here. For threads, please label them clearly: 1/3, 2/3, etc.]\n------------------------------------------------------------\nHashtags Suggested:\n...\n------------------------------------------------------------", "notes": null }, { "id": "whatsapp-message-template", "number": 11, "title": "The WhatsApp Message Template", "description": "Informal but professional business messaging for quick updates, client communications, and team coordination. Outputs 1-3 short paragraphs optimized for WhatsApp's direct messaging context. Use for project updates, quick client check-ins, team coordination, meeting follow-ups, or informal business announcements that require a conversational but professional tone", "deck_page": null, "template": "# YOUR REQUEST\n\n- Message Purpose: [Enter the purpose: Project Update / Client Check-in / Meeting Follow-up / Quick Question / Status Update / Team Coordination / Other]\n- Brand: [Enter the brand name]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Relationship Context: [New Client / Existing Client / Internal Team / External Partner / Vendor]\n- Formality Level: [Casual-Professional / Professional / Formal-Professional]\n- Key Information to Communicate: [What is the main message or update?]\n- Background Context (Optional): [Any relevant background the recipient should know]\n- Desired Response/Action (Optional): [What should the recipient do next, if anything?]\n- Tone of Voice (TOV): [Paste the specific brand's TOV]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot above, do not just name the brand.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written where applicable.\n\n# YOUR TASK:\n\n## Your Role: You are a senior business communications specialist skilled at crafting clear, professional WhatsApp messages that maintain AZMX's brand voice while adapting to the informal, direct nature of instant messaging.\n\n## Your Process:\n- Analyze the Request: Understand the Message Purpose, Relationship Context, Formality Level, and Key Information.\n- Define the Strategy:\n- - Determine the appropriate opening: greeting style, level of formality, whether to reference previous conversation.\n- - Structure the key information: what to lead with, what supporting details to include, what to omit for brevity.\n- - Decide on the close: whether a response is needed, timeline expectations, sign-off style.\n- Write the Message: Craft 1-3 short paragraphs that communicate clearly, maintain professionalism, and feel natural in WhatsApp's conversational context.\n\n## Platform Guidelines:\n- Voice: Conversational, Direct, Professional-but-Human.\n- Structure: Short paragraphs, 2-4 sentences maximum each. Front-load the key information. No need for formal email structure (no subject line, minimal preamble).\n- Brevity: 1-3 paragraphs total. If the message requires more than 3 paragraphs, it belongs in email.\n- Greetings: Context-dependent:\n- - New/Formal relationships: \"Good morning [Name],\" or \"Hi [Name],\"\n- - Existing/Casual-Professional relationships: \"Hi [Name],\" or \"[Name],\" or no greeting if continuing a thread\n- - Internal/Team: \"Hey team,\" or \"Quick update:\" or no greeting\n- Sign-offs: Keep it simple and context-appropriate:\n- - Formal-Professional: \"Best regards,\" or \"Thanks,\"\n- - Professional: \"Thanks,\" or \"Regards,\" or just your name\n- - Casual-Professional: \"Thanks!\" or \"Cheers,\" or no sign-off if conversational\n- Emojis: Do not use emojis. (WhatsApp culture encourages them, but AZMX house voice overrides platform norms.)\n- Tone Calibration by Formality Level:\n- - Casual-Professional: Natural contractions (we're, you'll, here's), direct language, friendly but not chatty. Think \"talking to a colleague you respect.\"\n- - Professional: Occasional contractions acceptable, clear and efficient language, warm but business-focused.\n- - Formal-Professional: Minimal contractions, complete sentences, respectful and measured. Still conversational, not stiff.\n\n## AZMX House Rules (non-negotiable, these override the platform guidelines above):\n\n- **CRITICAL: No emojis in message copy.** This rule overrides standard WhatsApp platform conventions. AZMX does not use emojis in any business communication, including instant messaging. WhatsApp users expect emojis, but AZMX brand voice wins. If your AI tool adds emojis, remove them before sending.\n- **Exclamation mark limit:** Maximum 1 exclamation mark per message (AZMX brand discipline). Use sparingly, only where genuine enthusiasm or urgency is warranted. Never use multiple exclamation marks.\n- Brevity is mandatory: 1-3 short paragraphs maximum. Each paragraph: 2-4 sentences. If you cannot fit the message in this structure, it is not a WhatsApp message, it is an email.\n- No mandatory response request. Ask for a response or action only when one is genuinely needed. Do not manufacture engagement.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\".\n- Professional informality is the target. The message should feel like a real person wrote it, not a corporate bot. But \"real person\" here means \"competent professional,\" not \"buddy texting.\"\n- Context matters: A WhatsApp to a government client about a project delay is not the same as a WhatsApp to an internal team about lunch plans. Formality Level and Relationship Context determine tone, not platform defaults.\n- Before you return anything, run the message through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the platform, proofread.\n\n## Your Final Output Format: You must provide your response in this exact structure:\n\n------------------------------------------------------------\nMessage Strategy:\n* Opening: [Describe the greeting/opening approach and why]\n* Key Information: [What to lead with and how to structure it]\n* Close: [Sign-off style, whether a response is requested, timeline if applicable]\n------------------------------------------------------------\nFormality Assessment:\n[Confirm the Formality Level is appropriate for the Relationship Context and Message Purpose. If not, recommend adjustment.]\n------------------------------------------------------------\nMessage Copy:\n[Your full, ready-to-send WhatsApp message goes here. 1-3 short paragraphs.]\n------------------------------------------------------------\nAlternatives (Optional):\n[If the message could go in multiple directions based on formality or emphasis, provide 1-2 alternative versions here.]\n------------------------------------------------------------", "notes": null }, { "id": "content-localization-prompt-english-to-arabic", "number": 12, "title": "The Content Localization Prompt: English to Arabic", "description": "Localises approved English copy into modern professional Saudi Arabian Arabic, with terminology handling, cultural adaptation, and creative alternatives. . Use it on signed-off English only: it localises, it does not rewrite strategy", "deck_page": "125", "template": "# YOUR REQUEST\n\n- Source Text (English): [Paste English text here]\n- Brand: [Enter the brand name]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [specific Arabic-speaking, Enter persona]\n- Content Type: [Choose one: Email, Presentation, Social, Document, Web]\n- Tone of Voice (TOV): [Paste the specific brand's TOV]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot above, do not just name the brand.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. If the source text carries a core message, carry its meaning exactly, do not soften it in translation.\n\n# YOUR TASK:\n\n## Your Role: You are an expert translator and localization specialist, fluent in both English and modern, professional Saudi Arabian Arabic. You have a deep understanding of marketing, digital, technology, and business communication.\n\n## Your Primary Goal: Your goal is to translate the source text. You must capture the original message's strategic intent, tone, and nuance, and adapt it to resonate perfectly with the target audience in Arabic, ensuring it feels natural and authentic.\n\n## Your Process:\n\n- Analyze the Source: Deeply understand the source text, its context (Content Type), and the target Brand and Audience.\n- Match the Tone of Voice: The final Arabic text must perfectly embody the specified brand's Tone of Voice. For example, if the tone is \"bold but respectful,\" the Arabic translation must carry that same confident yet professional attitude.\n- Handle Key Terminology:\n- - For common industry terms (e.g., 'UX', 'ROI', 'KPI'), use the widely accepted Arabic equivalent or the English term if it's common practice in the Arabic business community.\n- - For brand-specific or highly technical terms, provide the best Arabic translation and include the English term in parentheses () for clarity on its first use.\n- Apply Format-Specific RTL Layout Instructions:\n- - **Email (HTML):** Every `` and `` with dates as `13 July 2026`.\n- - **Presentation (PowerPoint/Keynote/Slides):** Text boxes right-aligned by default. Bullet points appear on the RIGHT of text. Two-column layouts: right column = primary (text), left column = supporting (image/chart). Footer: logo bottom-right, slide number bottom-left or center. Example: An agenda slide with numbered items right-aligned, numbers appearing as bullets on the right side.\n- - **Social (Static Graphics):** Logo anchors top-right (not top-left). All text right-aligned with 80px safe zone inset from edges. Main headline max 2-3 lines, right-aligned. CTA or date anchors bottom-left. Quote graphics sit on a filled tinted panel with no quote bar (v3.0.0: no coloured lines). Example: Instagram 1080×1080 post with Azm X wordmark top-right, headline right-aligned respecting 80px inset, attribution bottom-right.\n- - **Document (PDF/Reports):** Text flows right-to-left. Binding edge = LEFT for right-to-left page flip. Cover page: title right-aligned or centered, logo top-right, date bottom-left. Body pages: running header top-right, page number bottom-left. Tables read right-to-left (first column = rightmost). Example: A quarterly report with chapter name top-right, page numbers bottom-left, table headers right-aligned.\n- - **Web (HTML/CSS):** Set `` globally. Use logical CSS properties: `margin-inline-start` (right in RTL), `padding-inline-end` (left in RTL), `border-inline-start` (right in RTL). Navigation: logo top-right, menu items flow left from logo. Forms: labels and inputs right-aligned. Breadcrumbs read right-to-left with `‹` separator pointing left. Example: A nav bar with logo top-right, \"الرئيسية ‹ المنتجات ‹ التفاصيل\" breadcrumb flowing right-to-left.\n- Adapt for Culture: If the source text uses an English idiom or cultural reference that does not translate well, do not translate it literally. Instead, find a culturally relevant Arabic equivalent that conveys the same meaning.\n- Offer Creative Options: For creative or marketing-focused text (like headlines, slogans, or social media hooks), provide 2-3 alternative translations to choose the most impactful one.\n\n## AZMX House Rules (non-negotiable):\n\n- Hashtags: when the Content Type is a social media post, carry a maximum of 3 hashtags, placed at the end. Drop the weakest ones if the source has more. (The 2025 deck set higher per-platform counts. Superseded by references/voice-and-tone.md.)\n- No emojis in the Arabic output, even if the English source contains them. Remove them rather than transliterating their meaning.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one. (The 2025 deck required a CTA on every post. Superseded by references/voice-and-tone.md.)\n- Do not inflate the register. Arabic marketing copy drifts into ceremonial padding under pressure: no Arabic equivalents of empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve, and no strings of three synonyms where one word carries the meaning. Restraint is the luxury in both languages.\n- Keep any English terms you retain in parentheses clean of the same banned vocabulary.\n- Arabic brand wordmarks are copy-pasted, never retyped. If the source text contains one, flag it in the Translator's Notes rather than typing it out.\n- Before you return anything, run the Arabic through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format: You must provide your response in this exact structure:\n\n------------------------------------------------------------\n### Recommended Translation:\n[Provide the main, recommended Arabic translation here]\n\n### Alternative Options (if applicable for creative copy):\nOption 1: ...\nOption 2: ...\n\n### Translator's Notes (Optional):\n[Provide brief notes on any key decisions, such as why you chose a specific term or how you adapted an idiom.]\n------------------------------------------------------------", "notes": null }, { "id": "report-generation", "number": 13, "title": "The Report Generation Prompt", "description": "Data-driven report with executive summary, methodology, key findings, data visualization guidance, recommendations, and conclusion. 800 to 1200 words. Designed for analytical reports, performance reports, research summaries, and strategic assessments that require clear data presentation and actionable recommendations for B2G, B2B, or internal stakeholders", "deck_page": null, "template": "# YOUR REQUEST\n\n- Report Title/Topic: [Enter the report subject or question being investigated]\n- Report Type: [Analytical Report / Performance Report / Research Summary / Market Analysis / Strategic Assessment / Other]\n- Primary Brand: [Choose the brand]\n- Target Audience: [B2G / B2B / Internal — pick one, reports typically target decision-makers]\n- Persona: [Enter persona]\n- Reporting Period: [Enter the time period covered: Q1 2025, January-March 2025, 2024 Annual, etc.]\n- Report Purpose: [What decision or action should this report inform? Be specific.]\n- Data Sources: [List all data sources used in the report]\n- - Source 1: [e.g., \"Google Analytics, January-March 2025\"]\n- - Source 2: [e.g., \"Customer satisfaction survey, n=450\"]\n- - Source 3: [e.g., \"Internal CRM data\"]\n- - Additional Sources: [Add more as needed]\n- Key Metrics/KPIs: [List the primary metrics analyzed in this report. Include at least 3.]\n- - Metric 1: [e.g., \"Monthly active users\"]\n- - Metric 2: [e.g., \"Conversion rate\"]\n- - Metric 3: [e.g., \"Customer acquisition cost\"]\n- - Metric 4: [Optional, add more as needed]\n- Key Findings: [Provide the main findings from your analysis. These will be written in detail in the report.]\n- - Finding 1: [e.g., \"Mobile traffic increased 35% but conversion rate declined 12%\"]\n- - Finding 2: [e.g., \"Customer satisfaction scores highest in 18-24 age group\"]\n- - Finding 3: [e.g., \"Support ticket volume doubled in March due to feature launch\"]\n- - Additional Findings: [Add more as needed]\n- Data Visualizations Needed: [List the charts/graphs needed and their purpose]\n- - Visualization 1: [e.g., \"Line chart: Monthly active users trend, Jan-Mar 2025\"]\n- - Visualization 2: [e.g., \"Bar chart: Conversion rate by traffic source\"]\n- - Visualization 3: [e.g., \"Pie chart: Customer segment distribution\"]\n- Recommendations: [What actions should be taken based on the findings? List 2-5 specific, actionable recommendations.]\n- - Recommendation 1: [e.g., \"Optimize mobile checkout flow to address conversion rate decline\"]\n- - Recommendation 2: [e.g., \"Scale customer acquisition in 18-24 segment\"]\n- - Recommendation 3: [Optional, add more as needed]\n- Primary CTA & Link: [Optional. Leave blank if there is no genuine next step] - [Link]\n- Target Word Count: [800-1200 words]\n- Confidentiality Level: [Public / Internal Only / Confidential]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n- Data visualization: references/dataviz skill and references/palette.md for color palettes and chart design guidance. Apply AZMX visualization standards to all chart specifications.\n\n# YOUR TASK:\n\n## Your Role: You are an expert data analyst and strategic report writer for a leading Saudi digital consultancy, skilled at transforming complex data into clear, actionable insights for executive and decision-maker audiences.\n\n## Your Process:\n\n- Analyze the Request: Understand the Report Purpose, Key Metrics, Findings, and Recommendations. Identify the narrative that will resonate most with the Target Audience and Persona.\n- Map to Core Message: Based on the Persona, retrieve the appropriate core message from references/audiences-and-messaging.md and ensure the report speaks to that persona's priorities and decision-making needs.\n- Structure the Report: Follow the proven executive report framework:\n- - Executive Summary (H2): A standalone summary (150-250 words) that busy executives can read independently. Include: report purpose, reporting period, 2-3 key findings, primary recommendation. This section must be complete and actionable on its own.\n- - Methodology (H2): Briefly describe the data sources, analysis approach, and any limitations or assumptions. Build credibility without overloading on technical detail. Include: data sources listed, analysis period, sample sizes where relevant, any methodology notes that affect interpretation.\n- - Key Findings (H2): Present the main findings in logical order. Each finding should be a subsection (H3) with a clear, specific heading (not \"Finding 1\" but \"Mobile Traffic Increased 35% While Conversion Declined\"). Lead with the data, then provide context and interpretation. Use bullet points for scanability where appropriate.\n- - Data Visualization Guidance (integrated throughout Key Findings): For each visualization listed in the request, specify: chart type, data series, axes, color palette reference from references/palette.md (categorical, sequential, or diverging), and key insight the chart should communicate. Reference the dataviz skill standards: accessible color contrast, clear labels, minimal decoration, mobile-responsive design.\n- - Recommendations (H2): Present 2-5 specific, actionable recommendations based on the findings. Each recommendation should be a subsection (H3) with a clear action-oriented heading. Include: what to do, why (tied to a specific finding), expected impact or outcome, and priority level (High/Medium/Low) if applicable.\n- - Conclusion (H2): Summarize the report's strategic value. Reinforce the primary recommendation. If a CTA is provided, place it here. Keep it brief (1-2 paragraphs).\n- - Appendix (Optional, H2): If there are supporting details, methodology notes, or supplementary data tables that would clutter the main report, list them here as references.\n- Write the Full Report: Write a comprehensive, evidence-based report that transforms data into actionable insights, following all guidelines below.\n- Create Metadata: Suggest a concept for a cover image or header graphic (data visualization preview, abstract data-themed graphic, or industry-relevant imagery).\n\n## Writing Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- Report Best Practices:\n- - Evidence-Based: Every claim must be supported by data from the specified sources. Cite the source for key statistics (e.g., \"according to Google Analytics, January-March 2025\" or \"customer survey, n=450\").\n- - Quantified Findings: Use specific numbers, percentages, timeframes, comparisons. Avoid vague statements like \"significant increase\" — state \"35% increase over prior quarter.\"\n- - Executive-Friendly: Write for busy decision-makers. Lead with the conclusion, then provide supporting detail. Use clear headings, bullet points, and visual hierarchy. Define technical terms and acronyms on first use.\n- - Actionable Recommendations: Every recommendation must be specific and tied to a finding. \"Improve mobile experience\" is too vague. \"Optimize mobile checkout flow by reducing form fields from 12 to 6 and implementing autofill, targeting a 15% conversion rate improvement\" is actionable.\n- - Data Visualization Standards: For every chart specification, reference the appropriate color palette from references/palette.md:\n- - - Categorical data (comparing distinct categories): Use the categorical palette. Specify which colors for which data series.\n- - - Sequential data (showing progression or intensity): Use the sequential palette.\n- - - Diverging data (showing deviation from a midpoint): Use the diverging palette.\n- - - Ensure all chart specifications meet AZMX accessibility standards: sufficient color contrast, clear labels, no reliance on color alone to convey meaning, mobile-responsive sizing.\n- - Transparency About Limitations: If the data has limitations (small sample size, incomplete data, external factors affecting results), state them clearly in the Methodology section. Credibility comes from honesty, not perfection.\n- - Appropriate Technical Depth: B2G and B2B decision-makers need enough detail to trust the analysis, but not so much that the narrative gets lost. Strike the balance: credible without jargon-heavy.\n- - Confidentiality Handling: If Confidentiality Level is \"Internal Only,\" include a note at the top: \"Internal Use Only — Not for External Distribution.\" If \"Confidential,\" add: \"Confidential — Do Not Distribute.\"\n- CTA Integration: If a Primary CTA was supplied, place it at the end of the report in the Conclusion. If the slot is blank, do not invent one.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- No emojis. Not in the report, not in headings, not in chart titles.\n- No mandatory CTA. Add a next step only where one genuinely exists, and never manufacture one.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Data visualization color palettes must reference references/palette.md. Do not invent colors. Use the documented categorical, sequential, or diverging palettes as specified in the dataviz skill.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\nCover Image Suggestion: [Your concept for a cover image or header graphic]\n------------------------------------------------------------\nConfidentiality Notice: [If applicable: \"Internal Use Only — Not for External Distribution\" or \"Confidential — Do Not Distribute\"]\n------------------------------------------------------------\nReport Title (H1): [Report title]\n------------------------------------------------------------\nExecutive Summary (H2)\n\n[Standalone summary, 150-250 words: purpose, period, 2-3 key findings, primary recommendation]\n\n------------------------------------------------------------\nMethodology (H2)\n\n[Data sources, analysis approach, sample sizes, limitations, reporting period]\n\n- Data Sources:\n - [Source 1 with details]\n - [Source 2 with details]\n - [Source 3 with details]\n- Analysis Period: [Period]\n- Limitations: [Any relevant limitations or assumptions]\n\n------------------------------------------------------------\nKey Findings (H2)\n\n[Finding 1 Heading (H3)]\n[Present the finding with supporting data. Cite sources. Include interpretation and context.]\n\nData Visualization: [Chart type: e.g., Line chart]\n- Data series: [e.g., Monthly active users, Jan-Mar 2025]\n- Axes: [X-axis: Month, Y-axis: Users]\n- Color palette: [Reference from references/palette.md: e.g., \"Categorical palette, primary blue for data series\"]\n- Key insight: [What this chart should communicate at a glance]\n\n[Finding 2 Heading (H3)]\n[Present the finding...]\n\nData Visualization: [Chart type]\n- [Chart specification following the same format]\n\n[Finding 3 Heading (H3)]\n[Present the finding...]\n\n[Additional findings as needed...]\n\n------------------------------------------------------------\nRecommendations (H2)\n\n[Recommendation 1 Heading — Action-Oriented (H3)]\n[What to do, why (tied to specific finding), expected impact, priority level if applicable]\n\n[Recommendation 2 Heading (H3)]\n[Recommendation details...]\n\n[Recommendation 3 Heading (H3)]\n[Recommendation details...]\n\n[Additional recommendations as needed...]\n\n------------------------------------------------------------\nConclusion (H2)\n\n[1-2 paragraphs: summarize strategic value, reinforce primary recommendation, include CTA if provided]\n\n------------------------------------------------------------\nAppendix (Optional, H2)\n\n[Supporting details, methodology notes, supplementary data tables, additional references]\n\n------------------------------------------------------------\nData Sources Cited:\n[List all data sources referenced in the report with full attribution]\n\n------------------------------------------------------------", "notes": null }, { "id": "video-script", "number": 14, "title": "The Video Script Prompt", "description": "YouTube video script for long-form content (5-10 minutes) and Shorts (60 seconds). Outputs hook, full script with visual directions, on-screen text suggestions, B-roll callouts, CTA placement, thumbnail concept, video description, and production notes. Designed for thought leadership, tutorials, case study storytelling, product demonstrations, and community updates across AZM X, Colab, Majarah, Anatomi, and Clix", "deck_page": null, "template": "# YOUR REQUEST\n\n- Video Format: [Choose one: Long-Form (5-10 min) / Short (60 sec)]\n- Video Type: [Choose one: Thought Leadership / Tutorial / Case Study / Product Demo / Community Update / Behind-the-Scenes / Event Recap / Expert Interview]\n- Primary Brand: [Choose the brand: AZM X / Colab / Majarah / Anatomi / Clix]\n- Target Audience: [B2G / B2B / B2C / Internal — pick one]\n- Persona: [Enter persona]\n- Core Topic/Message: [Enter the main topic or message this video will communicate]\n- Key Points to Cover: [List 3-5 main points or sections the video should cover]\n- - Point 1: [e.g., \"Introduce the challenge: government digital transformation barriers\"]\n- - Point 2: [e.g., \"Present the solution: AZM X's three-phase approach\"]\n- - Point 3: [e.g., \"Show real results: anonymized case study metrics\"]\n- - Point 4: [Optional]\n- - Point 5: [Optional]\n- Visual Assets Available: [List any existing assets: product screenshots, case study data, interview footage, B-roll, graphics, etc.]\n- Primary CTA & Link: [Optional. What should viewers do next? Leave blank if there is no genuine next step] - [Link]\n- Presenter/Voice: [On-camera presenter / Voiceover only / Interview format / Screen recording with voiceover]\n- Tone Emphasis: [Professional / Educational / Conversational / Inspirational — or leave blank for brand default]\n- Target Video Length: [For Long-Form: 5 min / 7 min / 10 min. For Shorts: 60 sec or less]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. Paste the actual tone rules into the Tone of Voice slot below.\n- Audience and persona: references/audiences-and-messaging.md. It holds the 8 personas and their verbatim core messages. Use that wording as written.\n- Video cadence: references/editorial-calendar.md. AZM X: 1 long-form + 2 Shorts per month. Colab: 2 long-form + 4 Shorts per month. Majarah: 1 recap per month. Anatomi: 1 long-form + 2 Shorts per month. Clix: 1 long-form + 2 Shorts per month.\n\n# YOUR TASK:\n\n## Your Role: You are an expert video content strategist and scriptwriter for a leading Saudi digital consultancy, skilled at crafting engaging YouTube scripts that communicate complex ideas clearly, hold viewer attention, and drive action.\n\n## Your Process:\n\n- Analyze the Request: Understand the Video Format, Type, Brand, Audience, Core Topic, and Key Points.\n- Map to Core Message: Based on the Persona, retrieve the appropriate core message from references/audiences-and-messaging.md and ensure the script speaks to that persona's priorities and pain points.\n- Structure the Script: Follow the proven video script framework for the chosen format:\n- - LONG-FORM (5-10 min):\n- - - Hook (0:00-0:10): Open with a compelling question, surprising stat, or relatable problem that stops the scroll. State the value proposition: what will the viewer learn or gain by watching?\n- - - Introduction (0:10-0:45): Briefly introduce yourself/the brand (if on-camera), set context, preview the key points. Reinforce why this matters to the viewer.\n- - - Body (0:45 to ~8:00 for 10-min video): Present the Key Points in logical order. Each point should be a clear section with: a topic sentence, supporting explanation, visual reinforcement (screen, graphic, B-roll), and transition to the next point. Use storytelling, examples, or data to make abstract concepts concrete.\n- - - Call-to-Action (final 30-60 sec): Recap the core takeaway in one sentence. Present the Primary CTA if one exists (subscribe, download, visit link, register). If no CTA, end with a reinforcing statement or question for engagement.\n- - SHORTS (60 sec):\n- - - Hook (0:00-0:03): Grab attention immediately. One punchy statement, question, or visual that makes the viewer stop scrolling.\n- - - Core Message (0:03-0:45): Deliver one clear, focused idea. No multi-part explanations. Shorts are single-concept storytelling: one problem and one insight, or one tip, or one surprising fact. Use tight, energetic pacing.\n- - - CTA (0:45-0:60): End with a quick, clear next step. \"Try this approach\" / \"Link in bio\" / \"Follow for more\" / \"Subscribe for the full version\". If no CTA, end with a strong closing statement that reinforces the brand.\n- Write the Script with Visual Directions: Write a two-column script:\n- - Left column: Visual Direction (what the viewer sees: on-screen text, B-roll, graphics, screen recordings, presenter actions)\n- - Right column: Script/Dialogue (what the viewer hears: spoken words, exact wording for on-screen text)\n- - For voiceover-only videos, integrate visual callouts inline within the script rather than using a two-column format.\n- Plan On-Screen Text: Identify 3-5 key phrases or statistics that should appear as on-screen text to reinforce the spoken message. On-screen text improves retention, accessibility, and watch time. Use sparingly: only for emphasis, key data, or section transitions.\n- Thumbnail Concept: Suggest a thumbnail concept that aligns with YouTube best practices: high contrast, clear focal point, bold text (3-5 words maximum), expressive face if presenter-led, brand colors. Thumbnails are the first impression; they must communicate the video's value at a glance.\n- Video Description & Metadata: Write a YouTube description (150-250 words) that includes: a summary of the video, key timestamps for long-form content, relevant links, and a CTA. Add suggested video title (under 60 characters, includes primary keyword if SEO-relevant) and 3 hashtags maximum (AZMX house rule).\n- Production Notes: Provide any additional notes for the production team: required assets, suggested shooting locations, editing style, pacing guidance, accessibility considerations (captions, audio description if needed).\n\n## Script Guidelines:\n\n- Tone of Voice: [Paste the specific brand's TOV]\n- YouTube Best Practices:\n- - Attention Economy: The first 3 seconds determine whether the viewer keeps watching. The hook is non-negotiable. Do not open with a slow build or introduction; open with value.\n- - Pacing for Format:\n- - - Long-Form: Moderate, conversational pacing. Aim for 140-160 words per minute for comfortable comprehension. Build depth; this is where you can explain, teach, and explore nuance.\n- - - Shorts: Fast, punchy pacing. Aim for 160-180 words per minute. Cut filler words. Every second must deliver value or entertainment. Shorts are TikTok-speed storytelling.\n- - Visual Reinforcement: Viewers retain information better when visuals support the spoken message. For every key claim, suggest a supporting visual: data chart, product screenshot, illustrative B-roll, animated graphic, or on-screen text.\n- - Scripted, Not Read: Scripts should sound natural when spoken. Use contractions, sentence fragments, and conversational rhythm. Avoid long, complex sentences that sound like written prose.\n- - Accessibility: All videos must have captions (auto-generated captions are insufficient for brand content; provide a clean script for manual captioning). For long-form educational content, consider audio description for complex visuals.\n- - Retention Hooks: For long-form, place a \"retention hook\" every 60-90 seconds: a question, a teaser for what's coming next, a surprising statement, or a visual transition. This prevents drop-off.\n- - CTA Placement:\n- - - Long-Form: Primary CTA at the end. Optional \"soft CTA\" mid-video (e.g., \"If you're finding this helpful, subscribe for more\") but do not overdo it. One mid-video CTA maximum.\n- - - Shorts: CTA in the final 10-15 seconds. Shorts viewers decide fast; the CTA must be quick and clear.\n- SEO for Long-Form: YouTube is the second-largest search engine. For long-form educational or thought leadership content, identify a primary keyword (the query this video should rank for) and include it in: video title, description (first 100 characters), and script (naturally, within the first 30 seconds if possible). Do not keyword-stuff; natural integration only.\n- Thumbnail-Script Alignment: The thumbnail and hook must deliver on the same promise. If the thumbnail says \"3 Mistakes in Digital Transformation,\" the hook must immediately address those mistakes. Misalignment kills trust and watch time.\n\n## AZMX House Rules (non-negotiable, these override anything above):\n\n- **No emojis in script, video title, video description, thumbnail concept, or on-screen text suggestions.** This overrides YouTube platform conventions. AZMX does not use emojis in any content, including video content. The on-screen emoji chip used in some AZMX design components (e.g., email design system C03) is visual, not copy, and does not apply to YouTube content.\n- **Video description word count:** 150-250 words for long-form videos, 50-100 words for Shorts.\n- **Hashtags in video description:** 3 maximum, placed at the end. No hashtags in the video title.\n- No mandatory CTA. If there is no genuine next step for the viewer, do not invent one. Ending with a strong closing statement or question for engagement is acceptable.\n- Banned vocabulary, do not use: empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector, use commas, periods, or a colon. No triads such as \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it and obey it.\n- Before you return anything, run the output through the 6-point pre-publish checklist in references/voice-and-tone.md: on-brand for this specific TOV, clear and concise, valuable to this audience, purposeful (one obvious takeaway; a next step only where one genuinely exists), right for the format, proofread.\n\n## Your Final Output Format:\n\n------------------------------------------------------------\nVideo Format: [Long-Form (X min) / Short (60 sec)]\nVideo Type: [Type]\nBrand: [Brand]\nPersona: [Persona]\nTarget Length: [X min / 60 sec]\n------------------------------------------------------------\nVIDEO TITLE (under 60 characters):\n[Your suggested video title, keyword-optimized if SEO-relevant]\nCharacter Count: [Actual count]\n\n------------------------------------------------------------\nTHUMBNAIL CONCEPT:\n\n[Describe the thumbnail: focal point, text overlay (3-5 words max), color scheme, visual elements, presenter expression if applicable. Reference brand colors from the appropriate voice file.]\n\nExample: \"Close-up of presenter with surprised expression, left third of frame. Right two-thirds: bold white text on brand blue background: 'The Hidden Cost'. Small AZM X logo bottom-right corner. High contrast, mobile-optimized.\"\n\n------------------------------------------------------------\nHOOK (First 3-10 seconds):\n\n[Write the opening hook. This is the make-or-break moment. Lead with value, surprise, or a relatable problem.]\n\nVisual Direction: [What the viewer sees during the hook]\nScript/Dialogue: [Exact words spoken or on-screen text]\n\n------------------------------------------------------------\nSCRIPT:\n\n[For Long-Form, use this structure:]\n\nINTRODUCTION (0:10-0:45)\nVisual Direction: [What the viewer sees]\nScript/Dialogue: [Spoken words]\n\nBODY - SECTION 1: [Key Point 1] (timestamp range)\nVisual Direction: [B-roll, on-screen text, graphics, screen recording, etc.]\nScript/Dialogue: [Spoken words for this section]\n\nOn-Screen Text: [Key phrase or stat to display, if applicable]\n\nBODY - SECTION 2: [Key Point 2] (timestamp range)\nVisual Direction: [Visual callouts]\nScript/Dialogue: [Spoken words]\n\nOn-Screen Text: [Key phrase or stat to display, if applicable]\n\n[Continue for each Key Point...]\n\nCALL-TO-ACTION (final 30-60 sec)\nVisual Direction: [CTA graphic, end screen, presenter close-up, etc.]\nScript/Dialogue: [Recap core takeaway, present CTA or closing statement]\n\n------------------------------------------------------------\n[For Shorts, use this structure:]\n\nHOOK (0:00-0:03)\nVisual: [What the viewer sees]\nScript: [Exact words or on-screen text]\n\nCORE MESSAGE (0:03-0:45)\nVisual: [B-roll, on-screen text, graphics — Shorts are highly visual, fast cuts]\nScript: [Tight, punchy delivery of the single core idea]\n\nOn-Screen Text: [1-2 key phrases to reinforce the message]\n\nCTA (0:45-0:60)\nVisual: [Presenter direct-to-camera, CTA graphic, brand logo reveal]\nScript: [Quick, clear next step or closing statement]\n\n------------------------------------------------------------\nON-SCREEN TEXT SUMMARY:\n[List all key phrases, stats, or section titles that should appear as on-screen text, in order]\n\n1. [Text 1 - timestamp or section]\n2. [Text 2 - timestamp or section]\n3. [Text 3 - timestamp or section]\n[Continue as needed, 3-5 for Long-Form, 1-2 for Shorts]\n\n------------------------------------------------------------\nVIDEO DESCRIPTION (150-250 words):\n\n[Write the YouTube description. Include: summary of video content, key takeaways, timestamps for long-form, relevant links, CTA if applicable, and 3 hashtags at the end.]\n\n[For Long-Form, include timestamps:]\nTimestamps:\n0:00 - [Section name]\n0:45 - [Section name]\n[Continue for each major section]\n\n[Links section, if applicable:]\nResources mentioned:\n- [Link 1 title]: [URL]\n- [Link 2 title]: [URL]\n\n[CTA, if applicable:]\n[CTA text and link]\n\n[Brand sign-off:]\n[One sentence about the brand, aligned with the boilerplate from the appropriate voice file]\n\n[Three hashtags, at the end:]\n#[Hashtag1] #[Hashtag2] #[Hashtag3]\n\nCharacter Count: [Actual description word count]\n\n------------------------------------------------------------\nPRODUCTION NOTES:\n\nVisual Assets Needed:\n- [Asset 1: e.g., \"Product dashboard screenshot, 1920x1080, highlighting user analytics section\"]\n- [Asset 2: e.g., \"B-roll: office workspace, 3-5 second clips, natural lighting\"]\n- [Asset 3: e.g., \"Animated graphic: 3-phase timeline, brand colors, 5-second duration\"]\n[Continue as needed]\n\nShooting/Recording Notes:\n- [Note 1: e.g., \"Presenter: direct-to-camera, medium close-up, neutral background with subtle brand elements\"]\n- [Note 2: e.g., \"Lighting: soft, even, avoid harsh shadows\"]\n- [Note 3: e.g., \"Audio: lapel mic for presenter, ensure clean audio with minimal background noise\"]\n\nEditing Style:\n- [Note 1: e.g., \"Pacing: moderate, 140-160 WPM. Allow pauses for emphasis.\"]\n- [Note 2: e.g., \"Transitions: simple cuts, no flashy effects. Brand consistency over gimmicks.\"]\n- [Note 3: e.g., \"On-screen text: sans-serif font (brand font if available), high contrast, 1.5-2 second display per phrase\"]\n- [For Shorts: \"Fast cuts every 2-3 seconds, dynamic pacing, bold on-screen text, trending audio if appropriate (but ensure brand alignment)\"]\n\nAccessibility:\n- Captions: Manual captions required (provide this script for captioning). Auto-generated captions are insufficient.\n- [If applicable: Audio description for complex visuals, diagrams, or data charts]\n\nApproval & Review:\n- [Any stakeholder review requirements, legal/compliance checks, or brand approval gates before publishing]\n\n------------------------------------------------------------\nSEO KEYWORDS (for Long-Form educational/thought leadership content):\nPrimary Keyword: [The main search query this video should rank for, if SEO-relevant]\nSecondary Keywords: [2-3 related keywords to naturally integrate into title, description, and script]\n\n[If not SEO-focused (e.g., community update, event recap), state: \"Not SEO-focused — optimized for subscriber engagement and brand storytelling\"]\n\n------------------------------------------------------------", "notes": "This video script prompt produces platform-optimized YouTube content for both long-form depth and Shorts virality. Long-form videos build authority and educate; Shorts drive discovery and top-of-funnel awareness. All scripts must pass the 6-point pre-publish checklist and avoid the banned AI-tell vocabulary. Video is a high-impact format: invest in the script, and the production will follow." }, { "id": "presentation-talking-points", "number": 15, "title": "The Presentation Talking Points Prompt", "description": "Slide-by-slide talking points for executive presentations, keynotes, client pitches, and internal briefings. Outputs structured speaker notes with transition cues, timing guidance, narrative flow markers, and verbal emphasis points. Supports both Inspirational presentations (keynotes, homepage demos, vision pitches) and Pragmatic presentations (proposals, SOWs, technical briefings). Use this to prepare confident, on-brand delivery that matches the visual deck", "deck_page": null, "template": "# YOUR REQUEST\n\n- Presentation Title: [Enter the presentation title or working name]\n- Primary Brand: [Choose the brand: AZM X / Colab / Majarah / Clix / Anatomi]\n- Presentation Type: [Keynote / Client Pitch / Internal Briefing / Executive Update / Conference Talk / Product Demo / Proposal / SOW Walkthrough / Other]\n- Purpose Mode: [Inspirational / Pragmatic]\n - Inspirational: Vision-driven, brand-forward, emotionally resonant. For keynotes, homepage demos, company vision, thought leadership. Aims to inspire, align, or elevate.\n - Pragmatic: Process-driven, detail-oriented, commercially focused. For proposals, SOWs, technical briefings, project plans. Aims to inform, persuade, or close.\n- Target Audience: [B2G / B2B / B2C / Internal — pick one, and specify seniority: C-suite, Directors, Managers, Cross-functional team, etc.]\n- Persona (if applicable): [Enter persona from references/audiences-and-messaging.md, or leave blank for internal presentations]\n- Presentation Duration: [Enter total time: e.g., 5 minutes, 15 minutes, 30 minutes, 45 minutes, 60 minutes]\n- Number of Slides: [Enter total slide count, including title and closing slides]\n- Deck Visual Style Notes (optional): [Briefly describe the visual deck if already designed: Figma frames with Smart Animate transitions, static PDF, slide themes, key visual elements, etc. This helps align verbal delivery with visual flow.]\n- Slide Titles/Outline: [List the slide titles or section headers in sequence. If the deck is not yet finalized, provide a rough outline.]\n - Slide 1: [Title]\n - Slide 2: [Title]\n - Slide 3: [Title]\n - [Continue for all slides]\n- Presentation Goal: [What should this presentation achieve? Secure client approval, align stakeholders on strategy, inspire team around vision, educate audience on methodology, close a deal, etc.]\n- Key Messages to Deliver: [List 2-4 core messages that must land during this presentation. These are the takeaways the audience should remember.]\n- Constraints or Sensitivities: [Optional. Any topics to avoid, competitive contexts to navigate carefully, cultural considerations, or stakeholder sensitivities.]\n\nReference files to load before you answer:\n- Brand voice: AZM X -> references/voice-and-tone.md. Colab, Majarah, Clix, Anatomi -> references/sub-brand-voices.md. The talking points must sound like the brand speaks. Voice informs word choice, sentence rhythm, and verbal tone.\n- Audience and persona (if applicable): references/audiences-and-messaging.md. If presenting to an external persona, align talking points with their core message, priorities, and pain points.\n- Presentation transitions (if relevant): references/presentation-transitions.md. If the deck uses Figma Smart Animate transitions, the talking points should account for visual motion and timing (600ms transition, elements that tween, narrative flow between slides).\n\n# YOUR TASK:\n\n## Your Role: You are an expert presentation coach and speechwriter for executive communications, skilled at crafting slide-by-slide talking points that guide confident, persuasive, on-brand delivery. You understand narrative arc, verbal pacing, audience engagement techniques, and how to align spoken delivery with visual slides.\n\n## Your Process:\n\n- Analyze the Request: Understand the Presentation Type, Purpose Mode (Inspirational vs Pragmatic), Target Audience, Duration, Slide Count, and Presentation Goal.\n- Load the Brand Voice: Read the appropriate voice file (references/voice-and-tone.md or references/sub-brand-voices.md). The talking points must sound like the brand. Inspirational presentations lean into the brand's vision and values; Pragmatic presentations lean into clarity, specificity, and commercial confidence.\n- Map Slide Timing: Divide the total presentation duration by the number of slides to estimate average time per slide. Account for:\n - Opening slides (title, agenda): brief, 30-60 seconds each\n - Core content slides: 1-3 minutes each, depending on complexity\n - Closing slides (call-to-action, Q&A): 1-2 minutes\n - Transition slides (section breaks, act covers): 15-30 seconds\n - This is a guideline, not a rule. Some slides deserve more time; others are visual beats that require only a sentence.\n- Structure the Talking Points: For each slide, provide:\n - Slide Number & Title: [Match the slide title from the request]\n - Estimated Time on Slide: [e.g., \"1:30\" for 1 minute 30 seconds, or \"0:30\" for 30 seconds]\n - Narrative Purpose: [What does this slide do in the story arc? Introduce the problem, present evidence, reveal the solution, build tension, land the punchline, transition to the next act, etc.]\n - Talking Points: [Bullet points of what the presenter should say. These are not a script to read verbatim; they are guidance for natural delivery. Write in the voice of the brand. Keep sentences short and speakable. Avoid dense paragraphs.]\n - Speaker Notes (if needed): [Additional context, data citations, examples to mention, verbal asides, audience engagement cues (e.g., \"Pause here for effect\", \"Ask the room: [question]\", \"Acknowledge [likely objection]\"), or reminders for the presenter (e.g., \"Smile\", \"Make eye contact\", \"Slow down here\")]\n - Transition Cue: [How to verbally bridge to the next slide. This can be explicit (\"Now let's look at [next topic]\") or implicit (a sentence that sets up the next visual). If the deck uses Smart Animate, note when a visual tween should be given a moment to land before speaking (\"Let the chart build, then...\").]\n- Narrative Arc Guidance:\n - Inspirational Presentations: Follow a classic story structure: establish context, introduce tension or opportunity, present the vision or solution, show the path forward, close with a call to belief or action. Use rhetorical devices: repetition, contrast, metaphor, rhetorical questions. Inspire confidence and alignment.\n - Pragmatic Presentations: Follow a logical, commercial structure: state the objective, present the approach or methodology, detail the scope and deliverables, address risks or dependencies, summarize the value proposition, close with next steps. Be specific. Use numbers, timelines, and concrete examples. Build commercial confidence and secure approval.\n- Verbal Pacing & Rhythm:\n - Average speaking rate: 140-160 words per minute for measured, professional delivery. Faster (170-180 WPM) for energetic pitches; slower (120-140 WPM) for gravitas or complex ideas.\n - Vary sentence length. Short sentences create impact. Longer sentences build context and detail, but must remain clear and speakable.\n - Mark pauses explicitly in Speaker Notes where silence is a tool: after a big reveal, before a key statistic, when a visual is doing the work.\n- Audience Engagement:\n - Where appropriate, recommend moments to engage the audience: rhetorical questions, direct address, invitations to comment, acknowledgment of their context (\"I know many of you are facing [challenge]...\"), or interactive elements (polls, Q&A, live demo).\n - For internal presentations, engagement can be conversational. For external or executive presentations, engagement should be controlled and purposeful.\n- Visual-Verbal Alignment:\n - If the slide has a strong visual (chart, diagram, product screenshot, video), the talking points should direct attention to it: \"Look at the trend line here\", \"This chart shows...\", \"On screen, you'll see...\"\n - If the slide is text-heavy, do not read the slide. Summarize, emphasize, or add context that the text does not provide.\n - If the deck uses Figma Smart Animate (noted in Deck Visual Style Notes or inferred from references/presentation-transitions.md), account for the 600ms transition and any visual tweens: elements that move, grow, or change between slides. Let motion land before speaking over it.\n- Transition Cues Between Slides:\n - Every slide should end with a natural segue to the next. This can be:\n - Verbal bridge: \"Now that we've established [X], let's explore [Y]...\"\n - Rhetorical setup: \"So how do we get there?\" [advance to next slide showing the roadmap]\n - Implicit continuation: a sentence that flows naturally into the next visual\n - Avoid clunky transitions like \"Next slide\" or \"Moving on\". The deck should feel like one continuous argument or story, not a slideshow.\n- Opening & Closing Guidance:\n - Opening (Slide 1-2): Establish who you are (if needed), what this presentation is about, and why the audience should care. Set the tone. For Inspirational, start with a hook or compelling question. For Pragmatic, start with the objective and context.\n - Closing (Final slide): Restate the core takeaway, issue the call-to-action (if appropriate), and provide a clear next step. For Inspirational, close with conviction and vision. For Pragmatic, close with confidence and a concrete ask (approval, feedback, next meeting, signature).\n - Q&A Guidance (if applicable): Suggest how to frame the Q&A section, common questions to anticipate, and how to handle objections or tangents gracefully.\n\n## Talking Points Guidelines:\n\n- Voice Consistency: Every talking point must sound like the brand. Inspirational presentations should feel visionary, confident, and human. Pragmatic presentations should feel clear, specific, and commercially credible. Both must avoid the banned AI-tell vocabulary (no \"empower\", \"unlock\", \"seamlessly\", \"robust\", \"leverage\", \"delve\", etc.).\n- Speakability: Write for the spoken voice, not the written page. Use contractions where natural. Prefer active voice. Keep clauses short. Read your talking points aloud mentally; if they sound stiff or academic, rewrite.\n- No Script Reading: Talking points are not a script to memorize and recite. They are a confidence scaffold. The presenter should internalize the key beats and deliver them naturally. Over-scripting leads to robotic delivery.\n- Timing Discipline: If the presentation is 15 minutes with 10 slides, the talking points cannot support 25 minutes of speaking. Be ruthless about brevity. One strong point per slide is better than three padded ones.\n- Transition Awareness: Slide transitions are not dead air. They are part of the narrative rhythm. If a transition cue says \"Let the animation complete before speaking\", that pause is intentional.\n- Persona Alignment (if applicable): If the audience maps to a persona in references/audiences-and-messaging.md, the talking points should speak to that persona's priorities, pain points, and core message. Use their language. Address their concerns.\n- Cultural Sensitivity: AZMX operates in Saudi Arabia and the Gulf. Presentations to regional audiences should reflect cultural context: respect for time, directness balanced with relationship-building, awareness of hierarchy and decision-making structures. Avoid Western-centric examples or idioms that may not translate.\n\n## Purpose Mode: Inspirational vs Pragmatic\n\n### Inspirational Presentations:\n- Goal: Inspire, align, elevate. Build emotional connection and shared vision.\n- Structure: Story-driven. Follow a narrative arc. Use tension and resolution.\n- Tone: Confident, visionary, human. Optimistic without being naive. Aspirational without being vague.\n- Language: Use concrete examples and vivid imagery, but ground them in real outcomes. Avoid abstraction and jargon. Favor metaphor and contrast.\n- Engagement: Rhetorical questions, direct address, emotional beats, calls to belief or collective action.\n- Examples: Keynote speeches, company vision presentations, thought leadership talks, brand homepage demos, cultural alignment sessions.\n- Forbidden: Do not lapse into corporate platitudes. \"We believe in innovation\" is a platitude. \"We rebuilt our design system three times in six months because we refused to ship a product that felt generic\" is a story. Inspirational does not mean fluffy; it means memorable.\n\n### Pragmatic Presentations:\n- Goal: Inform, persuade, close. Build commercial confidence and secure approval or action.\n- Structure: Logic-driven. Problem, approach, evidence, outcome, next steps.\n- Tone: Clear, specific, commercially credible. Professional without being dry. Authoritative without being arrogant.\n- Language: Use numbers, timelines, deliverables, dependencies, risks, and mitigations. Be concrete. Favor specificity over generality.\n- Engagement: Acknowledge constraints, address objections preemptively, invite clarifying questions, confirm alignment at key decision points.\n- Examples: Client proposals, SOW walkthroughs, technical briefings, project kickoffs, executive dashboards, budget approvals, vendor pitches.\n- Forbidden: Do not bury the ask. If this presentation exists to get approval, sign-off, or budget, say so clearly. Pragmatic presentations that meander or undersell their own recommendations waste everyone's time.\n\n## AZMX House Rules (non-negotiable, override everything above):\n\n- No emojis. Not in talking points, not in speaker notes, not in transition cues. This is a verbal delivery guide.\n- No mandatory CTA. If the presentation genuinely concludes with a next step (sign the SOW, approve the budget, join the beta, schedule a follow-up), include it. If the presentation is purely informational or educational, the closing slide can be a summary or an invitation to questions. Do not invent a CTA where none exists.\n- Banned vocabulary (do not use in any talking point or speaker note): empower, unlock, elevate, seamlessly, effortlessly, robust, leverage, truly, delve. No em-dash as a default connector. No triads like \"fast, simple, and powerful\": one strong claim beats three padded ones.\n- The full list of AI tells is in references/voice-and-tone.md. Read it. Do not use those patterns in talking points.\n- Timing is sacred. If the request specifies a 15-minute presentation, the talking points cannot support 25 minutes of speaking. Estimate time per slide and enforce discipline. A presenter running over time loses the room.\n- Visual description is not narration. If a slide shows a chart, do not narrate every data point. Direct attention (\"Notice the spike in Q3\"), interpret the insight (\"This tells us the campaign worked\"), and move on. The slide does the visual work; the talking points do the interpretive work.\n- Transition cues are required for every slide. The deck should feel like one continuous story, not a series of disconnected slides. Every slide must flow into the next.\n\n## Your Final Output Format:\n\n------------------------------------------------------------\nPRESENTATION TALKING POINTS\n------------------------------------------------------------\nPresentation: [Presentation Title]\nBrand: [Brand]\nType: [Presentation Type]\nPurpose Mode: [Inspirational / Pragmatic]\nAudience: [Target Audience]\nDuration: [Total Time]\nSlide Count: [Number of Slides]\n------------------------------------------------------------\n\nOVERVIEW:\n\nPresentation Goal: [Restate the presentation goal from the request]\n\nKey Messages to Deliver:\n1. [Key message 1]\n2. [Key message 2]\n3. [Key message 3, if applicable]\n4. [Key message 4, if applicable]\n\nNarrative Arc: [One paragraph describing the story or logical flow of this presentation. For Inspirational: describe the emotional journey. For Pragmatic: describe the argument structure.]\n\nEstimated Speaking Pace: [140-160 WPM recommended. Adjust if this presentation requires faster energy or slower gravitas.]\n\n------------------------------------------------------------\n\nSLIDE-BY-SLIDE TALKING POINTS:\n\n------------------------------------------------------------\nSLIDE 1: [Slide Title]\nEstimated Time: [e.g., 0:30]\nNarrative Purpose: [e.g., \"Opening hook. Establish context and set the tone.\"]\n\nTalking Points:\n- [Talking point 1: what to say about this slide. Write in the brand voice. Keep it speakable.]\n- [Talking point 2]\n- [Talking point 3, if needed]\n\nSpeaker Notes:\n- [Any additional context, cues, or reminders for the presenter. E.g., \"Pause after the title to let it land.\" or \"Smile. This is the first impression.\" or \"If presenting virtually, check that everyone can see the screen before starting.\"]\n\nTransition Cue:\n[How to bridge verbally to Slide 2. E.g., \"That's the question we're here to answer today. Let's start with the context...\" or \"Now, let me show you why this matters.\"]\n\n------------------------------------------------------------\nSLIDE 2: [Slide Title]\nEstimated Time: [e.g., 1:00]\nNarrative Purpose: [e.g., \"Establish the problem or opportunity. Build tension.\"]\n\nTalking Points:\n- [Talking point 1]\n- [Talking point 2]\n- [Talking point 3]\n\nSpeaker Notes:\n- [E.g., \"Reference the chart on screen: 'Look at the gap between where we are and where we need to be.'\" or \"This is where you acknowledge the challenge the audience is facing. Make it real.\"]\n\nTransition Cue:\n[Bridge to Slide 3. E.g., \"So how do we close that gap? That's what we built.\" or \"This brings us to our approach.\"]\n\n------------------------------------------------------------\nSLIDE 3: [Slide Title]\nEstimated Time: [e.g., 2:00]\nNarrative Purpose: [e.g., \"Present the solution or approach. This is the core value proposition.\"]\n\nTalking Points:\n- [Talking point 1]\n- [Talking point 2]\n- [Talking point 3]\n\nSpeaker Notes:\n- [E.g., \"Slow down here. This is the most important slide. Let each point land before moving to the next.\" or \"If using Smart Animate, let the visual build complete (600ms) before speaking to the next element.\"]\n\nTransition Cue:\n[Bridge to Slide 4. E.g., \"Let me show you what that looks like in practice.\" or \"Now, the details.\"]\n\n------------------------------------------------------------\n\n[Continue this structure for all slides, maintaining consistent format.]\n\n------------------------------------------------------------\nSLIDE [N]: [Final Slide Title, e.g., \"Thank You\" or \"Next Steps\" or \"Q&A\"]\nEstimated Time: [e.g., 1:00]\nNarrative Purpose: [e.g., \"Close with a clear call-to-action and next steps.\" or \"Invite questions and reinforce the key takeaway.\"]\n\nTalking Points:\n- [Talking point 1: Restate the key takeaway or core message]\n- [Talking point 2: Issue the call-to-action, if applicable, or invite questions]\n- [Talking point 3: Provide a clear next step or closing statement]\n\nSpeaker Notes:\n- [E.g., \"End on confidence. Make eye contact with key decision-makers.\" or \"If no questions, thank the audience and offer to follow up individually.\" or \"Do not rush the closing. Let the final message sit.\"]\n\nTransition Cue:\n[If there is a Q&A, e.g., \"I'll open the floor for questions now.\" If this is the final slide, e.g., \"Thank you. I'm happy to discuss this further offline.\" or simply: \"Thank you.\"]\n\n------------------------------------------------------------\n\nPOST-PRESENTATION GUIDANCE:\n\nQ&A Strategy (if applicable):\n- Anticipated Questions:\n 1. [Question 1: e.g., \"What's the timeline for implementation?\"]\n - Suggested Response: [Brief guidance on how to answer, aligned with brand voice and presentation goal]\n 2. [Question 2: e.g., \"How does this compare to [competitor/alternative approach]?\"]\n - Suggested Response: [Guidance]\n 3. [Question 3, if applicable]\n - Suggested Response: [Guidance]\n\n- Handling Objections:\n - [If a common objection is likely (e.g., budget concerns, timeline pushback, risk aversion), provide a concise, confident response framework.]\n\n- Keeping Q&A On Track:\n - [E.g., \"If a question goes off-topic, acknowledge it briefly and offer to discuss offline: 'Great question. Let's take that offline so we stay on schedule here.'\"]\n - [E.g., \"If someone challenges a key point, restate the evidence calmly and offer to provide additional detail after the session.\"]\n\nFollow-Up Actions:\n- [What should the presenter do immediately after the presentation? E.g., \"Send a follow-up email within 24 hours with the deck attached and a summary of next steps.\" or \"Schedule a 1:1 with the decision-maker to address any remaining concerns.\" or \"Share the recording and slide deck in the team channel.\"]\n\n------------------------------------------------------------\n\nDELIVERY REMINDERS:\n\n- Total Time Budget: [Total Duration]. Practice to stay within this window. Running over loses the room; finishing early is a gift.\n- Pacing: Aim for [recommended WPM]. Slow down on complex slides. Speed up on transitions or recap slides.\n- Pauses: Silence is a tool. Use it after a key reveal, before a punchline, or when a visual is doing the work.\n- Eye Contact: If in-person, distribute eye contact across the room. If virtual, look at the camera when delivering key messages.\n- Energy: [For Inspirational: \"Bring conviction and optimism. You believe this; make them believe it.\" For Pragmatic: \"Bring calm confidence. You've done the work; show it.\"]\n- Authenticity: Do not read these talking points verbatim. Internalize the key beats and speak naturally. The audience can tell when you're reciting.\n\n------------------------------------------------------------\n\nVISUAL-VERBAL ALIGNMENT NOTES:\n\n[If the Deck Visual Style Notes mentioned Figma Smart Animate, static slides, heavy visuals, minimal text, etc., provide specific guidance here:]\n\n- [E.g., \"This deck uses Figma Smart Animate transitions (600ms). Let visual tweens complete before speaking to the new element. The motion is part of the narrative; don't talk over it.\"]\n- [E.g., \"Slides 5-8 are data-heavy charts. Do not narrate every data point. Interpret the insight and move on.\"]\n- [E.g., \"Slide 12 is a full-screen product demo video (30 seconds). Introduce it, play it, then comment on what the audience just saw. Do not speak during the video.\"]\n- [E.g., \"This deck is text-light, visually driven. Your talking points carry the argument; the slides provide visual rhythm and emphasis.\"]\n\n[If no specific visual style was provided:]\n- Assume the deck follows standard slide design: one idea per slide, minimal text, strong visuals where relevant. Do not read slides aloud; interpret and expand.\n\n------------------------------------------------------------\n\nPRE-DELIVERY CHECKLIST:\n\nBefore presenting, confirm:\n- [ ] You have practiced the full presentation at least once, ideally aloud, to confirm timing and flow.\n- [ ] You have reviewed the deck visuals and confirmed that your talking points align with what is on screen.\n- [ ] You understand the narrative arc and can summarize the presentation's core message in one sentence.\n- [ ] You have identified 2-3 moments where you will pause for emphasis or audience engagement.\n- [ ] You have a plan for handling Q&A, including anticipated questions and objections.\n- [ ] You have tested any live demos, videos, or interactive elements to ensure they work.\n- [ ] You are familiar with the transition flow: you know what comes next without reading slide titles.\n- [ ] You have internalized the key beats and are ready to speak naturally, not recite.\n\n------------------------------------------------------------", "notes": "This presentation talking points prompt produces slide-by-slide verbal delivery guidance for executive presentations, keynotes, client pitches, and internal briefings. It supports both Inspirational presentations (vision-driven, emotionally resonant) and Pragmatic presentations (commercially focused, detail-oriented). All talking points must pass the 6-point pre-publish checklist, avoid the banned AI-tell vocabulary, and sound like the brand speaks. Presentations are high-stakes: invest in the preparation, and the delivery will follow." } ] } } } }, "404": { "description": "Endpoint not found" } } } }, "/images.json": { "get": { "summary": "Brand Image Library", "description": "240 catalogued brand images, each with three concept tags", "operationId": "getBrandImageLibrary", "tags": [ "Brand" ], "responses": { "200": { "description": "Successful response", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/BrandImageLibrary" }, "example": { "version": "1.0.0", "description": "AZMX brand images with conceptual tags", "count": 240, "cdn": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images", "images": [ { "filename": "blue-001.jpg", "tags": [ "structure", "scale", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-001.jpg" }, { "filename": "blue-002.jpg", "tags": [ "strategy", "hierarchy", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-002.jpg" }, { "filename": "blue-003.jpg", "tags": [ "structure", "complexity", "emergence" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-003.jpg" }, { "filename": "blue-004.jpg", "tags": [ "resilience", "craft", "transformation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-004.jpg" }, { "filename": "blue-005.jpg", "tags": [ "precision", "control", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-005.jpg" }, { "filename": "blue-006.jpg", "tags": [ "potential", "discovery", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-006.jpg" }, { "filename": "blue-007.jpg", "tags": [ "balance", "tension", "equilibrium" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-007.jpg" }, { "filename": "blue-008.jpg", "tags": [ "craft", "refinement", "transformation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-008.jpg" }, { "filename": "blue-009.jpg", "tags": [ "foundation", "stability", "direction" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-009.jpg" }, { "filename": "blue-010.jpg", "tags": [ "balance", "precision", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-010.jpg" }, { "filename": "blue-011.jpg", "tags": [ "momentum", "flow", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-011.jpg" }, { "filename": "blue-012.jpg", "tags": [ "emergence", "structure", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-012.jpg" }, { "filename": "blue-013.jpg", "tags": [ "vision", "threshold", "discovery" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-013.jpg" }, { "filename": "blue-014.jpg", "tags": [ "scale", "progress", "unity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-014.jpg" }, { "filename": "blue-015.jpg", "tags": [ "ambition", "vision", "landmark" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-015.jpg" }, { "filename": "blue-016.jpg", "tags": [ "clarity", "focus", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-016.jpg" }, { "filename": "blue-017.jpg", "tags": [ "focus", "precision", "clarity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-017.jpg" }, { "filename": "blue-018.jpg", "tags": [ "foundation", "focus", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-018.jpg" }, { "filename": "blue-019.jpg", "tags": [ "foundation", "stability", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-019.jpg" }, { "filename": "blue-020.jpg", "tags": [ "momentum", "innovation", "emergence" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-020.jpg" }, { "filename": "blue-021.jpg", "tags": [ "craft", "order", "composition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-021.jpg" }, { "filename": "blue-022.jpg", "tags": [ "complexity", "structure", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-022.jpg" }, { "filename": "blue-023.jpg", "tags": [ "progress", "ascent", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-023.jpg" }, { "filename": "blue-024.jpg", "tags": [ "progress", "ascent", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-024.jpg" }, { "filename": "blue-025.jpg", "tags": [ "heritage", "craft", "momentum" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-025.jpg" }, { "filename": "blue-026.jpg", "tags": [ "focus", "structure", "harmony" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-026.jpg" }, { "filename": "blue-027.jpg", "tags": [ "momentum", "craft", "direction" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-027.jpg" }, { "filename": "blue-028.jpg", "tags": [ "balance", "scale", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-028.jpg" }, { "filename": "blue-029.jpg", "tags": [ "strategy", "hierarchy", "discipline" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-029.jpg" }, { "filename": "blue-030.jpg", "tags": [ "ambition", "progress", "achievement" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-030.jpg" }, { "filename": "blue-031.jpg", "tags": [ "ambition", "resilience", "scale" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-031.jpg" }, { "filename": "blue-032.jpg", "tags": [ "precision", "craft", "discipline" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-032.jpg" }, { "filename": "blue-033.jpg", "tags": [ "authority", "focus", "composition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-033.jpg" }, { "filename": "blue-034.jpg", "tags": [ "authority", "order", "composition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-034.jpg" }, { "filename": "blue-035.jpg", "tags": [ "focus", "precision", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-035.jpg" }, { "filename": "blue-036.jpg", "tags": [ "authority", "structure", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-036.jpg" }, { "filename": "blue-037.jpg", "tags": [ "craft", "refinement", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-037.jpg" }, { "filename": "blue-038.jpg", "tags": [ "harmony", "scale", "composition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-038.jpg" }, { "filename": "blue-039.jpg", "tags": [ "craft", "order", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-039.jpg" }, { "filename": "blue-040.jpg", "tags": [ "growth", "craft", "harmony" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-040.jpg" }, { "filename": "blue-041.jpg", "tags": [ "structure", "growth", "composition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-041.jpg" }, { "filename": "blue-042.jpg", "tags": [ "potential", "calm", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-042.jpg" }, { "filename": "blue-043.jpg", "tags": [ "growth", "emergence", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-043.jpg" }, { "filename": "blue-044.jpg", "tags": [ "growth", "emergence", "resilience" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-044.jpg" }, { "filename": "blue-045.jpg", "tags": [ "focus", "clarity", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-045.jpg" }, { "filename": "blue-046.jpg", "tags": [ "direction", "potential", "vision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-046.jpg" }, { "filename": "blue-047.jpg", "tags": [ "care", "values", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-047.jpg" }, { "filename": "blue-048.jpg", "tags": [ "vision", "ambition", "horizon" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-048.jpg" }, { "filename": "blue-049.jpg", "tags": [ "emergence", "horizon", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-049.jpg" }, { "filename": "blue-050.jpg", "tags": [ "growth", "potential", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-050.jpg" }, { "filename": "blue-051.jpg", "tags": [ "resilience", "scale", "horizon" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-051.jpg" }, { "filename": "blue-052.jpg", "tags": [ "clarity", "emergence", "vision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-052.jpg" }, { "filename": "blue-053.jpg", "tags": [ "progress", "structure", "momentum" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-053.jpg" }, { "filename": "blue-054.jpg", "tags": [ "focus", "insight", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-054.jpg" }, { "filename": "blue-055.jpg", "tags": [ "direction", "momentum", "progress" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-055.jpg" }, { "filename": "blue-056.jpg", "tags": [ "potential", "innovation", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-056.jpg" }, { "filename": "blue-057.jpg", "tags": [ "structure", "foundation", "layers" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-057.jpg" }, { "filename": "blue-058.jpg", "tags": [ "vision", "potential", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-058.jpg" }, { "filename": "blue-059.jpg", "tags": [ "layers", "structure", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-059.jpg" }, { "filename": "blue-060.jpg", "tags": [ "opportunity", "transition", "direction" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-060.jpg" }, { "filename": "blue-061.jpg", "tags": [ "strategy", "craft", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-061.jpg" }, { "filename": "blue-062.jpg", "tags": [ "excellence", "achievement", "ambition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-062.jpg" }, { "filename": "blue-063.jpg", "tags": [ "excellence", "ambition", "achievement" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-063.jpg" }, { "filename": "blue-064.jpg", "tags": [ "precision", "craft", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-064.jpg" }, { "filename": "blue-065.jpg", "tags": [ "balance", "harmony", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-065.jpg" }, { "filename": "blue-066.jpg", "tags": [ "value", "foundation", "growth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-066.jpg" }, { "filename": "blue-067.jpg", "tags": [ "growth", "potential", "care" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-067.jpg" }, { "filename": "blue-068.jpg", "tags": [ "clarity", "focus", "insight" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-068.jpg" }, { "filename": "blue-069.jpg", "tags": [ "balance", "foundation", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-069.jpg" }, { "filename": "blue-070.jpg", "tags": [ "focus", "balance", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-070.jpg" }, { "filename": "blue-071.jpg", "tags": [ "focus", "harmony", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-071.jpg" }, { "filename": "blue-072.jpg", "tags": [ "scale", "vision", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-072.jpg" }, { "filename": "blue-073.jpg", "tags": [ "depth", "layers", "transformation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-073.jpg" }, { "filename": "blue-074.jpg", "tags": [ "progress", "unity", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-074.jpg" }, { "filename": "blue-075.jpg", "tags": [ "depth", "contrast", "transformation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-075.jpg" }, { "filename": "blue-076.jpg", "tags": [ "care", "values", "trust" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-076.jpg" }, { "filename": "blue-077.jpg", "tags": [ "focus", "clarity", "direction" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-077.jpg" }, { "filename": "blue-078.jpg", "tags": [ "progress", "direction", "unity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-078.jpg" }, { "filename": "blue-079.jpg", "tags": [ "momentum", "ambition", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-079.jpg" }, { "filename": "blue-080.jpg", "tags": [ "emergence", "horizon", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-080.jpg" }, { "filename": "blue-081.jpg", "tags": [ "precision", "discipline", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-081.jpg" }, { "filename": "blue-082.jpg", "tags": [ "precision", "complexity", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-082.jpg" }, { "filename": "blue-083.jpg", "tags": [ "balance", "tension", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-083.jpg" }, { "filename": "blue-084.jpg", "tags": [ "balance", "layers", "harmony" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-084.jpg" }, { "filename": "blue-085.jpg", "tags": [ "vision", "ambition", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-085.jpg" }, { "filename": "blue-086.jpg", "tags": [ "innovation", "focus", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-086.jpg" }, { "filename": "blue-087.jpg", "tags": [ "focus", "craft", "insight" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-087.jpg" }, { "filename": "blue-088.jpg", "tags": [ "clarity", "opportunity", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-088.jpg" }, { "filename": "blue-089.jpg", "tags": [ "progress", "momentum", "discipline" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-089.jpg" }, { "filename": "blue-090.jpg", "tags": [ "progress", "opportunity", "horizon" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-090.jpg" }, { "filename": "blue-091.jpg", "tags": [ "clarity", "structure", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-091.jpg" }, { "filename": "blue-092.jpg", "tags": [ "focus", "insight", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-092.jpg" }, { "filename": "blue-093.jpg", "tags": [ "growth", "emergence", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-093.jpg" }, { "filename": "blue-094.jpg", "tags": [ "trust", "care", "connection" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-094.jpg" }, { "filename": "blue-095.jpg", "tags": [ "connection", "focus", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-095.jpg" }, { "filename": "blue-096.jpg", "tags": [ "simplicity", "balance", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-096.jpg" }, { "filename": "blue-097.jpg", "tags": [ "clarity", "focus", "insight" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-097.jpg" }, { "filename": "blue-098.jpg", "tags": [ "horizon", "calm", "scale" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-098.jpg" }, { "filename": "blue-099.jpg", "tags": [ "energy", "potential", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-099.jpg" }, { "filename": "blue-100.jpg", "tags": [ "resilience", "structure", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-100.jpg" }, { "filename": "blue-102.jpg", "tags": [ "structure", "order", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-102.jpg" }, { "filename": "blue-103.jpg", "tags": [ "innovation", "strategy", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-103.jpg" }, { "filename": "blue-104.jpg", "tags": [ "energy", "focus", "transformation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-104.jpg" }, { "filename": "blue-105.jpg", "tags": [ "balance", "harmony", "contrast" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-105.jpg" }, { "filename": "blue-106.jpg", "tags": [ "balance", "order", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-106.jpg" }, { "filename": "blue-107.jpg", "tags": [ "trust", "connection", "unity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-107.jpg" }, { "filename": "blue-108.jpg", "tags": [ "resilience", "horizon", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-108.jpg" }, { "filename": "blue-109.jpg", "tags": [ "precision", "discipline", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-109.jpg" }, { "filename": "blue-110.jpg", "tags": [ "precision", "craft", "excellence" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-110.jpg" }, { "filename": "blue-111.jpg", "tags": [ "balance", "harmony", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-111.jpg" }, { "filename": "blue-112.jpg", "tags": [ "focus", "flow", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-112.jpg" }, { "filename": "blue-113.jpg", "tags": [ "momentum", "direction", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/blue/blue-113.jpg" }, { "filename": "gradient-001.jpg", "tags": [ "energy", "flow", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-001.jpg" }, { "filename": "gradient-002.jpg", "tags": [ "clarity", "calm", "horizon" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-002.jpg" }, { "filename": "gradient-003.jpg", "tags": [ "emergence", "focus", "vision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-003.jpg" }, { "filename": "gradient-004.jpg", "tags": [ "horizon", "calm", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-004.jpg" }, { "filename": "gradient-005.jpg", "tags": [ "clarity", "simplicity", "openness" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-005.jpg" }, { "filename": "gradient-006.jpg", "tags": [ "contrast", "emergence", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-006.jpg" }, { "filename": "gradient-007.jpg", "tags": [ "depth", "tension", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-007.jpg" }, { "filename": "gradient-008.jpg", "tags": [ "depth", "calm", "subtlety" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-008.jpg" }, { "filename": "gradient-009.jpg", "tags": [ "flow", "energy", "transformation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-009.jpg" }, { "filename": "gradient-010.jpg", "tags": [ "momentum", "direction", "flow" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-010.jpg" }, { "filename": "gradient-011.jpg", "tags": [ "emergence", "horizon", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-011.jpg" }, { "filename": "gradient-012.jpg", "tags": [ "clarity", "expansion", "harmony" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-012.jpg" }, { "filename": "gradient-013.jpg", "tags": [ "clarity", "openness", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-013.jpg" }, { "filename": "gradient-014.jpg", "tags": [ "momentum", "energy", "direction" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-014.jpg" }, { "filename": "gradient-015.jpg", "tags": [ "depth", "flow", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-015.jpg" }, { "filename": "gradient-016.jpg", "tags": [ "calm", "simplicity", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-016.jpg" }, { "filename": "gradient-017.jpg", "tags": [ "direction", "momentum", "progress" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-017.jpg" }, { "filename": "gradient-018.jpg", "tags": [ "flow", "transformation", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-018.jpg" }, { "filename": "gradient-019.jpg", "tags": [ "contrast", "clarity", "transition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-019.jpg" }, { "filename": "gradient-020.jpg", "tags": [ "harmony", "flow", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-020.jpg" }, { "filename": "gradient-021.jpg", "tags": [ "clarity", "expansion", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-021.jpg" }, { "filename": "gradient-022.jpg", "tags": [ "flow", "harmony", "transition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-022.jpg" }, { "filename": "gradient-023.jpg", "tags": [ "emergence", "depth", "horizon" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-023.jpg" }, { "filename": "gradient-024.jpg", "tags": [ "expansion", "energy", "openness" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-024.jpg" }, { "filename": "gradient-025.jpg", "tags": [ "horizon", "clarity", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-025.jpg" }, { "filename": "gradient-026.jpg", "tags": [ "depth", "focus", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-026.jpg" }, { "filename": "gradient-027.jpg", "tags": [ "direction", "emergence", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-027.jpg" }, { "filename": "gradient-028.jpg", "tags": [ "contrast", "depth", "transition" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-028.jpg" }, { "filename": "gradient-029.jpg", "tags": [ "focus", "emergence", "clarity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-029.jpg" }, { "filename": "gradient-030.jpg", "tags": [ "harmony", "clarity", "expansion" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-030.jpg" }, { "filename": "gradient-031.jpg", "tags": [ "openness", "calm", "clarity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-031.jpg" }, { "filename": "gradient-032.jpg", "tags": [ "emergence", "contrast", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-032.jpg" }, { "filename": "gradient-033.jpg", "tags": [ "horizon", "calm", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-033.jpg" }, { "filename": "gradient-034.jpg", "tags": [ "transition", "clarity", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/gradient/gradient-034.jpg" }, { "filename": "green-001.jpg", "tags": [ "strategy", "ambition", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-001.jpg" }, { "filename": "green-002.jpg", "tags": [ "scale", "growth", "progress" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-002.jpg" }, { "filename": "green-003.jpg", "tags": [ "precision", "craft", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-003.jpg" }, { "filename": "green-004.jpg", "tags": [ "layers", "order", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-004.jpg" }, { "filename": "green-005.jpg", "tags": [ "unity", "connection", "scale" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-005.jpg" }, { "filename": "green-006.jpg", "tags": [ "focus", "balance", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-006.jpg" }, { "filename": "green-007.jpg", "tags": [ "momentum", "direction", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-007.jpg" }, { "filename": "green-008.jpg", "tags": [ "craft", "detail", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-008.jpg" }, { "filename": "green-009.jpg", "tags": [ "offering", "value", "care" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-009.jpg" }, { "filename": "green-010.jpg", "tags": [ "flow", "craft", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-010.jpg" }, { "filename": "green-011.jpg", "tags": [ "momentum", "direction", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/green/green-011.jpg" }, { "filename": "orange-001.jpg", "tags": [ "strategy", "ambition", "progress" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-001.jpg" }, { "filename": "orange-002.jpg", "tags": [ "scale", "growth", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-002.jpg" }, { "filename": "orange-003.jpg", "tags": [ "precision", "craft", "clarity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-003.jpg" }, { "filename": "orange-004.jpg", "tags": [ "potential", "craft", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-004.jpg" }, { "filename": "orange-005.jpg", "tags": [ "balance", "form", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-005.jpg" }, { "filename": "orange-006.jpg", "tags": [ "potential", "craft", "connection" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-006.jpg" }, { "filename": "orange-007.jpg", "tags": [ "clarity", "balance", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-007.jpg" }, { "filename": "orange-008.jpg", "tags": [ "structure", "balance", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-008.jpg" }, { "filename": "orange-009.jpg", "tags": [ "growth", "emergence", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-009.jpg" }, { "filename": "orange-010.jpg", "tags": [ "innovation", "energy", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-010.jpg" }, { "filename": "orange-011.jpg", "tags": [ "progress", "ascent", "growth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-011.jpg" }, { "filename": "orange-012.jpg", "tags": [ "depth", "perspective", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-012.jpg" }, { "filename": "orange-013.jpg", "tags": [ "harmony", "balance", "scale" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-013.jpg" }, { "filename": "orange-014.jpg", "tags": [ "focus", "order", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-014.jpg" }, { "filename": "orange-015.jpg", "tags": [ "craft", "simplicity", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-015.jpg" }, { "filename": "orange-016.jpg", "tags": [ "craft", "offering", "balance" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-016.jpg" }, { "filename": "orange-017.jpg", "tags": [ "craft", "flow", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-017.jpg" }, { "filename": "orange-018.jpg", "tags": [ "craft", "offering", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-018.jpg" }, { "filename": "orange-019.jpg", "tags": [ "growth", "potential", "care" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-019.jpg" }, { "filename": "orange-020.jpg", "tags": [ "focus", "discipline", "solitude" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-020.jpg" }, { "filename": "orange-021.jpg", "tags": [ "simplicity", "calm", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-021.jpg" }, { "filename": "orange-022.jpg", "tags": [ "flow", "abundance", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-022.jpg" }, { "filename": "orange-023.jpg", "tags": [ "order", "harmony", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-023.jpg" }, { "filename": "orange-024.jpg", "tags": [ "growth", "vitality", "emergence" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-024.jpg" }, { "filename": "orange-025.jpg", "tags": [ "threshold", "calm", "reflection" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-025.jpg" }, { "filename": "orange-026.jpg", "tags": [ "growth", "care", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-026.jpg" }, { "filename": "orange-027.jpg", "tags": [ "reward", "simplicity", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-027.jpg" }, { "filename": "orange-028.jpg", "tags": [ "craft", "flow", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/orange/orange-028.jpg" }, { "filename": "purple-001.jpg", "tags": [ "strategy", "structure", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-001.jpg" }, { "filename": "purple-002.jpg", "tags": [ "structure", "foundation", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-002.jpg" }, { "filename": "purple-003.jpg", "tags": [ "precision", "craft", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-003.jpg" }, { "filename": "purple-004.jpg", "tags": [ "care", "growth", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-004.jpg" }, { "filename": "purple-005.jpg", "tags": [ "progress", "balance", "emergence" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-005.jpg" }, { "filename": "purple-006.jpg", "tags": [ "growth", "emergence", "craft" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-006.jpg" }, { "filename": "purple-007.jpg", "tags": [ "flow", "craft", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-007.jpg" }, { "filename": "purple-008.jpg", "tags": [ "scale", "horizon", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-008.jpg" }, { "filename": "purple-009.jpg", "tags": [ "depth", "form", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-009.jpg" }, { "filename": "purple-010.jpg", "tags": [ "complexity", "emergence", "layers" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-010.jpg" }, { "filename": "purple-011.jpg", "tags": [ "balance", "foundation", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-011.jpg" }, { "filename": "purple-012.jpg", "tags": [ "horizon", "calm", "emergence" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-012.jpg" }, { "filename": "purple-013.jpg", "tags": [ "structure", "depth", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-013.jpg" }, { "filename": "purple-014.jpg", "tags": [ "flow", "calm", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-014.jpg" }, { "filename": "purple-015.jpg", "tags": [ "structure", "order", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-015.jpg" }, { "filename": "purple-016.jpg", "tags": [ "focus", "emergence", "vision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-016.jpg" }, { "filename": "purple-017.jpg", "tags": [ "momentum", "tension", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-017.jpg" }, { "filename": "purple-018.jpg", "tags": [ "resilience", "complexity", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-018.jpg" }, { "filename": "purple-019.jpg", "tags": [ "clarity", "vision", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-019.jpg" }, { "filename": "purple-020.jpg", "tags": [ "flow", "harmony", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-020.jpg" }, { "filename": "purple-021.jpg", "tags": [ "momentum", "direction", "flow" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-021.jpg" }, { "filename": "purple-022.jpg", "tags": [ "craft", "precision", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-022.jpg" }, { "filename": "purple-023.jpg", "tags": [ "calm", "horizon", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-023.jpg" }, { "filename": "purple-024.jpg", "tags": [ "transformation", "contrast", "tension" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/purple/purple-024.jpg" }, { "filename": "red-001.jpg", "tags": [ "strategy", "ambition", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-001.jpg" }, { "filename": "red-002.jpg", "tags": [ "scale", "growth", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-002.jpg" }, { "filename": "red-003.jpg", "tags": [ "precision", "craft", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-003.jpg" }, { "filename": "red-004.jpg", "tags": [ "momentum", "direction", "energy" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-004.jpg" }, { "filename": "red-005.jpg", "tags": [ "precision", "discipline", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-005.jpg" }, { "filename": "red-006.jpg", "tags": [ "ambition", "launch", "momentum" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-006.jpg" }, { "filename": "red-008.jpg", "tags": [ "craft", "abundance", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-008.jpg" }, { "filename": "red-009.jpg", "tags": [ "knowledge", "solitude", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-009.jpg" }, { "filename": "red-010.jpg", "tags": [ "emergence", "potential", "focus" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-010.jpg" }, { "filename": "red-011.jpg", "tags": [ "knowledge", "calm", "discovery" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-011.jpg" }, { "filename": "red-012.jpg", "tags": [ "emergence", "growth", "simplicity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-012.jpg" }, { "filename": "red-013.jpg", "tags": [ "emergence", "structure", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-013.jpg" }, { "filename": "red-014.jpg", "tags": [ "growth", "vitality", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-014.jpg" }, { "filename": "red-015.jpg", "tags": [ "growth", "harmony", "vitality" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-015.jpg" }, { "filename": "red-016.jpg", "tags": [ "emergence", "balance", "potential" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-016.jpg" }, { "filename": "red-017.jpg", "tags": [ "knowledge", "depth", "solitude" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-017.jpg" }, { "filename": "red-018.jpg", "tags": [ "knowledge", "discovery", "calm" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-018.jpg" }, { "filename": "red-019.jpg", "tags": [ "knowledge", "discovery", "contrast" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-019.jpg" }, { "filename": "red-020.jpg", "tags": [ "balance", "craft", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-020.jpg" }, { "filename": "red-021.jpg", "tags": [ "foundation", "structure", "stability" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-021.jpg" }, { "filename": "red-022.jpg", "tags": [ "progress", "ascent", "vision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-022.jpg" }, { "filename": "red-023.jpg", "tags": [ "layers", "structure", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/red/red-023.jpg" }, { "filename": "white-001.jpg", "tags": [ "precision", "craft", "complexity" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/white/white-001.jpg" }, { "filename": "white-002.jpg", "tags": [ "structure", "foundation", "order" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/white/white-002.jpg" }, { "filename": "white-003.jpg", "tags": [ "strategy", "structure", "precision" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/white/white-003.jpg" }, { "filename": "white-004.jpg", "tags": [ "balance", "tension", "harmony" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/white/white-004.jpg" }, { "filename": "white-005.jpg", "tags": [ "unity", "simplicity", "harmony" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/white/white-005.jpg" }, { "filename": "yellow-001.jpg", "tags": [ "strategy", "ambition", "structure" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/yellow/yellow-001.jpg" }, { "filename": "yellow-002.jpg", "tags": [ "scale", "growth", "foundation" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/yellow/yellow-002.jpg" }, { "filename": "yellow-003.jpg", "tags": [ "precision", "craft", "form" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/yellow/yellow-003.jpg" }, { "filename": "yellow-004.jpg", "tags": [ "layers", "flow", "depth" ], "url": "https://cdn.jsdelivr.net/gh/Gamaleldientarek/azmx-brand-cdn@main/images/yellow/yellow-004.jpg" } ] } } } }, "404": { "description": "Endpoint not found" } } } } }, "components": { "schemas": { "DesignTokens": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "name": { "type": "string" }, "source": { "type": "string" }, "source_version": { "type": "string" }, "exported": { "type": "string" }, "count": { "type": "integer" }, "collections": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "modes": { "type": "array", "items": { "type": "string" } }, "count": { "type": "integer" }, "tokens": { "type": "object", "additionalProperties": { "oneOf": [ { "type": "string" }, { "type": "integer" }, { "type": "number" }, { "type": "array", "items": { "type": "string" } } ] } } }, "required": [ "name", "modes", "count", "tokens" ] } } }, "required": [ "version", "description", "name", "source", "source_version", "exported", "count", "collections" ], "description": "AZM X Design Tokens - 601 design tokens across 6 collections" }, "ColorPalettes": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "count": { "type": "integer" }, "palettes": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "description": { "type": "string" }, "ramp": { "type": "array", "items": { "type": "object", "properties": { "step": { "type": "string" }, "hex": { "type": "string" }, "notes": { "type": "string" } }, "required": [ "step", "hex", "notes" ] } }, "signature": { "type": "string" }, "deep": { "type": "string" }, "text_safe_step": { "type": "string" }, "text_safe_hex": { "type": "string" } }, "required": [ "name", "description" ] } } }, "required": [ "version", "description", "count", "palettes" ], "description": "AZMX color palettes - one primary (Blue) and five secondary palettes" }, "TypographySystem": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "families": { "type": "array", "items": { "type": "object", "properties": { "role": { "type": "string" }, "family": { "type": "string" }, "variable": { "type": "string" }, "variable_id": { "type": "string" }, "notes": { "type": "string" } }, "required": [ "role", "family", "variable", "variable_id", "notes" ] } }, "weights": { "type": "array", "items": { "type": "object", "properties": { "weight": { "type": "string" }, "variable_id": { "type": "string" } }, "required": [ "weight", "variable_id" ] } }, "type_scale": { "type": "array", "items": { "type": "object", "properties": { "role": { "type": "string" }, "font": { "type": "string" }, "size": { "type": "string" }, "line_height": { "type": "string" }, "weight": { "type": "string" }, "tracking": { "type": "number" }, "case_style": { "type": "string" } }, "required": [ "role", "font", "size", "line_height", "weight", "tracking", "case_style" ] } }, "rules": { "type": "array", "items": { "type": "string" } }, "bilingual_note": { "type": "string" } }, "required": [ "version", "description", "families", "weights", "type_scale", "rules", "bilingual_note" ], "description": "AZMX typography system - font families, weights, type scale, and usage rules" }, "VoiceAndToneGuidelines": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "brand_language": { "type": "object", "properties": { "tagline": { "type": "string" }, "philosophy": { "type": "string" }, "boilerplate": { "type": "string" } }, "required": [ "tagline", "philosophy", "boilerplate" ] }, "voice_summary": { "type": "string" }, "tone_rules": { "type": "array", "items": { "type": "object", "properties": { "number": { "type": "string" }, "heading": { "type": "string" }, "description": { "type": "string" } }, "required": [ "number", "heading", "description" ] } }, "dimensions": { "type": "array", "items": { "type": "object", "properties": { "dimension": { "type": "string" }, "position": { "type": "string" }, "we_are": { "type": "string" }, "we_are_not": { "type": "string" } }, "required": [ "dimension", "position", "we_are", "we_are_not" ] } }, "calibration_examples": { "type": "array", "items": { "type": "object", "properties": { "dimension": { "type": "string" }, "wrong_formal": { "type": "string" }, "wrong_informal": { "type": "string" }, "azmx_voice": { "type": "string" } }, "required": [ "dimension", "wrong_formal", "wrong_informal", "azmx_voice" ] } }, "purpose_modes": { "type": "array", "items": { "type": "object", "properties": { "mode": { "type": "string" }, "surfaces": { "type": "string" }, "goal": { "type": "string" }, "example": { "type": "string" } }, "required": [ "mode", "surfaces", "goal", "example" ] } }, "writing_mechanics": { "type": "array", "items": { "type": "string" } }, "universal_principles": { "type": "array", "items": { "type": "object", "properties": { "principle": { "type": "string" }, "description": { "type": "string" } }, "required": [ "principle", "description" ] } }, "format_rules": { "type": "array", "items": { "type": "object", "properties": { "format": { "type": "string" }, "rules": { "type": "string" } }, "required": [ "format", "rules" ] } }, "platform_voice": { "type": "array", "items": { "type": "object", "properties": { "platform": { "type": "string" }, "voice": { "type": "string" }, "guidelines": { "type": "string" } }, "required": [ "platform", "voice", "guidelines" ] } }, "strategy_superseded": { "type": "array", "items": { "type": "object", "properties": { "deck_says": { "type": "string" }, "azmx_voice": { "type": "string" } }, "required": [ "deck_says", "azmx_voice" ] } }, "pre_publish_checklist": { "type": "array", "items": { "type": "object", "properties": { "number": { "type": "string" }, "heading": { "type": "string" }, "description": { "type": "string" } }, "required": [ "number", "heading", "description" ] } }, "quick_self_check": { "type": "array", "items": { "type": "string" } } }, "required": [ "version", "description", "brand_language", "voice_summary", "tone_rules", "dimensions", "calibration_examples", "purpose_modes", "writing_mechanics", "universal_principles", "format_rules", "platform_voice", "strategy_superseded", "pre_publish_checklist", "quick_self_check" ], "description": "AZMX voice and tone - brand language, tone rules, the four voice dimensions, writing mechanics, format rules, and platform-specific voice" }, "AudiencePersonas": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "count": { "type": "integer" }, "personas": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "motion": { "type": "string" }, "brands": { "type": "array", "items": { "type": "string" } }, "pain_points": { "type": "string" }, "core_message": { "type": "string" } }, "required": [ "name", "motion", "brands", "pain_points", "core_message" ] } }, "internal_audiences": { "type": "array", "items": { "type": "object", "properties": { "segment": { "type": "string" }, "needs": { "type": "string" }, "core_message": { "type": "string" } }, "required": [ "segment", "needs", "core_message" ] } }, "external_motions": { "type": "array", "items": { "type": "object", "properties": { "motion": { "type": "string" }, "brands": { "type": "array", "items": { "type": "string" } }, "needs": { "type": "string" }, "core_message": { "type": "string" } }, "required": [ "motion", "brands", "needs", "core_message" ] } }, "brands": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "description": { "type": "string" }, "motions": { "type": "array", "items": { "type": "string" } } }, "required": [ "name", "description", "motions" ] } } }, "required": [ "version", "description", "count", "personas", "internal_audiences", "external_motions", "brands" ], "description": "AZMX audience personas and messaging - 8 external personas, internal audiences, external motions, and brands" }, "ContentPromptTemplates": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "count": { "type": "integer" }, "prompts": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string" }, "number": { "type": "integer" }, "title": { "type": "string" }, "description": { "type": "string" }, "deck_page": { "type": "string", "nullable": true }, "template": { "type": "string" }, "notes": { "type": "string", "nullable": true } }, "required": [ "id", "number", "title", "description", "deck_page", "template", "notes" ] } } }, "required": [ "version", "description", "count", "prompts" ], "description": "AZMX content generation prompt templates - briefs, articles, case studies, social customisation, and localisation" }, "BrandImageLibrary": { "type": "object", "properties": { "version": { "type": "string" }, "description": { "type": "string" }, "count": { "type": "integer" }, "cdn": { "type": "string" }, "images": { "type": "array", "items": { "type": "object", "properties": { "filename": { "type": "string" }, "tags": { "type": "array", "items": { "type": "string" } }, "url": { "type": "string" } }, "required": [ "filename", "tags", "url" ] } } }, "required": [ "version", "description", "count", "cdn", "images" ], "description": "AZMX brand images with conceptual tags" } } } }
` must have `dir=\"rtl\"`. Wrap chevrons in `‹`. Wrap all Latin fragments (dates, numerals, URLs) in ``. Set inline `text-align:right` on all RTL text cells. Example: `نص عربي