Skill

Generate Apple Design Context Document

Builds a reusable Apple project design-context file so other HIG skills skip redundant discovery questions.

Works with github

73
Spark score
out of 100
Updated last month
Version 13.1.0
Models
claude

Add to Favorites

Why it matters

Automate the creation and maintenance of `.claude/apple-design-context.md` files. This skill gathers essential project context from various sources to streamline development and ensure consistency across Apple HIG skills.

Outcomes

What it gets done

01

Automatically discover project context from README, package manifests, Info.plist, code, and assets.

02

Present gathered context for user confirmation and gather missing information.

03

Generate a structured `.claude/apple-design-context.md` document.

04

Update existing context documents efficiently by identifying and incorporating changes.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-hig-project-context | bash

Overview

Apple HIG: Project Context

A skill that auto-discovers an Apple project's platform targets, technology stack, design system, and accessibility requirements from README, Xcode project files, and code, then generates a reusable .claude/apple-design-context.md file for other HIG skills. Use before other Apple HIG skills need project context, so discovery questions aren't repeated; not needed for non-Apple projects or when the context file is already current.

What it does

Creates and maintains a .claude/apple-design-context.md file so other Apple HIG skills can skip redundant questions about a project. It first checks whether this context file already exists and reuses it, then auto-discovers 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 imports revealing frameworks like SwiftUI vs. UIKit or HealthKit, Assets.xcassets (color assets, icon sets, dark mode variants), and an accessibility audit grepping for accessibility modifiers.

When to use - and when NOT to

Use this before other Apple HIG skills need project context - product overview, target platforms, technology stack, design system, accessibility requirements, user context, or existing design assets - so they don't have to ask the same questions repeatedly.

Not needed for non-Apple-platform projects, or once a current .claude/apple-design-context.md already exists and nothing has changed.

Inputs and outputs

After auto-discovery, presents findings for the user to confirm or correct, then asks only for what's still missing across seven areas: product overview (one-sentence description, category, stage), target platforms (iOS/iPadOS/macOS/tvOS/watchOS/visionOS, minimum OS versions, universal vs. platform-specific), technology stack (SwiftUI/UIKit/AppKit, single/multi-window or document-based architecture, Apple technologies in use), design system (system defaults vs. custom, brand colors/fonts/icon style, Dark Mode and Dynamic Type support), accessibility requirements (baseline/enhanced/comprehensive target level, VoiceOver/Switch Control considerations, WCAG/Section 508 regulatory requirements), user context (1-3 primary personas, key use cases and environments, known pain points), and existing design assets (Figma/Sketch files, Apple Design Resources, component library).

### Apple Design Context

### Product
- **Name**: [App name]
- **Description**: [One sentence]
- **Category**: [Category]
- **Stage**: [Concept / Development / Shipped / Redesign]

Generates the full context document from this gathered information; when updating an existing document, it reads the current file, asks only what changed, updates just those sections, and preserves everything else unchanged.

Integrations

Feeds directly into the rest of the Apple HIG skill family: 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), and hig-technologies (Apple technology relevance) - all of which can read the generated context file instead of re-asking the same discovery questions.

Who it's for

Teams working across the Apple HIG skill family on iOS, iPadOS, macOS, tvOS, watchOS, or visionOS apps who want project context captured once, kept accurate as the project evolves, and reused consistently across every HIG-related skill invocation instead of re-answering the same discovery questions each time.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.