CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-patterns

React、Next.js、状态管理(State Management)、性能优化(Performance Optimization)及 UI 最佳实践的前端开发模式。

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/frontend-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable catalog of complete, executable frontend code examples, well-organized by pattern, but it is a verbose monolithic document that reprises widely-known React patterns without splitting into reference files or providing any multi-step workflow with validation checkpoints.

Suggestions

Trim or move standard, widely-known patterns (useToggle, useDebounce, basic useMemo/useCallback) to a separate reference file to improve conciseness and reduce tokens on common knowledge.

Split the large body into bundled reference files (e.g., references/hooks.md, references/performance.md, references/a11y.md) with clearly signaled links from SKILL.md to raise progressive disclosure.

For patterns involving risky or multi-step operations (e.g., form submission, error boundaries), add explicit validation/recovery checkpoints so workflow clarity can reach 3.

DimensionReasoningScore

Conciseness

The body is predominantly code with minimal fluff prose, but at ~640 lines it extensively reprises standard React patterns (useToggle, useDebounce, useMemo/useCallback, basic ErrorBoundary) that Claude already knows, so it is mostly efficient but could be tightened rather than fully lean.

2 / 3

Actionability

Every section provides complete, executable, copy-paste-ready TypeScript examples (Card composition, Tabs compound components, useQuery, useVirtualizer, CreateMarketForm, ErrorBoundary, Framer Motion, keyboard nav), matching the 'fully executable code; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Content is organized into clear topical sections and a '何时激活' trigger list, but it is a flat pattern catalog with no multi-step workflow sequencing and no validation/checkpoint steps, so it sits above 'steps unclear' yet below 'explicit validation steps'.

2 / 3

Progressive Disclosure

The skill is well-organized into sections but is a monolithic ~640-line file with no bundle files (references/, scripts/, assets/ absent) and no external references, so content that could be split (e.g., hooks reference, performance guide) is inline; the under-50-line exemption does not apply, preventing a score of 3.

2 / 3

Total

9

/

12

Passed

Description

72%

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 specific, well-scoped frontend description with strong natural trigger terms and a clear niche, but it lacks concrete action verbs and any explicit 'Use when' guidance, capping specificity and completeness.

Suggestions

Add concrete action verbs (e.g., 'Build React components, manage state, optimize rendering performance') to lift specificity toward 3.

Append an explicit trigger clause such as 'Use when building or refactoring React/Next.js UIs, managing state, or optimizing frontend performance' to raise completeness to 3.

DimensionReasoningScore

Specificity

The description names a clear, comprehensive domain — "React、Next.js、状态管理、性能优化及 UI 最佳实践" — but is a noun phrase ("前端开发模式") with no concrete action verbs, so it falls below the 'lists multiple specific concrete actions' anchor without being vague enough to score 1.

2 / 3

Completeness

It states 'what' (frontend development patterns) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2; it is not a 1 because the 'what' is explicit and domain-specific.

2 / 3

Trigger Term Quality

It includes natural terms a user would actually say — React, Next.js, 状态管理 (state management), 性能优化 (performance optimization), UI 最佳实践, 前端 (frontend) — giving good coverage of likely trigger phrases.

3 / 3

Distinctiveness Conflict Risk

The React/Next.js framing carves out a clear frontend niche unlikely to conflict with non-frontend skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
xu-xiang/everything-claude-code-zh
Reviewed

Table of Contents

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.