Hey, it's Cindy 馃尡 You commented apple, so here's the skill from the reel with the real links, the exact install command, and what to ask it once it's in.
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)
set it up
What this actually is
It is an AI design reviewer grounded in Apple's Human Interface Guidelines, packaged as an agent skill. It audits against 123 HIG pages pulled straight from developer.apple.com, and it translates Apple's vocabulary into whatever you actually build in. The point is not to make your site look like Apple's. It is to apply the structural rules underneath it.
1 路 Install it One command, and it works for Claude Code, Codex, Cursor, Antigravity, OpenCode and Windsurf: npx skills add dickwu/apple-design-skilldickwu/apple-design-skill
2 路 Or clone it by hand Claude Code reads skills from .claude/skills/ in a project, or ~/.claude/skills/ for everything. Clone it into either. the repo
3 路 Trigger it It fires on any design-review request, and it is also available directly as /apple-design. how it triggers
4 路 Point it at what you already built This is the part people miss. You do not need a new project. Ask it to audit the site that exists. Apple's HIG, the source
5 路 Keep it updatednpx skills update apple-design pulls the latest version later, so your rules do not go stale. the skills CLI
the part that makes it work
What to actually ask it
"Make it look more premium" is the prompt that produces generic. Ask for the audit instead, and make it name the rule it is applying.
1 路 Audit, do not restyle Ask it to review what you built against the HIG and list what is wrong, before it changes a single thing. You get to disagree before any code moves. the skill
2 路 Make it cite the rule For each issue, ask which HIG principle it comes from. If it cannot name one, it is an opinion, not a rule, and you can ignore it. Apple's guidelines
3 路 Ask for the structural fixes first Spacing, balance, type scale and hierarchy. These are what make something read as considered. Shadow opacity and radius are the last five percent, not the first. Apple on layout
4 路 Then ask what it deliberately left alone A good audit says what is already fine. If everything is flagged, it is pattern-matching rather than reviewing. the repo
馃尡 Do not copy Apple's look. Their visual style on your product reads as costume. What transfers is the discipline underneath it: consistent spacing, a real type scale, and restraint.
what it speaks
It translates into what you actually build in
Apple's vocabulary is written for Apple's platforms. This skill maps it across, which is why it is useful even if you never ship an app.
React Native and Flutter Cross-platform mobile, with Apple's rules translated to each one's own layout language. see the list
Tauri and Electron Desktop apps built with web tech, which is where most indie desktop work lives. see the list
SwiftUI, UIKit and AppKit Apple's own frameworks, where the guidelines were written to apply in the first place. the HIG
iPhone Duo layouts It covers the two-display layouts specifically, which almost nothing else does yet. the repo
the honest bit
Two things worth knowing
1 路 A design skill cannot save a weak structure If the page has no hierarchy, this will make the spacing consistent and the page will still be boring. Fix what goes on the page first. start with hierarchy
2 路 Apple's rules are opinions, held very consistently That consistency is the value. It is not the only good design language, and on a warm, hand-made brand it can read as cold. Take the discipline, not the personality. the skill
the waitlist is now open
AI System Club is launching soon
Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.
btw this list gets first dibs the moment doors open :)