wrap

To save session learnings as rules and hooks, you can use a reflection workflow that scans your conversation history for behavior corrections and repeated workflows. It categorizes these insights into rules, skills, or hooks with appropriate project or user scope for future sessions.

Capturing user preferences to prevent repetitive tasks is best achieved through structured session reflection. This process identifies actionable signals like multi-step workflows from your conversation history and persists them as automated lifecycle hooks or behavioral directives.

You generate rules from conversation history by scanning for behavior corrections and repeated patterns at the end of a session. The identified insights are classified into behavioral directives, reusable workflows, or automated actions and assigned correct user or project scope.

Session reflection works for creating both project-level and user-level configurations by evaluating the applicability of identified insights. It assigns the correct scope based on whether a learning should be enforced across a specific project or for the user globally.

You can automate multi-step workflows as hooks by identifying repeated patterns in your session activity. The reflection process proposes these automated lifecycle actions for your approval and then creates the corresponding hook configurations to enforce consistent practices.

The limitation of automatically persisting learned behaviors is that it requires a guided execution flow with human approval. It generates a reflection report of proposed rules, skills, and hooks, but creates or updates files only after you explicitly confirm the changes.