hig-project-context
Skill153 starsChanged 9 months agoMITView on GitHub
Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says "set up my project context," "what platforms am I targeting," "configure HIG settings," or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- lucaszb-orla/claude-skillsword for word, first seen Oct 8, 2026
- ozgurakkaya90/claude-skillsword for word, first seen Aug 2, 2026
Other versions2 projects use a version of this.
Word for word · 2
- lucaszb-orla/claude-skills★ 0100% same
- ozgurakkaya90/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hig-components-contentSkill
- hig-components-controlsSkill
- hig-components-dialogsSkill
- hig-components-layoutSkill
- hig-components-menusSkill
- hig-components-searchSkill
- hig-components-statusSkill
- hig-components-systemSkill
- hig-foundationsSkill
- hig-inputsSkill
- hig-patternsSkill
- hig-platformsSkill
- hig-technologiesSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Create and maintain .claude/apple-design-context.md so other HIG skills can skip redundant questions.
- Very specific: line 18
Check for .claude/apple-design-context.md before asking questions.
- Distinctive: line 22
Before asking questions, auto-discover context from:
- Distinctive: line 115
When updating an existing context document:
- Very specific: line 117
Read the current .claude/apple-design-context.md
- Distinctive: line 118
Ask what has changed
- Distinctive: line 119
Update only the changed sections
≈ “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.
Files
Apple HIG: Project Context
Create and maintain .claude/apple-design-context.md so other HIG skills can skip redundant questions.
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
Gathering Context
Before asking questions, auto-discover context from:
- README.md -- Product description, platform targets
- Package.swift / .xcodeproj -- Supported platforms, minimum OS versions, dependencies
- Info.plist -- App category, required capabilities, supported orientations
- Existing code -- Import statements reveal frameworks (SwiftUI vs UIKit, HealthKit, etc.)
- Assets.xcassets -- Color assets, icon sets, dark mode variants
- Accessibility audit -- Grep for accessibility modifiers/attributes
Present findings and ask the user to confirm or correct. Then gather anything still missing:
1. Product Overview
- What does the app do? (one sentence)
- Category (productivity, social, health, game, utility, etc.)
- Stage (concept, development, shipped, redesign)
2. Target Platforms
- Which Apple platforms? (iOS, iPadOS, macOS, tvOS, watchOS, visionOS)
- Minimum OS versions
- Universal or platform-specific?
3. Technology Stack
- UI framework: SwiftUI, UIKit, AppKit, or mixed?
- Architecture: single-window, multi-window, document-based?
- Apple technologies in use? (HealthKit, CloudKit, ARKit, etc.)
4. Design System
- System defaults or custom design system?
- Brand colors, fonts, icon style?
- Dark mode and Dynamic Type support status
5. Accessibility Requirements
- Target level (baseline, enhanced, comprehensive)
- Specific considerations (VoiceOver, Switch Control, etc.)
- Regulatory requirements (WCAG, Section 508)
6. User Context
- Primary personas (1-3)
- Key use cases and environments (desk, on-the-go, glanceable, immersive)
- Known pain points or design challenges
7. Existing Design Assets
- Figma/Sketch files?
- Apple Design Resources in use?
- Existing component library?
Context Document Template
Generate .claude/apple-design-context.md using this structure:
# Apple Design Context
## Product
- **Name**: [App name]
- **Description**: [One sentence]
- **Category**: [Category]
- **Stage**: [Concept / Development / Shipped / Redesign]
## Platforms
| Platform | Supported | Min OS | Notes |
|----------|-----------|--------|-------|
| iOS | Yes/No | | |
| iPadOS | Yes/No | | |
| macOS | Yes/No | | |
| tvOS | Yes/No | | |
| watchOS | Yes/No | | |
| visionOS | Yes/No | | |
## Technology
- **UI Framework**: [SwiftUI / UIKit / AppKit / Mixed]
- **Architecture**: [Single-window / Multi-window / Document-based]
- **Apple Technologies**: [List any: HealthKit, CloudKit, ARKit, etc.]
## Design System
- **Base**: [System defaults / Custom design system]
- **Brand Colors**: [List or reference]
- **Typography**: [System fonts / Custom fonts]
- **Dark Mode**: [Supported / Not yet / N/A]
- **Dynamic Type**: [Supported / Not yet / N/A]
## Accessibility
- **Target Level**: [Baseline / Enhanced / Comprehensive]
- **Key Considerations**: [List any specific needs]
## Users
- **Primary Persona**: [Description]
- **Key Use Cases**: [List]
- **Known Challenges**: [List]Updating Context
When updating an existing context document:
- Read the current
.claude/apple-design-context.md - Ask what has changed
- Update only the changed sections
- Preserve all unchanged information
Related Skills
- hig-platforms -- Platform-specific guidance
- hig-foundations -- Color, typography, layout decisions
- hig-patterns -- UX pattern recommendations
- hig-components-* -- Component recommendations
- hig-inputs -- Input method coverage
- hig-technologies -- Apple technology relevance
Built by Raintree Technology · More developer tools
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
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.