chore(gocuke): mention incompatibility with LSP

Amolith created

Change summary

README.md                                       | 10 +++++-----
skills/testing-with-gocuke-and-gherkin/SKILL.md |  4 ++++
2 files changed, 9 insertions(+), 5 deletions(-)

Detailed changes

README.md 🔗 

@@ -410,13 +410,13 @@ Token breakdown:
 Token breakdown:
   Name:           14 tokens
   Description:    73 tokens
-  Body:         1127 tokens (101 lines)
+  Body:         1188 tokens (105 lines)
   References:
     bdd-practices.md                          1035 tokens
     gherkin-reference.md                       984 tokens
     gocuke-api.md                             1427 tokens
   ───────────────────────────────────────────────
-  Total:        4660 tokens
+  Total:        4721 tokens
 
 === working-with-tmux ===
 
@@ -468,15 +468,15 @@ SUMMARY
 
 Skills: 23
 Metadata: 1304 tokens
-Combined bodies: 22964 tokens
-Overall: 73962 tokens
+Combined bodies: 23025 tokens
+Overall: 74023 tokens
 Validation errors: 0
 
 Largest skills (by total tokens):
   1. writing-roc-lang                         30837 tokens
   2. ast-grep                                  5363 tokens
   3. frontend-accessibility                    4759 tokens
-  4. testing-with-gocuke-and-gherkin           4660 tokens
+  4. testing-with-gocuke-and-gherkin           4721 tokens
   5. authoring-skills                          3706 tokens
 ```

skills/testing-with-gocuke-and-gherkin/SKILL.md 🔗 

@@ -102,6 +102,10 @@ When the project has informal markdown specs with Gherkin-ish structure (bullet-
 
 The goal is feature files that a non-developer could read and confirm: "yes, that's the behaviour we want."
 
+## Editor tooling
+
+The Cucumber language server cannot discover gocuke step definitions. It expects explicit registration calls (Godog-style `ctx.Given("pattern", fn)`), not gocuke's runtime reflection. "Undefined step" warnings are false positives; disable the Cucumber language server for gocuke projects.
+
 ## Further reference
 
 - **BDD practices (Discovery, Formulation, Automation)**: See [references/bdd-practices.md](references/bdd-practices.md)