skills.rest
Haemeok
HaemeokOFFICIAL
Explore all skills by this author →
GitHub

compounding-lessons

Extract debugging lessons into persistent skill files and update indexes.

Updated Mar 13, 2025
Search Tags:#automation#debugging#claude#knowledge#lessons#compounding
One-click install
npx skills add https://github.com/Haemeok/Capstone-frontend --skill compounding-lessons
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compounding-lessons
Source: https://github.com/Haemeok/Capstone-frontend/tree/main/.claude/skills/compounding-lessons
Command: npx skills add https://github.com/Haemeok/Capstone-frontend --skill compounding-lessons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns a conversation's hard-won debugging wins into persistent knowledge files that seed future conversations, so the next Claude arrives already knowing.

Core Features & Use Cases

  • Extract five core items from a debugging session: Symptom, Root cause, Incorrect code, Correct code, and Principle.
  • Find a home for the lesson across project-local (.claude/skills) and user-global ( ~/.claude/skills ) repositories, aligning with existing skill structures.
  • Generate a rule file in the appropriate project-local skill, and update the skill's Quick Reference index to surface the new rule.

Quick Start

Invoke this skill at the end of a development cycle to generate a new rule file and update the relevant skill index.

Frequently Asked Questions about compounding-lessons

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

FAQPage Schema
How do I save debugging lessons so future Claude agents inherit the fix?▼

You can persist debugging lessons by extracting the Symptom, Root cause, Incorrect code, Correct code, and Principle from a session into a rule file within project-local or user-global skill directories, updating the skill index to surface the new rule for future agents.

What is the best way to stop Claude from re-discovering the same bug in new conversations?▼

To stop re-discovering bugs, extract debugging wisdom into persistent skill files at the end of a development cycle so the next Claude session arrives already knowing the fix without needing to debug the identical issue.

How do I capture debugging knowledge from a multi-iteration feature session?▼

Capture debugging knowledge by invoking a skill at the end of a development cycle to generate a rule file, update the relevant skill's Quick Reference index, and commit the changes to project-local or user-global directories.

Does this debugging knowledge persistence work with both project-local and user-global skill directories?▼

Yes, debugging knowledge persistence works by locating a home for the lesson across project-local (.claude/skills) and user-global (~/.claude/skills) repositories, aligning the generated rule file with existing skill structures.

When should I persist debugging lessons into skill files?▼

You should persist debugging lessons during end-of-session debugging, after multi-iteration feature work, or following subagent-driven development to capture hard-won fixes and seed future conversations with inherited knowledge.

What core items do I need to extract from a debugging session to persist it as a rule?▼

You need to extract five core items from a debugging session: Symptom, Root cause, Incorrect code, Correct code, and Principle, which are then used to generate a rule file and update the skill's Quick Reference index.

Related Skills

Explore More Education & Research Skills→
sswapnil2sswapnil2

systematic-debugging

Enforce a four-phase trace-back debugging process to identify root causes before fixes.

Community
Advanced
causify-aicausify-ai
144

skill.reorganize_rules

Organize agent rule files into correct sections without altering rule content.

Official
Intermediate
mkSteadymkSteady
9

project-onboard

Localize global Claude skills into a project's .skills directory.

Community
Intermediate
sandalsoftsandalsoft

qmd

Index and search local Markdown collections with BM25, semantic, or hybrid search.

Community
Intermediate