frontend-conventions

Coding conventions, architecture patterns, and testing rules for the SkillHub React frontend. Ensures agents follow Feature-Sliced Design and use the generated OpenAPI types.

Quality

68%

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 ./.agents/skills/frontend-conventions/SKILL.md

Quality

Content

75%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 content is a well-structured, actionable conventions reference with concrete commands and paths and a verification checkpoint in its main workflow. Minor gaps (no worked component example, no retry loop, and a dangling script reference) keep each dimension at 4 rather than 5.

Dimension	Reasoning	Score
Conciseness	The body is a lean, reference-style set of rules, tables, and commands that assumes Claude's competence; only minor trims (the HMR aside and the long dependency list) keep it below a 5.	4 / 5
Actionability	Concrete copy-paste `make` commands, specific file paths, and named libraries give mostly executable guidance, but the absence of a worked React/FSD component example leaves a minor gap versus fully covering the common cases.	4 / 5
Workflow Clarity	The API type-generation workflow has a clear sequence with an explicit verify step ('./scripts/check-openapi-generated.sh'), but it lacks an explicit fix-and-retry feedback loop, so it stops short of 5.	4 / 5
Progressive Disclosure	Sections and tables are well-organized in a single coherent conventions file with no bundle to navigate; it falls below 5 because the referenced './scripts/check-openapi-generated.sh' is not present as a bundle file and the dependencies list is slightly long.	4 / 5
	Total	16 / 20 Passed

Description

61%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 clearly communicates what the skill covers and is well-scoped to a distinct niche, but it omits explicit 'when to use' trigger guidance and relies on topic categories rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when adding or modifying SkillHub React/TypeScript frontend code') so the trigger is unambiguous and completeness can exceed 3.

Replace the abstract category list with concrete actions where possible (e.g., 'Place code by Feature-Sliced Design layer, generate OpenAPI types, run typecheck and lint') to lift specificity.

Include a couple of natural synonyms users might say ('frontend code', 'web UI', 'React components') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('SkillHub React frontend') and concrete items ('Feature-Sliced Design', 'generated OpenAPI types'), but the remaining coverage ('coding conventions, architecture patterns, and testing rules') reads as topic categories rather than concrete actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	The 'what' is clear (conventions, architecture, testing rules, FSD, OpenAPI types), but there is no 'Use when...' clause or equivalent trigger guidance, which the guidelines explicitly cap at 3.	3 / 5
Trigger Term Quality	Natural domain keywords a user would say are present ('React frontend', 'Feature-Sliced Design', 'OpenAPI types', 'coding conventions'), giving good keyword coverage; it falls short of 5 only because synonyms and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	Scoping to 'SkillHub React frontend' with FSD and OpenAPI types gives a clear niche with only minor overlap against generic React convention skills, though the absence of explicit distinct trigger phrases keeps it below 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: iflytek/skillhub
Path: .agents/skills/frontend-conventions/SKILL.md
Commit: b896c69

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