diff --git a/modules/home/claude-code/skills/haskell/SKILL.md b/modules/home/claude-code/skills/haskell/SKILL.md
index 38773d8..c501c20 100644
--- a/modules/home/claude-code/skills/haskell/SKILL.md
+++ b/modules/home/claude-code/skills/haskell/SKILL.md
@@ -120,10 +120,10 @@ When using relude prelude, follow these HLint recommendations (from https://gith
 
 ## Build instructions
 
-As you make code changes, start a subagent in parallel to resolve any compile errors in `ghcid.log`.
+As you make code changes, start a subagent in parallel to resolve any compile errors in `ghcid.txt`.
 
-**IMPORTANT**: Do not run build commands yourself. The human runs ghcid on the terminal, which then updates `ghcid.log` with any compile error or warning (if this file does not exist, or if ghcid has stopped, remind the human to address it). You should read `ghcid.log` (in _entirety_) after making code changes; this file updates near-instantly. Don't rely on VSCode diagnostics.
+**IMPORTANT**: Do not run build commands yourself. The human runs ghcid in the terminal, which then updates `ghcid.txt` with any compile error or warning (if this file does not exist, or if ghcid has stopped, remind the human to address it). You should read `ghcid.txt` (in _entirety_) after making code changes; this file updates near-instantly. You must **first** address VSCode diagnostics (includes build issues & hlint warnings) if any, before addressing those in `ghcid.txt`.
 
 **Adding/Deleting modules**: When a new `.hs` file is added or deleted, the `.cabal` file must be updated accordingly. However, if `package.yaml` exists in the project, run `hpack` instead to regenerate the `.cabal` file with the updated module list. This will trigger `ghcid` to restart automatically.
 
-**HLint warnings**: Once all code changes are made and `ghcid.log` shows success, check if the project has a `.hlint.yaml` file. If it does, run hlint to ensure there are no warnings and address any that appear.
+**HLint warnings**: Once all code changes are made and `ghcid.txt` shows success, check if the project has a `.hlint.yaml` file. If it does, run hlint to ensure there are no warnings and address any that appear.