Hig Project Context logo

Hig Project Context

Organization
raintree-technology
hig-project-context

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.

Overview

Publisherraintree-technology
Repositoryhig-doctor
Skill namehig-project-context
Stars
148
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by raintree-technology on GitHub. Read the source before you install it.

Installation

Install the Hig Project Context AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-project-context
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/raintree-technology/hig-doctor.git /tmp/hig-doctor
mkdir -p .claude/skills
cp -r /tmp/hig-doctor/skills/hig-project-context .claude/skills/hig-project-context
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hig Project Context in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hig Project Context on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hig Project Context is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 · More developer tools

Frequently asked questions

What does the Hig Project Context AI skill do?

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.

Why use Hig Project Context on TypingMind?

Because you install it once and use it with any model. Hig Project Context is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hig Project Context in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/raintree-technology/hig-doctor/tree/main/skills/hig-project-context. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Hig Project Context?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hig Project Context?

As many as you like. As long as a model supports skills, you can use Hig Project Context with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hig Project Context AI skill free?

Yes. It is published on GitHub by raintree-technology under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