CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

style-guide

Use when: authoring, modifying, or reviewing Primer React components, hooks, utilities, or component APIs.

Quality

74%

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 ./.github/skills/style-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Primer React Style Guide

Use this skill when creating, modifying, or reviewing Primer React components, hooks, utilities, or component APIs.

Before authoring component code, read contributor-docs/style.md and apply the guidelines that are relevant to the change. The style guide is the source of truth for component API design and implementation conventions in this repository.

When proposing, implementing, or reviewing a component change, explicitly apply the relevant style-guide principles to the design. If a change intentionally deviates from the style guide, call out the reason.

In addition, there are a set of topics below that may be used for guidance on a specific topic. Consult this to see if any apply to the task at hand.

TopicDescriptionLink
Component prop namingUse when deciding or evaluating the name for a prop in a React component.component-prop-naming
Component prop typesUse when designing or reviewing component prop types, including slot-based props.component-prop-types

Updating this skill

Keep SKILL.md minimal: usage instructions and a table linking to topics. When adding or updating guidance, edit the relevant topic under docs/. If no existing topic fits, create a new topic file under docs/ and add a row to the table with a link and a description of when to consult it. Keep detailed guidance and examples in topic files rather than in SKILL.md.

Repository

primer/react

Path

.github/skills/style-guide/SKILL.md

Last updated
First committed

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.