Technical Proposal Charting

Problem

After a technical proposal’s body copy is confirmed, it often lacks diagrams that clarify architecture, workflow, responsibility boundaries, and data flow. Direct generative charting can produce tiny text, random colors, repeated layouts, mismatched content, and misplaced DOCX insertions. This skill treats charting as a separate pipeline stage, aiming to deliver a charted DOCX without editing the body text.

How It Works

It starts from content_confirmed, reads sections in project_config.json, decides section by section whether images are needed, and appends only _charts. It derives brand and auxiliary colors from the project context card, then builds a five-step brightness gradient to avoid reusing historical project palettes.

Each section uses an “atmosphere image + structure image” pair: the atmosphere image sets context under the section title, while the structure image presents the information skeleton at the section end. Charts are rendered with plain HTML + CSS, screenshotted to PNG, and inserted into the DOCX by section. Key constraints include a 641px canvas, font size no smaller than 12px, lightest text no lighter than #6b7280, and no CSS animation or hover effects.

Boundaries

It is intended for confirmed proposal copy that needs structured visuals, such as flows, architecture, responsibility split, and data paths. It does not rewrite copy or reorganize content. For strong brand VI, complex vector graphics, or high-fidelity illustrations, human design review is still required.