Learn skill for claude

learn.md

Learn

Reflect on session learnings and capture them appropriately.

Reflect

Answer: "What is it you wish you had known at the start of this session?"

Consider:

• Gotchas encountered
• User preferences discovered
• Workflows that improved outcomes
• Mistakes that could have been avoided

Categorize Learnings

CLAUDE.md candidates - Add if it pulls its weight:

• Gotchas (things that surprised you, wasted time)
• Strong user preferences (coding style, workflow choices)
• Project-specific conventions not obvious from code
• Keep additions minimal and high-signal

Skill candidates - Create a skill instead if:

• It's a multi-step process
• It's contextual (applies in specific situations)
• It's a reusable workflow

Habit Hook candidates - Add a habit hook if:

• It's a recurring mistake
• It can be detected deterministically (AST, regex, linting rule)
• The fix is a short, repeatable action plan
• Check: Does the project have a Habit Hooks system? (look for quality runner, .quality-baseline.json, or similar)
  • If yes: Propose a new check with title, description, and actionGuidance
  • If no: Suggest implementing Habit Hooks (see implementation plan at https://gist.github.com/devill/1b711e2a6e73cf0dedf71106c7196e36)

Neither - Don't capture if:

• One-off situation unlikely to recur
• Already documented elsewhere
• Too specific to this task

Propose Changes

For CLAUDE.md additions: Show the specific lines to add and where.

For new skills: Draft the skill file.

For Habit Hooks:

• If system exists: Draft the check definition (title, description, actionGuidance, detection logic)
• If system missing: Propose implementing it, reference the Habit Hooks microfeature

Ask for approval before making changes.