What problem does it solve? Writing search-optimized travel review posts for Naver Blog requires keyword research, photo curation, D.I.A.-aligned structure, and a consistent personal tone, which is slow and error-prone when done manually for every trip or venue visit. ## Core Features & Use Cases - Material-driven drafting: Collects place name, dates, itinerary, costs, and impressions from the user, then produces a complete draft following a fixed structure (intro, info table, sections with photos, tips, honest downsides, closing). - Photo pipeline: Pulls trip photos from the local Apple Photos library via SQLite metadata queries, converts HEIC to JPEG, and enforces privacy rules such as blurring participant faces and identifying information. - SEO and tone rules: Targets long-tail keywords, enforces 1,000-2,000 character length, 15+ self-taken photos, and a plain factual tone with banned AI-sounding phrases; requires user approval before publishing. - Use Case: After returning from a Busan workation, provide the venue names, expenses, and timeline, and receive an approval-ready Naver Blog draft plus a parallel Tistory version. ## Quick Start Ask the agent to write a Naver Blog travel review draft using your trip dates, places visited, costs, and photo selection for approval before publishing.