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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: hig-project-context3description: Create or update a shared Apple design context document that other HIG skills use to tailor guidance.4license: MIT5---6
7# Apple HIG: Project Context
8
9Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.
10
11Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
12
13## Gathering Context
14
15Before asking questions, auto-discover context from:
16
171. **README.md** -- Product description, platform targets
182. **Package.swift / .xcodeproj** -- Supported platforms, minimum OS versions, dependencies
193. **Info.plist** -- App category, required capabilities, supported orientations
204. **Existing code** -- Import statements reveal frameworks (SwiftUI vs UIKit, HealthKit, etc.)
215. **Assets.xcassets** -- Color assets, icon sets, dark mode variants
226. **Accessibility audit** -- Grep for accessibility modifiers/attributes
23
24Present findings and ask the user to confirm or correct. Then gather anything still missing:
25
26### 1. Product Overview
27- What does the app do? (one sentence)
28- Category (productivity, social, health, game, utility, etc.)
29- Stage (concept, development, shipped, redesign)
30
31### 2. Target Platforms
32- Which Apple platforms? (iOS, iPadOS, macOS, tvOS, watchOS, visionOS)
33- Minimum OS versions
34- Universal or platform-specific?
35
36### 3. Technology Stack
37- UI framework: SwiftUI, UIKit, AppKit, or mixed?
38- Architecture: single-window, multi-window, document-based?
39- Apple technologies in use? (HealthKit, CloudKit, ARKit, etc.)
40
41### 4. Design System
42- System defaults or custom design system?
43- Brand colors, fonts, icon style?
44- Dark mode and Dynamic Type support status
45
46### 5. Accessibility Requirements
47- Target level (baseline, enhanced, comprehensive)
48- Specific considerations (VoiceOver, Switch Control, etc.)
49- Regulatory requirements (WCAG, Section 508)
50
51### 6. User Context
52- Primary personas (1-3)
53- Key use cases and environments (desk, on-the-go, glanceable, immersive)
54- Known pain points or design challenges
55
56### 7. Existing Design Assets
57- Figma/Sketch files?
58- Apple Design Resources in use?
59- Existing component library?
60
61## Context Document Template
62
63Generate `.claude/apple-design-context.md` using this structure:
64
65```markdown
66# Apple Design Context
67
68## Product
69- **Name**: [App name]
70- **Description**: [One sentence]
71- **Category**: [Category]
72- **Stage**: [Concept / Development / Shipped / Redesign]
73
74## Platforms
75| Platform | Supported | Min OS | Notes |
76|----------|-----------|--------|-------|
77| iOS | Yes/No | | |
78| iPadOS | Yes/No | | |
79| macOS | Yes/No | | |
80| tvOS | Yes/No | | |
81| watchOS | Yes/No | | |
82| visionOS | Yes/No | | |
83
84## Technology
85- **UI Framework**: [SwiftUI / UIKit / AppKit / Mixed]
86- **Architecture**: [Single-window / Multi-window / Document-based]
87- **Apple Technologies**: [List any: HealthKit, CloudKit, ARKit, etc.]
88
89## Design System
90- **Base**: [System defaults / Custom design system]
91- **Brand Colors**: [List or reference]
92- **Typography**: [System fonts / Custom fonts]
93- **Dark Mode**: [Supported / Not yet / N/A]
94- **Dynamic Type**: [Supported / Not yet / N/A]
95
96## Accessibility
97- **Target Level**: [Baseline / Enhanced / Comprehensive]
98- **Key Considerations**: [List any specific needs]
99
100## Users
101- **Primary Persona**: [Description]
102- **Key Use Cases**: [List]
103- **Known Challenges**: [List]
104```
105
106## Updating Context
107
108When updating an existing context document:
109
1101. Read the current `.claude/apple-design-context.md`
1112. Ask what has changed
1123. Update only the changed sections
1134. Preserve all unchanged information
114
115## Related Skills
116
117- **hig-platforms** -- Platform-specific guidance
118- **hig-foundations** -- Color, typography, layout decisions
119- **hig-patterns** -- UX pattern recommendations
120- **hig-components-*** -- Component recommendations
121- **hig-inputs** -- Input method coverage
122- **hig-technologies** -- Apple technology relevance
123
124---
125
126*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
127
128## When to Use
129This skill is applicable to execute the workflow or actions described in the overview.
130
131## Limitations
132- Use this skill only when the task clearly matches the scope described above.
133- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
134- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
nous-hermeshub