frontend-developer

Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/frontend-developer/SKILL.md

Quality

Content

31%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 reads as a persona/knowledge catalogue rather than operational guidance: it lists technologies Claude already knows, provides no executable code or commands, and inlines everything with no progressive disclosure. The only real workflow is a thin 4-step instruction list with vague validation.

Suggestions

Replace the Capabilities, Knowledge Base, and Behavioral Traits inventories with a short overview plus references to separate files (e.g. references/react-patterns.md, references/nextjs-app-router.md) so SKILL.md becomes a lean entry point.

Add concrete, copy-paste-ready examples for the most common tasks (e.g. a Server Component with Suspense, a Server Action with useOptimistic) instead of listing technology names.

Tighten the Instructions workflow with explicit validation checkpoints (e.g. 'Run the Lighthouse audit; if LCP > 2.5s, optimize images/font loading before proceeding') to add a real fix-and-retry feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is ~160 lines of bulleted inventories enumerating technologies Claude already knows ('React 19 features including Actions, Server Components...', 'Zustand, Jotai, and Valtio', 'Framer Motion, React Spring'), which is noticeably verbose padding rather than net-new guidance.	2 / 5
Actionability	Guidance stays high-level ('Clarify requirements, target devices, and performance goals', 'Choose component structure and state or data approach') with no executable code, commands, or concrete patterns — only hints missing the specific steps to execute.	2 / 5
Workflow Clarity	A 4-step sequence exists (Clarify → Choose → Implement → 'Validate performance and UX with profiling and audits') but the validation step is vague with no concrete checkpoint or fix-and-retry feedback loop, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	No bundle files exist and the entire capability/knowledge inventory is inlined in SKILL.md with no references to separate files; the bulk capability and Knowledge Base sections are exactly the content that belongs in referenced files, so structure alone does not rescue it.	2 / 5
	Total	9 / 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 strong, third-person description that clearly states capabilities and an explicit usage trigger with concrete phrases. Minor weaknesses are the credential-style 'Masters...' clause and somewhat broad frontend triggers that invite overlap with sibling skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Build React components, implement responsive layouts, and handle client-side state management', 'Optimizes performance and ensures accessibility'), but the 'Masters React 19, Next.js 15...' clause is a credential claim rather than an action, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	It explicitly answers both what ('Build React components, implement responsive layouts, and handle client-side state management') and when ('Use PROACTIVELY when creating UI components or fixing frontend issues') with concrete trigger phrases, matching the anchor that requires both clearly and explicitly.	5 / 5
Trigger Term Quality	Natural user-facing terms appear ('creating UI components', 'fixing frontend issues', 'React', 'Next.js'), giving good keyword coverage, though it lacks common synonyms and the 'PROACTIVELY' framing is more a usage directive than a pure trigger term.	4 / 5
Distinctiveness Conflict Risk	The React 19 / Next.js 15 niche is mostly distinct, but the trigger 'creating UI components or fixing frontend issues' is broad enough to overlap with general web/frontend skills, so minor conflict risk remains.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/frontend-developer/SKILL.md
Commit: 3eff4af

Reviewed: 24 days 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.