1---2name: save3description: Saves the latest learning as a numbered markdown file under ~/.claude/learnings and updates the learnings index with title and tags.4---56# INSTRUCTIONS78- Look at the files in ~/.claude/learnings9- Find the highest numbered file (e.g., 0119.md)10- Increment the number by 1 and zero-pad to 4 digits (e.g., 0120.md)11- Think hard and save your learnings to that new file in ~/.claude/learnings12- Extract the title from the learning (first heading after "# " in the new file)13- Extract relevant tags from the learning content by analyzing:14 - Technology/framework names (e.g., typescript, python, react, mcp, hopper-framework)15 - Key concepts (e.g., refactoring, testing, architecture, debugging)16 - Patterns and methodologies (e.g., monoids, agent-architecture, type-safety, functional-programming)17 - Tools and libraries mentioned (e.g., bun, effection, deepeval, playwright)18 - Convert all tags to lowercase and replace spaces with hyphens19 - Include 3-7 most relevant tags20- Update ~/.learnings/README.md by:21 - Adding a new entry AFTER the "## Key Topics" section with the format: `## {number}. [{title}](learnings/{filename}) {tags}`22 - The number should be the next sequential number (previous highest + 1)23 - Entries are in reverse chronological order (newest first)24 - If no specific title is found, use "Learnings" as the title25 - Tags should be formatted as backtick-wrapped hashtags (e.g., `#typescript` `#refactoring`)26 - Analyzing the Key Topics section and updating it if the new learning introduces:27 - A new major theme not yet represented28 - Significant additions to an existing topic (update the session count if applicable)29 - New frameworks, tools, or patterns that warrant inclusion30 - Keep the Key Topics section concise but comprehensive