cc-skill-frontend-patterns

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cc-skill-frontend-patterns/SKILL.md

Quality

Content

80%

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

The content is a well-organized, highly actionable catalog of executable React/Next.js TypeScript patterns that respects token budget by avoiding concept re-explanation. Its main weaknesses are the absence of any multi-step workflow with validation checkpoints and the monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Move large reference sections (e.g. Performance, Accessibility, Animation) into separate files under references/ and link to them from a concise overview to improve progressive disclosure.

For patterns involving risky or batch operations (e.g. virtualization, code splitting), add brief validation/verification checkpoints so workflow clarity can reach 3.

Remove the generic boilerplate 'When to Use' / 'Remember' lines that restate the overview without adding guidance.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable TypeScript with `// ✅` and `// Usage` markers and no explanatory padding of concepts Claude already knows (no 'what is React' prose), fitting 'lean and efficient; assumes Claude's competence; every token earns its place'; the only mild filler is the generic closing 'When to Use' and 'Remember' lines.	3 / 3
Actionability	Each section provides complete, copy-paste-ready TypeScript implementations with usage examples (e.g. useToggle, useQuery, ErrorBoundary, VirtualMarketList), matching 'fully executable code/commands; specific examples; copy-paste ready'.	3 / 3
Workflow Clarity	This is a patterns catalog organized by topic headers rather than a sequenced multi-step workflow; there are no explicit validation checkpoints or feedback loops, so it fits 'sequence present but checkpoints missing or implicit' (clear section structure, no workflow validation) rather than the checkpoint-driven level 3.	2 / 3
Progressive Disclosure	All ~630 lines of patterns live inline in a single SKILL.md with no bundle files and no references to separate files; section headers give structure, but content that could be split (e.g. per-category reference files) is inline, matching 'some structure but content that should be separate is inline'; at this length it does not qualify for the under-50-lines exception.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 clearly identifies a frontend/React/Next.js domain and lists relevant topic areas, but it describes topics rather than concrete actions and omits any 'Use when...' trigger guidance. It is adequately specific but lacks the explicit when-to-use triggers needed for higher completeness and distinctiveness.

Suggestions

Replace topic-area listing with concrete actions, e.g. 'Build React component patterns, custom hooks, and state-management solutions for Next.js apps.'

Add an explicit 'Use when...' clause, e.g. 'Use when implementing React/Next.js UIs, custom hooks, or performance optimizations.'

Add natural trigger variations users would say (e.g. 'React components', 'custom hooks', 'Next.js performance') to improve trigger-term coverage and reduce overlap with generic coding skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices' names a domain and several sub-areas, but lists topics rather than concrete actions (no verbs like 'extract', 'generate', 'build'), matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what the skill covers but provides no 'Use when...' or equivalent trigger guidance for when Claude should invoke it, which per the judging guidelines caps completeness at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	'React' and 'Next.js' are natural terms a user would say, but the leading 'Frontend development patterns' is generic and common variations/triggers are missing, fitting 'some relevant keywords but missing common variations' rather than the broad coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The React/Next.js/frontend niche is fairly specific, but without explicit triggers it could overlap with general web-development or coding skills, matching 'somewhat specific but could still overlap' rather than the distinct, trigger-anchored level 3.	2 / 3
	Total	8 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/cc-skill-frontend-patterns/SKILL.md
Commit: a3068b7

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

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.