These are personal writing rules applied to the user's Naver pioneer_law blog. If another account is requested, that request takes priority.
Standards and Tools
Before starting work, read the format standard document. The standard document is the source, and the same rules are not duplicated separately.
- For the browser, read the available
ego-browserskill and continue writing in the existing workspace. - Saved Tistory original text conversion:
/Users/danny/Documents/PARA/Resource/seomachine-ai-blog/scripts/naver_format.py - Naver editing and verification: in the same repository,
scripts/naver_transfer.mjs - fixed-width line break tool
scripts/naver_word_wrap.mjsis not used because the user rejected the width as too narrow. - Existing migration status: check
output/naver-migration-20260916/migration-register.csvand the per-postpublished.json. Do not interpret a migration record as publication approval for a new post.
Writing Posts
First load Naver's 템플릿 → 내 템플릿 → 메모리허브 기본형 · 자연스러운 폭. Replace it with new content and remove all placeholder text. The local source is the repository's templates/naver/centered-korean.html, and the bold headings in the HTML must be converted into actual subheadings after pasting. Templates are a feature for reusing formatting and paragraph structure, and they do not automatically guarantee word-wrapping for new sentences. Continue performing line break verification after replacing the content.
Center-align the title, body, and subheadings. The body defaults to Nanum Gothic 16px with 180% line spacing. Specify subheadings using SmartEditor's actual subheading format. Do not replace them with bold regular paragraphs. Split long paragraphs into about two sentences and place a blank line between paragraphs. Left-align tables and code, and preserve the characters, line breaks, and indentation of the code.
Correct Korean spacing, and also check visual line breaks split by 그리고가 그리 / 고. Use the original body width and allow lines to wrap naturally according to screen width. Do not force line breaks based on a short fixed width such as 240px or a character count. Do not insert spaces or invisible combining characters inside words. Do not assume that CSS is permanently saved on Naver. For popular blogs, refer only to the reading structure and do not copy the wording or images.
Migration and Verification
Preserve the original post's text, links, images, and public status. Perform public migration within the current approval scope and do not make private posts public. When editing an existing post, modify the same URL and do not create duplicate posts. Do not infer the scope of new post creation, publication, or scheduled publishing from format preferences alone.
First check the editing result on one post, then process the rest in the same way. If the cursor position or body preservation check fails, do not save and restore that edit. Immediately after a UI action, wait for a specific state change. When inserting a featured image, using the visual End position may place the image in the middle of a word, so check the start position of the first line.
After publishing, reopen the exact URL and verify the body text, Korean word order, original text links, actual subheadings, images, code, tables, center alignment, and public status. Verify sentence line breaks on PC and mobile. Do not hide unresolved exceptions such as narrow table cells or long single tokens. Record the checked screen widths and results in the work log.