Chess puzzles are great, but they isolate the winning moment for you. Your games hide tactics without you knowing. This intuition check and system can help find tactics like forks, pins, skewers, and discovered attacks faster:
Start with an intuition check on every move
Ask these three questions before picking candidate moves:
What are the weaknesses on the board? Look for targets.
What is the worst placed piece? Improve it or activate it.
What is my opponent intending? Prophylaxis saves games.
This helps keeps your focus on the right areas so tactical ideas pop naturally.
A system for every move
Forcing moves first: List checks, then captures, then threats. Calculate the forcing lines first.
Loose and overloaded pieces: Count attackers and defenders. Undefended or singly defended pieces likely can fall to tactics.
Files and Ranks: Scan files, ranks, and diagonals for piece alignments that create pins, skewers, and x rays.
Discovered possibilities: Ask what becomes uncovered if a piece moves. If the uncovered line gives check or capture values, you may have a discovered attack or double attack.
Using sites like Lichess and ChessTempo you can find the common puzzles / themes in games. Using the Chess Coach with the above system and check will help you spot tactics in your games.
I have been working on creating a chess coach to help myself and players improve.
In particular, surfacing tactical concepts like pins, skewers, discovered attacks and forks in games proved to be tricky.
I have been testing out a few implementations and have some decent results for a first pass but also many learnings.
For example, to make a move that forks two others pieces is more beneficial (from a material gain perspective) when those pieces are unprotected or not protected well.
Yet in chess.com definitions page of a fork I see "A fork is a basic chess tactic that consists of a single piece attacking two or more pieces at the same time. The attacking piece is known as the forking piece, while the attacked troops are known as the forked pieces."
This definition is great but does not mention any concept of protection vs un-protection of pieces.
I mention this because to program rules around when a fork / tactics should be triggered was an interesting process.
Thank you! The project in its current state includes all the capabilities I initially aimed for. So, I've been working on different projects to expand my portfolio for some time now, while making minor improvements to this one based on feedback like yours."
