MR
Mayur Rathi
@hesreallyhim
⭐ 45.1k GitHub stars

Workflow: Design Principles Example

Workflow: Design Principles Example是一款design方向的AI技能,核心价值是# S-Tier SaaS Dashboard Design Checklist (Inspired by Stripe, Airbnb, Linear) ## I,可用于解决开发者在design领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

# S-Tier SaaS Dashboard Design Checklist (Inspired by Stripe, Airbnb, Linear) ## I. Core Design Philosophy & Strategy * [ ] **Users First:** Prioritize user needs, workflows, and ease of use in ev

Last verified on: 2026-05-30
mkdir -p ./skills/claude-design-principles-example && curl -sfL https://raw.githubusercontent.com/hesreallyhim/awesome-claude-code/main/skills/claude-design-principles-example/SKILL.md -o ./skills/claude-design-principles-example/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# S-Tier SaaS Dashboard Design Checklist (Inspired by Stripe, Airbnb, Linear)


I. Core Design Philosophy & Strategy


* [ ] **Users First:** Prioritize user needs, workflows, and ease of use in every design decision.

* [ ] **Meticulous Craft:** Aim for precision, polish, and high quality in every UI element and interaction.

* [ ] **Speed & Performance:** Design for fast load times and snappy, responsive interactions.

* [ ] **Simplicity & Clarity:** Strive for a clean, uncluttered interface. Ensure labels, instructions, and information are unambiguous.

* [ ] **Focus & Efficiency:** Help users achieve their goals quickly and with minimal friction. Minimize unnecessary steps or distractions.

* [ ] **Consistency:** Maintain a uniform design language (colors, typography, components, patterns) across the entire dashboard.

* [ ] **Accessibility (WCAG AA+):** Design for inclusivity. Ensure sufficient color contrast, keyboard navigability, and screen reader compatibility.

* [ ] **Opinionated Design (Thoughtful Defaults):** Establish clear, efficient default workflows and settings, reducing decision fatigue for users.


II. Design System Foundation (Tokens & Core Components)


* [ ] **Define a Color Palette:**

* [ ] **Primary Brand Color:** User-specified, used strategically.

* [ ] **Neutrals:** A scale of grays (5-7 steps) for text, backgrounds, borders.

* [ ] **Semantic Colors:** Define specific colors for Success (green), Error/Destructive (red), Warning (yellow/amber), Informational (blue).

* [ ] **Dark Mode Palette:** Create a corresponding accessible dark mode palette.

* [ ] **Accessibility Check:** Ensure all color combinations meet WCAG AA contrast ratios.

* [ ] **Establish a Typographic Scale:**

* [ ] **Primary Font Family:** Choose a clean, legible sans-serif font (e.g., Inter, Manrope, system-ui).

* [ ] **Modular Scale:** Define distinct sizes for H1, H2, H3, H4, Body Large, Body Medium (Default), Body Small/Caption. (e.g., H1: 32px, Body: 14px/16px).

* [ ] **Font Weights:** Utilize a limited set of weights (e.g., Regular, Medium, SemiBold, Bold).

* [ ] **Line Height:** Ensure generous line height for readability (e.g., 1.5-1.7 for body text).

* [ ] **Define Spacing Units:**

* [ ] **Base Unit:** Establish a base unit (e.g., 8px).

* [ ] **Spacing Scale:** Use multiples of the base unit for all padding, margins, and layout spacing (e.g., 4px, 8px, 12px, 16px, 24px, 32px).

* [ ] **Define Border Radii:**

* [ ] **Consistent Values:** Use a small set of consistent border radii (e.g., Small: 4-6px for inputs/buttons; Medium: 8-12px for cards/modals).

* [ ] **Develop Core UI Components (with consistent states: default, hover, active, focus, disabled):**

* [ ] Buttons (primary, secondary, tertiary/ghost, destructive, link-style; with icon options)

* [ ] Input Fields (text, textarea, select, date picker; with clear labels, placeholders, helper text, error messages)

* [ ] Checkboxes & Radio Buttons

* [ ] Toggles/Switches

* [ ] Cards (for content blocks, multimedia items, dashboard widgets)

* [ ] Tables (for data display; with clear headers, rows, cells; support for sorting, filtering)

* [ ] Modals/Dialogs (for confirmations, forms, detailed views)

* [ ] Navigation Elements (Sidebar, Tabs)

* [ ] Badges/Tags (for status indicators, categorization)

* [ ] Tooltips (for contextual help)

* [ ] Progress Indicators (Spinners, Progress Bars)

* [ ] Icons (use a single, modern, clean icon set; SVG preferred)

* [ ] Avatars


III. Layout, Visual Hierarchy & Structure


* [ ] **Responsive Grid System:** Design based on a responsive grid (e.g., 12-column) for consistent layout across devices.

* [ ] **Strategic White Space:** Use ample negative space to improve clarity, reduce cognitive load, and create visual balance.

* [ ] **Clear Visual Hierarchy:** Guide the user's

🎯 Best For

  • Claude users
  • Claude Code users
  • Designers
  • Creative professionals
  • Product teams

💡 Use Cases

  • Design system documentation
  • Component specification creation

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or Claude Code and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Workflow: Design Principles Example to Your Work

    Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.

  4. 4

    Review and Refine

    Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.

❓ Frequently Asked Questions

Does Workflow: Design Principles Example generate production-ready design specs?

It generates detailed specifications that developers can use directly. Review and adjust for your specific design system.

How do I install Workflow: Design Principles Example?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/claude-design-principles-example/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Not reading the full skill

Skills contain important context and edge cases beyond the quick start.

🔗 Related Skills