three-best-practices

Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL/WebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL.

Quality

70%

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 ./skills/three-best-practices/SKILL.md

Quality

Content

50%

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-organized, prioritized reference catalog with several solid code examples, but it is held back by redundant rule listings, a lack of in-body executable detail for the majority of rules, missing validation feedback loops for destructive operations, and references to rule files that are not actually bundled.

Suggestions

Provide the referenced rules/*.md bundle files (or remove the 'Read individual rule files' instruction) so progressive disclosure resolves to real content instead of missing paths.

De-duplicate rules that recur across categories (e.g. geometry-merge-static, geometry-instanced-mesh, geometry-lod) and consolidate the quick-reference against the priority table to tighten token efficiency.

Add explicit validate-then-fix feedback loops for destructive/batch operations such as WebGL context-loss recovery, version migration, and memory disposal to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The reference catalog is terse (one-line rule summaries) and avoids explaining basics Claude knows, but it carries redundancy — several rule IDs repeat across categories (e.g. geometry-merge-static, geometry-instanced-mesh, geometry-lod) and the quick-reference re-lists the priority table — so it could be tightened.	2 / 3
Actionability	A handful of executable code blocks (import maps, disposeObject(), TSL usage, mobile pixel-ratio) are copy-paste ready, but most of the 120+ rules are bare one-line directives with no in-body code, and the rule files they point to for details are not bundled.	2 / 3
Workflow Clarity	Rules are prioritized via the impact table and a loose 'How to Use' sequence exists, but destructive/batch concerns (context-loss recovery, version migration, memory disposal) lack any validate-then-fix feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	The overview signals deeper detail via 'Read individual rule files' and lists rules/*.md paths, and sections are well-organized, but the referenced rules/ directory does not exist and no references/scripts/assets bundles are present, so the disclosed references resolve to nothing and most content stays inline.	2 / 3
	Total	8 / 12 Passed

Description

90%

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 strong, well-targeted description that answers both what and when with explicit, natural trigger terms and a distinct niche. Its only mild weakness is specificity, since the listed actions ('writing, reviewing, optimizing') are variants of a single theme rather than multiple discrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the Three.js performance domain and a few actions ('writing, reviewing, or optimizing'), but the actions all collapse to the same optimization theme rather than listing multiple distinct concrete operations.	2 / 3
Completeness	Explicitly states what it does ('Three.js performance optimization and best practices guidelines') and when to use it ('Use when... Triggers on...'), with third-person voice and no missing trigger clause.	3 / 3
Trigger Term Quality	Enumerates a strong set of natural trigger terms a user would actually say ('3D scenes, WebGL/WebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL') plus 'Three.js code'.	3 / 3
Distinctiveness Conflict Risk	The Three.js/WebGL/TSL niche with its enumerated triggers is clearly distinct and unlikely to fire for unrelated, non-3D skills.	3 / 3
	Total	11 / 12 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: zebbern/claude-code-guide
Path: skills/three-best-practices/SKILL.md
Commit: af7d491

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