TypingMindTypingMindThe best frontend for AI
Hig Components System logo

Hig Components System

Organization
raintree-technology
hig-components-system

Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: "widget design", "live activity", "notification design", "complication", "home screen quick action", "top shelf", "watch face", "app clip", "app shortcut", "system experience". Also use when the user says "how do I design a widget," "what should my notification look like," "how do Live Activities work," "should I make an App Clip," or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.

Overview

Publisherraintree-technology
Repositoryhig-doctor
Skill namehig-components-system
Stars
148
Forks
10
Bundled files
9
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 9 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by raintree-technology on GitHub. Read the source before you install it.

Installation

Install the Hig Components System AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-components-system
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/raintree-technology/hig-doctor.git /tmp/hig-doctor
mkdir -p .claude/skills
cp -r /tmp/hig-doctor/skills/hig-components-system .claude/skills/hig-components-system
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hig Components System in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hig Components System on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hig Components System is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Apple HIG: System Experiences

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

  1. Glanceable, immediate value. System experiences bring your app's most important content to surfaces the user sees without launching your app. Design for seconds of attention.

  2. Respect platform context. A Lock Screen widget has different constraints than a Home Screen widget. A complication is far smaller than a top shelf item.

  3. Widgets: show relevant information, not everything. Display the most useful subset, updated appropriately.

  4. Support multiple widget sizes with distinct layouts. Each size should be a thoughtful design, not a scaled version of another.

  5. Deep-link on tap. Take users to the relevant content, not the app's root screen.

  6. Live Activities: track events with a clear start and end. Deliveries, scores, timers, rides. Design for both Dynamic Island and Lock Screen.

  7. Stay updated and timely. Stale data undermines trust. End promptly when the event concludes.

  8. Respect user attention with notifications. Only send notifications for information users genuinely care about. No promotional or low-value notifications.

  9. Notifications: actionable and self-contained. Include enough context to understand and act without opening the app. Support notification actions. Use threading and grouping.

  10. Complications: focused data on the watch face. Design for the smallest useful representation. Support multiple families. Budget updates wisely.

  11. Home Screen quick actions: 3-4 most common tasks. Short titles, optional subtitles, relevant SF Symbol icons.

  12. Top Shelf: tvOS showcase. Feature content that entices: new episodes, featured items, recent content.

  13. App Clips: instant, focused functionality within a strict size budget. Load quickly without App Store download. Only what's needed for the immediate task, then offer full app install.

  14. App Shortcuts: surface key actions to Siri and Spotlight. Define shortcuts for frequent tasks. Use natural, conversational trigger phrases.

Reference Index

ReferenceTopicKey content
widgets.mdWidgetsGlanceable info, sizes, deep linking, timeline
live-activities.mdLive ActivitiesReal-time tracking, Dynamic Island, Lock Screen
notifications.mdNotificationsAttention, actions, grouping, content
complications.mdComplicationsWatch face data, families, budgeted updates
home-screen-quick-actions.mdQuick actionsHaptic Touch, common tasks, SF Symbols
top-shelf.mdTop shelfFeatured content, showcase
app-clips.mdApp ClipsInstant use, lightweight, focused task, NFC/QR
watch-faces.mdWatch facesCustom complications, face sharing
app-shortcuts.mdApp ShortcutsSiri, Spotlight, voice triggers

Output Format

  1. System experience recommendation -- which surface best fits the use case.
  2. Content strategy -- what to display, priority, what to omit.
  3. Update frequency -- refresh rate including system budget constraints.
  4. Size/family variants -- which to support and how layout adapts.
  5. Deep link behavior -- where tapping takes the user.

Questions to Ask

  1. What information needs to surface outside the app?
  2. Which platform?
  3. How frequently does the data update?
  4. What is the primary glanceable need?

Related Skills

  • hig-components-status -- Progress indicators in widgets or Live Activities
  • hig-inputs -- Interaction patterns for system experiences (Digital Crown for complications)
  • hig-technologies -- Siri for App Shortcuts, HealthKit for complications, NFC for App Clips

Built by Raintree Technology · More developer tools

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Hig Components System AI skill do?

Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: "widget design", "live activity", "notification design", "complication", "home screen quick action", "top shelf", "watch face", "app clip", "app shortcut", "system experience". Also use when the user says "how do I design a widget," "what should my notification look like," "how do Live Activities work," "should I make an App Clip," or asks about surfaces outside the main app. Cross-...

Why use Hig Components System on TypingMind?

Because you install it once and use it with any model. Hig Components System is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hig Components System in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-components-system. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Hig Components System?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hig Components System?

As many as you like. As long as a model supports skills, you can use Hig Components System with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hig Components System AI skill free?

Yes. It is published on GitHub by raintree-technology under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Openclaw Test Performance

openclaw
OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

82.2K
391K
1 files
View
openclaw logo

Openclaw Testing

openclaw
OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

82.2K
391K
2 files
View
openclaw logo

Release Openclaw Ci

openclaw
OrganizationPopular

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

82.2K
391K
3 files
View
openclaw logo

Release Openclaw Mac

openclaw
OrganizationPopular

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

82.2K
391K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