Web Technique to Skill Start from working code, not from prose. Reach for when the source is an article or a prompt pack that describes behavior. Reach for this when you built the thing, it works, and the knowledge is currently trapped in one file. Extract one mechanism per skill. A page that turned out well usually holds several; package them separately or each one gets diluted. Treat this as the living quality contract for every web-technique skill. On every creation or revision, audit this skill too. If the work exposes a missing fidelity rule, failure mode, packaging constraint, or verifi…