CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-patterns

Apple Human Interface Guidelines interaction and UX patterns.

46

Quality

49%

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 ./skills/hig-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Scale 1-5

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

This is a well-structured design-guidance skill that effectively organizes Apple HIG interaction patterns into a scannable, navigable format. Its strengths are excellent progressive disclosure with a comprehensive reference index and a useful pattern selection guide. Its main weakness is limited actionability—it provides design direction rather than concrete implementation examples, and the output format section could benefit from a worked example showing what a complete response looks like.

Suggestions

Add a concrete worked example showing a complete response for one pattern (e.g., onboarding), demonstrating the output format with specific implementation steps and platform variations.

Include at least one code snippet or SwiftUI example for a common pattern like showing a progress indicator or requesting permissions to increase actionability.

DimensionReasoningScore

Conciseness

The content is mostly efficient and well-structured. The key principles are concise and actionable. The reference index table is appropriately formatted. Minor verbosity in the 'When to Use' section and the marketing footer, but overall respects Claude's intelligence without over-explaining concepts.

4 / 5

Actionability

The skill provides a clear pattern selection guide and output format structure, but lacks concrete code examples or copy-paste ready implementations. The guidance is specific enough to direct behavior (e.g., 'three screens max' for onboarding) but remains at the design-guidance level rather than providing executable steps. For a design-guidelines skill this is somewhat expected, but the output format section is more of a template than concrete examples.

3 / 5

Workflow Clarity

The skill has a clear workflow: check context file → consult key principles → use pattern selection guide → follow output format → ask clarifying questions. The output format provides a clear 4-step structure. The 'Questions to Ask' section serves as a validation checkpoint. Minor gap: no explicit decision tree for when to consult reference files vs. answer directly.

4 / 5

Progressive Disclosure

Excellent progressive disclosure structure. The SKILL.md provides a concise overview of key principles, a well-organized reference index table with 25+ topic-specific reference files, clear navigation via the pattern selection guide, and related skills for cross-referencing. All references are one level deep with clear topic descriptions. However, no bundle files were provided to verify the referenced paths actually exist.

5 / 5

Total

16

/

20

Passed

Description

27%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.

This description is extremely terse and vague—it names a domain (Apple HIG) but fails to specify any concrete actions the skill performs or when it should be selected. Without a 'Use when...' clause or enumerated capabilities, Claude would struggle to reliably choose this skill from a pool of alternatives.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Provides guidance on Apple HIG-compliant layouts, navigation patterns, typography, and component usage for iOS, macOS, watchOS, and visionOS apps.'

Include an explicit 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks about iOS/macOS UI design, Apple design guidelines, HIG compliance, or platform-specific UX patterns.'

Add synonyms and related terms users might naturally say, such as 'HIG,' 'iOS design,' 'macOS UI,' 'SwiftUI components,' 'Apple accessibility,' or 'app store design review.'

DimensionReasoningScore

Specificity

Names the domain (Apple Human Interface Guidelines, UX patterns) but provides no concrete actions. What does it actually do—generate designs, review layouts, answer questions about guidelines? Entirely unclear.

2 / 5

Completeness

There is no clear 'what does this do' beyond a vague topic reference, and there is no 'when should Claude use it' clause at all. Both dimensions are essentially missing.

1 / 5

Trigger Term Quality

Includes relevant keywords like 'Apple Human Interface Guidelines' and 'UX patterns,' but misses natural user phrases such as 'iOS design,' 'macOS UI,' 'HIG,' 'SwiftUI,' 'accessibility,' or 'app design guidelines.'

3 / 5

Distinctiveness Conflict Risk

The mention of 'Apple Human Interface Guidelines' provides some specificity, but 'interaction and UX patterns' is broad enough to overlap with general UX/UI design skills or other platform-specific design guideline skills.

3 / 5

Total

9

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.