fix: address Copilot review comments

- README: fix ESLint ecmaVersion (latest), npm start description (no auto-reload),
  lint section (test:lint vs lint), docker image (pierreb/node)
- skill/verify: use npm run test:lint instead of npm run lint
- skill/naming: fix model patterns (model.mongoose.js, schema.js), optional name segment
- skill/create-module: align module structure with actual tasks template
  (controller.js, data.service.js, model.mongoose.js, schema.js, unit+integration tests)
- skill/feature: fix responses helper signature (responses.success(res, msg)(data))

Author: PierreBrisorgueil

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

@@ -44,7 +44,7 @@ Search and replace the following tokens across the new module:
 
 Files to check in `modules/{new-module-name}/`:
 
-- File names (controllers, services, repositories, models, policies, routes, tests)
+- File names (controllers, services, repositories, models, schemas, policies, routes, tests)
 - Mongoose model name and collection name
 - Route paths and prefixes
 - Joi validation schemas
@@ -66,7 +66,7 @@ Use safe search+replace to avoid false positives:
 ### 7. Run verify
 
 ```bash
-npm run lint
+npm run test:lint
 npm test
 ```
 
@@ -77,30 +77,35 @@ Provide a summary:
 - ✅ Module created at: `modules/{new-module-name}`
 - ✅ Renamed tokens: `tasks` → `{new-module-name}`, etc.
 - ✅ Verification: lint passed, tests passed
-- 📝 Next steps: Customize the model schema, update business logic in services, register routes in `lib/services/express.js` if needed
+- 📝 Next steps: Customize the schema, update business logic in services, register routes in `lib/services/express.js` if needed
 
 ## Module Structure
 
 ```
 modules/{new-module-name}/
 ├── controllers/
-│   └── {module}.crud.controller.js
+│   └── {module}.controller.js
 ├── services/
-│   └── {module}.crud.service.js
+│   └── {module}.service.js
+│   └── {module}.data.service.js
 ├── repositories/
 │   └── {module}.repository.js
 ├── models/
-│   └── {module}.model.js
+│   └── {module}.model.mongoose.js
+│   └── {module}.model.sequelize.js  (optional)
+│   └── {module}.schema.js
 ├── policies/
-│   └── {module}.crud.policy.js
+│   └── {module}.policy.js
 ├── routes/
 │   └── {module}.routes.js
 └── tests/
-    └── {module}.integration.tests.js
+    ├── {module}.integration.tests.js
+    └── {module}.unit.tests.js
 ```
 
 ## Notes
 
 - Preserves the layered architecture: controllers → services → repositories → models
 - Follows modularity rules: keeps the module self-contained
 - Policy functions control route authorization — update them for your use case
+- Remove `{module}.model.sequelize.js` if not using SQL

.claude/skills/feature/SKILL.md

@@ -29,7 +29,7 @@ Routes → Controllers → Services → Repositories → Models
 - **Controllers** (`controllers/`): Handle HTTP req/res, call services, format responses via `lib/helpers/responses.js`
 - **Services** (`services/`): Business logic, call repositories, throw `AppError` for domain errors
 - **Repositories** (`repositories/`): Database access only, use Joi schemas for validation
-- **Models** (`models/`): Mongoose schema definition
+- **Models** (`models/`): Mongoose schema definition (`*.model.mongoose.js`) and Joi schema (`*.schema.js`)
 
 ### 3. Apply modularity rules
 
@@ -39,13 +39,13 @@ Routes → Controllers → Services → Repositories → Models
   - Place it in `lib/helpers/` or `lib/services/`
   - Provide **explicit justification** for why it must be shared
 - Keep these inside the module (`modules/{module}/**`):
-  - Controllers, services, repositories, models, policies, routes, tests
+  - Controllers, services, repositories, models, schemas, policies, routes, tests
 
 ### 4. Use existing helpers
 
 Before writing new utilities, check:
 
-- `lib/helpers/responses.js` — JSend response wrapper (`success`, `error`)
+- `lib/helpers/responses.js` — JSend response wrapper
 - `lib/helpers/AppError.js` — Custom error class for domain errors
 - `lib/helpers/errors.js` — Error formatting utilities
 - `lib/helpers/joi.js` — Shared Joi validation helpers
@@ -54,19 +54,19 @@ Before writing new utilities, check:
 
 ### 5. Follow API response format
 
-All API responses must use the JSend wrapper:
+All API responses must use the JSend wrapper from `lib/helpers/responses.js`:
 
 ```js
 // Success
-res.status(200).json(responses.success(data));
-// Error (caught by controller)
-res.status(err.status).json(responses.error(err.message, err.errors));
+responses.success(res, 'task list')(data);
+// Error
+responses.error(res, 422, 'Unprocessable Entity', errors.getMessage(err))(err);
 ```
 
 ### 6. Run verify
 
 ```bash
-npm run lint
+npm run test:lint
 npm test
 ```
 

.claude/skills/naming/SKILL.md

@@ -11,33 +11,37 @@ Audit or apply the project's file and folder naming conventions.
 
 ### Folders
 
-| Location        | Case       | Example                          |
-| --------------- | ---------- | -------------------------------- |
-| Top-level dirs  | kebab-case | `lib/`, `modules/`, `config/`    |
-| Module dirs     | kebab-case | `modules/tasks/`, `modules/home/`|
+| Location        | Case        | Example                           |
+| --------------- | ----------- | --------------------------------- |
+| Top-level dirs  | kebab-case  | `lib/`, `modules/`, `config/`     |
+| Module dirs     | kebab-case  | `modules/tasks/`, `modules/home/` |
 | Module sub-dirs | fixed names | `controllers/`, `services/`, `repositories/`, `models/`, `policies/`, `routes/`, `tests/`, `config/`, `doc/` |
 
 ### Files
 
