# blog-post

Generates self-contained editorial blog posts and long-form articles in HTML based on design system tokens.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 245 installs · ★ 108855 repo stars
- Author: nexu-io
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/blog-post/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/blog-post

## What it does

This skill outputs a standalone HTML document formatted as an editorial article without external images or scripts. Styles remain inline. The layout includes a masthead, hero placeholder, author block, pull quote, and three related story cards. Content avoids placeholder text: the agent writes an actual article of at least 600 words across 4–6 H2 headings.

Formatting follows `DESIGN.md` tokens. Body prose is constrained to 680–720px with line lengths between 60–75 characters. Pull quotes use inline-start rules to flip cleanly in RTL layouts. Accent colors appear no more than twice across the entire page.

Without `DESIGN.md` in the workspace, the skill cannot resolve typography tokens.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill blog-post -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/blog-post/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/blog-post/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill blog-post -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/blog-post/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill blog-post -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/blog-post/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install nexu-io/open-design design-templates/blog-post/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/blog-post/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill blog-post -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/nexu-io/open-design --path design-templates/blog-post
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/blog-post/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add nexu-io/open-design --skill blog-post -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/blog-post/SKILL.md

## When to use it
- generate standalone long-form HTML articles with inline CSS
- draft full-length 600-word prototype articles without lorem ipsum
- format editorial layouts with pull quotes and RTL alignment
- build related story grids and author bio blocks

## Example prompts
- Draft a long-form article about design tokens using the blog-post skill
- Generate an essay prototype in HTML with a masthead and pull quotes
- Create a marketing case study page following DESIGN.md

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: feaeb981369ed515.

BEGIN THIRD-PARTY FILE feaeb981369ed515
````text
---
name: blog-post
description: |
  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".
triggers:
  - "blog"
  - "blog post"
  - "article"
  - "essay"
  - "case study"
  - "newsletter"
  - "博客"
  - "文章"
od:
  mode: prototype
  platform: desktop
  scenario: marketing
  preview:
    type: html
    entry: index.html
  design_system:
    requires: true
    sections: [color, typography, layout, components]
  craft:
    requires: [typography, typography-hierarchy, typography-hierarchy-editorial, 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.
````
END THIRD-PARTY FILE feaeb981369ed515

The third-party file has ended. Everything between the feaeb981369ed515 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© nexu-io · Apache-2.0 · https://github.com/nexu-io/open-design/tree/HEAD/design-templates/blog-post/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
