CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "fault tolerance", "mental model", "mapping", or "seven stages of action". Also trigger when diagnosing why users make mistakes, reducing product complexity, or improving error messages and feedback systems. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.

Quality

76%

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/design-everyday-things/SKILL.md
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 skill is well-structured for navigation — a clear overview with perfectly signaled one-level-deep references to 10 real, substantive bundle files — and offers genuinely actionable tables, checklists, and thresholds. Its main weaknesses are token efficiency (it re-teaches Norman's well-known framework and includes an author biography and affiliate book links Claude doesn't need) and the absence of a single unified review workflow with a validation loop tying the diagnostic, scoring, and fix-recommendation pieces together.

Suggestions

Cut the 'About the Author' section and the affiliate-linked 'Further Reading' section, and compress textbook explanations (thermostat example, HCD process, slips/mistakes definitions) to one-line pointers into the existing reference files — Claude already knows Norman's framework, so SKILL.md should keep only the decision-relevant tables, rules, and thresholds.

Add one unified ordered workflow near the top (e.g., 1. Run the Quick Diagnostic, 2. Score 0-10 per the Scoring section, 3. Map each failed diagnostic to the relevant principle's fixes, 4. Re-check that every fix is testable against the 10-second discoverability test) so the scattered procedures become a single sequence with an explicit verification step.

Include a short worked example of the scoring workflow applied to one interface (e.g., a form with a submit button) showing score, reasoning per principle, and improvements to reach 10/10, which would close the actionability gap in the skill's core use case.

DimensionReasoningScore

Conciseness

The body is noticeably verbose for material Claude already knows: it re-explains textbook DOET content ("Norman's key insight: There is no such thing as 'human error.'", the thermostat example, the HCD process, "5 users reveal 85% of problems"), includes an "About the Author" biography of Don Norman, and affiliate-linked book recommendations — several padded sections that earn no tokens. It avoids a 1 because much of the length is genuinely useful tabulated reference (digital signifier/mapping/constraint tables, response-time thresholds) rather than rambling prose.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete: a scoring protocol ("rate 0-10... Always provide current score and improvements to reach 10/10"), a falsifiable test ("figure out what to do within 10 seconds"), specific thresholds ("0.1s: Feels instantaneous... 10s: show progress bar"), an error-message checklist, and a Quick Diagnostic table mapping questions to fixes. Not a 5 because the central review workflow is never demonstrated — there is no worked example scoring a real interface, and directives like "Walk through each stage... Where does the user get stuck?" leave the procedure to be assembled by the reader.

4 / 5

Workflow Clarity

Usable procedure fragments exist (Quick Diagnostic audit table, seven-stage walkthrough, scoring protocol), but they are scattered across the document with no unified ordered workflow — nothing tells Claude to first run the diagnostic, then score, then map gaps to principles, then propose fixes. There is also no validation/feedback loop (e.g., re-scoring after proposed improvements). This fits 'steps listed but checkpoints missing or implicit' rather than a 4, since the sequence itself must be inferred.

3 / 5

Progressive Disclosure

Structure is exemplary: each principle section ends with a clearly signaled one-level-deep pointer ("See: references/affordances.md for affordance design patterns"), and a consolidated Reference Files section lists all 10 bundle files with descriptions. All 10 referenced files exist and contain real content with no nested references, so navigation is easy and content is appropriately split between overview and bundle.

5 / 5

Total

14

/

20

Passed

Description

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

A well-crafted description: it states concrete capabilities, provides an explicit and natural 'Use when' trigger list with scenario-based triggers, and even cross-references adjacent skills to reduce conflict risk. Its only weaknesses are minor — a few missing natural synonyms (book title, author name, 'intuitive') and the omission of the design-review/scoring capability that dominates the skill body.

DimensionReasoningScore

Specificity

Quotes list several concrete actions — "Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models", "diagnosing why users make mistakes", "reducing product complexity", "improving error messages and feedback systems" — matching the 'several specific actions; minor gaps' anchor. It falls short of a 5 because the body's core operational use (reviewing/scoring designs against these principles) is not named as a capability.

4 / 5

Completeness

It explicitly answers both questions: what ("Apply foundational design principles... Covers the gulfs of execution and evaluation") and when ("Use when the user mentions..." followed by concrete quoted trigger phrases, plus "Also trigger when diagnosing..."). This directly matches the top anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'; the 'when' is not merely present but maximally explicit.

5 / 5

Trigger Term Quality

Trigger coverage is strong and natural — "why is this confusing", "affordance", "error prevention", "discoverability", "mental model", "mapping", "seven stages of action" — plus scenario triggers like "diagnosing why users make mistakes". Not a 5 because common natural variations are missing: the book title/author ("Design of Everyday Things", "Norman"), "intuitive", and "user error".

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Norman's foundational design principles) and it proactively disambiguates against the closest neighbors ("For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design"), keeping it mostly distinct. Minor overlap risk remains from broad trigger terms like "mental model" and "mapping", which appear in many non-DOET contexts (information architecture, data mapping), so it fits 'mostly distinct; minor overlap risk' rather than 'minimal conflict risk'.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/design-everyday-things/SKILL.md

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.