-| Type        | Pattern                        | Example                          |
-| ----------- | ------------------------------ | -------------------------------- |
-| Controller  | `{module}.{name}.controller.js`| `tasks.crud.controller.js`       |
-| Service     | `{module}.{name}.service.js`   | `tasks.crud.service.js`          |
-| Repository  | `{module}.repository.js`       | `tasks.repository.js`            |
-| Model       | `{module}.model.js`            | `tasks.model.js`                 |
-| Policy      | `{module}.{name}.policy.js`    | `tasks.crud.policy.js`           |
-| Router      | `{module}.routes.js`           | `tasks.routes.js`                |
-| Test        | `{module}.{type}.tests.js`     | `tasks.integration.tests.js`     |
-| Config      | `{name}.js`                    | `app.js`, `default.js`           |
+| Type            | Pattern                               | Example                                                    |
+| --------------- | ------------------------------------- | ---------------------------------------------------------- |
+| Controller      | `{module}[.{name}].controller.js`     | `tasks.controller.js`                                      |
+| Service         | `{module}[.{name}].service.js`        | `tasks.service.js`, `tasks.data.service.js`                |
+| Repository      | `{module}.repository.js`              | `tasks.repository.js`                                      |
+| Mongoose Model  | `{module}.model.mongoose.js`          | `tasks.model.mongoose.js`                                  |
+| Sequelize Model | `{module}.model.sequelize.js`         | `tasks.model.sequelize.js`                                 |
+| Schema          | `{module}.schema.js`                  | `tasks.schema.js`                                          |
+| Policy          | `{module}[.{name}].policy.js`         | `tasks.policy.js`                                          |
+| Router          | `{module}.routes.js`                  | `tasks.routes.js`                                          |
+| Test            | `{module}.{type}.tests.js`            | `tasks.integration.tests.js`, `tasks.unit.tests.js`        |
+| Config          | `{name}.js`                           | `app.js`, `default.js`                                     |
+
+> `[.{name}]` is optional — the reference `tasks` module uses the short form (e.g., `tasks.controller.js`, `tasks.service.js`).
 
 ### Naming Tokens
 
 From a module name (e.g., `my-feature`):
 
 - **kebab-case**: `my-feature` (folder names, file prefixes, route paths)
-- **PascalCase**: `MyFeature` (class names, Mongoose model names)
+- **PascalCase**: `MyFeature` (Mongoose model names, class names)
 - **lowerCamelCase**: `myFeature` (variable names, function names, JS exports)
-- **UPPER_SNAKE_CASE**: `MY_FEATURE` (constants, env keys)
+- **UPPER_SNAKE_CASE**: `MY_FEATURE` (constants)
 
 ## Layer Order
 

.claude/skills/verify/SKILL.md

@@ -9,14 +9,15 @@ Run lint → tests and report results.
 
 ## Steps
 
-1. Run `npm run lint` to check code quality
+1. Run `npm run test:lint` to check code quality (read-only, no auto-fix)
 2. Run `npm test` to run all tests
 3. Summarize results:
    - ✅ All checks passed → ready to commit
    - ❌ Some checks failed → show what failed and suggest next action
 
 ## Notes
 
+- Use `npm run test:lint` (not `npm run lint`) — `lint` auto-fixes files which is not suitable for verification
 - Does not run tests in watch mode (use `npm run test:watch` manually for that)
 - Does not run coverage (use `npm run test:coverage` manually for that)
 - Does not commit or push changes

README.md

@@ -22,7 +22,7 @@ Designed to be cloned into downstream projects and kept up-to-date via `git merg
 | Upload       | [Mongo GridFS](https://docs.mongodb.com/manual/core/gridfs/) - [Multer](https://github.com/expressjs/multer) - [Sharp](https://github.com/lovell/sharp) - Image stream, all content types                                                                                                                             |
 | Testing      | [Jest](https://github.com/facebook/jest) - [SuperTest](https://github.com/visionmedia/supertest) - Coverage & Watch                                                                                                                                                                                                   |
 | CI           | [GitHub Actions](https://github.com/pierreb-devkit/Node/actions)                                                                                                                                                                                                                                                       |
-| Linter       | [ESLint](https://github.com/eslint/eslint) ecmaVersion 10 (2019)                                                                                                                                                                                                                                                       |
+| Linter       | [ESLint](https://github.com/eslint/eslint) ecmaVersion latest                                                                                                                                                                                                                                                          |
 | Developer    | [Dependabot](https://dependabot.com/) - [Snyk](https://snyk.io/test/github/pierreb-devkit/node) <br> [semantic-release](https://github.com/semantic-release/semantic-release) - [commitlint](https://github.com/conventional-changelog/commitlint) - [commitizen](https://github.com/commitizen/cz-cli)               |
 | Dependencies | [npm](https://www.npmjs.com)                                                                                                                                                                                                                                                                                           |
 | Deliver      | Docker & Docker-compose                                                                                                                                                                                                                                                                                                 |
@@ -62,7 +62,7 @@ npm install
 npm start
 ```
 
-Runs dev server with auto-reload at `http://localhost:3000/`
+Runs the server at `http://localhost:3000/`. For auto-reload during development, use `npm run debug` (nodemon).
 
 **CORS Note:** When connecting to the Vue stack, ensure CORS is configured:
 
@@ -89,7 +89,8 @@ Tests are organized per module in `modules/*/tests/`
 ### Code Quality
 
 ```bash
-npm run lint              # Check code quality
+npm run test:lint         # Check code quality (read-only)
+npm run lint              # Check and auto-fix code quality issues
 ```
 
 ### Database Seeding