hig-foundations
by raintree-technologyhig-foundations is the Apple HIG foundations skill for UI Design. Use it for color, typography, symbols, materials, motion, privacy, layout, RTL, accessibility, and system-aligned decisions before moving into patterns or components.
This skill scores 84/100, which means it is a solid listing candidate for directory users. It has a clear trigger scope for Apple HIG foundations topics and enough workflow guidance to help an agent act with less guesswork than a generic prompt, though it would benefit from more operational detail and supporting assets.
- Strong triggerability: the frontmatter explicitly lists many user intents such as HIG color, typography, accessibility, dark mode, Dynamic Type, contrast, and icon/style questions.
- Good operational guidance: the body includes key principles and a direct instruction to check existing `.claude/apple-design-context.md` before asking questions, which helps agents use prior context.
- Useful cross-references: it points users to related skills for platforms, patterns, and components, improving routing across the skill set.
- No install command, scripts, or reference files are present, so adoption depends entirely on the markdown instructions rather than executable support.
- The repository appears to be a single skill file with no supporting resources, which limits depth for edge cases and advanced implementation workflows.
Overview of hig-foundations skill
hig-foundations is the Apple Human Interface Guidelines foundations skill for early design decisions that affect clarity, accessibility, and system fit. Use the hig-foundations skill when you need practical guidance on color, typography, symbols, materials, motion, privacy, layout, RTL, or inclusive design for Apple platforms. It is best for UI designers, product teams, and agents that need to turn a rough interface idea into Apple-aligned design choices without guessing.
What hig-foundations is for
This skill helps answer “what should this look and feel like?” before you move into screens, components, or platform patterns. It is especially useful when the problem is foundational: dark mode contrast, Dynamic Type support, using system colors, choosing a font, or making icons feel native. If the goal is to align a feature with Apple HIG rather than invent a custom visual language, hig-foundations is the right starting point.
When it is the right fit
Use hig-foundations for UI Design when you need decisions that apply across an app, not just one screen. It fits cases like brand styling on Apple devices, accessibility-first visual systems, and foundation reviews for product specs or design prompts. It is less useful if you already need a narrow interaction pattern or platform-specific implementation detail.
Main differentiators
The value of hig-foundations is that it pushes you toward system defaults and accessibility-aware choices instead of decorative design guesses. The skill also points you to related HIG areas through cross-references, so you can move from foundations into platforms, patterns, or components without starting over. That makes the hig-foundations guide more practical than a generic “follow Apple style” prompt.
How to Use hig-foundations skill
Install and prepare the skill
Install with npx skills add raintree-technology/apple-hig-skills --skill hig-foundations. For best results, use it in a workflow where the agent can inspect the skill file and nearby context before drafting recommendations. The hig-foundations install is most effective when you keep your product goal, target platform, and accessibility constraints ready to share.
Give the skill the right input
A weak prompt says: “Make this feel more Apple-like.” A stronger prompt says: “Apply hig-foundations to this iOS onboarding screen: use system colors, support Dynamic Type, keep motion minimal, and make the CTA readable in dark mode.” Include the platform, audience, existing design constraints, and any known problem such as contrast, icon mismatch, or RTL layout. The more concrete the current state, the less the skill has to infer.
Read the source in this order
Start with SKILL.md, because it contains the core decision rules and cross-references. Then inspect any linked repo context mentioned in the skill, especially README.md, AGENTS.md, metadata.json, and supporting folders if they exist. In this repository, the key practical signal is the guidance inside SKILL.md itself, so a quick pass there usually tells you whether the hig-foundations usage matches your task.
Workflow that produces better output
Use the skill in three steps: define the UI problem, constrain it with platform and accessibility requirements, then ask for a recommendation or rewrite. For example: “Review this iPad settings page against hig-foundations and suggest changes for color, hierarchy, and touch target clarity.” This gives the model a concrete design surface to evaluate instead of forcing it to invent one from scratch. If you are working from copy or a wireframe, include both; foundation guidance improves when text and layout are reviewed together.
hig-foundations skill FAQ
Is hig-foundations only for designers?
No. The hig-foundations skill is useful for designers, PMs, frontend engineers, and agents that need Apple-aligned UI direction. If you are writing implementation tickets or reviewing interface copy, it can still help because many foundation issues affect code as much as visuals.
How is it different from a generic prompt?
A generic prompt may mention Apple style, but hig-foundations gives you a reusable decision frame for foundations such as system colors, accessibility, and visual hierarchy. That usually reduces vague output and makes the hig-foundations guide more reliable for repeated use across screens or features. It is still not a substitute for product context, but it is more disciplined than asking for “better design” in plain language.
When should I not use this skill?
Do not use hig-foundations if you need a highly specific interaction pattern, a component library decision, or a platform implementation deep dive. In those cases, a more focused skill or a direct platform guide will be faster. Also avoid it when the design already follows Apple conventions and you only need small copy edits.
Is it beginner-friendly?
Yes, if you can describe the product screen and the problem you are trying to solve. You do not need to know every HIG term in advance. The best hig-foundations usage comes from simple, explicit prompts that name the device, the issue, and the constraint set.
How to Improve hig-foundations skill
Give sharper design constraints
The biggest quality jump comes from stating what must not change: brand color, existing layout, supported languages, or minimum accessibility targets. For example, say “keep the current structure but make the hierarchy more Apple-like, preserve the brand accent, and pass dark mode contrast.” That lets the skill focus on tradeoffs instead of restating obvious advice.
Ask for decisions, not general principles
The hig-foundations skill is strongest when you ask it to choose. Prompt for “which system colors fit this status card?” or “should this motion be reduced or removed?” instead of “explain accessibility.” Concrete decisions produce output you can apply immediately and review quickly.
Iterate with the first draft
After the first response, narrow the scope to the weakest part: typography, contrast, iconography, or layout density. Feed back the specific failure, such as “the CTA feels too prominent” or “the content is still too crowded for Dynamic Type.” Iteration works well with hig-foundations because foundation problems are usually easier to fix one layer at a time.