Until this month, the only mark on my site was an AI-generated avatar made from a photo. I wanted my name to work as a brand, so I needed a real logo. In about two hours I designed one with AI: a geometric falcon's head, because Tuğrul is a bird of prey in Turkish mythology, with the Orkhon rune 𐱃 as its face marking. The logo isn't an image file. It's a few named numbers in TypeScript, 11 unit tests guard it, and the same source draws all nine of the site's icons.
Here's how it got there: the AI clichés I started with, the research that fixed them, and the engineering that keeps it consistent.
TL;DR
- AI on its own gave me twelve generic logos. AI working from research-backed design rules gave me one I'm proud of.
- The logo is code: a circle, an arc and a rune on a 64-unit grid, and one source for the header, favicon, app icons and share card.
- Tests treat the design rules as requirements: geometry, contrast and icon files can't drift.
Why did I need a logo?
A personal brand needs something people recognise at a glance, in a browser tab or beside a LinkedIn post. An avatar of my face worked as a photo, not a brand. I wanted a mark that is mine in meaning, not just my initials.
Two things were already mine: my name and the script it can be written in. Tuğrul means a bird of prey, and I've always embraced that. The Orkhon runes, the old Turkic script, already sign this site: the runic seal in the footer spells my name in them. Being creative matters when you want to stand apart, so the logo had to come from that story.
What went wrong with the first AI logos?
My first attempt produced twelve AI-generated directions, and most were forgettable. There was a lowercase "ts" in a black square, a <ts/> code tag in terminal green, a falcon drawn wing by wing to form a T, and a heavy seal. Each one looked like a logo. None looked like me.
Round one: four of the twelve AI directions, redrawn from the first canvas. Competent, generic, and full of developer clichés.
The problem wasn't the tool's skill. I had asked for a logo without telling it what makes a logo good.
What changed when I researched how logos are made?
I used Claude's Research feature to write myself a brand guide: how professional designers build marks, with sources. Then I asked the AI to redraw its best ideas by those rules, and within five rounds of studies the logo appeared.
The guide's core idea came from Paul Rand, who designed the IBM and ABC logos: "A logo doesn't sell (directly), it identifies." My logo doesn't need to say "software engineer". It needs to identify me.
Each rule changed the design in a specific way:
| Rule from the research | What it changed |
|---|---|
| Keep it simple | The head became one circle, one straight forehead and one arc for the beak. The rune is the only detail. |
| Suggest, don't illustrate | No feathers or wings. Only the eye, the hooked beak and the face stripe say "falcon". |
| Design in black and white first | The rune and eye are cut out of the head, so the mark works in a single ink and reversed. Colour came last. |
| Test at 16 pixels | At favicon size the rune's thin lines turn to mush, so there's a separate small version with just the eye and the stripe. |
| One accent colour | Turquoise for the mark and a touch of gold for the eye, chosen from five schemes, each checked for contrast in light and dark mode. |
I didn't follow the guide everywhere. It recommended a "TS" monogram and warned against falcons. I kept its rules and ignored that suggestion, because a falcon drawn by suggestion meets every rule and says far more about me than two initials.
What do the falcon and the rune mean?
Behind the Name traces Tuğrul to the Turkish word for a mythical bird of prey, from a Turkic word meaning "falcon", and notes it was the name of the 11th-century founder of the Seljuk Empire.
The rune 𐱃 is the T of Tuğrul in the Orkhon script, the alphabet of the 8th-century Orkhon inscriptions and long out of everyday use. It's the same rune that opens my footer seal, so the logo and the signature share a letter. On the falcon it does double duty: its chevron becomes the brow, and its stem and diamond become the dark stripe under a falcon's eye.
How is the logo constructed?
The whole mark is drawn on a 64-by-64 grid from a handful of numbers. A circle with a radius of 22 forms the crown, an arc with a radius of 12 forms the hooked beak, and a straight line joins them as the forehead. The eye is a circle of radius 4.1, and the rune is scaled 4.2 times and centred on it.
The original post has an interactive version of this figure: toggle the construction lines and resize the mark. Try it on my site.
The numbers live in one file, named rather than magic:
export const GRID = 64; export const HEAD = { crown: { centre: { x: 30, y: 30 }, radius: 22, from: 180, to: -50 }, beakTop: { x: 57, y: 27 }, beak: { radius: 12, tip: { x: 54, y: 39 } }, // …gape, throat and neck points } as const; export const EYE = { centre: { x: 36, y: 24 }, radius: 4.1 } as const; Everything else is computed from them, so changing one number redraws every version of the logo. The rune and eye are cut out with an SVG mask rather than painted on top, which is why the mark stays a single colour and works on any background.
One source, nine icons
Every icon the site needs is generated from that geometry at build time, so there's no folder of exported PNGs to keep in sync.
| Output | Where it appears |
|---|---|
| Header logo | Next to the site name on every page |
icon.svg | Browser tabs; it recolours itself in dark mode |
favicon.ico | Older browsers and bookmarks |
| Apple icon | iPhone and iPad home screens |
| 4 app icons (2 maskable) | Android home screens, where the system crops icons into circles |
| Share card | Link previews on LinkedIn, Slack and X |
The real files, as this site serves them: the browser-tab icon, the Apple home-screen icon, an Android app icon and the share card. All four come from the same geometry.
How do you test a logo?
I treat the design rules as requirements and check them with 11 unit tests. If a future change breaks one, CI fails before anything ships.
- Geometry: every point stays inside the grid, and the crown is exactly the arc I designed.
- Rune placement: the rune is the footer seal's own shape, its diamond never touches the throat, and the eye sits where the stem meets the chevron.
- App icons: the crown, beak and eye stay inside the circle Android keeps when it crops an icon.
- Colour: the logo's colours match the site's design tokens, and the mark keeps at least 3:1 contrast with the page, the accessibility minimum for graphics. It measures 5.4:1 in light mode and 8.1:1 in dark mode.
- Files: the committed
icon.svgmust match what the code generates, and the rune must be a real cut-out, not paint.
Results
| Measure | Before | After |
|---|---|---|
| Identity | AI avatar from a photo | A falcon-and-rune mark with a story |
| Directions explored | 12 generic AI logos | 5 rounds of studies, then 1 mark |
| Icons | None of my own | 9 outputs from one source |
| Safety net | None | 11 tests; contrast 5.4:1 light, 8.1:1 dark |
From research-backed studies to merged code took about two hours, and the whole logo shipped as 338 lines in src/lib/logo.
What I learned about designing with AI
AI is very fast at producing options and poor at judging them. Asked for "a logo", it gives you the average of every logo it has seen. Give it real design principles and concrete tests, and it produces work worth choosing from.
The choices stayed mine: the falcon over the monogram, the rune, turquoise over cobalt. The research gave me the vocabulary to make them. Writing the result as tested code means the mark I chose is the mark that ships, at every size.
I write about building this site and the engineering behind it. Follow me on LinkedIn for the next post.







