Visual DNA — RankFlow AI

This is the source of truth for all image-generation prompts used by RankFlow AI.

The homepage docs still reflect an older gold-and-navy system. The active visual language is the locked Rise / Quiet Signal brand. All prompts must preserve the page strategy while expressing the current brand system.

1. Master Style Prefix#

Quiet Signal / Rise visual DNA. Swiss editorial product illustration or product-interface render for appointment-led Indian local business software. Paper White #F6F6F8 canvas, Card White #FFFFFF surfaces, Deep Ink #011821 structure and typography, Graphite #3B3E47 secondary information, Mist #E3E4E8 guides and borders, single Ember Orange #EC652B reserved only for directional signal, active flow, booked outcome, and the logic of the RankFlow Rise mark. Precision 1.5px linework, orthographic or shallow isometric at most, asymmetrical left-weighted composition, strict 12-column grid, 4px spacing discipline, 8px UI radius, high-end grotesk typography equivalent to Suisse Intl and Suisse Intl Mono if labels are unavoidable, calm premium whitespace, no decorative clutter, export-clean.

2. Negative Suffix#

No stock-photo look, no faces, no mascots, no photoreal people, no medical cross as hero symbol, no stethoscope cliché, no map-pin as the main logo idea, no AI purple, no neon, no glossy gradients, no blue glows, no decorative particles, no fantasy dashboard clutter, no generic three-card SaaS layout, no bubbly consumer-health UI, no oversized KPI tiles, no clipart, only #EC652B as the accent color.

3. Visual Rules#

Palette#

Composition#

• 12-column grid
• 4px base spacing
• 8px standard component radius
• 35-50% breathing space on most compositions
• asymmetry over centered balance
• orthographic or restrained isometric only
• image plates should leave calm zones for HTML overlays whenever possible

Typography In Images#

• Prefer no baked text
• If text is necessary, keep it minimal and structural
• Use neutral grotesk + mono logic
• Caption case or compact uppercase only
• Avoid long readable marketing copy inside generated images

Accent Discipline#

• Orange must point to a flow, active route, booking action, publish event, or completion state
• Orange must not be used as a wash, atmosphere, or decorative glow
• Forest Teal is reserved for verified or live confirmation

4. Asset Types We Actually Generate#

5. Assets That Must Stay Code-Native Or Source-Native#

• RankFlow logo and mark
• Section 1A orbit diagram
• Section 3 loop animation / SVG / Lottie
• customer logos
• backer logos
• compliance badges

Do not send those through image generation.

6. Prompt Formula#

Every production prompt should follow this exact structure:

[MASTER STYLE PREFIX]
Asset: [what it is]
Format: [dimensions + orientation]
Layout: [where empty space goes, how the composition is weighted]
Subject: [the actual objects or UI shown]
Elements: [specific components, modules, environment pieces]
Accent behavior: [exactly where #EC652B appears]
Text policy: [no text / tiny structural labels only / exact text if unavoidable]
Output notes: [clean plate / overlay-safe / product-buildable]
[NEGATIVE SUFFIX]

7. Quality Gate#

• Uses #011821, not legacy deep navy
• Uses #EC652B, not legacy gold
• Orange appears only in active signal moments
• Image can plausibly be rebuilt in frontend code
• No AI-slop dashboard clutter
• No stock-medical clichés
• No excessive perspective, glow, or decorative effects