设计风格选择器

设计与多媒体 社区

技能解读

当前原文的自动摘译,尚未人工审校。

目的

使用这项技能将模糊的品味转化为具体的视觉选择。我们的目标不是猜测最终设计;而是猜测。它是生成一组结构化的选项,快速暴露用户的品味边界。

核心规则

如果用户已经表示不能描述抽象样式,则不要要求他们描述。生成可比较的视觉证据,让他们挑选,然后从选定的参考中实施。

工作流程

重申真实目标 说出用户实际选择的内容:设计系统风格、业务应用程序界面、登陆页面、平台、组件库等。将主要工件与验证样本分开。如果任务是设计系统,业务屏幕是可选的验证示例,而不是主要的可交付成果。保留任何现有的 UI、资产、令牌、布局、品牌线索和域上下文,除非用户明确要求丢弃它们。

提示模式

生成图像时,包括:

需要保留的教训

用户说“不彩色”可能意味着“没有几十个等重量的小色片”,而不是“去除所有颜色”。用户说“更多权重”可能意味着视觉权威和层次结构,而不是暗模式控制室。对于设计系统工作,不要用业务仪表板替换系统。商业屏幕可以验证风格,但不应该成为答案。始终创建有意的边界样本。它们使“太多”变得可见并加快选择速度。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
设计与多媒体
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@daymade · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# Design Style Picker

## Purpose

Use this skill to turn vague taste into concrete visual choices. The goal is not to guess one final design; it is to generate a structured set of options that exposes the user's taste boundary quickly.

## Core Rule

Do not ask the user to describe an abstract style if they already said they cannot. Generate comparable visual evidence, let them pick, then implement from the selected references.

## Workflow

1. **Restate The Real Target**
   - Say what the user is actually choosing: design-system style, business app surface, landing page, deck, component library, etc.
   - Separate the primary artifact from validation samples. If the task is a design system, business screens are optional validation samples, not the main deliverable.
   - Preserve any existing UI, assets, tokens, layout, brand cues, and domain context unless the user explicitly asks to discard them.

2. **Collect Existing Assets First**
   - Inspect the current rendered UI or screenshots.
   - Read design tokens, CSS variables, component names, key images, brand/domain references, and existing screenshots.
   - Treat current assets as the starting vocabulary. Do not generate unrelated "fresh" concepts over them.

3. **Generate A Matrix, Not Minor Variants**
   - Use at least two axes when taste is unclear:
     - Vertical ladder: one dimension changes by large steps, such as color intensity 20/35/50/65/80.
     - Horizontal directions: different organization strategies, such as data-driven color, brand spine, warm product imagery, scenario modules, or governance-led layout.
   - Make options visibly different. If two images look like siblings, regenerate one with a clearer contrast.
   - Prefer batch generation. The user is waiting for selection, not watching one slow image at a time.

4. **Use Color As A System**
   - "Less colorful" does not mean black-and-white. It usually means fewer competing focal points.
   - Keep the product palette alive, but assign color roles:
     - Broad zones and section bands for architecture.
     - Data visualization and evidence systems for multi-color semantics.
     - Brand/risk colors for rare, high-signal emphasis.
     - Neutral components for routine UI.
   - Include explicit upper-bound samples when the user is tuning color: safe, middle, high, and overload boundary.

5. **Review Before Presenting**
   - Open generated images yourself.
   - Mark which are likely too dead, too colorful, too generic, too business-system-like, or closest to the target.
   - Present file paths and a short decision note for each useful candidate.

6. **Implement From Selected Images**
   - Extract principles, not pixels: color roles, layout density, focal hierarchy, component treatment, image use, governance/data placement.
   - Fuse selected references explicitly. Example: "Use H02 for color placement and V04 for palette intensity."
   - Keep implementation scoped to the existing UI unless the user asks for a new artifact.
   - Run rendered visual QA after implementation.

## Prompt Pattern

When generating images, include:

```text
This is an evolution of the existing UI/design system, not a replacement.
Preserve these assets: <tokens, imagery, sections, components, brand cues>.
Axis: <vertical ladder or horizontal direction>.
Variant name: <clear label>.
Color/visual rule: <specific budget or organization method>.
Primary focal point: <one thing>.
Avoid: <known rejected styles from the user>.
```

## Lessons To Preserve

- A user saying "not colorful" may mean "no dozens of equal-weight small color chips", not "remove all color".
- A user saying "more weight" may mean visual authority and hierarchy, not dark-mode control room.
- For design-system work, do not replace the system with a business dashboard. Business screens can validate style, but should not become the answer.
- Always create deliberate boundary samples. They make "too much" visible and speed up selection.
- After selection, fuse the chosen references and name what each contributes.

## References

- Read `references/selection-playbook.md` when running a full style-selection session or when the user gives taste corrections during image exploration.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。