CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

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

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.

The body is well-structured and highly actionable with real TypeScript examples and concrete thresholds, but it is a monolithic wall of text across many domains and would benefit from splitting into reference files and trimming tutorial-style explanations.

Suggestions

Split large sections (e.g., Type Safety, Error Handling, Refactoring) into separate reference files and link to them one level deep from SKILL.md to improve progressive disclosure.

Tighten tutorial-flavored feature intros (satisfies, branded types, template literal types) to terse rule statements, since Claude already knows these TypeScript features.

Add an explicit validation/verification checkpoint to the refactoring procedure (e.g., 'run the type check and tests before declaring the change complete') to lift workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient rule statements with targeted code, but tutorial-flavored intros ('satisfies Operator', branded types, template literal types) and restated data-flow prose could be tightened, fitting score 2 rather than the lean score-3 anchor.

2 / 3

Actionability

Concrete executable TypeScript (type guards, Result<T,E>, AppError, immutable setUsers, env validation) plus specific thresholds ('0-2 parameters', '3-7 props ideal') match the copy-paste-ready score-3 anchor, not the pseudocode score-2 case.

3 / 3

Workflow Clarity

The refactoring procedure has a sequence ('Understand Current State -> Gradual Changes -> Behavior Verification -> Final Validation') but no concrete validation checkpoint, matching the score-2 anchor with implicit checkpoints rather than the explicit-validation score-3 anchor.

2 / 3

Progressive Disclosure

The ~215-line body is a single monolithic file spanning many domains that could be split into references; it is well-headed but inline content that should be separate fits score 2, not the one-level-deep-reference score-3 anchor.

2 / 3

Total

9

/

12

Passed

Description

100%

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 names concrete capability areas, includes natural trigger terms, has an explicit 'Use when' clause, and occupies a clear React/TypeScript frontend niche. It uses third-person voice with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete capability domains ('type safety, component design, state management, and error handling') matching the score-3 anchor of multiple specific actions rather than the narrower score-2 anchor.

3 / 3

Completeness

Explicitly answers both what ('React/TypeScript frontend development rules including...') and when ('Use when implementing React components, TypeScript code, or frontend features.'), with a present 'Use when' clause avoiding the cap at 2.

3 / 3

Trigger Term Quality

Natural user-facing terms ('React components, TypeScript code, or frontend features') are exactly what a user would say, satisfying the score-3 anchor; not the score-2 case of missing common variations.

3 / 3

Distinctiveness Conflict Risk

The React/TypeScript frontend niche with distinct triggers is unlikely to fire for unrelated skills, matching the score-3 anchor rather than the overlap-prone score-2.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
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.