design-patterns

Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.

Quality

73%

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 ./examples/skills/design-patterns/SKILL.md

Quality

Content

57%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 well-structured and highly actionable for a complex multi-mode skill, with concrete detection heuristics and clear per-mode workflows. Its main weaknesses are verbosity from inlined templates and redundant pattern enumeration, missing validation feedback loops, and references to bundle files that are not provided.

Suggestions

Move the long Detection/Suggestion/Evaluation output-format templates and the 23-pattern catalog into the referenced reference/signatures files so SKILL.md stays a lean overview, and ensure those bundle files actually ship with the skill.

Add an explicit validation checkpoint to the detection workflow (e.g. re-Read low-confidence candidates and re-score before reporting) to create a verify-and-retry feedback loop for batch scans.

Trim redundant content Claude already knows — the full GoF pattern enumeration and the Version/Integration-with-Other-Skills sections — to recover token budget.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with real skill-specific value (detection rules, confidence bands, CLI commands), but padded by enumerating all 23 GoF patterns Claude already knows, long inline JSON/Markdown output templates, and non-essential Version/Integration sections.	3 / 5
Actionability	Concrete Glob patterns, Grep signatures, regex heuristics, confidence bands, and copy-paste CLI commands give mostly executable guidance, with minor gaps where suggestion examples use placeholder comments like /* credit logic */.	4 / 5
Workflow Clarity	The five phases and per-mode numbered steps are clearly sequenced, but validation/verification checkpoints are implicit only — confidence scoring acts as a partial gate yet there is no explicit validate-and-retry loop for batch detection.	3 / 5
Progressive Disclosure	A dedicated Reference Files section clearly signals one-level-deep references, but none of the referenced signature/checklist/reference files actually exist in a bundle, and long output-template and pattern-catalog content that should live in those files is inlined.	3 / 5
	Total	13 / 20 Passed

Description

88%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 is strong: it cleanly states three concrete capabilities and pairs them with an explicit 'Use when' clause listing natural trigger phrases and named stacks. Its only gaps are minor trigger-term synonyms/extensions and slight overlap with general refactoring skills.

Dimension	Reasoning	Score
Specificity	"Detect, suggest, and evaluate GoF design patterns" lists three concrete, distinct actions that comprehensively cover the skill's surface, matching the multiple-specific-actions anchor.	5 / 5
Completeness	It explicitly states what ("Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases") and when ("Use when refactoring code, applying ... patterns, reviewing pattern quality, or finding stack-native alternatives ...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like "refactoring code", "applying singleton/factory/observer/strategy patterns", and "reviewing pattern quality" plus named stacks give good coverage, but file extensions and common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The GoF-patterns-plus-named-stacks niche is mostly distinct, but there is minor overlap risk with closely related refactoring/code-review/architecture skills that the body itself references.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (567 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: FlorianBruniaux/claude-code-ultimate-guide
Path: examples/skills/design-patterns/SKILL.md
Commit: 752edfe

Reviewed: about 9 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.