apple-design-skill
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-06
- Stars
- ★ 0
- Forks
- 0
02 资源文件 21
- 参考文档app.md10.3 KB
- 参考文档checklist.md3.1 KB
- 参考文档components.md8.0 KB
- 参考文档design-system.md9.5 KB
- 参考文档examples/account.html18.8 KB
- 资产文件examples/screenshots/01-hero-tiers.png184.7 KB
- 资产文件examples/screenshots/02-unified-panel.png138.0 KB
- 资产文件examples/screenshots/03-modal-sheet.png266.5 KB
- 资产文件examples/screenshots/04-mobile.png561.3 KB
- 资产文件examples/screenshots/05-app-wallet.png304.3 KB
- 资产文件examples/screenshots/06-app-sheet.png305.8 KB
- 参考文档examples/wallet.html9.6 KB
- 参考文档icons.md5.4 KB
- 许可证LICENSE2.3 KB
- 参考文档motion.md7.1 KB
- 参考文档patterns.md3.7 KB
- 参考文档README.md8.6 KB
- 参考文档README.zh-CN.md8.4 KB
- 参考文档reference.html23.3 KB
- 参考文档review.md3.7 KB
- 其他tokens.css5.0 KB
03 SKILL.md 正文
Apple Liquid Glass — Design Skill
You are designing in the latest Apple visual language: calm, premium, restrained. The goal is that a user feels "this looks like Apple" within 1.5 seconds — not through gimmicks, but through the sum of small correct decisions.
One sentence: Apple light grey-white ground + unified white surfaces + hairline dividers; glass only where layers truly overlap. Restraint is the luxury.
When to use
- Building any web page / component / app screen meant to feel Apple-grade (App / iOS screens: also read
app.mdfor the device frame + mobile shell). - Redesigning a UI that feels fragmented, "carded", or generic.
- The user mentions Apple, apple.com, macOS, liquid glass, 苹果风, 液态玻璃, or "clean / premium / minimal".
The 5 philosophy rules (decide by these, in order)
- Unified surface > fragmented cards. Many sibling items go on one white panel with hairline dividers, not a pile of separately-bordered, separately-tinted cards. Fragmentation is enemy #1.
- Glass is seasoning, not the dish.
backdrop-filterfrost only where layers actually overlap: sticky nav, modals/popovers, colored CTA blocks. Plain content areas get solid#fff+ soft shadow — never glass. (Web has few overlapping layers; over-glassing reads as dirty.) - Restraint is luxury. A thousand "no"s for one "yes". If whitespace and hierarchy can solve it, don't add a border, fill, icon, or number. Reject data-slop.
- Hierarchy from weight + size + grayscale, not color. The body world is black-white-grey. Color is only for accent (one blue), heat (one orange), brand/live. Never color to fill space.
- Apple quality lives in details. Negative letter-spacing on big titles,
tabular-numsnumbers, hairline dividers, gentle hover lift, 180%-saturation glass — the total of these small things is what reads as "Apple".
Interaction foundations (reason with these names, beyond the visual)
- Wayfinding — every screen answers four questions: Where am I? Where can I go? What's there? How do I get out? Never trap the user.
- Feedback comes in four kinds: status, completion, warning, error. Validate inline, not on submit; expose ongoing status.
- Grouping & mapping. Place a control next to what it affects; arrange controls to mirror what they change. If a control needs a label to be understood, the mapping is weak.
- Agency & forgiveness. Easy undo beats confirmation dialogs; reserve confirmations for genuinely destructive, irreversible actions (overuse trains click-through).
- Direct, specific labels beat safe generic ones. "Progress" / "Library", not "Home". Specificity creates predictability.
Two modes
- Build — making new UI. Follow the workflow below.
- Review — auditing existing CSS / a page / a component for "is this Apple / make it consistent". Use
review.md(find the real visual surface → score against the system → prioritized findings → fix toward the tokens). The biggest wins are usually one off-system theme file that everything renders through.
Workflow — Build mode (follow in order)
- Read
design-system.md— the full spec (color, type, spacing, radius, shadow, glass recipe, components, responsive). - Drop in
tokens.css— the:rootcustom properties. Reference everything viavar(--…); never hard-code raw hex/px that a token already names. - Pick a page recipe from
patterns.md— container (720 read / 1080 grid), archetype (detail / index / home / form), and run its decision trees (panel vs cards, glass vs solid, color vs grayscale). - Compose from
components.md— copy the proven snippets (nav, unified panel list, card/grid, segmented pill, tag, button, colored CTA, live dot). Adapt content, keep structure + tokens. - If it's an App / iOS screen (mobile mockup, app 原型, anything inside a phone) — read
app.mdfor the mobile shell the core files don't ship: device frame (exact iPhone spec — never hand-roll the island/status bar/home indicator), large-title-collapse nav, tab bar, edge-anchored bottom sheet, safe areas, touch targets. The content still comes fromcomponents.md;app.mdis only the shell around it, and the same rules hold (unified panels, glass-on-overlap, grayscale + one accent, no color-by-status on list values). Needs icons (tab bar, object-type rows, actions)? Readicons.md— the line-icon layer (curated Lucide inline set, one 24-grid stroke, grayscalecurrentColor, accent only on action/active, and the restraint rules so icons earn their place — no grey squares, no emoji). - If the UI has interactive layers (dialog / sheet / popover / drawer / anything summoned & dismissed) — read
motion.mdand apply the fluid-motion treatment: pointer-down feedback, spring-like easing tokens, same-path enter/exit, materialize (blur+scale+opacity together), interruptibility, and the three reduced-* media queries. Static content keeps the tiny motion budget. - Check against
reference.html— open it; your output must look like it belongs on the same page. If a screenshot diverges, fix toward the reference. - Run the gate —
checklist.md(or the condensed self-check below) before claiming done; interactive layers also pass the motion self-check at the end ofmotion.md; App screens pass the App self-check at the end ofapp.md.
Portable: these files assume no framework. In React/Vue/etc., translate the CSS to your styling system but keep the exact token values, the panel-not-cards pattern, and the glass-only-on-overlap rule. Match the visual output; don't copy structure that doesn't fit.
Anti-slop — what makes it NOT Apple (avoid every one)
- ❌ Fragmented cards: each item with its own border + tint + colored left-bar. → one panel + hairlines.
- ❌ Glass everywhere: blurring plain content blocks. → glass only on nav/overlay/CTA.
- ❌ Color as decoration: tinted backgrounds, multi-color, rainbow gradients washing the page. → grayscale body, one accent.
- ❌ Generic fonts (Inter/Roboto/Arial as the brand face). → system SF / PingFang stack, negative tracking on titles.
- ❌ Warm cream / beige / kraft "paper" ground — the over-used AI look. → cool
#f5f5f7. - ❌ Purple-gradient-on-white hero, hard black borders, heavy single drop-shadows, emoji confetti, "in today's fast-paced world" filler.
- ❌ Even, timid spacing: everything equally padded. → intentional whitespace, sections breathe (
clamp(34px,6vw,56px)), panels short or tall as needed. - ❌ Numbers/stats added to look "data-rich". → only numbers that carry meaning, in
tabular-nums.
Self-check (gate before "done")
- [ ] Ground
#f5f5f7(cool), content on#fffsurfaces, container centered (max-width720 reading / 1080 grid). - [ ] Sibling items use one panel + hairline (
rgba(0,0,0,0.07)), not fragmented cards. - [ ] Glass appears only on nav / overlay / CTA. Plain blocks are solid white + soft shadow.
- [ ] Big titles have negative letter-spacing; long body line-height ≥ 1.85; numbers
tabular-nums. - [ ] Radius + shadow taken from the named token tiers, not ad-hoc values.
- [ ] Accent color is blue / heat-orange / brand only — everything else grayscale.
- [ ] Layout uses flex/grid +
gap(not inline + margin); touch targets ≥ 44px;clamp()for responsive; mobile collapses to one column, secondary info hidden. - [ ] Removed avoidable noise (extra icons, stats, decoration, emoji).
- [ ] Visually matches
reference.html.
Files in this skill
design-system.md— full spec + token table + decision guidance.tokens.css—:rootcustom properties (portable; drop into any project).components.md— copy-paste HTML+CSS for every core component.patterns.md— page-level recipes (containers, archetypes) + decision trees.checklist.md— the standalone "done" gate.motion.md— fluid interaction layer: springs/easing, interruptibility, same-path + anchored origin, materialize, gesture physics, reduced-motion (adapted from emilkowalski/skills apple-design, MIT).app.md— App / iOS shell layer: device frame (exact iPhone spec), status bar, large-title-collapse nav, tab bar, edge-anchored bottom sheet, safe areas, mobile-first rules.icons.md— line-icon layer: Lucide-based inline set (24-grid, one stroke), grayscalecurrentColorwith accent only on action/active, size table, restraint rules.review.md— Review-mode workflow for auditing existing UI.reference.html— rendered "living style guide" (open it; your ground truth).
04 同仓库更多 Skills
frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on "design DNA", "extract design style", "analyze design", "design tokens from reference", "generate design from JSON", "design system from screenshot", "design profile", "style guide JSON", "visual effects analysis", "design with effects", "3d design analysis".
wireframe
Generate JSON wireframe with HTML preview
social-publishing
Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.
hermes-tweet
Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.