This reference does not add architecture. It makes the frozen distinctions operational.
Smothered Mate vs Philidor's Legacy
Smothered Mate
- final checker: knight;
- king surrounded by own pieces;
- general pattern.
Philidor's Legacy
- forcing combination ending in smothered mate;
- commonly includes queen sacrifice/forced recapture;
- specific sequence family.
Never use as universal synonyms.
Arabian vs Anastasia vs Hook
Arabian
- rook + knight;
- archetypal corner geometry;
- knight protects rook and removes key flight.
Anastasia
- rook/queen + knight;
- king on edge;
- knight removes inner flights;
- self-blocking pawn/piece closes remaining escape.
Hook
- rook + knight + pawn support chain;
- knight protects rook and is often protected by pawn;
- defending pawn/piece commonly limits final flight.
Same piece family can produce different mating pattern.
Back-Rank Weakness vs Back-Rank Mate
Weakness
Potential vulnerability:
- king lacks luft;
- self-blocked by own pieces.
Mate
Current legal result:
- heavy-piece check;
- no escape/capture/block.
Epaulette vs Dovetail vs Swallow's Tail
All use self-blocking around king, often queen mate.
Epaulette
- two side/shoulder squares occupied by own pieces.
Dovetail/Cozio
- queen mate with characteristic pair of self-blockers in dovetail arrangement.
Swallow's Tail
- related but mirrored/different V-shaped self-block orientation.
Greco vs Morphy vs Opera
All can involve rook/queen plus bishop, but names attach to different recurring/historical geometries.
Greco
- heavy-piece edge-file/rank mate;
- bishop controls inner flight.
Morphy
- rook+bishop against castled/edge king with self-blocking shelter/rook often contributing.
Opera
- final rook+bishop geometry abstracted from Morphy's Opera Game finish.
Do not label every rook+bishop mate with a historical name.
Damiano final geometry vs common h-file route
Final geometry
- queen mates close to king;
- supported by pawn/bishop;
- king restricted.
Common route
- rook sacrifice/open h-file;
- queen enters.
Route ≠ definition.
Légal Mate vs Légal Trap
Mate
Final minor-piece mating geometry.
Trap
Opening combination/trap, commonly involving apparent queen sacrifice, that can lead to mate/material gain.
Blind Swine vs Ladder
Ladder
Two major pieces create successive parallel barriers and drive king to edge.
Blind Swine
Two rooks penetrate seventh/second rank and coordinate lateral checks/captures around confined king.
Both use two rooks; mechanism differs.
Supported mate vs named mate
Supported mate is a generic function:
- checker protected.
A named pattern may also be supported.
Therefore:
- generic mechanism can overlap named family;
- a generic mechanism can overlap a named family, so one label does not exclude another.
Pattern Identification Template
For any named mating pattern, record the final checker, support pieces, controlled flights, self-blockers, board-edge role, typical aliases and the feature that distinguishes it from its nearest lookalike.
Anti-pattern questions
For every named pattern, study near-misses such as:
- same pieces, wrong king placement;
- same visual shape, one flight open;
- checker capturable;
- support removed;
- interposition possible;
- pattern achieved but move is illegal due own king;
- related pattern with different exact geometry.
Recognition should survive rotation and reject near-misses.
Compare Functions Before Labels
When two patterns look similar, fill in the same functional template for both:
| Question | Pattern A | Pattern B |
|---|---|---|
| Final checker | ? | ? |
| Checker support | ? | ? |
| King's location | ? | ? |
| Self-blocking pieces | ? | ? |
| Key controlled flights | ? | ? |
| Typical forcing route | ? | ? |
| Defining difference | ? | ? |
This turns pattern comparison into chess analysis rather than vocabulary recall.
The Key Distinction: Smothered Mate vs Philidor's Legacy
The defining position of a smothered mate is the final geometry: a knight mates a king that has no flight because its own pieces surround it.
Philidor's Legacy refers to a traditional forcing combination that commonly produces that geometry, often involving a queen sacrifice that forces a defender to occupy a critical square before the knight mates.
So:
- smothered mate = final mating family;
- Philidor's Legacy = famous route/combinational pattern.
Geometry Check: Arabian, Anastasia and Hook
These patterns can all involve rook-and-knight cooperation near an edge king.
Do not identify them from the piece list alone. Compare:
- which square the knight controls;
- where the rook gives check;
- whether a pawn/self-blocker completes the cage;
- whether another attacker supports the rook.
If the geometry does not match a stable definition, describe it functionally rather than forcing a name.
Self-Block Geometry: Epaulette, Dovetail and Swallow's Tail
These are queen-mate families in which the defender's own pieces occupy characteristic escape squares around the king.
The names are especially vulnerable to diagram-set variation. For durable learning, record the exact self-blocking squares and queen-control geometry. The label comes second.
Functional Comparison: Greco, Morphy and Opera
These names are often associated with heavy-piece entry supported by bishops or other line pieces. Their historical examples and modern pattern definitions should not be collapsed into one story.
A practical comparison asks:
- who checks?
- what supports the checker?
- which line has been opened?
- which defensive square has disappeared?
Sequence vs Finish: Légal Mate and Légal Trap
A mate pattern is the final geometry. A trap is the move sequence or opening idea that induces the opponent into a tactical loss.
The Légal family is a particularly useful reminder that a famous trap may culminate in a recognizable mate, but not every occurrence of one implies the other.
Same Pieces, Different Mechanism: Blind Swine and Ladder
Both may use two rooks, but their roles differ.
Ladder mate uses alternating parallel barriers to drive a king toward the edge.
Blind-swine attacks typically involve deeply active paired rooks, often around the seventh rank, creating checks, captures and mating threats against a king with limited mobility.
Same material does not mean same mechanism.
Named Pattern vs Generic Mechanism
A position can be a supported mate, edge mate, self-block mate or battery mate without belonging to a famous named family.
That is not a deficiency. Generic mechanisms are often more useful because they describe the function directly.
When classification is uncertain, prefer:
rook edge mate supported by knight; king self-blocked by pawn
rather than an unsupported historical label.
Final Classification Checklist
Before naming a pattern, ask:
- Is it actually mate?
- Does the supposed defining piece perform the expected function?
- Is one characteristic blocker missing?
- Is the familiar arrangement only the threat of the named mate?
- Is the position the final geometry, or merely a forcing route into it?
- Would another reputable source plausibly use a different alias?
These questions make the reference useful across books, languages and puzzle platforms that do not always use identical naming conventions.