Skills hig-project-context
📦

hig-project-context

Content revision r2 Safe ⚙️ External commands🌐 Network access

Build Shared Apple Design Context

Repeated discovery questions slow Apple design reviews and create inconsistent guidance. This skill builds a shared context document from project evidence and confirmed requirements.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "hig-project-context" from https://skillstore.io/skills/sickn33-hig-project-context.md and its manifest at https://skillstore.io/api/skills/sickn33-hig-project-context/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "hig-project-context". Create context for our SwiftUI iPhone app and identify missing information.

Expected outcome:

  • Discovered: SwiftUI interface, iOS target, dark mode color assets, and accessibility labels.
  • Confirmation needed: minimum iOS version, primary persona, Dynamic Type status, and target accessibility level.
  • Next step: confirm these findings before the context document is generated.

Using "hig-project-context". Update the context because the app now supports iPadOS and multi-window workflows.

Expected outcome:

The Platforms and Technology sections are updated for iPadOS and multi-window support. All unrelated product, design, and accessibility details remain unchanged.

Using "hig-project-context". Check whether our project context still matches the repository.

Expected outcome:

  • Confirmed: SwiftUI, CloudKit, iOS, and iPadOS remain consistent with project evidence.
  • Conflict found: the context lists no dark mode support, but the asset catalog contains dark variants.
  • Confirmation requested before changing the Design System section.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All five external-command findings are false positives caused by inline backticks and a fenced Markdown template. The hardcoded URLs are attribution links, not instructions to perform network requests, and no semantic security issue was found.

1
Files scanned
137
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-hig-project-context/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-hig-project-context/security.svg)](https://skillstore.io/skills/sickn33-hig-project-context?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-hig-project-context?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-hig-project-context/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-hig-project-context.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). hig-project-context security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-hig-project-context/audits/5

BibTeX citation

@techreport{sickn33-sickn33-hig-project-context-2026, author = {sickn33}, title = {hig-project-context security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-hig-project-context/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "hig-project-context security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-hig-project-context/audits/5" identifiers: - type: other value: "skillstore:sickn33-hig-project-context:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
91
Spec Compliance

What You Can Build

Start a New Apple App

Capture platform, framework, design, accessibility, and user decisions before detailed interface work begins.

Document an Existing Codebase

Extract verified design context from project files so future HIG guidance reflects the current implementation.

Prepare a Design Review

Consolidate product constraints and accessibility goals before reviewing patterns, components, or platform conventions.

Try These Prompts

Create Basic Context
Create the Apple design context for this project. Review available files, show your findings, and ask me to confirm missing details.
Update Existing Context
Review the existing Apple design context and update only the sections affected by these changes: [describe changes].
Focus on Accessibility
Build or update the project context with emphasis on accessibility goals, current implementation evidence, user needs, and regulatory requirements.
Reconcile Context with Code
Compare the current Apple design context with project files. Identify conflicts, request confirmation, and revise only verified sections.

Best Practices

  • Confirm discovered facts before writing or changing the shared context document.
  • Record concrete platform versions, frameworks, accessibility goals, and user environments.
  • Update only changed sections and preserve verified information.

Avoid

  • Do not assume requirements that project files and the user have not confirmed.
  • Do not replace the entire context document when only one section changed.
  • Do not treat the context document as proof of HIG or accessibility compliance.

Frequently Asked Questions

What file does this skill create?
It creates or updates `.claude/apple-design-context.md` in the project.
Which Apple platforms can it document?
It covers iOS, iPadOS, macOS, tvOS, watchOS, and visionOS.
Does it inspect existing project files?
Yes. It can review documentation, project configuration, code imports, property lists, assets, and accessibility usage.
Will it overwrite existing context?
It should update only changed sections and preserve unchanged information.
Does it guarantee Apple HIG compliance?
No. It records context for tailored guidance but does not replace design review or testing.
Can it support accessibility planning?
Yes. It records accessibility targets, implementation evidence, user considerations, and applicable regulatory requirements.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

10 downloads · 93 views

File structure

📄 SKILL.md