1---2name: save3description: Save the latest learning as a numbered markdown file under ~/.claude/learnings and update the learnings index with title and tags. Use when the user says "save", asks to record a learning, or wants the current insight stored for later.4metadata:5 source: https://skillmd.com/skills/sdiamante13/save6---78# INSTRUCTIONS910- Look at the files in ~/.claude/learnings11- Find the highest numbered file (e.g., 0119.md)12- Increment the number by 1 and zero-pad to 4 digits (e.g., 0120.md)13- Think hard and save your learnings to that new file in ~/.claude/learnings14- Extract the title from the learning (first heading after "# " in the new file)15- Extract relevant tags from the learning content by analyzing:16 - Technology/framework names (e.g., typescript, python, react, mcp, hopper-framework)17 - Key concepts (e.g., refactoring, testing, architecture, debugging)18 - Patterns and methodologies (e.g., monoids, agent-architecture, type-safety, functional-programming)19 - Tools and libraries mentioned (e.g., bun, effection, deepeval, playwright)20 - Convert all tags to lowercase and replace spaces with hyphens21 - Include 3-7 most relevant tags22- Update ~/.learnings/README.md by:23 - Adding a new entry AFTER the "## Key Topics" section with the format: `## {number}. [{title}](learnings/{filename}) {tags}`24 - The number should be the next sequential number (previous highest + 1)25 - Entries are in reverse chronological order (newest first)26 - If no specific title is found, use "Learnings" as the title27 - Tags should be formatted as backtick-wrapped hashtags (e.g., `#typescript` `#refactoring`)28 - Analyzing the Key Topics section and updating it if the new learning introduces:29 - A new major theme not yet represented30 - Significant additions to an existing topic (update the session count if applicable)31 - New frameworks, tools, or patterns that warrant inclusion32 - Keep the Key Topics section concise but comprehensive