Article Authoring

Pipeline

This skill is the entry point for a new article. The steps after it are separate skills; read the one you need when you reach it, and tell the owner what is still outstanding.

1. external-model-research — before writing, when the page covers a model or node you have not verified
2. article-authoring (here) — the Japanese page. JA is always the source
3. workflow-json / ia-nav-adr — when the page ships workflow files, or changes placement, slug or nav
4. preview-site — check it on localhost. Not a one-off step: look again after any later step changes what a page renders
5. localization — EN/ZH, only when the owner asks
6. news-readme-update — for a new page only, one news row per language that exists
7. release-check — before commit, re-audit the complete article package from the final Japanese source; prior step completion is not evidence
8. publish-pr — only on an explicit request

Do not run steps 5-8 on your own initiative. Finish the step you are on, then say which steps remain.

Read First

• Read /ops/style-writing.md for style, structure, media embeds, mediaRow, tags, and translation-adjacent rules.
• Read /ops/ia.md when adding a page or changing page placement.
• Read nearby articles in the same section and language before writing.

Workflow

1. Confirm the target language, section, slug, and scope.
2. Preserve the owner's authorship. Do not rewrite beyond the requested fix unless the text is factually wrong, confusing, or structurally broken.
3. Keep Japanese as the source for new content unless the owner requested localization.
4. Use frontmatter consistently:
   • section, slug, navId, title, summary, created, updated
   • tags are optional and max 5.
   • notes uses noteTags; do not substitute normal tags.
   • seoTitle / seoDescription are optional search-result overrides for <title> (before | site name), og:/twitter: title and description, meta description, and JSON-LD description. The visible H1 and summary stay unchanged. Write them in the page language around what searchers type (model or node name, "ComfyUI", the task); describe the owner's readable-workflow approach in plain words rather than the coined term. The owner writes or approves the wording. Every indexable page in every language must have summary, seoTitle, and seoDescription (enforced by npm run check:content); keep seoTitle within 64 display columns and seoDescription within 260 (JA/ZH) or 170 characters (EN). Mark body-less "coming soon" stubs robots: noindex.
5. Use H2/H3 only for article body structure unless an existing page pattern requires otherwise.
6. Use media markup consistently. {media=...} is the display mode and works for R2 and Gyazo URLs; {gyazo=...} is a compatible alias:
   • static image: {media=image}
   • loop: {media=loop}
   • player: {media=player}
   • R2 media is referenced only as /media/<logical name> (for example /media/basic-workflows/minimax-h3/minimax_h3_audio_driven_i2va.png: <section>/<article slug>/<lowercase_snake_case file name>), backed by an original in COMFY_MEDIA_ORIGINALS. Unuploaded originals preview on the dev server; the pre-commit hook runs npm run media:sync to upload and register them in src/_data/media.json. Never run uploads on the owner's behalf unless asked. Never write media.comfyui.nomadoor.net URLs directly, and never invent or rename logical names without the owner.
   • Gyazo and other external media URLs are written directly.
7. When linking workflow JSON, use paths under /workflows/....
   • Keep Performance data beside its Workflow JSON; never put it in front matter. Replace the normal Markdown link with {% workflow "/workflows/.../example.json", level=2, gpu="RTX 4070 Ti 12GB", ram="DDR5 64GB", time="51s", tags=["2.3MP"] %}.
   • For multiple measured environments, pass runs=[{ gpu: "...", ram: "...", time: "...", tags: ["..."] }, ...] to the same workflow shortcode.
   • Sampler speed is optional. Enter the value exactly as ComfyUI reports it using either s/it or it/s, for example samplers=[{ speed: "2.3 s/it" }] or samplers=[{ speed: "1.72 it/s" }]; the popup normalizes either form to s/it. Multiple Samplers are allowed, but every entry then requires a short identifying name, for example samplers=[{ name: "Base", speed: "2.3 s/it" }, { name: "Refiner", speed: "1.72 it/s" }].
   • For a workflowPicker, pass an object containing file and the same Performance fields in place of that Workflow's path string.
   • Keep generation-size tags compact with an approximate megapixel value such as 1MP, 2.3MP, or 4MP. Decimal values are allowed when useful; do not force the value to an integer. Use exact W×H only when those dimensions are important beyond performance context.

Editing Owner Drafts

• Treat the facts, examples, and explanations present in the owner's draft as the content boundary. When asked to "整える" or fix a rough passage, repair wording and structure without inventing examples, recommendations, parameter values, or background explanations.
• Do not expand a shorthand statement merely because a generic tutorial would explain it more fully. Add prose only when the owner explicitly asks for an explanation, or when a sentence cannot be understood without it.
• Respect the page sequence. If the page says it continues from or shares behavior with an earlier page, explain only the difference here. Do not repeat inherited mechanics or settings unless the owner wrote them again for a reason.
• If research reveals a missing fact or dependency, report it to the owner before inserting it. Factual review is not permission to enlarge the draft.
• Read several nearby articles before editing and copy their site-specific conventions, not a generic documentation template. In particular, model download links include the displayed file size and are followed by the matching ComfyUI/models/ placement tree.
• Preserve deliberate brevity, looseness, and author judgments. Do not replace them with textbook transitions, comprehensive lists, or polished marketing prose.

Checks

• git diff --check
• npm run check:content
• npm run build
• Add or run npm run test:playwright when the edit affects UI behavior, nav, search, notes, or layout.