frontend-developer

Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture.

Quality

50%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/frontend-developer/SKILL.md

The canonical home for this skill is frontend-developer in rmyndharis/antigravity-skills

Quality

Content

35%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 skill is a well-sectioned persona profile, but it is token-heavy with enumerated technologies Claude already knows and offers mostly abstract guidance instead of concrete, executable direction. The workflow has a sequence but lacks concrete validation checkpoints, and nothing is offloaded to reference files.

Suggestions

Trim the Capabilities and Knowledge Base catalogs to the non-obvious specifics, dropping library lists Claude already knows.

Replace abstract Instructions/Response Approach steps with concrete, executable guidance (e.g. representative code snippets, named profiling commands, or specific RSC/Server Action patterns).

Add an explicit validation step with a feedback loop (e.g. "Run Lighthouse/axe-core; if scores below threshold, fix and re-audit") to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is a long catalogue of technologies Claude already knows (Zustand, Jotai, Valtio, emotion, styled-components, Framer Motion, Nx, Turbo, Lerna, etc.) across ten padded sections; noticeably verbose with several low-marginal-value enumerations that could be tightened.	2 / 5
Actionability	Guidance is high-level ("Choose component structure and state or data approach", "Suggest performance-optimized solutions using React 19 features") with no executable code, commands, or concrete patterns; minimal concrete guidance beyond hints.	2 / 5
Workflow Clarity	The Instructions section lists a sequenced 4-step flow (clarify -> choose -> implement -> validate), but the validation checkpoint ("Validate performance and UX with profiling and audits") is vague and implicit with no error-recovery loop.	3 / 5
Progressive Disclosure	Single monolithic 170-line file with well-labeled sections but no bundle references; the large inline Capabilities/Knowledge Base catalog competes for context and could be split or trimmed rather than carried in the always-loaded SKILL.md.	3 / 5
	Total	10 / 20 Passed

Description

66%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 names a clear domain and several concrete actions with strong trigger terms, but omits any explicit "Use when..." guidance, which caps completeness. It is otherwise specific and largely distinguishable from sibling skills.

Suggestions

Append an explicit trigger clause, e.g. "Use when building React or Next.js UI, fixing frontend performance/accessibility issues, or designing client-side data flows."

Drop or tighten the "Masters React 19, Next.js 15..." claim to avoid over-claiming and free tokens for trigger phrases.

Add a couple of natural synonyms ("frontend", "web app", "UI components") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the React/Next.js domain and three concrete actions ("Build React components, implement responsive layouts, and handle client-side state management"); the trailing "Masters React 19, Next.js 15..." is a capability claim rather than an action, so coverage is not comprehensive enough for a 5.	4 / 5
Completeness	There is a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance; per the rubric a missing "when" caps completeness at 3.	3 / 5
Trigger Term Quality	Good coverage of natural terms users would say ("React components", "responsive layouts", "Next.js 15", "client-side state management"); a few common variants (e.g. "frontend", "UI", "web app") are absent, so it stops short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Mostly distinct React 19 / Next.js 15 niche with minimal conflict risk; "modern frontend architecture" is somewhat broad and could overlap with adjacent web-dev skills, keeping it just below a 5.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/frontend-developer/SKILL.md
Commit: 57c135b

Reviewed: 4 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.