FT Visual Style

Core direction

Create a single iconic visual on a near-black, charcoal, or otherwise restrained field. The image should feel nocturnal, technical, and intentional: generous negative space, a clear focal discontinuity, and a limited palette with one identity hue carrying most of the energy.

Use one primary motif, not a collage. Favor faceted or sculptural forms, translucent energy, signal geometry, flowing line bundles, mesh/network connections, or precise technical marks. Render with controlled depth: crisp silhouette, selective rim light, a soft localized glow, and subtle atmospheric color blooms. Treat darkness and quiet zones as composition, not unused space.

Palette and material

• Start with an obsidian or cool-charcoal base.
• Choose the project’s signature hue; keep saturation concentrated at the focal point.
• Use a second hue only when it clarifies a relationship, direction, or data flow.
• Keep neutrals near-white, soft gray, and dark plate tones.
• Prefer faceted matte surfaces, smoky/translucent ribbons, fine grids, grain, or glass-like layers over generic smooth gradients.
• Use the project-specific palette when it is known. Typical identity directions include ember orange, vivid green, cyan with coral, ultraviolet, or magenta/cyan signal light.

Composition

• Reserve broad quiet space for product copy or UI overlay, but do not render text into generated artwork.
• Center or offset one hero object; support it with only a few particles, hairlines, nodes, or directional traces.
• Use a deliberate void, dark channel, or clean field to create contrast with the luminous subject.
• For social cards, keep the mark/object distinct and leave a calm copy zone rather than filling the frame.
• Make small-scale silhouettes survive favicon or app-icon reduction.

Logos and marks

For a logo, app mark, or favicon, request a fully transparent background by default. State that the alpha channel must remain transparent around the mark and that the image must not simulate transparency with a dark, white, checkerboard, or scenic field. Use an opaque background only when the user explicitly asks for a lockup, social card, or other composed artwork.

Keep the silhouette simple enough to survive small-size reduction. Avoid rendered words beyond the exact text the user explicitly requests.

Prompt structure

Write prompts in this order: subject, concept, composition, material/light, palette, texture, and exclusions. Name the chosen project hue and what it represents. Explain why the negative space exists.

Example direction:

A single faceted violet core suspended in a near-black field, with two translucent signal ribbons curling around it and a narrow vertical quiet channel beside the core. Sparse cyan and magenta frequency marks imply data flow without becoming a dashboard. Sculptural matte depth, sharp rim highlights, fine technical grain, generous empty space for adjacent copy. No text, no stock-photo people, no generic blue SaaS gradient, no busy collage.

Avoid

• Generic blue-purple SaaS gradients or undirected neon.
• Flat clip art, glossy plastic, photorealistic stock scenes, or crowded dashboard fragments.
• More than one dominant object.
• Dense decoration across the whole canvas.
• Rendered text, logos copied from an existing project, or project-specific mascots unless explicitly requested.
• Treating all projects as violet: the shared language is dark restraint and concentrated identity color, not one fixed palette.