اتفاقيات تسمية المكونات

The hardest problems in component libraries are not technical - they are naming. A poorly named component is hard to find, easy to misuse, and painful to rename later.

Good names act as documentation and reduce the questions teammates ask.

Name components by what they are or do, not by clever metaphors.

• Good: UserAvatar, PrimaryButton
• Avoid: Blob, Sparkle, Thingy

A new teammate should guess the purpose from the name alone.

Pick one casing rule and never deviate. The web convention:

• Components: PascalCase (CardHeader)
• Props: camelCase (isDisabled)
• CSS classes: kebab-case (card-header)

Mixing casing styles erodes trust in the library.

Boolean props read best with an is, has, or should prefix. They sound like questions and default to false.

The snippet below shows the pattern.

Establish predictable prop names across all components:

• variant for visual style (primary, ghost)
• size for scale (sm, md, lg)
• onChange, onClick for event handlers

If every component uses the same names, learning one teaches you all.

Do not bake fragile details into names. BlueButton becomes a lie the moment the brand color changes.

Prefer intent-based names like PrimaryButton. The intent is stable even when the styling evolves.

Many systems prefix components to avoid clashes and signal origin: DsButton, AcmeCard.

This helps when consuming apps already have their own components. Choose a short prefix and apply it everywhere or nowhere - consistency over preference.

Related parts should share a family name: Card, CardHeader, CardBody, CardFooter.

The shared prefix groups them in autocomplete and signals they belong together. This is far clearer than Card, Heading, Content.

Once a component name ships, every consuming app depends on it. Renaming becomes a breaking change requiring deprecation cycles.

Invest time in the name up front. A 10-minute naming discussion saves months of migration pain.

Write your naming conventions down in the contribution guide. New contributors should not have to reverse-engineer your patterns.

A short, enforced naming doc keeps the library coherent as more people contribute.

Ultimately, a component's name and prop names form a public API contract. Treat them with the same care as any API.

Predictable names let developers compose your library confidently without reading the source.

Test your naming instincts.

You learned naming conventions that keep a component library usable:

• Be descriptive and intent-based, not clever or color-bound.
• Use consistent casing and predictable prop names.
• Group compound components with shared prefixes.
• Document the rules and remember renaming is costly.

Good names are quiet documentation.