CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-layout

Apple Human Interface Guidelines for layout and navigation components.

48

Quality

52%

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-components-layout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 advisory skill for Apple HIG layout and navigation guidance. Its strengths are the comprehensive reference index, the navigation pattern selection table, and the layout adaptation checklist. Its main weaknesses are the lack of executable code examples (SwiftUI/UIKit snippets would significantly improve actionability) and the absence of a clearly sequenced workflow with validation steps.

Suggestions

Add concrete SwiftUI code snippets for the most common navigation patterns (e.g., NavigationSplitView with sidebar, TabView with .sidebarAdaptable) to improve actionability.

Define an explicit numbered workflow sequence: e.g., 1) Check context file, 2) Ask clarifying questions, 3) Select navigation pattern, 4) Verify against checklist, 5) Output recommendation — to improve workflow clarity.

DimensionReasoningScore

Conciseness

The content is mostly efficient and well-structured. The key principles section has some statements that are somewhat obvious to Claude (e.g., 'Users should always know where they are'), and the trailing marketing line and 'When to Use' section add no value. But overall, the tables and checklists are dense and informative.

4 / 5

Actionability

The navigation pattern selection table provides concrete, specific guidance mapping app structures to recommended patterns with platform adaptations. The layout adaptation checklist and output format are actionable. However, there are no executable code examples (e.g., SwiftUI NavigationSplitView snippets), which would elevate this for a design/development skill.

4 / 5

Workflow Clarity

The skill describes a consultative workflow (ask questions, recommend pattern, specify hierarchy, describe adaptation) via the output format and questions sections, but there's no explicit sequencing of steps, no validation checkpoints, and no feedback loop for verifying recommendations against requirements. For a non-destructive advisory skill this is acceptable but still lacks clear step ordering.

3 / 5

Progressive Disclosure

The reference index table with 12 clearly labeled reference files is well-organized and provides one-level-deep navigation. The related skills section adds useful cross-references. However, since no bundle files were provided, we cannot verify the referenced paths exist, and the skill could benefit from slightly clearer signaling about when to consult each reference (some of this is implicit from the table's 'Key content' column).

4 / 5

Total

15

/

20

Passed

Description

36%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 too terse and lacks actionable detail. While it identifies the domain (Apple HIG) and a sub-area (layout and navigation), it fails to specify concrete actions and entirely omits trigger guidance for when Claude should select this skill. It would benefit significantly from listing specific capabilities and adding explicit 'Use when...' clauses.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Apple design guidelines', 'HIG', 'iOS layout', 'navigation bar', 'tab bar', 'sidebar navigation', or 'SwiftUI layout'.

List concrete actions such as 'Apply Apple HIG spacing and margin rules, implement navigation patterns (tab bars, sidebars, navigation stacks), validate layout hierarchy against Apple guidelines'.

Include common synonyms and abbreviations like 'HIG', 'iOS', 'macOS', 'iPadOS', 'visionOS' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Apple Human Interface Guidelines) and mentions 'layout and navigation components' but provides no concrete actions like 'apply spacing rules', 'implement tab bars', or 'validate navigation patterns'.

2 / 5

Completeness

Provides a vague 'what' (layout and navigation components from Apple HIG) but completely lacks a 'when' clause. There is no guidance on when Claude should select this skill, which caps this dimension at 3 per the rubric, and the 'what' is itself quite vague, bringing it to 2.

2 / 5

Trigger Term Quality

Includes relevant keywords like 'Apple Human Interface Guidelines', 'layout', and 'navigation components', but misses natural user phrases like 'HIG', 'iOS design', 'SwiftUI layout', 'tab bar', 'sidebar', or 'Apple design guidelines'.

3 / 5

Distinctiveness Conflict Risk

The mention of 'Apple Human Interface Guidelines' provides some specificity, but 'layout and navigation components' is broad enough to overlap with general UI/UX skills, iOS development skills, or other Apple design-related skills.

3 / 5

Total

10

/

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.