跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

artifact-design

Design artifacts, HTML pages, dashboards, charts, slides, a slide deck or decks, a presentation or presentations, reports, plans, memos, summaries, code snippets, and logs.

ahmadrosid · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add ahmadrosid/nakama --skill artifact-design

技能说明


name: artifact-design description: Design artifacts, HTML pages, dashboards, charts, slides, a slide deck or decks, a presentation or presentations, reports, plans, memos, summaries, code snippets, and logs. include-body-on-match: true

Design complete deliverables that the user can revisit in the profile Artifacts tab. These instructions are loaded directly when this skill is active.

Choose the output

  • Use HTML for visual reports, plans, memos, slide decks, landing pages, and browser games.
  • Keep the format the user requests. Use Markdown for pages only when the user or another active skill requires it.
  • Keep code, logs, and structured data in their appropriate formats. Preserve existing formats when moving files or editing artifacts.

Design the page

  1. Use the existing design system when the request provides one. Otherwise, base the design on the subject, audience, and content.
  2. Give editorial pages, landing pages, and games a bold treatment. Keep plans, memos, and other working documents polished and restrained.
  3. Write the design plan as CSS custom properties before building the page. Define colors, font families, type sizes, spacing, borders, and radii.
  4. Use those tokens throughout the page. Give every color token a light and dark value, including chart colors and interaction states.
  5. Support both themes through prefers-color-scheme. If an existing design system provides an explicit theme signal, respect it.
  6. Choose typefaces deliberately. Pair fonts only when the pairing improves hierarchy, and keep a consistent type scale with readable fallback fonts.
  7. Use only facts from the request or available sources. Do not add dates, durations, team sizes, customers, quotes, metrics, integrations, or feature details that were not supplied; omit them. Label supplied sample data; a "sample" label does not permit invented content.
    • Calculate totals, ratios, and deltas from the source rows with a tool that runs code, such as bash. Do not do arithmetic in the reply. If no tool can calculate, show the source rows and label the totals as not verified.
    • When a source metric differs from the target metric, such as impressions against a reach target, label that target as not verified. Do not calculate a variance for it.
  8. Write plain, direct copy. Use meaningful headings and labels; omit filler and placeholder sections.

Avoid generic defaults: cream with terracotta accents, purple gradients, Inter for every subject, emoji, and grids of boxed items (a dashboard's stat-card row is the one exception). Organize content with spacing, rules, and typography; show features and phases as rows divided by --rule, without a per-item background or border. Keep an established brand's choices when they fit the request.

Nakama style recipes

When no other brand is supplied, use Nakama's neutral surfaces, amber accents, and clear typography. Choose one recipe; adapt it to the subject. These names are design guides, not labels to put on the page.

StyleUse and layoutToken overrides
BriefPlans and memos: one readable column, a clear decision, ruled action rows. Keep sections open.Use the shared defaults.
LedgerReports and dashboards: aligned tabular numbers, directly labeled charts, mono values. Dashboards follow Dashboards below. Amber highlights the main finding; neutral tones show context.--width: 64rem; --title: clamp(1.75rem, 4vw, 2.5rem);
FeatureLaunch pages and explainers: a large heading beside one useful subject visual, then open sections. Stack columns on phones.--width: 72rem; --title: clamp(2.5rem, 7vw, 5rem);
DeckSlide decks and presentations: one 16:9 slide at a time. Follow Slide decks below.Use the shared defaults; size slide text in cqw.

Use this shared token example, then apply only the chosen overrides. Every color alias follows the active theme. Inter is intentional for Nakama styling; use other typefaces when the subject calls for them. Load named fonts through Google Fonts or use the fallbacks. Artifacts do not inherit app fonts or CSS.

:root {
  color-scheme: light;
  --bg: #ffffff; --text: #171717; --surface: #f5f5f5;
  --muted: #52525b; --line: #e5e5e5;
  --primary: #b45309; --on-primary: #ffffff;
  --focus: var(--primary); --chart-focus: var(--primary);
  --chart-context: var(--muted);
  --sans: "Inter", ui-sans-serif, system-ui, sans-serif;
  --mono: "JetBrains Mono", ui-monospace, monospace;
  --small: .875rem; --body: 1rem; --section: 1.5rem;
  --title: clamp(2rem, 5vw, 3rem); --width: 48rem;
  --gutter: clamp(1rem, 4vw, 3rem); --gap: 2rem;
  --radius: .625rem; --rule: 1px solid var(--line);
}
@media (prefers-color-scheme: dark) {
  :root {
    color-scheme: dark;
    --bg: #0a0a0b; --text: #fafafa; --surface: #1f1f23;
    --muted: #a1a1aa; --line: #27272a;
    --primary: #f59e0b; --on-primary: #0a0a0b;
  }
}
body { margin: 0; padding-inline: var(--gutter); background: var(--bg); color: var(--text); font-family: var(--sans); }

Use --on-primary on filled primary actions. Reserve amber for meaningful emphasis and --radius for controls or panels. Use no shadows. Separate sections by at least --gap. Give ruled rows at least .75rem vertical padding.

Dashboards

Use this layout when the user asks for a dashboard, KPI page, or performance report with metrics and a chart.

  1. Start from the shared tokens and the Ledger recipe. Add these tokens, each with a light and a dark value: --grid (#f0f0f0 / #1c1c1f), --series-1 (#171717 / #fafafa), --series-2 (#d97706 / #f59e0b), --good (#15803d / #4ade80), --bad (#c2410c / #fb923c).
  2. Order the page: title, a one-line subtitle with the channels, period, and comparison source exactly as the user named them (keep a named source, such as the CRM or sheet the targets come from), one row of 3–5 stat cards (two columns on phones; never leave one card alone on a row), the
阅读完整来源 ↗