canvas-component-naming

Use simple, generic names. Never prefix component names with the project or site name. Components should be reusable and their names should describe their purpose, not their origin.

Use kebab-case for component names (for example, machineName, src/components/<name>/, and story filenames).

When copying and modifying an example component, keep the original name unless the component serves a fundamentally different purpose. When creating a new component without an example, choose a simple, descriptive name.

# Correct - simple, descriptive names
footer
hero
navigation
contact-form

# Wrong - prefixed with project/site name
nebula-footer
acme-hero
mysite-navigation
projectx-contact-form

This ensures components remain portable and their names clearly communicate their function rather than their project context.