CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-foundations

Apple Human Interface Guidelines design foundations.

48

Quality

51%

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/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

71%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-structured, token-efficient overview that practices progressive disclosure cleanly via a verified reference table and a clear output workflow. Its main weakness is actionability: it tells Claude what to produce but provides no executable code patterns or concrete worked examples.

Suggestions

Add one minimal inline code example (e.g., a SwiftUI snippet using semantic system colors and Dynamic Type) so the 'Provide concrete code patterns' directive has a concrete model to follow.

Remove or replace the vague trailing 'When to Use' line ('applicable to execute the workflow or actions described in the overview') with explicit trigger conditions.

Tie each 'Applying Foundations Together' item to the specific reference file and section it draws from, making the cross-cutting guidance directly navigable.

DimensionReasoningScore

Conciseness

The body is terse — eight concise principle bullets and a reference table with no padding about what HIG is — but the vague 'When to Use' line and the marketing footer are minor trim-able verbosity, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

It gives some concrete directives ('Check for .claude/apple-design-context.md', 'Cite the specific HIG foundation with file and section', 'Provide concrete code patterns (SwiftUI/UIKit/AppKit)') but supplies no actual code or executable specifics, matching 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

There is a clear sequence — check context, ask the listed questions, then follow the four-step Output Format — and the operation is advisory rather than destructive, so 'clear sequence with most checkpoints present; minor validation gaps' fits without triggering the destructive-operation cap.

4 / 5

Progressive Disclosure

The SKILL.md is a clean overview with a well-signaled, one-level-deep Reference Index table whose 18 links all resolve to real files in references/, matching 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

16

/

20

Passed

Description

31%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 bare topic label with no concrete actions and no trigger guidance, leaving Claude with little signal on what the skill actually does or when to invoke it. It identifies a niche but does not distinguish it from sibling HIG skills.

Suggestions

Add concrete actions (e.g., 'Apply, audit, and explains Apple HIG design foundations across iOS, iPadOS, macOS, watchOS, tvOS, and visionOS').

Append an explicit trigger clause such as 'Use when designing or reviewing Apple-platform UIs, or when the user mentions HIG, Apple design guidelines, or SwiftUI/UIKit/AppKit look-and-feel.'

Differentiate from sibling skills, e.g. 'Use this for cross-platform foundations; use hig-platforms for per-platform differences.'

DimensionReasoningScore

Specificity

The description 'Apple Human Interface Guidelines design foundations.' names only a topic with no verbs or concrete actions, matching the 'entirely vague; no concrete actions' anchor and falling below even 'Processes PDF files'.

1 / 5

Completeness

It offers a vague 'what' (a topic label) and no 'when' / 'Use when...' clause at all, matching the 'vague what and no when' anchor; the missing trigger guidance caps completeness below 3.

2 / 5

Trigger Term Quality

'Apple Human Interface Guidelines' and 'design foundations' are relevant natural terms a user might say, but common variations/synonyms (e.g., 'iOS design', 'Apple UI guidelines') are absent, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Apple HIG niche is specific and unlikely to trigger for unrelated work, but the four sibling HIG skills (hig-platforms, hig-patterns, hig-components-*) create real overlap risk the description does not disambiguate, fitting 'somewhat specific but could still overlap with similar skills'.

3 / 5

Total

9

/

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.