Automated Travel Guide System

What It Solves

Travel-guide generation often fails not because of writing, but because multiple outputs are maintained at the same time: QQ text is split, HTML pages miss modules, external images break, and large inline CSS/JS blocks are truncated during file writes. This skill turns those constraints into an executable workflow for scheduled travel-content generation and delivery, with emphasis on completeness, stable channel formatting, and local output.

How It Works

• Separate outputs: QQ text follows a text template and is sent in one message; HTML follows a page template and is published to a local directory.
• Three-layer frontend flow: ui-ux-pro-max plans structure, frontend-design defines color, typography, and motion direction, and Node.js builder assembles code, injects effects, and writes the file.
• Tiered scraping: plain, dynamic, and anti-bot pages use different fetchers with shared timeout and retry rules; text is used for content, while images come from a local image library.
• Conservative writing: large final HTML files are not written directly with write; a Builder script handles emoji, inline styles, and Canvas, and failures trigger a full rewrite.

Boundaries And Notes

It is better treated as an engineering spec for a fixed publishing pipeline than as a general travel assistant. It depends on local publish paths, a local image library, and fixed templates; outside those paths, output may fail to publish or images may break. Keep scraping and writing scripts separate, and remember that P2 Canvas effects using position:fixed must also set pointer-events:none.