CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-patterns

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

49

Quality

54%

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 ./.kiro/skills/frontend-patterns/SKILL.md

The canonical home for this skill is frontend-patterns in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

63%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-organized, code-heavy pattern catalog with executable examples and minimal prose padding. Its weaknesses are length (much of it restates knowledge Claude already has), a fully monolithic structure with no reference files, and placeholder gaps in a few code examples.

Suggestions

Move advanced or long-tail sections (Framer Motion animations, virtualization, accessibility patterns) into references/ files and keep a short overview with pointers in SKILL.md, reserving inline content for non-obvious knowledge like the sort-mutation and refetch-loop pitfalls.

Fill placeholder gaps ('{/* Dropdown implementation */}', '{/* Other fields */}', bare '// Success handling' comments) with complete executable code, and note required dependencies (framer-motion, @tanstack/react-virtual).

Add brief selection guidance per section — one line on when to prefer each pattern (e.g. render props vs. custom hook vs. context+reducer) — to replace the vague closing 'Choose patterns that fit your project complexity.'

DimensionReasoningScore

Conciseness

Prose is lean with no concept tutorials, but the ~650-line body catalogs patterns Claude already knows natively (useToggle, useDebounce, compound components, ErrorBoundary, controlled forms); only occasional comments (the sort-mutation note, the refetch ref-loop explanation) add non-obvious knowledge, so it could be substantially tightened rather than merely trimmed at the edges.

3 / 5

Actionability

Code is concrete, near-complete TypeScript with usage examples for every pattern, fitting 'mostly executable guidance with minor gaps'; not 5 because of placeholder gaps ('{/* Dropdown implementation */}', '{/* Other fields */}'), stub comment bodies like '// Success handling', and imports of dependencies (framer-motion, @tanstack/react-virtual) that are never installed/declared.

4 / 5

Workflow Clarity

This is a well-sectioned pattern catalog with a clear 'When to Activate' list, not a multi-step process, and it involves no destructive or batch operations, so no validation cap applies; it falls short of 5 only because the sole selection guidance is the vague 'Choose patterns that fit your project complexity' with no direction on when to prefer one pattern over another.

4 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/ directories) and everything is inlined in a single 658-line SKILL.md; section headers give it structure, but content that plausibly belongs in separate reference files (animations, accessibility, virtualization) is inline, matching 'some structure but content that should be separate is inline.'

3 / 5

Total

14

/

20

Passed

Description

45%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 domain label with a topic list rather than an action-and-trigger description. It lacks any 'Use when...' clause and concrete capability verbs, leaving both completeness and specificity at the middle of the scale.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building React/Next.js components, managing client state, or optimizing rendering performance.'

Replace topic labels with concrete actions, e.g. 'Implements component composition, custom hooks, context+reducer state, memoization, and form validation patterns.'

Add natural trigger variations users would say (hooks, components, forms, virtualization, lazy loading) to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('React, Next.js, state management, performance optimization') but offers only topic labels rather than concrete actions — no verbs describing what the skill actually does, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2-concrete-actions anchor above.

2 / 5

Completeness

The 'what' is clear (frontend development patterns for the listed areas) but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'React', 'Next.js', 'state management', and 'performance optimization' are natural user terms, but common variations users would say — 'hooks', 'components', 'forms', 'frontend' — are absent, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

Naming React and Next.js gives some specificity, but 'UI best practices' and 'performance optimization' are broad enough to overlap with other web/UI skills, fitting 'somewhat specific but could still overlap with similar skills' rather than the mostly-distinct anchor.

3 / 5

Total

11

/

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

skill_md_line_count

SKILL.md is long (659 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.