cyberneticlibrary

Write long-form editorial blog posts

blog-postskillsetup L241,165
nexu-io/open-design
What it does

Write long-form blog post article with editorial layout and no marketing chrome

Best for

Design-system-first content sites where each blog post is a mini-editorial product with consistent type hierarchy and brand voice.

Inputs
  • · Topic (from brief)
  • · Active DESIGN.md with typography tokens
  • · Article outline (4-6 H2 sections, ≥600 words)
Outputs
  • · Single HTML document: complete article with masthead, header, hero image, body, author footer, related cards
  • · Inline CSS styling per design system tokens
  • · Type hierarchy unambiguous (H1 headline, H2 sections, pull quotes non-competing)
  • · One pull quote, one figure with caption, one list, one blockquote per body
Requires
  • · Design system (DESIGN.md) for typography tokens and layout rules
Preconditions
  • · DESIGN.md loaded with font, color, and layout tokens
  • · Topic is substantive (no lorem ipsum)
  • · Article has ≥4 H2 sections with prose depth
Failure modes
  • · No DESIGN.md → uses generic defaults instead of brand tokens
  • · Line length >75 chars → poor readability
  • · Accent color used >2x → visual noise instead of emphasis
  • · Missing required elements (pull quote, figure, list, blockquote) → shallow depth
Trust signals
  • · Specific element requirements: masthead, article header, hero image, body (with 4 required element types), author footer, related cards
  • · Self-check list: unambiguous type hierarchy, line length 60-75 chars, accent ≤2x, no drop caps unless serif mood
  • · Output format: complete HTML with inline CSS, artifact tags with identifier and title