Add best practices, hooks, memory files, and scripts from recent sessions

Includes: spec-driven and test-driven development best practices,
reproduce-before-fixing debugging workflow, require-plan-file hook,
find-project-root script, session logs, memory files for decisions/
gotchas/process-lessons, and updates to existing best practice topics.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

memory/skill-context-load.md

@@ -0,0 +1,28 @@
+# skill: /context-load
+
+**Location:** `custom-claude-skills/skills/context-load/SKILL.md`
+**Symlinked to:** `~/.claude/skills/context-load`
+
+## Purpose
+
+Reloads project context into the conversation after `/clear` or when context has been lost mid-session. Equivalent to the context that `start-claude` injects at session start via `--append-system-prompt`.
+
+## Usage
+
+```
+/context-load
+```
+
+Run from any project directory. The skill will gather context from cwd upward, just like the `context-load` script does at launch.
+
+## How it works
+
+- Uses `!`context-load`` to run the `scripts/context-load` script at skill load time
+- The script output (CLAUDE.md files, trees, CONTEXT.md, MEMORY.md, BESTPRACTICES.md, git status) is injected directly into the skill prompt
+- Claude reads and internalizes the output, then confirms what it loaded
+
+## Gotchas
+
+- Depends on `context-load` being on `$PATH` (symlinked to `~/sbin/context-load`)
+- Output size scales with the number of projects in the directory hierarchy — deep nesting or large index files may use significant tokens
+- Only loads index files, not topic files from `memory/` or `context/` — Claude must use Read tool for those if needed