hig-project-context
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
Best use case
hig-project-context is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
Teams using hig-project-context should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hig-project-context/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hig-project-context Compares
| Feature / Agent | hig-project-context | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.technology) · [More developer tools](https://raintree.technology)* ## 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.
Related Skills
systems-programming-rust-project
You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing
startup-business-analyst-financial-projections
Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios
sred-project-organizer
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
redesign-existing-projects
Use when upgrading existing websites or apps by auditing generic UI patterns and applying premium design fixes without rewrites.
recursive-context-pruning-token-budgeting
Optimizes AI agent performance by pruning redundant context, managing token usage, and enforcing ultra-concise, direct-to-value responses.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
project-skill-audit
Audit a project and recommend the highest-value skills to add or update.
project-development
This skill covers the principles for identifying tasks suited to LLM processing, designing effective project architectures, and iterating rapidly using agent-assisted development.
product-marketing-context
Create or update a reusable product marketing context document with positioning, audience, ICP, use cases, and messaging. Use at the start of a project to avoid repeating core marketing context across tasks.
odoo-project-timesheet
Expert guide for Odoo Project and Timesheets: task stages, billable time tracking, timesheet approval, budget alerts, and invoicing from timesheets.
new-rails-project
Create a new Rails project
filesystem-context
Use for file-based context management, dynamic context discovery, and reducing context window bloat. Offload context to files for just-in-time loading.