CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

make-interfaces-feel-better

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable reference body: every principle carries exact values, properties, or tokens, and the review output format and checklist make the deliverable unambiguous. Its main weakness is progressive disclosure — the four clearly-signaled reference files do not exist in the bundle, so the detail they promise is unavailable — with minor redundancy between the Quick Reference, Common Mistakes, and Reference Files sections.

Suggestions

Ship the four referenced files (typography.md, surfaces.md, animations.md, performance.md) in the bundle, or inline their essential patterns (e.g., the Motion/CSS cross-fade) — as delivered, every reference link in the body dangles and the delegated detail is unreachable.

Drop the 'Reference Files' section: it repeats the Quick Reference table's four links verbatim, and merge any Common Mistakes rows that merely restate a core principle (concentric radius, tabular-nums, transition: all) into the principle itself to cut redundancy.

Add a short ordered 'how to run a review' sequence (scope the diff → check each principle → emit Before/After tables → confirm with the checklist) so the review workflow is explicitly sequenced rather than implied by section order.

DimensionReasoningScore

Conciseness

Lean, principle-per-line format with no padding and no explanation of concepts Claude already knows; every principle carries actionable specifics. Anchor 4 rather than 5 because of minor redundancy that could be trimmed: the 'Reference Files' section duplicates the Quick Reference table's four links, and the 'Common Mistakes' table restates several core principles (concentric radius, tabular-nums, initial={false}, transition: all, will-change, hit areas).

4 / 5

Actionability

Fully concrete, copy-paste-ready guidance throughout: exact values ('about 0.96-0.97', '~100ms delay', '40x40px', '1px low-opacity outline'), exact properties and tokens ('text-wrap: balance', 'font-variant-numeric: tabular-nums', 'transition-property: scale, opacity', 'outline-[var(--border)]', 'active:scale-[0.96] transition-transform'), plus worked Before/After examples that cite specific files and properties. Specific examples cover the common cases, matching the anchor-5 pattern.

5 / 5

Workflow Clarity

The review workflow is coherent and well-supported: Quick Reference routes to topic areas, the Review Output Format section precisely specifies deliverable structure with a worked example, and the Review Checklist serves as an explicit coverage checkpoint. Anchor 4 rather than 5 because the process is never explicitly sequenced (no ordered steps for conducting a review) and there is no verify-after-apply feedback loop; not 3 because the checklist and output-format example provide real checkpoints.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep (Quick Reference table, inline 'see animations.md'/'see surfaces.md'), which is good design. However, all four referenced files (typography.md, surfaces.md, animations.md, performance.md) are absent from the bundle — the links dangle, navigation breaks, and delegated detail such as the 'Motion and CSS cross-fade patterns' is unreachable. Missing reference targets are more than a minor organization gap, so this sits between anchors 3 and 4.

3 / 5

Total

16

/

20

Passed

Description

91%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 strong description with explicit what/when structure, highly natural trigger phrases, and a well-delineated UI-polish niche. Its only weaknesses are describing scope and triggers rather than the concrete techniques it applies, and broad catch-all clauses ('any visual detail work') that create minor overlap risk with general frontend skills.

DimensionReasoningScore

Specificity

Names the domain and many concrete areas ('building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations') plus specific techniques ('stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines'). Falls at anchor 4: several specific items with minor gaps — it enumerates scope and triggers rather than comprehensively listing the concrete actions performed, keeping it below the anchor-5 example of multiple fully concrete actions.

4 / 5

Completeness

Explicitly answers both: what ('Design engineering principles for making interfaces feel polished') and when ('Use when building UI components, reviewing frontend code, implementing animations... Triggers on...'). This mirrors the anchor-5 example's structure of a clear capability statement followed by an explicit Use-when clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: users' own phrases ('make it feel better', 'feels off', 'UI polish', 'design details') alongside technical synonyms and variations ('border radius', 'font smoothing', 'tabular numbers', 'image outlines', 'box shadows', 'stagger animations'). Matches the anchor-5 pattern of full synonym coverage; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (UI polish/visual detail work) with distinctive triggers ('make it feel better', 'feels off', stagger animations), but the catch-all clauses 'building UI components' and 'any visual detail work' are broad and overlap with general frontend/component skills. Mostly distinct with minor overlap risk — anchor 4 rather than 5 because of those broad triggers.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 8 missing

Warning

Total

14

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/make-interfaces-feel-better/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.