typescript-rules

React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

Quality

65%

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/typescript-rules/SKILL.md

Quality

Content

61%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.

A well-organized, mostly lean ruleset with concrete thresholds in places, but much of the guidance defers to repository conventions and there is no sequenced workflow with validation checkpoints.

Suggestions

For rules that currently say "follow the repository's X", add one concrete default or example so the guidance is executable when no established convention exists.

Add a short ordered workflow (e.g. type-check -> lint -> verify boundary validation) with an explicit validation checkpoint to give the ruleset a sequenced feedback loop.

Tighten the longest compound sentences (Type Safety default rule, bundle-budget rule) by splitting into separate short directives.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean directive bullets that assume Claude's knowledge (no explaining what React/TypeScript is), with only minor over-elaboration in a few compound rules such as the Type Safety default and the bundle-budget performance rule that could be tightened.	4 / 5
Actionability	It mixes concrete signals ("handle `string \| null`", "review ownership or splitting above 10", "Prefer 0-2 parameters") with many directives that defer to "the repository's established pattern" / "accepted design" / the PRD, which give conditional guidance but not the concrete answer to execute.	3 / 5
Workflow Clarity	This is a categorized ruleset rather than a multi-step process, so there is no sequenced workflow with validation checkpoints; sections are organized but no explicit step sequence or validate-fix-retry feedback loop is present.	3 / 5
Progressive Disclosure	Content is well structured into clearly headed sections (Type Safety, Coding Conventions, Error Handling, etc.) in a self-contained file with no need for external references; at ~95 lines it slightly exceeds the under-50-line simple-skill bar that would warrant a 5.	4 / 5
	Total	14 / 20 Passed

Description

70%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 and when with natural triggers and a distinct niche, though its capability list reads as topic categories rather than concrete actions.

Suggestions

Replace topic-bucket phrasing with concrete verbs, e.g. "enforce type safety, design components, manage state, and handle errors in React/TypeScript code".

Add common synonyms or file cues users say (e.g. ".tsx", "hooks", "JSX") to broaden trigger coverage toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Names the domain plus four rule areas ("type safety, component design, state management, and error handling"), but these are topic buckets rather than concrete verb-actions like "extract"/"fill"/"merge", so it sits at the domain-plus-topics level rather than listing specific actions.	3 / 5
Completeness	Both halves are present — a "what" (React/TypeScript frontend rules across four areas) and an explicit "Use when..." clause with three trigger phrases — but the "what" enumerates rule topics rather than concrete capabilities, leaving it slightly below the fully concrete anchor 5.	4 / 5
Trigger Term Quality	Natural user-facing terms appear ("React components", "TypeScript code", "frontend features") that a user would actually say, but coverage lacks synonyms and file extensions, so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The React+TypeScript frontend niche with those specific triggers is mostly distinct, with only minor overlap risk against a generic TypeScript or general React skill.	4 / 5
	Total	15 / 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: shinpr/claude-code-workflows
Path: skills/typescript-rules/SKILL.md
Commit: 83cf695

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