KiriBaku

Why this name is shaped the way it is

Both surnames cut to four letters, both still obvious afterwards. This is the shape a blend takes when neither name needs help, and it is why this fandom sustains several near-identical constructions without confusion.

What our own engine would have built

Handed Kirishima and Bakugou with no knowledge of the fandom, the blender proposes Bakushima, Kirisugou, Bakuhima, Kiriugou, Kirisgou, Bakugishima. KiriBaku is not among them. That is the normal result, and it is the clearest illustration of why this site refuses to call any candidate the best one. A community picked KiriBaku for reasons no software can see.

Reading it out loud

The join sits at ib, and that is the part worth saying aloud before committing to a name. KiriBaku carries it without trouble, which is a large part of why it stuck: a ship name has to survive being said in a sentence, not only being typed into a tag. It matters more than it sounds. A blend that reads cleanly on a page and stumbles in speech tends to lose to a plainer alternative, however elegant it looked when it was written down.

If you are naming a pairing of your own

The useful lesson from KiriBaku is not the name itself but what it kept. A blend that works holds enough of both halves that a reader who knows Kirishima and Bakugou recognises them without being told, and stops there. Taking more from one side than the other is what produces a name that reads as one person rather than two.

If you want to run the same check on a name of your own, the draft checker does exactly what produced the breakdown above, and the ship name generator builds candidates from two names you supply. The method behind the scoring explains what the coverage figures mean and, more importantly, what they cannot tell you.