@chessceo/mcp 0.19.0 → 0.24.0

package/docs/prep-files-guide.md

@@ -25,40 +25,18 @@ Six tools:
 
 Duplicate files are the #1 way to lose your user's trust in this system.
 
-## PGN structure
-
-Real chess prep files are PGN with parenthesised variations. Learn the shape:
-
-```pgn
-[Event "Prep vs Firouzja (Black) — 2026-07-23"]
-[White "Firouzja, Alireza"]
-[Black "Van Foreest, Jorden"]
-[Date "2026.07.23"]
-
-1. e4 c5 2. Nf3 d6 3. d4 cxd4 4. Nxd4 Nf6 5. Nc3 a6 6. Be3 e5 7. Nb3
-{Main line. Firouzja plays this in 68% of his English Attacks (32 games, 2023-2025).}
-7... Be6 8. f3
-(8. Qd2 Nbd7 9. f3 h5 {Sideline he tried once and lost — probably patched.})
-8... Nbd7 9. Qd2 h5
-{Critical position for us. Lc0 at multipv=3 gives:
- - h5: +0.12 (main line, active)
- - Be7: +0.08 (calm, more classical)
- - Rc8: 0.00 (Stockfish preferred)}
-
-*
-```
+## PGN authoring — separate concern
+
+Everything about **how to write good PGN** (structure, NAGs, arrows, coloured squares, variation discipline, common pitfalls) lives in `pgn-authoring.md` — call `read_pgn_authoring_guide` for the full doc. That guide is universal to any chess file you might write; this guide is about the prep-files *feature* on top.
+
+Minimum you should know before calling `save_prep_file`:
+
+- Mainline = your top recommendation. Alternative candidates go in parenthesised variations at the branching move.
+- **Variations are MOVES**, not prose describing moves. `7...Be6 (7...h5 8.Nd5)` — never `{if Black plays h5 White responds with Nd5}`.
+- **Plans, prep-signal, and interpretation** go in `{curly-brace comments}`. Cite tool output; don't invent chess prose.
+- `Event` tag is the file's user-facing name.
 
-The pieces:
-
-- **PGN tag pairs at the top** (`[Key "Value"]`) — `Event` is the name you show the user. `White` / `Black` set the game headers. `Date` is standard.
-- **Mainline** = your top recommendation. Numbered SAN moves separated by whitespace.
-- **Variations** in parentheses `(...)` at the branching move. Nesting is allowed but be conservative — three deep is a lot.
-- **Comments** in curly braces `{...}` between moves. This is where you cite tool output:
-  - `{Lc0 says +0.15 in this line vs 0.00 for the alternative}`
-  - `{Firouzja plays this in 32/47 games with Black. Scores 41%.}`
-  - `{Stockfish sees h4 as a tactical shot; Lc0 disagrees. Deep look needed.}`
-- **NAG glyphs** for evaluations at a move (optional): `$1` (!), `$2` (?), `$3` (!!), `$4` (??), `$6` (=), `$10` (=), `$14` (+/=). Placed right after the SAN: `7. Nb3 $1`.
-- **Result marker** at the end: `*` for unfinished (prep files are always unfinished), `1-0`, `0-1`, `1/2-1/2`.
+Full details, NAG table, arrow/highlight syntax, and worked example: `read_pgn_authoring_guide`.
 
 ## Editing without breaking the tree
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chessceo/mcp",
-  "version": "0.19.0",
+  "version": "0.24.0",
   "description": "Model Context Protocol server for chess.ceo — 11.7M+ games, ~1.5M FIDE player profiles, opening preparation, live broadcasts.",
   "type": "module",
   "bin": {
@@ -43,6 +43,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.0.0",
     "chess.js": "^1.4.0",
+    "chessops": "^0.15.1",
     "zod": "^3.23.0"
   },
   "devDependencies": {