Agent Skills › nevertoday/zhongguo-traditional-colors › xxd-color-brief

xxd-color-brief

GitHub

将模糊的传统色彩描述转化为可执行的设计简报。通过解析情绪词、受众定位等，输出温度、饱和度等具体约束及3-5个起始色，避免过早选色冲突，并路由至后续配色或应用技能。

skills/xxd-color-brief/SKILL.md nevertoday/zhongguo-traditional-colors

触发场景

用户提供了模糊的色彩方向如“高级”、“东方” 需要将客户反馈或情绪词转化为具体的色彩约束在正式选择颜色前需要明确设计目标和风险

安装

npx skills add nevertoday/zhongguo-traditional-colors --skill xxd-color-brief -g -y

更多选项

不安装直接使用

npx skills use nevertoday/zhongguo-traditional-colors@xxd-color-brief

指定 Agent (Claude Code)

npx skills add nevertoday/zhongguo-traditional-colors --skill xxd-color-brief -a claude-code -g -y

安装 repo 全部 skill

npx skills add nevertoday/zhongguo-traditional-colors --all -g -y

预览 repo 内 skill

npx skills add nevertoday/zhongguo-traditional-colors --list

SKILL.md

Frontmatter

{
    "name": "xxd-color-brief",
    "description": "Turn vague visual direction into a practical Chinese traditional color brief. Use when a user has mood words, client feedback, audience positioning, references, or an unclear Chinese traditional color direction that must become palette constraints before choosing colors."
}

xxd-color-brief

Purpose

Use this skill before picking colors. Its job is to turn soft language like "高级", "东方", "年轻", "克制", "松弛", "科技感", or "不要太俗" into a brief that a designer can defend and reuse.

Pain Points This Solves

Stakeholders use adjectives, references, or dislikes, but the designer needs concrete color constraints.
Moodboards create alignment, but they often stop before deciding hue, brightness, saturation, contrast, and usage risk.
Teams jump into swatches too early and later argue because the success criteria were never named.

Data Contract

Use the bundled references inside this skill:
- references/chinese-color-master-list.md: full 742-color Markdown source list.
- references/chinese-color-harmony.csv: complete machine-readable harmony table for all 742 colors.
- references/chinese-color-harmony.md: Markdown version of the same harmony relationships.
Starting colors must include color name, HEX, and the reason they fit the brief.
If the user provides an outside HEX, map it to the nearest project color and label it as a mapping.
Do not produce a full palette unless the user explicitly asks; route to the next skill instead.

Briefing Workflow

Identify the job behind the words: brand, UI, poster, data visualization, content series, packaging, or audit.
Translate each adjective into observable constraints:
- Temperature: warm, cool, neutral, or controlled contrast.
- Lightness: pale, mid, deep, or high-contrast.
- Saturation: muted, clean, vivid, gray-toned, or ceremonial.
- Cultural signal: historical, editorial, product, youthful, premium, festive, technical.
- Risk: cliche, low readability, too decorative, too flat, too commercial, too nostalgic.
Detect conflicts. For example, "年轻又古典" needs a modern neutral base plus one traditional accent, not an all-antique palette.
Choose 3 to 5 starting colors from the 742-color set, each with a role hypothesis.
Name the avoid list as concrete color families, contrast levels, or usage patterns.
Route the next step:
- Need actual color combinations: xxd-palette-builder
- Need placement on a layout: xxd-palette-applier
- Need UI variables: xxd-ui-token
- Need contrast repair: xxd-accessible-color
- Need long-term brand rules: xxd-brand-system
- Need charts: xxd-data-viz
- Need to repair existing work: xxd-existing-design-audit
- Need repeated content: xxd-content-series
- Need physical production: xxd-print-packaging

Output Shape

Brief name: one project-facing phrase.
Design decision: 2 to 4 sentences explaining the color direction in plain Chinese.
Constraint table: mood word, translated color constraint, risk if misread.
Starting colors: role hypothesis, color name, HEX, why it belongs.
Avoid list: 2 to 4 concrete exclusions.
Next move: one recommended skill and what it should produce.

If the user only provides a mood word with no surface, state the missing surface and give a provisional brief instead of blocking.