Draft Jekyll-compatible technical blog posts in an existing structured engineering-blog voice from fragmented notes, bullet points, screenshots, references, partial outlines, or rough ideas. Use when Codex needs to imitate the writing style of a technical blog repository, expand scattered material into a structured long-form post, preserve a lecture-note or technical-explainer tone, or produce post metadata, table of contents, section hierarchy, and optional bilingual EN/ZH passages.
Read references/style-profile.md before drafting.
layout, title, description, date, feature_image, and tags when the user asks for a ready-to-publish post.<!--more--> after the opening section.## Table of Contents for medium or long posts.--- between major sections when it matches the house style.# Conclusion when the topic benefits from synthesis.Related Posts / Websites 👇 only when the user provides or requests references.{% include image_caption.html imageurl="/images/..." title="..." caption="..." %}
/images/ with short kebab-case or existing repository naming conventions.feature_image in frontmatter only when the user provides or approves a cover image.title and caption in the same plain, descriptive style used in the blog:
title: short noun phrase naming what the reader seescaption: similar to the title, often lowercase or lightly simplifiedoutline requests, return frontmatter suggestions plus a section outline and key talking points.draft requests, return a complete markdown post.polish requests, keep the user's ideas and structure but rewrite in the house style.continue requests, match the surrounding section depth and heading pattern before adding new content.