Export your analysis report in multiple formats to share with designers, developers, and stakeholders (Spec 4.5 Export Options).
Markdown export
Download a complete report as Markdown. Includes overview scores, flow complexity, **analysis run context** (Figma page and starting screens from the wizard when stored), **Designer Dev Stack** (token/component sources and a synced color table when project tokens exist, Spec 4.3a), issues with patch plans, and embedded screenshots when Figma is connected—up to 15 base64 images for Notion, Confluence, or GitHub Wiki. For flow diagrams and additional visuals, use Print/PDF.
Print / PDF
Use Print / PDF for stakeholder presentations (Spec 4.5). The print view includes scores, **flow structure** (list of screens and connections), **Analysis run context** (wizard page and starting screens), **Designer Dev Stack** (token/component sources and a synced color table, up to 36 rows), and the issues table—aligned with Markdown export. The full interactive flow diagram is in the web report. Opens a print-friendly view; use your browser's Print or Save as PDF.
Figma comments
Copy-paste formatted comment blocks for each issue. Paste into Figma comment threads to link Blue Painter findings directly to frames or specific screens. When your project is connected to Figma and flow nodes are mapped, each comment includes a direct link to the affected frame (Figma URL with node-id). When design tokens are synced (Designer Dev Stack), the batch export header includes a one-line **palette handoff** (Spec 4.3a) so designers validate fills against the same colors as code.
Share link
Use Copy link on the report to copy a shareable URL. Recipients can view the full analysis report if they have access. Useful for async collaboration and stakeholder review.
Export to GitHub
Create GitHub issues from your report (Spec 4.5 GitHub Integration). Connects via OAuth and creates one issue per finding (or, when configured, one issue per major flow with sub-tasks for individual fixes). Each issue gets labels by severity and type (e.g. missing-state, complexity). When an issue has a patch plan, its steps are added as checkbox sub-tasks so you can track progress. Each issue body links back to the full Blue Painter report; when tokens are synced, a **Designer Dev Stack** footer notes the palette count (Spec 4.3a). Requires GitHub integration in Settings. If your repo doesn't have type labels yet, export still succeeds using severity and blue-painter.