eslint-plugin-code-style 1.15.0 → 1.17.0

package/AGENTS.md

@@ -4,9 +4,9 @@ Instructions for AI coding agents working with this codebase.
 
 ## Project Overview
 
-**eslint-plugin-code-style** is an ESLint plugin providing 77 custom formatting rules (67 auto-fixable, 17 configurable, 10 report-only) for React/JSX projects. It's designed for ESLint v9+ flat config system.
+**eslint-plugin-code-style** is an ESLint plugin providing 79 custom formatting rules (70 auto-fixable, 19 configurable, 9 report-only) for React/JSX projects. It's designed for ESLint v9+ flat config system.
 
-- **Main entry:** `index.js` - Contains all 77 rules in a single file
+- **Main entry:** `index.js` - Contains all 79 rules in a single file
 - **Type definitions:** `index.d.ts` - TypeScript declarations for IDE support
 - **Recommended configs:** `recommended-configs/` - Ready-to-use ESLint configurations
 - **Test apps:** `_tests_/` - Sample apps for testing rules
@@ -33,7 +33,7 @@ Each test project in `_tests_/` corresponds to a specific tech stack. Rules shou
 | **TypeScript rules** | ❌ | ✅ | ✅ | ❌ |
 | **Tailwind rules** | ❌ | ✅ | ❌ | ✅ |
 
-**TypeScript-only rules** (69 rules in JS projects, 77 in TS projects):
+**TypeScript-only rules** (71 rules in JS projects, 79 in TS projects):
 - `component-props-inline-type`
 - `enum-format`
 - `interface-format`
@@ -87,7 +87,7 @@ index.js
 ├── imports (fs, path, url)
 ├── Rule 1 definition (const ruleName = { create(), meta: {} })
 ├── Rule 2 definition
