What problem does it solve? Setting up and maintaining API documentation with Gehtsoft's docgen tool involves a non-obvious three-layer pipeline (source extraction, XSLT conversion, .ds merging) with silent failure modes like shadowed keys, lost CRC suffixes, and broken cross-references that are hard to diagnose without deep knowledge of the tool. ## Core Features & Use Cases - Project Scaffolding: Copy ready-made doc/ directory templates for five workflows: manual-only docs, C# with Asm2Xml auto-generation, C++ or Java with doxygen, and multi-language sites. - .ds Authoring and Editing: Write and edit @group, @article, @class, and @member blocks with correct markdown/BBCode formatting, escaping rules, and merge semantics. - Merge Diagnostics: Debug silent first-wins key merging, CRC-suffixed member overrides, broken [link=key] references, and auto-generated content that fails to appear. - Use Case: A developer adds docgen documentation to a C# library: the skill scaffolds doc/ with project.proj, project.xml, and preparesettings.xml, wires Asm2Xml extraction, and explains how to hand-write namespace overviews that merge with auto-generated member docs. ## Quick Start Set up a docgen documentation project for my C# library with auto-generated API reference from XML doc comments.
