Hig Project Context
>-
mkdir -p ./skills/hig-project-context && curl -sfL https://raw.githubusercontent.com/mayurrathi/awesome-agent-skills/main/skills/hig-project-context/SKILL.md -o ./skills/hig-project-context/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 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:
1. **README.md** -- Product description, platform targets
2. **Package.swift / .xcodeproj** -- Supported platforms, minimum OS versions, dependencies
3. **Info.plist** -- App category, required capabilities, supported orientations
4. **Existing code** -- Import statements reveal frameworks (SwiftUI vs UIKit, HealthKit, etc.)
5. **Assets.xcassets** -- Color assets, icon sets, dark mode variants
6. **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:
```markdown
# 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:
1. Read the current `.claude/apple-design-context.md`
2. Ask what has changed
3. Update only the changed sections
4. 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](https://raintree.techn
🎯 Best For
- Claude users
- Software engineers
- Development teams
- Tech leads
💡 Use Cases
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Hig Project Context to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is Hig Project Context compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for Hig Project Context?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install Hig Project Context?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/hig-project-context/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.