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".
DeepseekModel
キュレーション済みスキル
品質 優秀 · 90
v1.0.0
取得
https://deepseekmodel.com/api/download.php?id=nexu-io-open-design-plugins-official-examples-blog-post-skill-md&format=skill
ダウンロード .skill
標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能
.skill ファイルの system_prompt フィールドの実際の内容。
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","featured":11,"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 Read the active DESIGN.md (injected above). Lean into the typography tokens — long-form is 70% type, 20% image, 10% chrome. Pick the topic from the brief and write a real article — at least 600 words across 4–6 H2 sections. No lorem ipsum. 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. 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. 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.
このスキルを起動するキーワード。クリックでコピーできます。
このスキルにはトリガーワードがありません。
ダウンロードした .skill に含まれるフィールド。
| フィールド | 説明 |
|---|---|
| format | フォーマット識別子（skill/v1） |
| skill_id | スキル固有 ID |
| name | スキル名 |
| version | バージョン |
| description | 説明 |
| category | カテゴリ（配列） |
| trigger_words | トリガーワード |
| tags | タグ |
| source | ソース |
| source_url | ソース URL（本ページ） |
| exported_at | エクスポート日時（ダウンロード毎） |
| system_prompt | システムプロンプト本文 |
| model_config | モデル設定：provider / model / temperature / max_tokens / top_p |
| examples | サンプル |
| install_guide | 各プラットフォームの導入説明（Coze / Dify / Claude / カスタム） |
