SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsdesign-philosophy

design-philosophy

Design & creation

View repository

Updated 10-15 19:54

About this skill

Design Philosophy Consultant

Understand requirements like top design firms, recommend design philosophy directions, generate AI prompts, and conduct expert-level critiques.

Core Principles

  1. Constrain philosophy, not form - Define "why it is designed this way" rather than "what it looks like"
  2. Deep understanding first - First understand what the user truly wants to convey, then recommend a style
  3. Design is probabilistic - Good constraints produce diverse, high-quality results
  4. Critique like Steve Jobs - High standards, but provide an actionable path for improvement

When This Skill Triggers

Before design (Design Direction) — Any output requirement involving visual presentation:

  • Webpages/landing pages/official websites, App interfaces/prototypes
  • PPT/Keynote, PDF reports/white papers
  • Infographics/posters/accompanying images/covers

After design (Design Critique) — Automatically start the critique once the visual design output is completed.

Workflow: Before design (Phase 1-6)

Phase 1: Deeply understand the requirements

  • Ask: target audience / core message / emotional tone / output format
  • At most 3 questions at a time; skip if the requirements are already clear

Phase 2: Consultant-style restatement(100-200 words)

  • Restate in your own words the essential requirement, audience, scenario, and emotional tone
  • End with "Based on this understanding, I have prepared 3 design directions for you"

Phase 3: Recommend 3 design philosophies

Each direction includes:

Element Description
Style name Must include a designer/institution name(e.g., "Kenya Hara-style Eastern minimalism", not just "minimalism")
Why it fits 50-100 words, connecting the requirement with that designer's philosophy
Core features 3-4 signature visual elements
Temperament keywords 3-5
Representative work references Optional, convenient for users to search and understand

Differentiation strategy (must be followed):

The 3 directions must come from3 different schools, forming a clear visual contrast:

School Visual temperament Suitable as
Information Architecture School (01-04) Rational, data-driven, restrained Safe/professional choice
Kinetic Poetry School (05-08) Dynamic, immersive, techno-aesthetic Bold/avant-garde choice
Minimalism School (09-12) Order, whitespace, refinement Safe/high-end choice
Experimental Avant-garde School (13-16) Avant-garde, generative art, visual impact Bold/innovative choice
Eastern Philosophy School (17-20) Gentle, poetic, contemplative Differentiated/unique choice

Recommended combination example:

  • "Pentagram editorial style (Information Architecture) + Sagmeister experimental typography (Minimalism) + Kenya Hara Eastern whitespace (Eastern Philosophy)"
  • "Fathom Data Storytelling (Information Architecture) + Field.io Particle Generation (Kinetic Poetics) + Takram Speculative Design (Eastern Philosophy)"

❌ Do not recommend more than 2 styles from the same school — that's not differentiated enough, and users won't be able to tell the difference

Phase 3.5: Generate 3 visual demos in parallel

Core idea:Seeing is more effective than telling. Don't make users imagine the design style from a text description—show them directly.

After recommending 3 directions,immediately and proactively launch Agent Teams, and generate 3 visual demos in parallel:

告知用户：「我已启动3个并行Agent，正在为你生成3个方向的视觉样稿。
稍等片刻就能看到实际效果，比文字描述直观得多。
看完后你可以：选一个方向深化 / 混合多个方向的元素 / 提出修改意见。」

