Apple HIG: Project Context
Selective Reading Rule
Start with:
references/senior-master-standard.mdreferences/usage-routing.mdreferences/quality-checklist.md
Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.
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: ALWAYS use this when the request matches HIG Project Context: Create or update a shared Apple design context document that other HIG skills use to tailor guidance.4---56# Apple HIG: Project Context78## Selective Reading Rule910Start with:1112- `references/senior-master-standard.md`13- `references/usage-routing.md`14- `references/quality-checklist.md`1516Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.1718Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.1920Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.2122## Gathering Context2324Before asking questions, auto-discover context from:25261. **README.md** -- Product description, platform targets272. **Package.swift / .xcodeproj** -- Supported platforms, minimum OS versions, dependencies283. **Info.plist** -- App category, required capabilities, supported orientations294. **Existing code** -- Import statements reveal frameworks (SwiftUI vs UIKit, HealthKit, etc.)305. **Assets.xcassets** -- Color assets, icon sets, dark mode variants316. **Accessibility audit** -- Grep for accessibility modifiers/attributes3233Present findings and ask the user to confirm or correct. Then gather anything still missing:3435### 1. Product Overview36- What does the app do? (one sentence)37- Category (productivity, social, health, game, utility, etc.)38- Stage (concept, development, shipped, redesign)3940### 2. Target Platforms41- Which Apple platforms? (iOS, iPadOS, macOS, tvOS, watchOS, visionOS)42- Minimum OS versions43- Universal or platform-specific?4445### 3. Technology Stack46- UI framework: SwiftUI, UIKit, AppKit, or mixed?47- Architecture: single-window, multi-window, document-based?48- Apple technologies in use? (HealthKit, CloudKit, ARKit, etc.)4950### 4. Design System51- System defaults or custom design system?52- Brand colors, fonts, icon style?53- Dark mode and Dynamic Type support status5455### 5. Accessibility Requirements56- Target level (baseline, enhanced, comprehensive)57- Specific considerations (VoiceOver, Switch Control, etc.)58- Regulatory requirements (WCAG, Section 508)5960### 6. User Context61- Primary personas (1-3)62- Key use cases and environments (desk, on-the-go, glanceable, immersive)63- Known pain points or design challenges6465### 7. Existing Design Assets66- Figma/Sketch files?67- Apple Design Resources in use?68- Existing component library?6970## Context Document Template7172Generate `.claude/apple-design-context.md` using this structure:7374```markdown75# Apple Design Context7677## Product78- **Name**: [App name]79- **Description**: [One sentence]80- **Category**: [Category]81- **Stage**: [Concept / Development / Shipped / Redesign]8283## Platforms84| Platform | Supported | Min OS | Notes |85|----------|-----------|--------|-------|86| iOS | Yes/No | | |87| iPadOS | Yes/No | | |88| macOS | Yes/No | | |89| tvOS | Yes/No | | |90| watchOS | Yes/No | | |91| visionOS | Yes/No | | |9293## Technology94- **UI Framework**: [SwiftUI / UIKit / AppKit / Mixed]95- **Architecture**: [Single-window / Multi-window / Document-based]96- **Apple Technologies**: [List any: HealthKit, CloudKit, ARKit, etc.]9798## Design System99- **Base**: [System defaults / Custom design system]100- **Brand Colors**: [List or reference]101- **Typography**: [System fonts / Custom fonts]102- **Dark Mode**: [Supported / Not yet / N/A]103- **Dynamic Type**: [Supported / Not yet / N/A]104105## Accessibility106- **Target Level**: [Baseline / Enhanced / Comprehensive]107- **Key Considerations**: [List any specific needs]108109## Users110- **Primary Persona**: [Description]111- **Key Use Cases**: [List]112- **Known Challenges**: [List]113```114115## Updating Context116117When updating an existing context document:1181191. Read the current `.claude/apple-design-context.md`1202. Ask what has changed1213. Update only the changed sections1224. Preserve all unchanged information123124## Related Skills125126- **hig-platforms** -- Platform-specific guidance127- **hig-foundations** -- Color, typography, layout decisions128- **hig-patterns** -- UX pattern recommendations129- **hig-components-*** -- Component recommendations130- **hig-inputs** -- Input method coverage131- **hig-technologies** -- Apple technology relevance132133---134135*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*136137## When to Use138This skill is applicable to execute the workflow or actions described in the overview.139140## Limitations141- Use this skill only when the task clearly matches the scope described above.142- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.143- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
anhvu1107