author-swift-docc-docs

To write DocC documentation for a Swift package, you need to author structurally correct symbol comments, articles, extension files, and topic groups. A focused workflow can detect your repo shape and infer the specific documentation task to keep your authoring aligned.

Reviewing DocC content in an Xcode project involves checking symbol docs, landing pages, and tutorial depth boundaries. A task-inference workflow classifies the review request and applies configurable knobs to ensure the documentation meets structural requirements without drifting into unrelated build tasks.

Yes, you can author Swift tutorials and control their depth using DocC by applying configurable tutorial-depth boundaries. The workflow gates tutorial-aware reviews and enforces depth limits through customizable settings persisted in a user config location.

Yes, the DocC authoring workflow supports handing off to Apple docs lookup by producing a clear JSON contract. When a request exceeds local authoring or review scope, it triggers a handoff to broader Apple documentation exploration or build and export execution workflows.

Structuring DocC articles and topic groups requires organizing your Swift code documentation into a coherent hierarchy. The workflow classifies your request as a structure task and helps you produce correct extension files and landing pages tailored to your detected repository shape.

You should hand off DocC authoring to a Swift package build workflow when your task requires actual execution or export rather than content creation. The workflow generates a JSON contract that explicitly routes build and lookup tasks away from local DocC authoring.