remember

Capture friction and user corrections as methodology notes to refine AI behavior.

20|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/zby/llm-do --skill remember-zby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/zby/llm-do/tree/main/arscontexta/skills/arscontexta-remember
Command: npx skills add https://github.com/zby/llm-do --skill remember-zby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps capture and formalize learnings from interactions, turning friction points and corrections into actionable methodology notes that improve AI behavior over time.

Core Features & Use Cases

  • Explicit Capture: Record specific instructions or corrections provided by the user.
  • Contextual Review: Analyze recent conversation history for implicit corrections or user adjustments.
  • Session Mining: Scan past session transcripts for recurring patterns of friction or undocumented decisions.
  • Use Case: After an AI makes a mistake, you can use /remember "Don't process personal notes like research" to capture that correction. Later, if you notice a pattern of similar mistakes, you can use /remember --mine-sessions to scan past interactions for these issues and generate new methodology notes.

Quick Start

Use the remember skill to capture the instruction "always check for duplicates before creating".

Frequently Asked Questions about remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture AI corrections and turn them into methodology notes?

To capture AI corrections, you can provide explicit instructions or analyze recent conversation history for implicit adjustments. This turns friction points into actionable methodology notes that refine AI behavior over time.

What is session mining for recurring AI friction patterns?

Session mining scans past session transcripts to identify recurring patterns of friction or undocumented decisions. It generates new methodology notes from these patterns to continuously evolve system specifications.

How do I document implicit user adjustments from recent conversations?

You document implicit user adjustments by using contextual review to analyze recent conversation history. This identifies undocumented corrections and integrates them into a methodology learning loop to refine AI behavior.

Does this methodology learning loop require any external dependencies?

No external dependencies are required to run the methodology learning loop. It operates independently to capture friction and evolve system specifications without needing additional software engineering frameworks.

When should I use explicit capture versus contextual review for documentation?

Use explicit capture for direct instructions like specific corrections, and use contextual review when analyzing recent conversation history for implicit adjustments. Both generate methodology notes to refine AI behavior.