How do I install the Human Interface Guidelines Patterns skill?

Run npx skillmds@latest add caglarbaranbora/human-interface-guidelines-patterns in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Human Interface Guidelines Patterns safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Human Interface Guidelines Patterns?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Human Interface Guidelines Patterns free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Human Interface Guidelines Patterns?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Human Interface Guidelines Patterns by caglarbaranbora

Name: Human Interface Guidelines Patterns
Author: caglarbaranbora

Human Interface Guidelines Patterns

Route Human Interface Guidelines Patterns design tasks to the correct Knowledge Contracts -- onboarding, searching, settings, notifications, feedback, and undo/redo. Use when designing or reviewing an iOS/iPadOS first-run flow, in-app search placement, settings-screen structure, notification content/timing, status/error feedback, or undo/redo affordances. This is design-level guidance, not implementation code -- for UserNotifications/UIKit/SwiftUI implementation see the respective implementation domain; for copy wording see style-guide. Triggers on onboarding, first-run experience, searching, search UI, settings screen, notification design, feedback, error feedback, undo, redo, HIG patterns.

File contents

Human Interface Guidelines — Patterns Skill

Purpose

Route iOS/iPadOS Patterns design-guidance tasks to the minimum required Human Interface Guidelines Knowledge Contracts. v1 scope is a curated 6-topic subset of HIG Patterns, not the full section.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/human-interface-guidelines/.

First-run flow -> onboarding.md
Search UI -> searching.md
Settings screen structure -> settings.md
Notification design -> notifications.md
System/status feedback -> feedback.md
Undo/redo affordances -> undo-and-redo.md

Never load more than the contracts relevant to the specific question. For pattern copy/wording, route to skill.style-guide.writing instead. Notification design is covered here; the UserNotifications API belongs to a future Tier 2 domain, not yet built.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/human-interface-guidelines/ — do not guess or fall back to general knowledge. Foundations topics route to skill.human-interface-guidelines.foundations; Components/Inputs topics route to skill.human-interface-guidelines.components. Any other HIG Patterns topic (e.g. Charts, Drag and Drop, Entering Data, Full-Screen Experiences, Launching, Loading, Managing Accounts, Modality, Multitasking, Playing Audio, Printing, Ratings and Reviews, Sharing, Status, Syncing, Workouts) is out of scope (see docs/architecture/domain-map.md) — report that explicitly rather than answering from general knowledge.

This domain decides what a screen must communicate, never how the words are formed. Once the content requirement is settled, terminology, capitalization, and phrasing are style-guide's — stop and report that rather than wording the text here. The two directions are the same boundary read from opposite sides.

---name: human-interface-guidelines-patternsdescription: Route Human Interface Guidelines Patterns design tasks to the correct Knowledge Contracts -- onboarding, searching, settings, notifications, feedback, and undo/redo. Use when designing or reviewing an iOS/iPadOS first-run flow, in-app search placement, settings-screen structure, notification content/timing, status/error feedback, or undo/redo affordances. This is design-level guidance, not implementation code -- for UserNotifications/UIKit/SwiftUI implementation see the respective implementation domain; for copy wording see style-guide. Triggers on onboarding, first-run experience, searching, search UI, settings screen, notification design, feedback, error feedback, undo, redo, HIG patterns.---# Human Interface Guidelines — Patterns Skill## PurposeRoute iOS/iPadOS Patterns design-guidance tasks to the minimumrequired Human Interface Guidelines Knowledge Contracts. v1 scope is acurated 6-topic subset of HIG Patterns, not the full section.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/human-interface-guidelines/.- First-run flow -> onboarding.md- Search UI -> searching.md- Settings screen structure -> settings.md- Notification design -> notifications.md- System/status feedback -> feedback.md- Undo/redo affordances -> undo-and-redo.mdNever load more than the contracts relevant to the specific question.For pattern copy/wording, route to `skill.style-guide.writing` instead.Notification *design* is covered here; the UserNotifications APIbelongs to a future Tier 2 domain, not yet built.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/human-interface-guidelines/ — do not guess orfall back to general knowledge. Foundations topics route to`skill.human-interface-guidelines.foundations`; Components/Inputstopics route to `skill.human-interface-guidelines.components`. Anyother HIG Patterns topic (e.g. Charts, Drag and Drop, Entering Data,Full-Screen Experiences, Launching, Loading, Managing Accounts,Modality, Multitasking, Playing Audio, Printing, Ratings and Reviews,Sharing, Status, Syncing, Workouts) is out of scope (seedocs/architecture/domain-map.md) — report that explicitly rather thananswering from general knowledge.This domain decides what a screen must communicate, never how the wordsare formed. Once the content requirement is settled, terminology,capitalization, and phrasing are `style-guide`'s — stop and report thatrather than wording the text here. The two directions are the sameboundary read from opposite sides.

Frequently asked questions