docs(skills): add multi-entity naming and config-driven enum rules

[PierreBrisorgueil]

Summary

• Add multi-entity module naming convention to /naming skill (files must be prefixed by module name, not entity name)
• Add config-driven enum guidance to /create-module skill (business values must come from module config, not hardcoded)

Test plan

• Lint passes (0 errors)
• All 159 unit tests pass
• Verify skills render correctly in Claude Code

Summary by CodeRabbit

• Documentation
  • Updated module creation guidance documentation with clarified heading structure and improved reference paths.
  • Enhanced naming convention documentation with additional module mapping examples.

[Copilot]

Pull request overview

Updates internal Claude skills documentation to clarify naming for multi-entity modules and to encourage config-driven enums when scaffolding new modules.

Changes:

• Document multi-entity module file naming (module-prefixed filenames even when modeling multiple entities).
• Add guidance to /create-module on defining enum-like business values in module config and referencing them from models/schemas.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.claude/skills/naming/SKILL.md	Adds “multi-entity modules” naming guidance and a generalized {module}.{entity}... pattern.
.claude/skills/create-module/SKILL.md	Adds a “config-driven enums” subsection describing where to define and how to reference business enums.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: d1153995-8a96-4214-9190-4e6ce585e759

📥 Commits

Reviewing files that changed from the base of the PR and between 5e59e6f and be96340.

📒 Files selected for processing (2)

• .claude/skills/create-module/SKILL.md
• .claude/skills/naming/SKILL.md

---

Walkthrough

Documentation updates to Claude skills modules: correcting header formatting in create-module skill documentation and updating a reference path from relative to absolute format, plus adding a mapping example to naming skill documentation.

Changes

Cohort / File(s)	Summary
Documentation - create-module skill .claude/skills/create-module/SKILL.md	Header level adjusted for "Config-driven enums" section; reference path updated from users.schema.js to modules/users/models/users.schema.js with reference label refined.
Documentation - naming skill .claude/skills/naming/SKILL.md	Added documentation line with new mapping example: organizations.crud.service.js → crud.service.js.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-skills-naming-conventions

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can customize the tone of the review comments and chat replies.

Configure the tone_instructions setting to customize the tone of the review comments and chat replies. For example, you can set the tone to Act like a strict teacher, Act like a pirate and more.