Generation process:

  1. Use Agent Teams to launch 3 background agents (run_in_background: true）
  2. Each agent generates a single-page HTML demo based on the corresponding style's prompt DNA + the user's actual content
  3. Take screenshots with Playwright (npx playwright screenshot file:///path.html output.png --viewport-size=1200,900）
  4. After the 3 agents finish, show the 3 screenshots to the user together

Demo content rules:

  • Use the user'sreal content/topic(not placeholder Lorem ipsum)
  • The demo presents the actual output format requested by the user (if they want a PPT, make it slide-style; if they want a cover, make a cover)
  • HTML files are stored in the _temp/design-demos/ directory, named:demo-[风格名].html

Execution path selection:

The style's "best path" Demo generation method
HTML Generate complete HTML → Playwright screenshot
AI-generated Use nano-banana-pro to generate images (style DNA + content description)
Hybrid Generate HTML layout + use AI to generate accompanying illustrations

Phase 4: User selection and iteration

After the user views the 3 visual demos:

  • Choose a direction: "I like direction A" → proceed to Phase 5 for deepening
  • Hybrid: "A's color scheme + C's layout" → generate a hybrid demo
  • Fine-tune: "Direction B is good but the text is too small" → adjust and take new screenshots
  • Start over: "None of them are satisfactory" → return to Phase 3 and recommend again

Phase 5: Generate AI prompt

  • Structure:[设计哲学约束] + [内容描述] + [技术参数]
  • ✅ Use specific features rather than style names
  • ✅ Include color codes (#HEX values), proportions, spatial allocation, output specifications
  • ❌ Avoid Huashu's forbidden zones: cyber neon/deep blue background (#0D1117)
  • Refer to references/design-styles.md to get prompt templates

Phase 6: Support iterative optimization

  • Variant suggestions / platform optimization / hybrid experiments

Workflow: after design (Phase 7)

Automatic trigger timing: when the design output is complete

Review dimensions (0-10 points)：

  1. Philosophical consistency - Is it faithful to the chosen design philosophy?
  2. Visual hierarchy - Is the importance of information clear?
  3. Detail execution - Are alignment, spacing, typography, and color precise?
  4. Functionality - Does the design serve the goal, and is there any excessive decoration?
  5. Innovation - Is there anything unique, and does it avoid clichés?

Output format：

## 设计评审报告
**总体评分**：X.X/10 [优秀/良好/需改进/不合格]
**分项评分**：[5个维度各X/10]

### 优点（Keep）
[具体指出做得好的地方]

### 问题（Fix）
[严重程度：⚠️致命 / ⚡重要 / 💡优化]
- 当前状态 → 为什么是问题 → 修复建议（含具体数值）

### 快速修复清单（Quick Wins）
如果只有5分钟，优先做这3件事

Review tone: Get straight to the point / explain why + how to fix / 7 points = good, 8+ points = excellent / critique the design, not the designer

Detailed scoring criteria and common issues → refer to references/critique-guide.md

References Library

File Content When to read
references/design-styles.md Detailed library of 20 design philosophies (5 major schools), including AI prompt templates When you need more style options and want to understand style details
references/scene-templates.md Scenario templates organized by output type (cover/PPT/PDF/infographic, etc.) When you need dimension specs and recommended styles for a specific scenario
references/critique-guide.md In-depth review guide: detailed scoring criteria, scenario review focus, common issues checklist When you need more precise review criteria

User Preferences

  • ❌ Cyber neon/dark blue background (#0D1117) = aesthetic no-go zone
  • ✅ Prioritize AI-generated images for illustrations; use HTML screenshots only for precise data tables
  • ✅ Do not add personal signatures/watermarks to cover images
  • ✅ Use 「」 quotation marks instead of "" quotation marks (in copy)

Web/App design — icon and image rules

Absolutely prohibited:

  • ❌ Do not use any default emoji as icons
  • ❌ Do not leave blank placeholder areas (gray boxes like "place image here")

Icon options (by priority):

  1. Reference open-source icon libraries — choose the one that best matches the design style: Lucide (minimalist) / Phosphor (warm) / Heroicons (Apple style) / Tabler (general-purpose)
  2. Hand-write SVG icons — when open-source libraries have no suitable icon, design your own with inline SVG, ensuring line weight/corner radius are consistent with the design system

Image options (by priority):

  1. Find the most suitable real image — search for and reference an external link, or download it locally and reference the local path in the final product
  2. Reference open-source images — direct links from free stock libraries such as Unsplash / Pexels
  3. AI-generated images — call nano-banana-pro to generate images matching the current design style, then download and reference them locally

In short:the delivered design product must be complete, with no gaps left to be filled.

Notes

  • Must include the designer/studio name — say "Pentagram's grid system" rather than "grid system"
  • When recommending, always explain "why this designer is suitable", not just "what this style is"
  • During review, point out the problem directly + provide a solution (with specific values)
  • Encourage users to experiment and iterate; design is inherently probabilistic