What problem does it solve? After fixing a concrete technical problem, engineers often want to preserve the lesson learned, but raw debugging notes are tied to specific project names, file paths, and libraries, making them useless to others. This Skill transforms a one-off troubleshooting experience into a de-projectized, portable reference document that any developer facing the same class of problem can follow. ## Core Features & Use Cases - De-specificization workflow: Systematically replaces concrete project names, file names, library names, and absolute paths with placeholders and category terms so the document stays portable. - Fixed document structure: Enforces a standard skeleton covering symptoms, root cause, numbered solution steps, verification checklist, maintenance notes, and rejected alternatives with reasons. - Style and boundary control: Applies a serious third-person technical tone, relative paths only, and explicit applicability boundaries (tool, platform, version constraints). - Use Case: After fixing a clangd indexing failure caused by build-generated headers in a nonstandard directory, produce a generic guide any developer with a similar generated-header setup can apply to their own project. ## Quick Start Turn the problem we just fixed into a generic reusable solution document without any specific project or file names, saved as a local Markdown file.
