paniolo-naming-best-practices

Requires: file-read, terminal (linting/testing). No network access needed.

Reference: naming — code examples for use* vs compute*, type/variable/component naming, file naming table, and success criteria.

Use When

Use this skill when:

• Naming new files, functions, hooks, types, or variables.
• Renaming symbols during refactors for clarity and convention compliance.

Execution workflow:

1. Choose names based on behavioral intent (fetch, compute, subscribe, run, etc.).
2. Ensure hook names (use*) only apply when React hooks are called internally.
3. Keep file and symbol names aligned with nearby project patterns.
4. Recheck references/imports after renames and validate with npm run lint.