session-to-project-skilllisted

# Turn a session into a durable project skill This is the highest-leverage habit in this whole library. It was requested at least eight separate times, and every good project skill here came out of it. **The thing being saved is not the code.** Git has the code. What is expensive and undocumented is: why it is built this way, what was already tried and failed, which facts the owner corrected, and what breaks if you touch it. --- ## The test a good project skill must pass > A brand-new session, given only this skill and no transcript, can be told *"fix the site"* and do > the right thing — including knowing what NOT to touch. If your draft fails that test, it is a summary, not a skill. Summaries are worthless here. ## What goes in — in this order ### 1. Frontmatter that actually triggers The `description` is the only thing a cold model sees when deciding whether to load you. Write it for retrieval, not for a human reader. ```yaml --- name: <matches the directory name exactly> description: >- <What it is + the stack, in one sentence.> Load this whenever the user works on <project>, "<the vague name they actually use>", <feature>, <feature>, or anything in <folder>. Use it even for vague asks like "fix the site", "it's broken on my phone", "deploy my changes", "why isn't X showing" — it carries <the things it carries>. For <adjacent concern> see `<other-skill>`. --- ``` Include the **user's own vocabulary**, not yours. If they call it "the import site", that p