agentleFS
SharqiewiczSharqiewicz/skills/rules-apple/SKILL.md

rules-apple

Skill1 starsChanged 42 days agoNo licenceView on GitHub

Apple's Human Interface Guidelines translated for the web (CSS/HTML/JS/React), for frontend and design engineers. Use when building OR reviewing Apple-style interfaces: color & semantic tokens, dark mode, materials/translucency/backdrop-filter, typography & type scale, layout & safe areas, SF-style icons, accessibility, RTL, privacy/permission copy, UX writing — plus UX patterns (onboarding, loading/skeletons, feedback, modality, data entry & inline validation, search, settings, accounts/sign-in, notifications, undo/redo, drag & drop) — components (buttons, sheets, popovers, alerts, action sheets, menus, toggles, sliders, steppers, text fields, pickers, lists & tables, tab bars, toolbars, sidebars, search fields, segmented controls, progress indicators, badges) — inputs (gestures, keyboard, pointer/hover, focus & selection) — motion (springs, velocity, interruptibility, momentum, reduced-motion) — and Apple technologies on the web (Sign in with Apple, Apple Pay on the Web). Triggers on: Apple design, HIG, Human Interface Guidelines, iOS/macOS/iPadOS look, native-feeling web UI, Apple-style component, tap target, 44px, contrast ratio, prefers-color-scheme, prefers-reduced-motion, prefers-reduced-transparency, prefers-contrast, dark mode, backdrop-filter, translucency, vibrancy, Dynamic Type, safe-area-inset, semantic color, sheet, action sheet, popover, alert dialog, segmented control, tab bar, toolbar, sidebar, skeleton screen, inline validation, modal usage, delayed sign-in, Sign in with Apple, Apple Pay web.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.