troubleshooting-docs

Use the `/doc-fix` command after confirming a solution is verified. The Skill captures module context, symptoms, investigation steps, root cause, and solution details, then generates a standardized Markdown document with YAML frontmatter organized in your troubleshooting knowledge base for fast reuse.

Troubleshooting documentation requires module name, symptom description, investigation attempts, root cause analysis, the verified solution, environment details (SDK version, OS, build tools), and prevention steps. The Skill validates this data against YAML frontmatter enums and organizes it by symptom category.

Yes. The Skill automatically categorizes documentation by symptom type—such as build failures, parameter issues, and SVG/panel rendering problems—creating a structured taxonomy. This category-based organization makes solutions searchable and reusable across your development context.

Solutions are stored as sanitized, date-stamped Markdown documents with validated YAML frontmatter. The standardized format ensures consistency, searchability, and compatibility with knowledge-base systems.

No. The Skill generates standardized filenames and validates YAML frontmatter automatically, eliminating manual formatting. You provide problem context through a 7-step workflow; the Skill produces the final structured document.