docs: fix links

Author: ryanatkn

skills/fuz-stack/SKILL.md

@@ -366,10 +366,10 @@ mdz auto-linkifies bare paths starting with `./`, `../`, or `/` when preceded
 by whitespace. Use this in CLAUDE.md files and other markdown docs to make
 file and directory references navigable:
 
-- **Navigational paths** — bare, no backticks: ./grimoire/lore/fuz/design/
+- **Navigational paths** — bare, no backticks: `./grimoire/lore/fuz/design/`
 - **CLI commands and code** — backticked: `gro check`, `src/lib/`
 - **Template/placeholder paths** — bare, consistent even though they won't
-  resolve: ./{project}/CLAUDE.md
+  resolve: `./{project}/CLAUDE.md`
 
 Each file assumes the reader is in the file's parent directory. For
 `~/dev/CLAUDE.md`, all project paths are `./project/` since `~/dev/` is the
@@ -380,6 +380,11 @@ Deeply nested files (e.g. `lore/fuz_app/CLAUDE.md`) would need `../../../` to
 reach repos — use `~/dev/` for those cross-tree references where the relative
 path is unwieldy.
 
+Note: in files rendered by mdz on a website (like this SKILL.md on fuz_docs),
+example paths must be backticked to prevent mdz from linkifying them. The bare
+syntax is for CLAUDE.md files and docs where the paths resolve relative to the
+file's location on disk.
+
 ## Testing
 
 Tests live in `src/test/` (NOT co-located). Core repos (fuz_app, fuz_ui,