moai-domain-frontend

Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.

Quality

63%

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 ./.claude/skills/moai-domain-frontend/SKILL.md

Quality

Content

42%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-sectioned catalog but is noticeably verbose with repeated framework listings and prose-only quickstarts instead of executable code, and it lacks reference files to offload deep-dive content. Its own Refactor Notes confirm the main weaknesses: duplication and missing decomposition.

Suggestions

Replace the prose Implementation Quickstart with actual executable code snippets (a React 19 server component, a Next.js server action, a Vue composable, a CVA button) so guidance is copy-paste ready.

De-duplicate the framework listings: keep one canonical reference (e.g., Technology Stack) and have Quick Reference and Patterns point to it rather than re-enumerating the same items.

Extract framework-specific deep-dives into one-level-deep reference files under references/ and link to them from the body, matching the restructuring already noted in the Refactor Notes.

Dimension	Reasoning	Score
Conciseness	The same frameworks are enumerated across Quick Reference, Patterns, and Technology Stack, and the Implementation Quickstart is prose that restates concepts Claude already knows; the Refactor Notes themselves flag the duplication and verbosity.	2 / 5
Actionability	The quickstart sections give detailed prose guidance (named imports, schema fields, composable structure) but contain no executable code blocks, leaving concrete-but-not-copy-paste-ready instruction.	3 / 5
Workflow Clarity	There is no sequenced multi-step workflow, but the Verification checklist supplies explicit checkpoints; content is organized by topic rather than as a guided process.	3 / 5
Progressive Disclosure	Section headers provide reasonable structure, but no bundle reference files exist and framework-specific deep-dives are inlined; the Refactor Notes acknowledge this content should be split into separate modules.	3 / 5
	Total	11 / 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.

The description cleanly answers both what the skill does and when to use it, with concrete trigger phrases and specific framework anchors. Its main weakness is that the listed actions are somewhat generic and the broad frontend scope invites overlap with related skills.

Dimension	Reasoning	Score
Specificity	Lists several distinct actions ("building web UIs, implementing components, optimizing frontend performance, or integrating state management") alongside named frameworks, though the actions are somewhat high-level rather than fully concrete.	4 / 5
Completeness	Explicitly states what it covers ("Frontend development specialist covering React 19, Next.js 16, Vue 3.5...") and provides a concrete "Use when..." trigger clause, satisfying both what and when.	5 / 5
Trigger Term Quality	Natural user phrases like "building web UIs", "components", "frontend performance", and "state management" appear with framework names, but synonym/variation coverage is incomplete.	4 / 5
Distinctiveness Conflict Risk	Named frameworks (React 19, Next.js 16, Vue 3.5) carve a niche, but the broad "frontend development" framing risks overlap with sibling UI/UX and component-library skills.	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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: modu-ai/moai-adk
Path: .claude/skills/moai-domain-frontend/SKILL.md
Commit: 2213871

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