craft-skills-and-memorieslisted

# Craft Skills and Memories One skill for both ends of the lifecycle of an agent's instruction sources: creating skills and memories worth keeping, and repairing them when they fail in practice. A broken skill or a stale memory is a bug. Working around it and moving on re-breaks the next session. Scope: - **Skills are general-purpose.** Nothing in a skill should be project-specific. A fact that only holds for one project belongs in that project's own docs or memories, not in the skill. - **Memories may be project-specific or common.** Create and fix a memory at the scope it belongs to: a project memory in that project's store, a common memory in the shared store. ## The Quality Bar (creating and fixing alike) - **Example-, scenario-, or concept-led, never quote-led.** The concrete specimen (the failing command, the corrected block, a worked scenario) recalls far better in a future session than abstract explanation or the user's verbatim words. - Structure each entry specimen-first: what happened and where, then the rule it taught, then the boundary or exceptions. - Keep a short verbatim phrase only when the exact wording IS the directive (a ban, a naming rule). Otherwise paraphrase into the rule. - When touching an old quote-led entry, retrofit it. - **Descriptions are triggers**: short, "Use when ...", stating the one moment the thing should fire, never summarizing contents. A summary-shaped description is an activation bug. - **Skills** carry runnable copy-paste