learner

To document Unity debugging discoveries, you can use quality-gated extraction to filter out generic advice and append structured learning entries with context, findings, and relevant files to your project's CLAUDE.md file for future reuse.

The best way to capture codebase-specific learnings is to classify the discovery as expertise or workflow, record its context and relevant files, and store it chronologically with confidence-based pattern analysis to identify recurring project patterns.

Yes, this project learning approach applies strict quality gates to filter out temporary workarounds, style preferences, obvious fixes, and generic advice, preserving only non-obvious, codebase-specific discoveries for long-term reuse.

Yes, you can use structured documentation for recurring workflow patterns in Unity development by applying confidence scoring and categorization to identify systemic project patterns that may eventually become formal skills or rules.

You should append a qualified learning to a project's CLAUDE.md file immediately after resolving a non-trivial bug, such as an asynchronous scene-loading race condition, to preserve the non-obvious cause and workflow for future debugging sessions.

You need to classify project learnings as expertise or workflow types to separate architectural conventions and undocumented system interactions from recurring workflow patterns, enabling accurate chronological storage and confidence-based pattern analysis.