CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-foundations

Apple Human Interface Guidelines design foundations.

44

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/hig-foundations/SKILL.md

The canonical home for this skill is hig-foundations in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized foundations overview with excellent progressive disclosure via a verified reference index, but it is more descriptive than instructional: it lacks concrete code patterns and explicit workflow validation checkpoints, and carries minor boilerplate padding.

Suggestions

Add a short "Quick start" or worked example showing one concrete decision (e.g., a SwiftUI snippet choosing a semantic color and Dynamic Type text style) so the guidance is copy-paste actionable rather than purely descriptive.

Tighten conciseness by removing the generic "When to Use" line and the promotional footer, which add tokens without guidance value.

Make the workflow explicit with checkpoints: e.g., 1) read .claude/apple-design-context.md, 2) confirm target platforms + accessibility level, 3) apply foundations with citations, 4) verify contrast/Dynamic Type/RTL against the relevant reference before finalizing.

DimensionReasoningScore

Conciseness

The principles and reference index are mostly efficient and assume competence, but the boilerplate "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview.") and the Raintree footer add padding that could be trimmed, matching the mostly-efficient-with-some-unnecessary-content anchor; not a 4 because that filler is avoidable.

3 / 5

Actionability

It names concrete specifics (semantic colors label/secondaryLabel/systemBackground, SF Pro/SF Symbols, VoiceOver, Dynamic Type) and gives an output format plus reference pointers, but the principles describe rather than instruct and no executable code patterns are shown, matching the some-concrete-guidance-but-incomplete anchor; not a 4 because key execution detail is missing.

3 / 5

Workflow Clarity

A loose process is implied (check .claude/apple-design-context.md → ask the four questions → apply foundations → output with citations), but there are no explicit validation checkpoints or feedback loops, matching the steps-present-but-checkpoints-implicit anchor; the skill is non-destructive so the destructive-cap does not apply.

3 / 5

Progressive Disclosure

A clear Reference Index table signals one-level-deep links to 18 reference files, all of which exist in references/, keeping the overview lean while routing detail to dedicated files, matching the clear-overview-with-well-signaled-one-level-deep-references anchor.

5 / 5

Total

14

/

20

Passed

Description

36%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a terse topic label rather than a capability statement: it names the Apple HIG domain well but states no actions, omits any "Use when…" trigger guidance, and overlaps with sibling HIG skills. It is recognizable but under-specified for triggering.

Suggestions

Rewrite the description in third person with concrete verbs, e.g. "Applies Apple Human Interface Guidelines foundations (color, typography, layout, motion, accessibility) to UI design decisions for iOS, iPadOS, macOS, watchOS, tvOS, and visionOS."

Add an explicit "Use when…" trigger clause naming natural terms users say, including the "HIG" abbreviation and platform names (e.g., "Use when designing or reviewing Apple platform UIs, or when the user mentions HIG, SF Symbols, Dynamic Type, or system colors").

Differentiate from sibling skills by scoping to foundational decisions (versus hig-platforms per-platform specifics or hig-components structural patterns).

DimensionReasoningScore

Specificity

"Apple Human Interface Guidelines design foundations." names a specific domain but contains no action verbs describing what the skill does, matching the anchor that names a domain with minimal/generic actions; it is not a 1 because the domain is concrete rather than pure abstraction.

2 / 5

Completeness

The description gives only a vague "what" (a topic label, no concrete actions) and entirely lacks a "when"/"Use when…" clause, fitting the anchor for a vague what with no when; not a 3 because the what is not concrete actions.

2 / 5

Trigger Term Quality

"Human Interface Guidelines" and "design foundations" are phrases a user might say, but common synonyms like "HIG", "iOS/macOS UI design", or "Apple design" are missing, matching the anchor for some relevant keywords lacking common variations.

3 / 5

Distinctiveness Conflict Risk

The Apple HIG niche is specific, but the skill explicitly has closely related siblings (hig-platforms, hig-patterns, hig-components-*) creating real overlap risk, matching the anchor for somewhat specific but overlapping with similar skills.

3 / 5

Total

10

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.