CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-component-guidelines

Guidelines for writing React components. Use this when creating a new react component.

Quality

73%

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/react-component-guidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, high-signal guidelines document: nearly every line is an applicable rule with named utilities, class names, and API shapes, organized under clear headers. The main improvement levers are trimming the conceptual opening paragraph, adding a small code example for the type-level rules, and potentially splitting the Icons/Overlays detail into reference files.

Suggestions

Delete or compress the introductory paragraph explaining what components are and why encapsulation matters — Claude already knows this, and the bullets carry the actual guidance.

Add one short TypeScript example showing the discriminated-union prop pattern (e.g. { status: 'loading' } | { status: 'loaded'; data: T }) to make the Explicit States rules copy-paste concrete.

Consider moving the detailed Icons and Overlays conventions into reference files (e.g. references/icons.md) to keep SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

The body is dense, imperative guidance ("No unused props", "Always prefer `Pick<>` over `Omit<>`") with almost no padding, but the opening paragraph ("Components are useful because they act as an encapsulated unit and therefore promote composition...") explains React fundamentals Claude already knows and could be trimmed. This is "efficient with minor instances of over-explanation" (anchor 4) rather than 5.

4 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: named controllers (DropdownMenuController, PopoverController, DialogController), an exact icon scale (icon-sm 12px through icon-xl 28px), and specific API shapes (openDialog(payload), <Trigger asChild>). Minor gaps keep it below 5: a few judgment-call rules ("MAJOR benefit... use your best judgement here") and no illustrative snippet for the type-level rules like the discriminated-union guidance.

4 / 5

Workflow Clarity

This is a guideline-collection skill rather than a sequenced process, and each section's single action is unambiguous with no destructive or batch operations requiring validation. It merits 4 rather than 5 because it is a multi-concern collection (icons, overlays, styling, typing) with no guidance on ordering, prioritization, or how to verify compliance when rules conflict.

4 / 5

Progressive Disclosure

The body is well organized into clear topical sections with no nested references (no bundle files exist, and none are referenced). It falls just short of 5: the body is slightly over the ~50-line threshold, and the detailed project-specific Icons and Overlays sections are candidates for separate reference files under the simple-skill exception.

4 / 5

Total

16

/

20

Passed

Description

57%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 correctly answers both 'what' and 'when' with an explicit trigger clause, but the 'what' side is thin: it names the domain without enumerating any concrete guideline areas, and trigger synonyms are sparse. It is serviceable but sits below the strong examples in both specificity and keyword coverage.

Suggestions

Enumerate the concrete guideline areas in the description, e.g. "Guidelines for writing React components covering prop design, composition, explicit state types, icons, and overlays".

Broaden trigger coverage with natural variations: "Use when creating, building, or refactoring React components".

State the value of following the guidelines (consistent, composable design-system components) so the 'what' goes beyond the generic word "guidelines".

DimensionReasoningScore

Specificity

"Guidelines for writing React components" names the domain but the only stated action is the generic "guidelines for writing" — no concrete capabilities (props design, composition, icons, overlays) are enumerated. This matches anchor 2 ("Names the domain but actions are minimal or generic") rather than 3, which requires 1-2 concrete listed actions.

2 / 5

Completeness

Both parts are present: a what ("Guidelines for writing React components") and an explicit when ("Use this when creating a new react component"). Not 5 because the 'what' is generic ('guidelines') and the 'when' is narrower than the body's actual scope; not 3 because the 'when' clause is explicit rather than merely implied.

4 / 5

Trigger Term Quality

"Use this when creating a new react component" includes the natural phrase "creating a new react component", but misses common variations users would say such as "build", "write", "refactor", or "new component" alone. Some relevant keywords are present, but synonym coverage is incomplete, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

"react component" is a distinct, specific trigger with a clear niche, giving minimal conflict risk with unrelated skills. It is not 5 because there is residual overlap risk with closely related React-ecosystem skills (testing, hooks, general styling guidelines).

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

langfuse/langfuse

Path

.agents/skills/react-component-guidelines/SKILL.md

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.