Technical documentation, with a clearer story.

A practical workflow

1. Start with the architecture and the question the document answers. Record boundaries and assumptions rather than leaving the diagram to speak for itself.
2. Describe important components, connections, tradeoffs, and known limitations. Preview generated documentation and remove unsupported claims.
3. Export Markdown with your diagram source, or use the GitHub documentation workflow to commit to a repository you control.

Try this starting prompt

Diagram a background job system with an API, queue, workers, and a database. Show job submission, processing, retries, and results. Keep the main flow readable for a new engineer joining the team.

Adapt the names, connections, and constraints to your own system. AI output is a draft: inspect its assumptions and edit the result before sharing.

Choose the handoff

Use the visual canvas for presentation, Code or Split view for precise changes, and saved versions before major revisions. A read-only link is useful for a quick review; export source or an editable project backup when the recipient needs to continue editing.