-├── ... (77 rules total)
+├── ... (79 rules total)
 └── export default { meta: {}, rules: {} }
 ```
 
@@ -651,7 +651,7 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 - **Comment Rules** — Comment formatting
   - `comment-format`
 - **Component Rules** — React component patterns
-  - `component-props-destructure`, `component-props-inline-type`, `folder-component-suffix`, `no-redundant-folder-suffix`, `svg-component-icon-naming`
+  - `component-props-destructure`, `component-props-inline-type`, `folder-based-naming-convention`, `folder-structure-consistency`, `no-redundant-folder-suffix`, `svg-icon-naming-convention`
 - **Control Flow Rules** — if/switch/block statements
   - `block-statement-newlines`, `if-else-spacing`, `if-statement-format`, `multiline-if-conditions`, `no-empty-lines-in-switch-cases`, `ternary-condition-multiline`
 - **Function Rules** — Function declarations and params
@@ -659,7 +659,7 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 - **Hook Rules** — React hooks formatting
   - `hook-callback-format`, `hook-deps-per-line`
 - **Import/Export Rules** — Import/export statements
-  - `absolute-imports-only`, `export-format`, `import-format`, `import-source-spacing`, `index-export-style`, `index-exports-only`, `module-index-exports`
+  - `absolute-imports-only`, `export-format`, `import-format`, `import-source-spacing`, `index-export-style`, `index-exports-only`, `inline-export-declaration`, `module-index-exports`
 - **JSX Rules** — JSX elements and attributes
   - `classname-dynamic-at-end`, `classname-multiline`, `classname-no-extra-spaces`, `classname-order`, `jsx-children-on-new-line`, `jsx-closing-bracket-spacing`, `jsx-element-child-new-line`, `jsx-logical-expression-simplify`, `jsx-parentheses-position`, `jsx-prop-naming-convention`, `jsx-simple-element-one-line`, `jsx-string-value-trim`, `jsx-ternary-format`, `no-empty-lines-in-jsx`
 - **Object Rules** — Object literal formatting
@@ -687,7 +687,7 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 
 ## Documentation Files
 
-- `README.md` - Main documentation with all 77 rules
+- `README.md` - Main documentation with all 79 rules
 - `recommended-configs/<config-name>/README.md` - Config-specific documentation (references main README for rule details)
 - `index.d.ts` - TypeScript types for IDE autocomplete
 
@@ -695,7 +695,7 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 
 - Most rules should be auto-fixable (`fixable: "code"` or `fixable: "whitespace"` in meta)
 - Rules that require file creation/movement or architectural decisions may be report-only
-- Currently: 67 auto-fixable rules, 17 configurable rules, 10 report-only rules
+- Currently: 70 auto-fixable rules, 19 configurable rules, 9 report-only rules
 - Use 4-space indentation throughout
 - Object properties in `context.report()` must be alphabetically sorted
 - Keep rules self-sufficient (no dependencies on other ESLint rules)
@@ -708,10 +708,10 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 **IMPORTANT:** When adding/removing rules, update the rule counts in ALL these locations:
 
 ### Current Counts (update these when changing rules)
-- **Total rules:** 77
-- **Auto-fixable:** 67 (43 with `fixable: "code"` + 24 with `fixable: "whitespace"`)
-- **Configurable:** 17 (rules with ⚙️ that have options)
-- **Report-only:** 10
+- **Total rules:** 79
+- **Auto-fixable:** 70
+- **Configurable:** 19 (rules with ⚙️ that have options)
+- **Report-only:** 9
 
 **IMPORTANT:** All counts must be uniform across ALL files. When updating:
 - Total rules, auto-fixable count, configurable count, and report-only count must match everywhere
@@ -722,21 +722,21 @@ Rules are organized in these categories (alphabetically sorted in index.js and R
 
 | File | Line(s) | What to Update |
 |------|---------|----------------|
-| `README.md` | ~22 | `*77 rules (67 auto-fixable, 17 configurable)*` |
-| `README.md` | ~30 | `**76 custom rules** (66 auto-fixable, 17 configurable)` |
-| `README.md` | ~39 | `67 of 77 rules support auto-fix` |
-| `README.md` | ~100 | `**67 rules** support automatic fixing. **17 rules** have configurable options` |
-| `README.md` | ~266 | `**77 rules total** — 67 with auto-fix, 17 configurable` |
-| `README.md` | ~3650 | `67 of 77 rules support auto-fixing` |
-| `AGENTS.md` | ~7 | `77 custom formatting rules (67 auto-fixable, 17 configurable, 10 report-only)` |
-| `AGENTS.md` | ~9 | `Contains all 77 rules` |
-| `AGENTS.md` | ~36 | `(69 rules in JS projects, 77 in TS projects)` |
-| `AGENTS.md` | ~89 | `(77 rules total)` |
-| `AGENTS.md` | ~675 | `all 77 rules` |
-| `AGENTS.md` | ~697 | `67 auto-fixable rules, 17 configurable rules, 10 report-only` |
+| `README.md` | ~22 | `*79 rules (70 auto-fixable, 19 configurable)*` |
+| `README.md` | ~30 | `**79 custom rules** (70 auto-fixable, 19 configurable)` |
+| `README.md` | ~39 | `70 of 79 rules support auto-fix` |
+| `README.md` | ~100 | `**70 rules** support automatic fixing. **19 rules** have configurable options` |
+| `README.md` | ~266 | `**79 rules total** — 70 with auto-fix, 19 configurable` |
+| `README.md` | ~3650 | `70 of 79 rules support auto-fixing` |
+| `AGENTS.md` | ~7 | `79 custom formatting rules (70 auto-fixable, 19 configurable, 9 report-only)` |
+| `AGENTS.md` | ~9 | `Contains all 79 rules` |
+| `AGENTS.md` | ~36 | `(71 rules in JS projects, 79 in TS projects)` |
+| `AGENTS.md` | ~89 | `(79 rules total)` |
+| `AGENTS.md` | ~675 | `all 79 rules` |
+| `AGENTS.md` | ~697 | `70 auto-fixable rules, 19 configurable rules, 9 report-only` |
 | `AGENTS.md` | Rule Count Locations section | Current Counts table |
-| `recommended-configs/react-ts-tw/README.md` | ~396 | `**67 auto-fixable rules** (77 total, 17 configurable, 10 report-only)` |
-| `recommended-configs/react/README.md` | ~286 | `**67 auto-fixable rules** (77 total, 17 configurable, 10 report-only)` |
+| `recommended-configs/react-ts-tw/README.md` | ~396 | `**70 auto-fixable rules** (79 total, 19 configurable, 9 report-only)` |
+| `recommended-configs/react/README.md` | ~286 | `**70 auto-fixable rules** (79 total, 19 configurable, 9 report-only)` |
 
 ### Quick Verification Commands
 

package/CHANGELOG.md

@@ -7,6 +7,84 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [1.17.0] - 2026-02-09
+
+**New Rule + Enhancements to Naming & Import Rules**
+
+**Version Range:** v1.16.0 → v1.17.0
+
+### Added
+
+**New Rules (1)**
+- `inline-export-declaration` - Enforce inline export declarations (`export const x = ...`) instead of grouped export statements (`export { x }`) in non-index files 🔧
+  - Auto-fixable: adds `export` to each declaration and removes the grouped export statement
+  - Skips index files (barrel re-exports) and aliased exports (`export { a as b }`)
+
+### Enhanced
+
+- **`folder-based-naming-convention`** - Extended camelCase suffix enforcement for data/constants/strings/services/reducers folders
+  - Exports in `data/` must end with `Data` (e.g., `buttonTypeData`)
+  - Exports in `constants/` must end with `Constants` (e.g., `localeConstants`)
+  - Exports in `strings/` must end with `Strings` (e.g., `appStrings`)
+  - Exports in `services/` must end with `Service`, `reducers/` with `Reducer`
+- **`absolute-imports-only`** - Files within the same module folder must use relative imports instead of absolute to avoid circular dependencies 🔧
+  - Detects files at any depth inside module folders (e.g., `data/auth/login/guest.tsx`)
+  - Allows both `./` and `../` relative imports within the same module folder
+  - Auto-fixes absolute imports to own module folder (e.g., `@/data/auth/login/guest` → `../../login/guest`)
+  - Now marked as auto-fixable (`fixable: "code"`)
+- **`folder-structure-consistency`** - Added loose module file detection: standalone files matching module folder names (e.g., `data.js`, `strings.js`) are flagged — must use folder structure instead
+
+### Stats
+
+- Total Rules: 79 (was 78)
+- Auto-fixable: 70 rules (was 69) 🔧
+- Configurable: 19 rules (was 18)
+- Report-only: 9 rules (was 10)
+
+**Full Changelog:** [v1.16.0...v1.17.0](https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.16.0...v1.17.0)
+
+---
+
+## [1.16.0] - 2026-02-09
+
+**New Rule + Enhancements + Rule Renames**
+
+**Version Range:** v1.15.0 → v1.16.0
+
+### Added
+
+**New Rules (1)**
+- `folder-structure-consistency` - Enforce consistent folder structure (flat vs wrapped) in module folders
+  - Applies to all module folders (same list as `module-index-exports`)
+  - Detects mixed structures (some flat files, some in subfolders)
+  - Flags unnecessary wrapper folders when each has only one file
+  - Configurable `moduleFolders` and `extraModuleFolders` options
+
+### Enhanced
+
+- **`folder-based-naming-convention`** (renamed from `folder-component-suffix`)
+  - Support nested files with chained folder names (e.g., `layouts/auth/login.tsx` → `LoginAuthLayout`)
+  - Match files at any depth within module folders
+  - Expanded to cover: views, layouts, pages, providers, reducers, services, contexts, themes (with suffix), atoms and components (chaining only, no suffix)
+  - Added `VariableDeclarator` detection for non-JSX folders (contexts, themes)
+- **`no-redundant-folder-suffix`** - Also check folder names for redundant suffixes (e.g., `views/access-control-view/` is now flagged)
+
+### Renamed
+
+- `folder-component-suffix` → `folder-based-naming-convention` (now handles more than just components)
+- `svg-component-icon-naming` → `svg-icon-naming-convention` (consistent with other naming convention rules)
+
+### Stats
+
+- Total Rules: 78 (was 77)
+- Auto-fixable: 67 rules
+- Configurable: 18 rules (was 17)
+- Report-only: 11 rules (was 10)
+
+**Full Changelog:** [v1.15.0...v1.16.0](https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.15.0...v1.16.0)
+
+---
+
 ## [1.15.0] - 2026-02-06
 
 **New Rule: no-redundant-folder-suffix**
@@ -1728,6 +1806,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+[1.17.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.16.0...v1.17.0
+[1.16.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.15.0...v1.16.0
 [1.15.0]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.14.4...v1.15.0
 [1.14.4]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.14.3...v1.14.4
 [1.14.3]: https://github.com/Mohamed-Elhawary/eslint-plugin-code-style/compare/v1.14.2...v1.14.3

package/README.md

@@ -19,7 +19,7 @@
 
 **A powerful ESLint plugin for enforcing consistent code formatting and style rules in React/JSX projects.**
 
-*77 rules (67 auto-fixable, 17 configurable) to keep your codebase clean and consistent*
+*79 rules (70 auto-fixable, 19 configurable) to keep your codebase clean and consistent*
 
 </div>
 
@@ -27,7 +27,7 @@
 
 ## 🎯 Why This Plugin?
 
-This plugin provides **77 custom rules** (67 auto-fixable, 17 configurable) for code formatting. Built for **ESLint v9 flat configs**.
+This plugin provides **79 custom rules** (70 auto-fixable, 19 configurable) for code formatting. Built for **ESLint v9 flat configs**.
 
 > **Note:** ESLint [deprecated 79 formatting rules](https://eslint.org/blog/2023/10/deprecating-formatting-rules/) in v8.53.0. Our recommended configs use `@stylistic/eslint-plugin` as the replacement for these deprecated rules.
 
@@ -36,7 +36,7 @@ This plugin provides **77 custom rules** (67 auto-fixable, 17 configurable) for
 - **Works alongside existing tools** — Complements ESLint's built-in rules and packages like eslint-plugin-react, eslint-plugin-import, etc
 - **Self-sufficient rules** — Each rule handles complete formatting independently
 - **Consistency at scale** — Reduces code-style differences between team members by enforcing uniform formatting across your projects
-- **Highly automated** — 67 of 77 rules support auto-fix with `eslint --fix`
+- **Highly automated** — 70 of 79 rules support auto-fix with `eslint --fix`
 
 When combined with ESLint's native rules and other popular plugins, this package helps create a complete code style solution that keeps your codebase clean and consistent.
 
@@ -60,7 +60,7 @@ We provide **ready-to-use ESLint flat configuration files** that combine `eslint
 
 ### 💡 Why Use These Configs?
 
