360 Secure SkillHub
360 安全技能中心

Minimalist Ui - OpenAI/Notion Style

这是适配Notion×OpenAI风格的极简UI设计系统,核心基于“清晰优先”等5大原则,遵循5步设计流程与严格风格约束,配套设计令牌、组件规范等参考资源。适用于设计仪表盘、聊天界面、控制面板等需干净排版、高信息密度、低噪视觉的产品界面,输出含界面意图、结构、交互状态及落地指导,确保界面高可用性与可执行性。

mes28io
mes28io
热度 71.28
最近更新 2026-05-11 17:27:24
分类:开发依赖:纯提示词应用场景:UI 原型 / 代码生成 / 模板

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add minimalist-ui
Metadata
name
minimalist-ui
description
Design system and implementation playbook for minimalist Notion x OpenAI style UI/UX. Use when designing dashboards, chat interfaces, agent control panels, docs UIs, or product surfaces that need clean typography, high information density, subtle hierarchy, low-noise visuals, and execution-ready frontend specs.

Minimalist Notion × OpenAI UI

Build crisp, low-noise product UI with strong hierarchy and operator-grade usability.

Core Principles

  1. Prioritize clarity over decoration.
  2. Keep layout breathable but dense enough for serious work.
  3. Use typography, spacing, and contrast as the primary hierarchy tools.
  4. Avoid visual noise (heavy shadows, flashy gradients, random color accents).
  5. Every element must justify its presence.

Workflow

  1. Define screen intent in one sentence.
  2. Choose one primary user action.
  3. Build skeleton with spacing + typography first (no color dependency).
  4. Add semantic color only for state/meaning.
  5. Run the checklist in references/qa-checklist.md.

Mandatory Style Constraints

  • Max 1 accent color per screen.
  • Border radius: 8–12px (consistent scale).
  • Shadows: subtle only; no layered “dribbble” effects.
  • Animation: 120–180ms, ease-out, functional only.
  • Empty states must suggest a next action.
  • Error states must include fix guidance.

Use These References

  • Token system: references/design-tokens.md
  • Layout and spacing logic: references/layout-patterns.md
  • Components and behavior: references/component-specs.md
  • Acceptance gate: references/qa-checklist.md

Output Contract (when generating UI specs/code)

Always produce:

  • Intent: what this screen optimizes for
  • Structure: zones/regions and hierarchy
  • Tokens used: type scale, spacing, colors
  • Interaction states: hover/focus/disabled/loading/error
  • Accessibility: keyboard + contrast notes
  • Implementation notes: concrete Tailwind/CSS/React guidance

Keep output implementation-ready and concise.