distill

Extract recurring session patterns into CLAUDE.md and AGENTS.md rules.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/leejaedus/pepcode --skill distill-leejaedus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/leejaedus/pepcode/tree/main/skills/distill
Command: npx skills add https://github.com/leejaedus/pepcode --skill distill-leejaedus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill session patterns, corrections, and evolving conventions into durable project documentation (CLAUDE.md, AGENTS.md, etc.) so teams start smarter in future sessions.

Core Features & Use Cases

  • Capture recurring user preferences, corrections, and workflow adjustments from a session.
  • Update CLAUDE.md and AGENTS.md with actionable rules and boundaries to enforce consistency.
  • Generate compact project documentation that accelerates onboarding and reduces repetitive context-switching.

Quick Start

Extract and publish behavioral rules to CLAUDE.md and AGENTS.md in your next session.

Frequently Asked Questions about distill

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

FAQPage Schema
How do I extract session patterns into durable CLAUDE.md project rules?

Extract session patterns into durable CLAUDE.md rules by detecting recurring user preferences and corrections, then generating actionable rules that merge safely with existing documentation while preserving prior content.

What is the best way to update AGENTS.md with recurring corrections from a debugging session?

Updating AGENTS.md with recurring corrections involves detecting repeated workflow adjustments during long debugging efforts, generating compact rules, and safely merging them with existing boundaries to enforce consistency.

Can I safely merge new project documentation rules without overwriting existing CLAUDE.md content?

Merging new project documentation rules preserves existing CLAUDE.md content by applying safe merging logic that appends generated rules and boundaries while maintaining prior documentation intact.

When do I need to distill session patterns into project documentation?

Distill session patterns into project documentation during multi-session projects or long debugging efforts when recurring user preferences and evolving conventions require continuous refinement of rules.

Does distill work for multi-session projects to continuously refine AGENTS.md boundaries?

Distill works for multi-session projects by continuously refining AGENTS.md boundaries, capturing evolving conventions and workflow adjustments across sessions to generate actionable rules for future consistency.

Why does my project documentation lose context across multiple debugging sessions?

Project documentation loses context across debugging sessions because recurring patterns and corrections are not captured into durable rules, requiring continuous refinement of CLAUDE.md and AGENTS.md to prevent context loss.