-- **Complete Coverage** — Combines ESLint built-in rules, third-party plugins, and all 77 code-style rules
+- **Complete Coverage** — Combines ESLint built-in rules, third-party plugins, and all 79 code-style rules
 - **Ready-to-Use** — Copy the config file and start linting immediately
 - **Battle-Tested** — These configurations have been refined through real-world usage
 - **Fully Documented** — Each config includes detailed instructions and explanations
@@ -97,7 +97,7 @@ We provide **ready-to-use ESLint flat configuration files** that combine `eslint
 <td width="50%">
 
 ### 🔧 Auto-Fixable Rules
-**67 rules** support automatic fixing with `eslint --fix`. **17 rules** have configurable options. 10 rules are report-only (require manual changes).
+**70 rules** support automatic fixing with `eslint --fix`. **19 rules** have configurable options. 9 rules are report-only (require manual changes).
 
 </td>
 <td width="50%">
@@ -199,13 +199,14 @@ rules: {
     "code-style/comment-format": "error",
     "code-style/component-props-destructure": "error",
     "code-style/component-props-inline-type": "error",
-    "code-style/svg-component-icon-naming": "error",
+    "code-style/svg-icon-naming-convention": "error",
     "code-style/curried-arrow-same-line": "error",
     "code-style/empty-line-after-block": "error",
     "code-style/enum-format": "error",
     "code-style/enum-type-enforcement": "error",
     "code-style/export-format": "error",
-    "code-style/folder-component-suffix": "error",
+    "code-style/folder-based-naming-convention": "error",
+    "code-style/folder-structure-consistency": "error",
     "code-style/no-redundant-folder-suffix": "error",
     "code-style/function-arguments-format": "error",
     "code-style/function-call-spacing": "error",
@@ -222,6 +223,7 @@ rules: {
     "code-style/import-source-spacing": "error",
     "code-style/index-export-style": "error",
     "code-style/index-exports-only": "error",
+    "code-style/inline-export-declaration": "error",
     "code-style/interface-format": "error",
     "code-style/jsx-children-on-new-line": "error",
     "code-style/jsx-closing-bracket-spacing": "error",
@@ -267,7 +269,7 @@ rules: {
 
 ## 📖 Rules Categories
 
-> **77 rules total** — 67 with auto-fix 🔧, 17 configurable ⚙️, 10 report-only. See detailed examples in [Rules Reference](#-rules-reference) below.
+> **79 rules total** — 70 with auto-fix 🔧, 19 configurable ⚙️, 9 report-only. See detailed examples in [Rules Reference](#-rules-reference) below.
 >
 > **Legend:** 🔧 Auto-fixable with `eslint --fix` • ⚙️ Customizable options
 
@@ -294,9 +296,10 @@ rules: {
 | **Component Rules** | |
 | `component-props-destructure` | Component props must be destructured `({ prop })` not received as `(props)` 🔧 |
 | `component-props-inline-type` | Inline type annotation `} : {` with matching props, proper spacing, commas, no interface reference 🔧 |
-| `folder-component-suffix` | Components in `views/` folder must end with "View", `pages/` with "Page", `layouts/` with "Layout" |
-| `no-redundant-folder-suffix` | Disallow file names that redundantly include the parent folder name as a suffix |
-| `svg-component-icon-naming` | SVG components must end with "Icon" suffix; "Icon" suffix components must return SVG |
+| `folder-based-naming-convention` | Enforce naming based on folder: suffix for views/layouts/pages/providers/reducers/contexts/themes, camelCase suffix for data/constants/strings/services/reducers folders, chained folder names for nested files 🔧 |
+| `folder-structure-consistency` | Enforce consistent folder structure (flat vs wrapped) in module folders (atoms, components, hooks, enums, views, etc.) ⚙️ |
+| `no-redundant-folder-suffix` | Disallow file and folder names that redundantly include the parent folder name as a suffix |
+| `svg-icon-naming-convention` | SVG components must end with "Icon" suffix; "Icon" suffix components must return SVG |
 | **Class Rules** | |
 | `class-method-definition-format` | Consistent spacing in class/method definitions: space before `{`, no space before `(` 🔧 |
 | `class-naming-convention` | Class declarations must end with "Class" suffix (e.g., `ApiServiceClass`) 🔧 |
@@ -321,12 +324,13 @@ rules: {
 | `hook-deps-per-line` | Collapse deps ≤ threshold to one line; expand larger arrays with each dep on own line (default: >2) 🔧 ⚙️ |
 | `use-state-naming-convention` | Boolean useState variables must start with is/has/with/without prefix 🔧 ⚙️ |
 | **Import/Export Rules** | |
-| `absolute-imports-only` | Use alias imports from index files only (not deep paths), no relative imports (default: `@/`) ⚙️ |
+| `absolute-imports-only` | Use alias imports from index files only (not deep paths), no relative imports; files within the same module folder must use relative imports — auto-fixes absolute imports to relative (default: `@/`) 🔧 ⚙️ |
 | `export-format` | `export {` on same line; collapse ≤ threshold to one line; expand larger with each specifier on own line (default: ≤3) 🔧 ⚙️ |
 | `import-format` | `import {` and `} from` on same line; collapse ≤ threshold; expand larger with each specifier on own line (default: ≤3) 🔧 ⚙️ |
 | `import-source-spacing` | No leading/trailing spaces inside import path quotes 🔧 |
 | `index-export-style` | Index files: no blank lines, enforce shorthand or import-export style; Regular files: require blank lines between exports (default: shorthand) 🔧 ⚙️ |
 | `index-exports-only` | Index files should only contain imports and re-exports, not code definitions (types, functions, variables, classes) |
+| `inline-export-declaration` | Enforce inline export declarations instead of grouped export statements in non-index files 🔧 ⚙️ |
 | `module-index-exports` | Index files must export all folder contents (files and subfolders) ⚙️ |
 | **JSX Rules** | |
 | `classname-dynamic-at-end` | Dynamic expressions (`${className}`) must be at the end of class strings (JSX and variables) 🔧 |
@@ -1812,13 +1816,14 @@ const [error, setError] = useState<boolean>(false);
 
 ### `absolute-imports-only`
 
-**What it does:** Enforces importing from folder index files using absolute paths (aliases like `@/`) instead of relative paths or deep file imports.
+**What it does:** Enforces importing from folder index files using absolute paths (aliases like `@/`) instead of relative paths or deep file imports. Files within the same module folder must use relative imports (`./` or `../`) instead of absolute paths to avoid circular dependencies through the index file. Auto-fixes absolute imports to own module folder into relative paths. 🔧
 
 **Why use it:**
 - Absolute imports are cleaner than `../../../components`
 - Index imports create a public API for each folder
 - Refactoring file locations doesn't break imports
 - Encourages proper module organization
+- Relative imports within the same module folder avoid circular dependencies
 
 ```javascript
 // ✅ Good — import from index files using alias
@@ -1830,7 +1835,20 @@ import { formatDate } from "@/utils";
 // ✅ Good — assets allow deep imports by default
 import logo from "@/assets/images/logo.png";
 
-// ❌ Bad — relative imports
+// ✅ Good — relative import within the same module folder (siblings)
+// File: utils/formatters.js
+import { isNumber } from "./validators";
+
+// ✅ Good — relative import within the same module folder (nested)
+// File: data/auth/forget-password/index.ts
+import { guestLoginData } from "../../login/guest";
+
+// ❌ Bad — absolute import to own module folder (should use relative)
+// File: data/auth/forget-password/index.ts
+import { guestLoginData } from "@/data";
+// → use relative import instead: import { guestLoginData } from "../../login/guest";
+
+// ❌ Bad — relative imports across different folders
 import { Button } from "../../components";
 import { useAuth } from "../../../hooks";
 
@@ -2084,6 +2102,46 @@ export function helper() { ... }                      // Move to utils.ts
 
 ---
 
+### `inline-export-declaration`
+
+**What it does:** Enforces that exports are declared inline with the declaration (`export const`, `export function`) instead of using grouped export statements (`export { ... }`). Auto-fixable: adds `export` to each declaration and removes the grouped export statement.
+
+**Why use it:** Inline exports make it immediately clear which declarations are public. Grouped exports at the bottom of a file require scrolling to discover what's exported, and they can become stale or inconsistent with the actual declarations.
+
+**Important exceptions:**
+- **Index files** (barrel re-exports) are skipped entirely -- they should use grouped/re-export syntax
+- **Aliased exports** (`export { a as b }`) are skipped since they cannot be expressed as inline exports
+
+```javascript
+// ✅ Good — inline export declarations
+export const strings = {
+    title: "Hello",
+    subtitle: "World",
+};
+
+export const MAX_RETRIES = 3;
+
+export function fetchData() {
+    return fetch("/api/data");
+}
+
+// ❌ Bad — grouped export statement
+const strings = {
+    title: "Hello",
+    subtitle: "World",
+};
+
+const MAX_RETRIES = 3;
+
+function fetchData() {
+    return fetch("/api/data");
+}
+
+export { strings, MAX_RETRIES, fetchData };
+```
+
+---
+
 ### `module-index-exports`
 
 **What it does:** Ensures module folders have index files that export all their contents, creating a proper public API for each module.
@@ -3061,65 +3119,163 @@ export const Card = ({ a, b } : { a: string, b: string }) => (
 
 ---
 
-### `folder-component-suffix`
+### `folder-based-naming-convention`
+
+**What it does:** Enforces naming conventions based on folder location, with chained folder names for nested files. Also enforces camelCase suffix for data/constants/strings/services/reducers folders (e.g., `authData`, `apiConstants`, `loginStrings`, `userServices`):
+
+| Folder | Suffix | Example |
+|--------|--------|---------|
+| `views/` | View | `DashboardView` |
+| `layouts/` | Layout | `MainLayout` |
+| `pages/` | Page | `HomePage` |
+| `providers/` | Provider | `AuthProvider` |
+| `reducers/` | Reducer | `UserReducer` |
+| `contexts/` | Context | `AuthContext` |
+| `theme/` / `themes/` | Theme | `DarkTheme` |
+| `data/` | Data (camelCase) | `authData` |
+| `constants/` | Constants (camelCase) | `apiConstants` |
+| `strings/` | Strings (camelCase) | `loginStrings` |
+| `services/` | Services (camelCase) | `userServices` |
+| `atoms/` | *(none)* | `Button` |
+| `components/` | *(none)* | `Card` |
 
-**What it does:** Enforces naming conventions for components based on folder location:
-- Components in `views/` folder must end with "View" suffix
-- Components in `pages/` folder must end with "Page" suffix
-- Components in `layouts/` folder must end with "Layout" suffix
+Nested files chain folder names (e.g., `layouts/auth/login.tsx` → `LoginAuthLayout`, `atoms/input/password.tsx` → `PasswordInput`).
 
-**Why use it:** Consistent naming based on folder structure makes component purpose immediately clear. View components, page components, and layout components have different responsibilities, and the suffix reflects this.
+**Why use it:** Consistent naming based on folder structure makes purpose immediately clear. The chained naming encodes the full path context into the name. The camelCase suffix for data/constants/strings/services/reducers folders distinguishes these utility modules from PascalCase component-like entities.
 
 ```tsx
-// ✅ Good — in views/dashboard-view.tsx
+// ✅ Good — suffix folders
+// in views/dashboard.tsx
 export const DashboardView = () => <div>Dashboard</div>;
 
-// ✅ Good — in pages/home-page.tsx
-export const HomePage = () => <div>Home</div>;
+// in layouts/auth/login.tsx (chained: Login + Auth + Layout)
+export const LoginAuthLayout = () => <div>Login</div>;
 
-// ✅ Good — in layouts/main-layout.tsx
-export const MainLayout = () => <div>Main</div>;
+// in providers/auth.tsx
+export const AuthProvider = ({ children }) => <AuthContext.Provider>{children}</AuthContext.Provider>;
 
-// ❌ Bad — in views/dashboard.tsx (missing "View" suffix)
-export const Dashboard = () => <div>Dashboard</div>;
+// in contexts/auth.ts
+export const AuthContext = createContext(null);
 
-// ❌ Bad — in pages/home.tsx (missing "Page" suffix)
-export const Home = () => <div>Home</div>;
+// in reducers/user.ts
+export const UserReducer = (state, action) => { ... };
 
-// ❌ Bad — in layouts/main.tsx (missing "Layout" suffix)
-export const Main = () => <div>Main</div>;
+// in themes/dark.ts
+export const DarkTheme = { primary: "#000" };
+
+// ✅ Good — camelCase suffix folders
+// in data/auth.ts
+export const authData = { ... };
+
+// in constants/api.ts
+export const apiConstants = { ... };
+
+// in strings/login.ts
+export const loginStrings = { ... };
+
+// in services/user.ts
+export const userServices = { ... };
+
+// ✅ Good — no-suffix folders (chaining only)
+// in atoms/input/password.tsx (chained: Password + Input)
+export const PasswordInput = () => <input type="password" />;
+
+// in atoms/button.tsx
+export const Button = () => <button>Click</button>;
+
+// in components/card.tsx
+export const Card = () => <div>Card</div>;
+
+// ❌ Bad
+// in layouts/auth/login.tsx (should be "LoginAuthLayout")
+export const Login = () => <div>Login</div>;
+
+// in reducers/user.ts (should be "UserReducer")
+export const User = (state, action) => { ... };
+
+// in atoms/input/password.tsx (should be "PasswordInput")
+export const Password = () => <input type="password" />;
+```
+
+> **Note:** Module barrel files (e.g., `views/index.ts`) are skipped. Interfaces, enums, and types have their own naming rules (`interface-format`, `enum-format`, `type-format`). Auto-fix renames the identifier and all its references.
+
+---
+
+### `folder-structure-consistency`
+
+**What it does:** Enforces that module folders have a consistent internal structure — either all flat files or all wrapped in subfolders. Wrapped mode is only justified when at least one subfolder contains 2+ files. Applies to the same folders as `module-index-exports`: atoms, components, hooks, utils, enums, types, interfaces, reducers, layouts, views, pages, and more.
+
+**Why use it:** Mixing flat files and wrapped folders in the same directory creates inconsistency. This rule ensures a uniform structure — if one item needs a folder (because it has multiple files), all items should be wrapped; if none do, keep everything flat.
+
+**Configurable options:**
+| Option | Default | Description |
+|--------|---------|-------------|
+| `moduleFolders` | Same as `module-index-exports` (atoms, components, hooks, utils, enums, types, views, layouts, pages, etc.) | Replace the entire folder list |
+| `extraModuleFolders` | `[]` | Add extra folders on top of the defaults |
+
+```
+// ✅ Good — flat mode (all direct files)
+atoms/input.tsx
+atoms/calendar.tsx
+
+// ✅ Good — wrapped mode (justified — input has multiple files)
+atoms/input/index.tsx
+atoms/input/helpers.ts
+atoms/calendar/index.tsx
+
+// ❌ Bad — mixed (some flat, some wrapped with justification)
+atoms/input.tsx              → "all items should be wrapped in folders"
+atoms/calendar/index.tsx
+atoms/calendar/helpers.ts
+
+// ❌ Bad — wrapped but unnecessary (each folder has only 1 file)
+atoms/input/index.tsx        → "use direct files instead"
+atoms/calendar/index.tsx
+
+// ❌ Bad — mixed without justification
+atoms/input.tsx
+atoms/calendar/index.tsx     → "use direct files instead"
 ```
 
+> **Note:** This rule applies equally to all module folders — component folders (atoms, components, views), data folders (enums, types, interfaces), and utility folders (hooks, utils, helpers). The `folder-based-naming-convention` naming rule is separate and enforces export naming based on folder location.
+
 ---
 
 ### `no-redundant-folder-suffix`
 
-**What it does:** Flags files whose name redundantly includes the parent (or ancestor) folder name as a suffix. Since the folder already provides context, the file name doesn't need to repeat it.
+**What it does:** Flags files and folders whose name redundantly includes the parent (or ancestor) folder name as a suffix. Since the folder already provides context, the name doesn't need to repeat it.
 
-**Why use it:** This complements `folder-component-suffix` — the *file name* should stay clean while the *exported component name* carries the suffix. For example, `layouts/main.tsx` exporting `MainLayout` is better than `layouts/main-layout.tsx` exporting `MainLayout`.
+**Why use it:** This complements `folder-based-naming-convention` — the *file name* should stay clean while the *exported component name* carries the suffix. For example, `layouts/main.tsx` exporting `MainLayout` is better than `layouts/main-layout.tsx` exporting `MainLayout`.
 
 ```
-// ✅ Good — file names don't repeat the folder name
+// ✅ Good — names don't repeat the folder name
 layouts/main.tsx           → export const MainLayout = ...
 atoms/button.tsx           → file "button" has no redundant suffix
 views/dashboard.tsx        → file "dashboard" has no redundant suffix
-hooks/use-auth.ts          → file "use-auth" has no redundant suffix
+views/access-control/...   → folder "access-control" has no redundant suffix
+atoms/input/index.tsx      → uses "index" inside folder (correct)
+
+// ❌ Bad — file name matches parent folder name (use index instead)
+atoms/input/input.tsx      → use "input/index.tsx" instead
+components/card/card.tsx   → use "card/index.tsx" instead
 
 // ❌ Bad — file names redundantly include the folder suffix
 layouts/main-layout.tsx    → redundant "-layout" (already in layouts/)
 atoms/button-atom.tsx      → redundant "-atom" (already in atoms/)
 views/dashboard-view.tsx   → redundant "-view" (already in views/)
-hooks/use-auth-hook.ts     → redundant "-hook" (already in hooks/)
 
-// Nested files are also checked against ancestor folders
+// ❌ Bad — folder names redundantly include the ancestor suffix
+views/access-control-view/ → redundant "-view" (already in views/)
+
+// Nested names are also checked against ancestor folders
 atoms/forms/input-atom.tsx → redundant "-atom" from ancestor "atoms/"
 ```
 
-> **Note:** Index files (`index.ts`, `index.js`, etc.) are skipped. Folder names are singularized automatically (e.g., `layouts` → `layout`, `categories` → `category`, `classes` → `class`).
+> **Note:** Index files (`index.ts`, `index.js`, etc.) are skipped for file name checks. Folder names are singularized automatically (e.g., `layouts` → `layout`, `categories` → `category`, `classes` → `class`).
 
 ---
 
-### `svg-component-icon-naming`
+### `svg-icon-naming-convention`
 
 **What it does:** Enforces naming conventions for SVG icon components:
 - Components that return only an SVG element must have a name ending with "Icon"
@@ -3930,7 +4086,7 @@ const UseAuth = () => {};          // hooks should be camelCase
 
 ## 🔧 Auto-fixing
 
-67 of 77 rules support auto-fixing. Run ESLint with the `--fix` flag:
+70 of 79 rules support auto-fixing. Run ESLint with the `--fix` flag:
 
 ```bash
 # Fix all files in src directory
@@ -3983,6 +4139,8 @@ Contributions are welcome! Please feel free to submit a Pull Request.
 
 This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
 
+Copyright (c) 2026 Eslint Plugin Code Style. All rights reserved. 
+
 <br />
 
 ---