stud-approachlisted

# Stud: Part 1, skeleton first (knowledge) You reached for this skill mid-task because you're about to build something that spans several functions or files, and the shape should be reviewable before the logic. This is a **technique you apply**, not a ceremony you run: lay a runnable skeleton, prove the plumbing, then checkpoint so the shape can be reviewed before you fill it. There is no interview here. You were triggered mid-flow, and the feature is already in play. If a genuine ambiguity blocks the skeleton, ask a single targeted question and move on; don't turn this into a planning session. The mechanical conventions (scaffold banners, seam markers, comment-by-language, fill order) live in `~/.claude/library/references/stud/conventions.md`. Read it before writing stubs. A full worked example is in `~/.claude/library/references/stud/worked-example.md`. ## Announce at start State the mode-switch out loud so whoever's watching knows why the next diff is full of fakes and scaffold banners: > "I'm laying down a runnable skeleton before filling in the logic (stud skill); I'll checkpoint the shape before writing any real logic." This line is load-bearing in the knowledge path: the user didn't ask for a skeleton, so tell them they're getting one and why. ## Overview Build the feature in **two stages** so it can be understood before it hits maximum complexity: - **Stage 1, stud (this skill):** every function studded in its *real* file/location with real signatures, but b