Skip to main content
skill CX Codex

hig-project-context — Claude Code skill: Apple project context

Writes one shared document about your Apple project so the other HIG skills stop asking the same setup questions.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add raintree-technology/hig-doctor --skill hig-project-context -a claude-code
Open on GitHub

What hig-project-context does

The skill creates and maintains .claude/apple-design-context.md. That file holds the product description, target platforms, minimum OS versions, UI framework, design system, accessibility targets, personas and known design challenges. Other HIG skills — hig-foundations, hig-platforms, hig-components-*, hig-inputs, hig-technologies — read it and tailor their advice instead of interrogating you again.

Discovery runs before any questions. The skill checks README.md, Package.swift or .xcodeproj, Info.plist, import statements in your code, Assets.xcassets and accessibility modifiers. It shows what it found and asks you to confirm or correct. When a context file already exists, it reads that first and only asks about what changed, leaving the rest of the sections alone.

Run it at the start of an Apple project, or when the platform list and stack shift. Without the file, every other HIG skill will pull the same details out of you one more time.

What it helps with

  • pin down target platforms and minimum OS versions in one file
  • stop repeating stack and design-system answers to every HIG skill
  • collect project context from README, Info.plist and imports before answering by hand
  • update only the changed sections when the platform list shifts
  • record accessibility targets and personas for later recommendations

Example prompts for the agent

  • set up my project context
  • what platforms am I targeting?
  • configure HIG settings for a new watchOS target

How to install hig-project-context

1Skills CLI (Vercel)

npx skills add raintree-technology/hig-doctor --skill hig-project-context -a claude-code

2Manually: put the files in place

~/.claude/skills/hig-project-context/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hig-project-context/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hig-project-context

How do I install hig-project-context in Claude?

Run npx skills add raintree-technology/hig-doctor --skill hig-project-context -a claude-code. The skill lands at ~/.claude/skills/hig-project-context/SKILL.md.

What does hig-project-context do?

It creates and updates .claude/apple-design-context.md, a shared document covering product, platforms, stack, design system and accessibility. Other HIG skills read it to avoid repetitive questions.

Do I have to fill in the context by hand?

No. The skill first inspects README.md, Package.swift or .xcodeproj, Info.plist, code imports and Assets.xcassets, then presents its findings for you to confirm or correct.

Source text

SKILL.md · MIT
---
name: hig-project-context
version: 1.0.0
description: >-
  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.
---

# 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)*

© raintree-technology · MIT · raintree-technology/hig-doctor

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set14

hig-components-dialogs Provides Apple Human Interface Guidelines for alerts, sheets, popovers, and digit entry views. Helps pick the right modal UI pattern across iOS, iPadOS, macOS, and visionOS. CX Codex +1 647installs hig-components-menus Guides button and menu architecture across Apple platforms based on official Human Interface Guidelines. Helps choose proper controls and organize toolbars. CX Codex +1 643installs hig-components-content Provides Apple Human Interface Guidelines for content components like charts and collections. It helps choose standard controls across Apple platforms. CX Codex +1 641installs hig-components-status Provides Apple Human Interface Guidelines for progress indicators and status bars. Useful when building interfaces for iOS and watchOS. CX Codex +1 636installs hig-components-search Tells your agent how to design search, paging and breadcrumbs the Apple HIG way. Useful while you are still sketching navigation for an iOS or macOS app. CX Codex +1 634installs hig-inputs A skill that feeds your agent Apple HIG guidance on input: gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, focus. CX Codex +1 633installs hig-components-system Adds Apple HIG guidelines for widgets, Live Activities, complications, and alerts. Guides design choices for interfaces outside your main app. CX Codex +1 625installs hig-technologies A skill that feeds your agent Apple HIG rules for Siri, Apple Pay, HealthKit, ARKit, iCloud and other system technologies. CX Codex +1 620installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor