marco/open-design
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
open-design/skills/blog-post/SKILL.md
marco 5dd70b5016
Some checks failed
ci / Validate workspace (push) Successful in 12m32s
Details
landing-page-ci / Validate landing page (push) Successful in 9m41s
Details
landing-page-deploy / Deploy landing page (push) Failing after 5m23s
Details
github-metrics / Generate repository metrics SVG (push) Failing after 2m3s
Details
refresh-contributors-wall / Refresh contributors wall cache bust (push) Failing after 11s
Details
Initial import: open-design source for helix-mind.ai distribution 
This repository contains the open-design daemon CLI source code, built
and packaged at https://helix-mind.ai/cli/open-design/latest.tgz for use
by the HelixMind /design slash command.

Licenses: Apache-2.0 (root) + MIT (skills/*)
2026-05-06 20:50:24 +02:00

2.9 KiB
Raw Permalink Blame History

name description triggers od
blog-post A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
blog
blog post
article
essay
case study
newsletter
博客
文章
mode platform scenario featured preview design_system craft
prototype desktop marketing 11
type entry
html index.html
requires sections
true
color
typography
layout
components
requires
rtl-and-bidi

Blog Post Skill

Produce a single long-form article page — editorial layout, no chrome.

Workflow

  1. Read the active DESIGN.md (injected above). Lean into the typography tokens — long-form is 70% type, 20% image, 10% chrome.
  2. Pick the topic from the brief and write a real article — at least 600 words across 4–6 H2 sections. No lorem ipsum.
  3. Sections, in order:
    • Masthead — small wordmark + 4–6 nav links, plain.
    • Article header — category eyebrow, headline (display token, large), deck (1–2 sentence subhead), author name + role + date.
    • Hero image — a 16:9 placeholder block using a DS-tinted gradient or solid fill (no external images). Add a 1-line caption underneath.
    • Body — alternating prose paragraphs with at least:
      • 1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under dir="rtl").
      • 1 figure (image placeholder + caption).
      • 1 list (numbered or bulleted).
      • 1 inline blockquote.
    • Author footer — author avatar (initials in a circle), bio paragraph.
    • Related — 3 cards linking to other posts. Each card: tiny image block, title, 1-line excerpt, date.
  4. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline.
    • Article body uses the DS body font, centered, max-width per DS layout rule (typically 680–720px).
    • Drop caps (first-letter) only if the DS mood is editorial / serif — skip on tech-y DSes.
    • data-od-id on the headline, hero, body, pull quote, related grid.
  5. Self-check:
    • Type hierarchy is unambiguous — H1 is clearly the headline; H2s are section dividers; pull quotes do not compete with H1.
    • Line length 60–75 chars for body prose.
    • Accent appears at most twice (eyebrow + pull-quote rule, or one link).
    • The page reads like a magazine, not a marketing landing.

Output contract

Emit between <artifact> tags:

<artifact identifier="post-slug" type="text/html" title="Article Title">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.