What problem does it solve? Maintaining consistent, non-redundant documentation across a growing Python package is difficult: docstrings drift out of sync with signatures, parameter descriptions get copy-pasted, and related functions end up scattered across docs pages. This Skill provides structured patterns and a checklist to keep package documentation consistent and complete. ## Core Features & Use Cases - Docstring Patterns: Templates for public functions, internal helpers, classes with __repr__/to_dict, and functions sharing many parameters. - Redundancy Reduction: Guidance on reusing shared parameter docs, cross-referencing related functions with See Also sections, and grouping related APIs on one docs page. - Documentation Workflow: An eight-step workflow from writing the function to building docs with mkdocs and verifying with pytest doctest checks. - Use Case: When adding a new exported function like new_rag_tool to a package, apply the shared-parameter pattern from _base_tool, add cross-references to sibling functions, and validate the docs build renders correctly. ## Quick Start Document the new function I just added to this Python package following the project docstring style, reusing shared parameter docs and adding cross-references to related functions.
