web-naming

React component files use PascalCase matching the component identifier, like UserProfile.tsx exporting UserProfile. Hook files start with use plus camelCase, like useAuth.ts. If the repo already standardizes on kebab-case component files, keep that repo convention instead.

Treat acronyms as ordinary words: HttpClient, parseUrl, and userId. Only capitalize the first letter in PascalCase and never uppercase the whole acronym, except for platform-mandated names like XMLHttpRequest.

Prefer string unions or as const objects for discrete states, like type Status = 'pending' | 'paid'. Numeric enums are discouraged because an uninitialized value silently becomes 0, which looks like a real state. If an enum is required, use explicit string members.

Names like utils, helpers, common, and misc do not communicate responsibility and grow into unmaintainable grab-bags over time. Split them by responsibility into focused modules such as date.ts, url.ts, or crypto.ts, one concept per file.

No, it covers browser-side UI code only: React components, hooks, props, frontend modules, and their test files. Vue-specific SFC conventions belong to the vue-* skills, and pure backend Node or Hono libraries are out of scope.

Repo-level conventions always win. If the repository's AGENTS.md or ESLint config mandates a different style, such as kebab-case component files or all-caps acronyms, follow the repo rather than this guide, and never mass-correct files during review.