CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-frontend-patterns

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

38

Quality

37%

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/cc-skill-frontend-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Scale 1-3

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

This skill is essentially a comprehensive React patterns reference guide that teaches Claude things it already knows well. While the code examples are high-quality and executable, the massive volume of standard React knowledge (composition, hooks, context, memoization, error boundaries, animations, accessibility) provides minimal value since Claude is already deeply familiar with these patterns. The content would benefit enormously from being reduced to project-specific conventions and decisions rather than general React education.

Suggestions

Reduce content by 80%+ by removing standard React patterns Claude already knows (composition, hooks, memoization, error boundaries, etc.) and focus only on project-specific conventions, preferred libraries, or non-obvious decisions.

Split remaining content into separate reference files (e.g., HOOKS.md, PERFORMANCE.md, ACCESSIBILITY.md) with SKILL.md serving as a brief overview with navigation links.

Add project-specific decision criteria: when to use which state management approach, which animation library is preferred, specific component naming conventions, or file structure requirements.

Include workflow guidance for common tasks like 'adding a new feature component' with validation steps (linting, testing, accessibility checks) rather than just pattern catalogs.

DimensionReasoningScore

Conciseness

This is extremely verbose at ~500+ lines, covering many well-known React patterns (composition, compound components, render props, hooks, context+reducer, memoization, error boundaries, framer motion, accessibility) that Claude already knows thoroughly. Almost every pattern shown is standard React knowledge that doesn't need to be taught. The skill reads like a React tutorial rather than project-specific guidance.

1 / 3

Actionability

The code examples are fully executable TypeScript/React components with complete implementations, proper typing, and usage examples. Every pattern includes copy-paste ready code with clear interfaces and real-world usage demonstrations.

3 / 3

Workflow Clarity

The content is organized into clear sections by pattern type, but there's no workflow sequencing—it's a reference catalog of patterns rather than a guided process. There are no validation steps, decision criteria for when to use which pattern, or guidance on how patterns compose together in a real project.

2 / 3

Progressive Disclosure

All content is inlined in a single monolithic file with no references to external files. At this length (~500+ lines), the content should be split into separate files (e.g., HOOKS.md, PERFORMANCE.md, ACCESSIBILITY.md) with the SKILL.md serving as a concise overview with navigation links.

1 / 3

Total

7

/

12

Passed

Description

32%Scale 1-3

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 identifies the technology domain (React/Next.js frontend) but reads more like a topic list than an actionable skill description. It lacks concrete actions (verbs), has no 'Use when...' clause, and uses category-level terms rather than specific capabilities. The description would benefit significantly from specifying concrete actions and explicit trigger conditions.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about React components, Next.js routing, state management with Redux/Zustand, or frontend performance optimization.'

Replace abstract categories with concrete actions, e.g., 'Creates React components, implements Next.js routing and SSR, configures state management with Redux or Zustand, optimizes bundle size and rendering performance.'

Expand trigger terms to include common user phrases like 'component', 'hooks', 'SSR', 'server-side rendering', 'bundle size', 'lazy loading', 'CSS', 'responsive design', '.tsx', '.jsx'.

DimensionReasoningScore

Specificity

Names the domain (frontend development) and lists some areas (React, Next.js, state management, performance optimization, UI best practices), but these are categories rather than concrete actions. No specific verbs like 'create components', 'optimize bundle size', or 'implement routing'.

2 / 3

Completeness

Describes 'what' at a high level (frontend development patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.

1 / 3

Trigger Term Quality

Includes some relevant keywords users might say like 'React', 'Next.js', 'state management', and 'performance optimization', but misses common variations like 'component', 'hooks', 'CSS', 'styling', 'TypeScript', 'SSR', 'server-side rendering', or 'responsive design'.

2 / 3

Distinctiveness Conflict Risk

Mentioning React and Next.js specifically provides some distinctiveness, but 'frontend development patterns' and 'UI best practices' are broad enough to overlap with general web development, CSS/styling, or JavaScript skills.

2 / 3

Total

7

/

12

Passed

Validation

81%

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

Validation — 9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

11

Passed

Repository
popey/claude-code-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.