@schafevormfenster/eslint-config 0.0.8 → 0.0.10

package/.turbo/turbo-check.log

@@ -0,0 +1,6 @@
+
+
+> @schafevormfenster/eslint-config@0.0.9 check /Users/jan-henrik.hempel/Projects/commons/packages/eslint-config
+> echo 'eslint-config: no build required'
+
+eslint-config: no build required

package/CONTRIBUTING.md

@@ -0,0 +1,323 @@
+# Contributing to @schafevormfenster/eslint-config
+
+Thank you for your interest in contributing to our ESLint configuration hub! This document describes the package structure, maintenance responsibilities, and how to contribute effectively.
+
+## Package Overview
+
+This package serves as the **Configuration Hub** for ESLint across the `@schafevormfenster` monorepo. It orchestrates community standards (Next.js, TypeScript, Prettier) and integrates our internal custom rules from `@schafevormfenster/eslint-plugin`.
+
+### Key Responsibilities
+
+- **Standardization**: Ensures all projects follow the same coding standards
+- **Simplification**: Bundles multiple ESLint plugins into composable configurations
+- **Modularity**: Provides pre-configured rule sets for different tech stacks
+
+## Package Structure
+
+```
+packages/eslint-config/
+├── index.js              # Default base configuration
+├── base.js               # Minimal plugin registration
+├── next.js               # Next.js + React + Hooks
+├── library.js            # Pure TypeScript libraries
+├── logging.js            # Logging standards
+├── architecture.js       # File naming and structure
+├── rest.js               # REST API patterns
+├── caching.js            # Caching strategies
+├── stack.js              # Technology choices
+├── playwright.js         # E2E testing
+├── vitest.js             # Unit testing
+├── integration.js        # Integration testing
+├── docs/
+│   └── RULES_REFERENCE.md  # Comprehensive rule documentation
+├── README.md             # Package overview and usage
+├── CONTRIBUTING.md       # This file
+└── package.json          # Dependencies and exports
+```
+
+## Modular Configuration Files
+
+Each configuration file exports a Flat Config array that can be composed in consuming applications:
+
+- **Base configurations** (`index.js`, `base.js`, `next.js`, `library.js`): Provide foundation rules from community plugins
+- **Domain configurations** (`logging.js`, `architecture.js`, `rest.js`, etc.): Add domain-specific custom rules
+- **Testing configurations** (`playwright.js`, `vitest.js`, `integration.js`): Apply testing-specific rules
+
+## Documentation Maintenance
+
+### Critical: Keeping RULES_REFERENCE.md in Sync
+
+**⚠️ IMPORTANT**: The `docs/RULES_REFERENCE.md` file contains a comprehensive mapping of all rules to their configurations. This documentation **MUST** be updated whenever rules change in `@schafevormfenster/eslint-plugin`.
+
+#### When to Update RULES_REFERENCE.md
+
+Update the reference documentation when:
+
+1. **New rules are added** to `@schafevormfenster/eslint-plugin`
+   - Add the rule to the appropriate configuration table
+   - Update rule counts if displayed
+   - Add to the "Key rules" section if significant
+
+2. **Rules are removed** from `@schafevormfenster/eslint-plugin`
+   - Remove the rule from configuration tables
+   - Update any examples that referenced the rule
+
+3. **Rule severity changes** (error ↔ warn)
+   - Update the severity column in the configuration tables
+   - Verify the change is reflected in all relevant sections
+
+4. **Rules are moved** between configurations
+   - Remove from old configuration table
+   - Add to new configuration table
+   - Update any explanatory text
+
+5. **New configurations are added** to this package
+   - Add a new section explaining the configuration's purpose
+   - Create a rule table for the configuration
+   - Add usage examples
+   - Update the configuration list in README.md
+
+#### How to Update RULES_REFERENCE.md
+
+1. **Check the source of truth**: Review `@schafevormfenster/eslint-plugin/index.js` to see the current rule definitions:
+   ```javascript
+   const loggingRules = {
+     [`${pluginName}/enforce-log-before-throw`]: "error",
+     // ... other rules
+   };
+   ```
+
+2. **Update the tables**: Locate the relevant configuration section in RULES_REFERENCE.md and update the rule table:
+   ```markdown
+   | Rule | Severity | Description |
+   |------|----------|-------------|
+   | `new-rule-name` | error | Description of what the rule does |
+   ```
+
+3. **Update counts and summaries**: If rule counts are mentioned, update them
+
+4. **Test the documentation**: Verify all links work and paths are correct
+
+5. **Cross-reference**: Ensure the README.md configuration list matches RULES_REFERENCE.md
+
+#### Automation Opportunity
+
+Currently, this synchronization is **manual**. Future improvements could include:
+- Script to extract rules from `@schafevormfenster/eslint-plugin/index.js`
+- Automated table generation
+- CI check to ensure documentation is in sync
+
+## Making Changes
+
+### Adding a New Configuration
+
+1. **Create the configuration file** (e.g., `new-domain.js`):
+   ```javascript
+   import svfPlugin from "@schafevormfenster/eslint-plugin";
+   
+   export default [
+     svfPlugin.configs.base,
+     svfPlugin.configs["new-domain"]
+   ];
+   ```
+
+2. **Add to package.json exports**:
+   ```json
+   {
+     "exports": {
+       "./new-domain": "./new-domain.js"
+     }
+   }
+   ```
+
+3. **Update README.md**: Add to the "Available Configurations" list
+
+4. **Update RULES_REFERENCE.md**:
+   - Add a new section explaining the configuration
+   - Create a rule table
+   - Add usage examples
+   - Update the Quick Navigation links
+
+### Updating Existing Configurations
+
+1. **Modify the configuration file** as needed
+
+2. **Update documentation** if:
+   - The purpose changes
+   - Files/globs change
+   - Dependencies change
+   - Usage patterns change
+
+3. **Test in a consuming app** to ensure it works correctly
+
+### Updating Dependencies
+
+When updating community plugin versions:
+
+1. **Test compatibility** with consuming applications
+2. **Update package.json** version constraints
+3. **Document breaking changes** if any
+4. **Update examples** if plugin usage changed
+
+## Development Workflow
+
+### Local Development
+
+```bash
+# This package has no build step
+cd packages/eslint-config
+
+# Check that everything is valid (no-op currently)
+pnpm run check
+
+# Test in a consuming app
+cd /path/to/consuming-app
+pnpm link ../../packages/eslint-config
+```
+
+### Testing Changes
+
+To test configuration changes:
+
+1. Make changes to configuration files
+2. Link the package to a consuming application
+3. Run the consuming app's linter: `pnpm lint`
+4. Verify rules are applied correctly
+5. Check that there are no unexpected errors
+
+### Validation Checklist
+
+Before submitting changes:
+
+- [ ] All configuration files are valid JavaScript/ESM
+- [ ] `package.json` exports are correct
+- [ ] README.md is updated with any new configurations
+- [ ] RULES_REFERENCE.md is updated (if rules changed)
+- [ ] Changes tested in at least one consuming application
+- [ ] No unintended side effects on existing configurations
+
+## Release Process
+
+1. **Make changes** to configuration files or documentation
+2. **Update RULES_REFERENCE.md** if rules changed in eslint-plugin
+3. **Test thoroughly** in consuming applications
+4. **Version bump** following semantic versioning:
+   - **Patch** (0.0.x): Documentation updates, bug fixes
+   - **Minor** (0.x.0): New configurations, new rules (backward compatible)
+   - **Major** (x.0.0): Breaking changes to existing configurations
+5. **Update changelog** if maintained
+6. **Publish** using `pnpm run release` or `../../scripts/smart-publish.sh`
+
+## Documentation Standards
+
+### README.md
+
+- Keep it concise and focused on usage
+- Link to RULES_REFERENCE.md for detailed information
+- Include basic examples
+- List all available configurations
+
+### RULES_REFERENCE.md
+
+- **Comprehensive** but **organized** - use sections and tables
+- **Accurate** - must reflect actual rule implementations
+- **Helpful** - include usage examples and guidance
+- **Up-to-date** - synchronize with eslint-plugin changes
+- **Searchable** - use clear headings and consistent terminology
+
+### Writing Style
+
+- **Clear and direct** - developers should understand quickly
+- **Example-driven** - show real usage patterns
+- **Consistent** - use the same terminology across all documentation
+- **Accessible** - explain concepts, don't assume knowledge
+
+## Relationship with @schafevormfenster/eslint-plugin
+
+This package **re-exports** configurations from `@schafevormfenster/eslint-plugin`. Understanding this relationship is crucial:
+
+### Dependency Flow
+
+```
+@schafevormfenster/eslint-plugin
+    ↓ (defines rules and base configs)
+@schafevormfenster/eslint-config
+    ↓ (composes configs with community plugins)
+Consuming Applications
+```
+
+### When Changes Happen in eslint-plugin
+
+If `@schafevormfenster/eslint-plugin` changes:
+
+1. **New rules added**: Update RULES_REFERENCE.md tables
+2. **Rules removed**: Update RULES_REFERENCE.md tables
+3. **Severity changed**: Update RULES_REFERENCE.md tables
+4. **New config added**: Consider adding a new file here that exposes it
+5. **Breaking changes**: May require a major version bump here too
+
+### Staying in Sync
+
+- Monitor changes to `@schafevormfenster/eslint-plugin`
+- Review the plugin's changelog/commits regularly
+- Update documentation proactively
+- Test compatibility when plugin version updates
+
+## Common Tasks
+
+### Task: Add a New Configuration
+
+```bash
+# 1. Create the config file
+echo 'import svfPlugin from "@schafevormfenster/eslint-plugin";\n\nexport default [\n  svfPlugin.configs.base,\n  svfPlugin.configs["your-domain"]\n];' > your-domain.js
+
+# 2. Add to package.json exports (manual edit required)
+
+# 3. Update README.md (manual edit required)
+
+# 4. Update RULES_REFERENCE.md (manual edit required)
+
+# 5. Test in a consuming app
+```
+
+### Task: Sync with eslint-plugin Rule Changes
+
+```bash
+# 1. Check what changed in eslint-plugin
+cd ../eslint-plugin
+git log --oneline -10
+git diff HEAD~5 index.js  # or appropriate commit range
+
+# 2. Note the changes to rules (added, removed, severity changed)
+
+# 3. Update RULES_REFERENCE.md in eslint-config
+cd ../eslint-config
+vim docs/RULES_REFERENCE.md  # Update the relevant tables
+
+# 4. Verify accuracy
+grep "your-rule-name" docs/RULES_REFERENCE.md
+```
+
+### Task: Update Documentation Only
+
+```bash
+# Edit the documentation
+vim docs/RULES_REFERENCE.md
+# or
+vim README.md
+
+# No build step needed - documentation is ready to commit
+git add docs/RULES_REFERENCE.md README.md
+git commit -m "docs: update rule reference for X"
+```
+
+## Questions and Support
+
+- **For rule behavior**: See `@schafevormfenster/eslint-plugin` documentation
+- **For configuration usage**: See README.md and RULES_REFERENCE.md
+- **For contributing**: This file and the main repository CONTRIBUTING.md
+- **For architecture questions**: Consult with the platform team
+
+## Code of Conduct
+
+Please be respectful and constructive in all interactions. We're building tools to help our team write better code together.

package/README.md

@@ -8,6 +8,16 @@ This package serves as the central **Configuration Hub** for ESLint across the `
 - **Simplicity**: Projects only need to install this one package instead of managing dozens of ESLint plugins and dependencies.
 - **Modularity**: Provides composable configurations for different tech stacks (Next.js, Library, Playwright, etc.).
 
+## Documentation
+
+> **For detailed rule documentation, usage examples, and offline access patterns**, see [**RULES_REFERENCE.md**](docs/RULES_REFERENCE.md) or the [@schafevormfenster/eslint-plugin documentation](https://www.npmjs.com/package/@schafevormfenster/eslint-plugin).
+
+The RULES_REFERENCE guide includes:
+- Complete mapping of all rules by configuration
+- Path patterns to find documentation in node_modules (for offline/isolated environments)
+- Detailed explanations of when and how to use each modular config
+- Guidance for AI coding agents on referencing documentation
+
 ## General Approach
 
 This package exports **Flat Config** arrays that can be easily combined in your project's `eslint.config.mjs`. It wraps:
@@ -45,7 +55,10 @@ export default defineConfig([
 
 ### Available Configurations
 
+> For detailed information about each configuration's purpose, rules, and when to use them, see [RULES_REFERENCE.md](docs/RULES_REFERENCE.md).
+
 - **`@schafevormfenster/eslint-config`** (default): Base TypeScript & Node.js rules.
+- **`@schafevormfenster/eslint-config/base`**: Minimal plugin registration only (advanced usage).
 - **`@schafevormfenster/eslint-config/next`**: For Next.js applications (includes React & Hooks).
 - **`@schafevormfenster/eslint-config/library`**: For pure TypeScript libraries.
 - **`@schafevormfenster/eslint-config/logging`**: Enforces internal logging standards.
@@ -55,3 +68,4 @@ export default defineConfig([
 - **`@schafevormfenster/eslint-config/stack`**: Enforces tech stack constraints (e.g. forbidden imports).
 - **`@schafevormfenster/eslint-config/playwright`**: For E2E test suites.
 - **`@schafevormfenster/eslint-config/vitest`**: For Unit test suites.
+- **`@schafevormfenster/eslint-config/integration`**: For Integration test suites.

package/docs/RULES_REFERENCE.md

@@ -0,0 +1,418 @@
+# ESLint Rules Reference
+
+This document provides a comprehensive reference for all ESLint configurations available in `@schafevormfenster/eslint-config`, including how to find detailed rule documentation both online and offline.
+
+## Quick Navigation
+
+- [Finding Rule Documentation](#finding-rule-documentation)
+- [Modular Configurations](#modular-configurations)
+- [Rules by Configuration](#rules-by-configuration)
+- [Usage Examples](#usage-examples)
+
+## Finding Rule Documentation
+
+### Online Documentation
+
+For the most up-to-date documentation of custom rules, visit:
+- **npm package**: https://www.npmjs.com/package/@schafevormfenster/eslint-plugin
+- **GitHub repository**: https://github.com/schafe-vorm-fenster/commons/tree/main/packages/eslint-plugin
+
+### Offline/Local Documentation
+
+When working in isolated or offline environments, you can find rule documentation in your `node_modules`:
+
+```bash
+# Custom rules documentation (from @schafevormfenster/eslint-plugin)
+node_modules/.pnpm/@schafevormfenster+eslint-plugin@*/node_modules/@schafevormfenster/eslint-plugin/docs/rules/
+
+# If using npm or yarn instead of pnpm
+node_modules/@schafevormfenster/eslint-plugin/docs/rules/
+
+# Example: View documentation for a specific rule
+cat node_modules/@schafevormfenster/eslint-plugin/docs/rules/enforce-log-before-throw.md
+```
+
+### Documentation Structure in node_modules
+
+```
+@schafevormfenster/eslint-plugin/
+├── docs/
+│   ├── instructions/          # Coding guidelines and best practices
+│   │   ├── logging-guide.md
+│   │   ├── rest-service-design-guide.md
+│   │   ├── caching-guide.md
+│   │   ├── testing-standards-guide.md
+│   │   └── ...
+│   └── rules/                 # Individual rule documentation
+│       ├── enforce-log-before-throw.md
+│       ├── no-sensitive-log-keys.md
+│       ├── enforce-api-route-structure.md
+│       └── ...
+└── README.md                  # Full overview and rule catalog
+```
+
+## Modular Configurations
+
+`@schafevormfenster/eslint-config` provides several modular configurations that you can mix and match based on your project's needs.
+
+### Base Configurations
+
+#### `@schafevormfenster/eslint-config` (default)
+**Purpose**: Base TypeScript and Node.js rules for all projects  
+**Includes**: TypeScript ESLint, import ordering, SonarJS code quality, Unicorn best practices, Zod schema validation  
+**Use when**: Setting up any TypeScript project in the monorepo
+
+#### `@schafevormfenster/eslint-config/base`
+**Purpose**: Minimal base configuration that only registers the custom plugin  
+**Includes**: Only the plugin registration from `@schafevormfenster/eslint-plugin`  
+**Use when**: You want to manually configure rules without any presets (advanced usage)
+
+#### `@schafevormfenster/eslint-config/library`
+**Purpose**: Configuration for pure TypeScript libraries (non-UI packages)  
+**Includes**: Base config plus library-specific rules  
+**Use when**: Building reusable npm packages without UI components
+
+#### `@schafevormfenster/eslint-config/next`
+**Purpose**: Configuration for Next.js applications  
+**Includes**: Base config + Next.js rules + React + React Hooks  
+**Use when**: Building Next.js web applications
+
+### Domain-Specific Configurations
+
+These configurations enforce domain-specific patterns and are designed to be used **alongside** base configurations.
+
+#### `@schafevormfenster/eslint-config/logging`
+**Purpose**: Enforces structured logging standards with Pino  
+**Key rules**:
+- Must log before throwing errors
+- Enforce structured logging (context object + message)
+- Prevent logging sensitive data (passwords, tokens, etc.)
+- Require proper log levels
+- Use custom logger instead of console
+
+**Use when**: Your project uses the `@schafevormfenster/logging` package
+
+**Related documentation**: See `docs/instructions/logging-guide.md` in `@schafevormfenster/eslint-plugin`
+
+#### `@schafevormfenster/eslint-config/architecture`
+**Purpose**: Enforces architectural patterns and file organization  
+**Key rules**:
+- Kebab-case file naming with semantic suffixes
+- Folder structure conventions (src/app, src/clients, src/services, etc.)
+- Layer dependency rules (clients → services → coordinators)
+- One function per file
+- No re-export files
+
+**Use when**: You want to enforce consistent project structure
+
+**Related documentation**: See `docs/instructions/client-service-coordinator-guide.md` in `@schafevormfenster/eslint-plugin`
+
+#### `@schafevormfenster/eslint-config/rest`
+**Purpose**: Enforces REST API design standards  
+**Key rules**:
+- API route structure (requires route.test.ts, *.contract.ts, *.schema.ts)
+- Zod schema type exports
+- Token validation in API paths
+- Schema extension best practices
+
+**Use when**: Building REST API endpoints
+
+**Related documentation**: See `docs/instructions/rest-service-design-guide.md` in `@schafevormfenster/eslint-plugin`
+
+#### `@schafevormfenster/eslint-config/caching`
+**Purpose**: Enforces correct caching strategies  
+**Key rules**:
+- No "use cache" directive in POST handlers
+- Semantic cache headers in GET handlers
+
+**Use when**: Implementing caching in Next.js applications
+
+**Related documentation**: See `docs/instructions/caching-guide.md` in `@schafevormfenster/eslint-plugin`
+
+#### `@schafevormfenster/eslint-config/stack`
+**Purpose**: Enforces technology stack choices  
+**Key rules**:
+- Prevents use of forbidden imports (libraries with preferred alternatives)
+
+**Use when**: You want to enforce specific library choices across the project
+
+### Testing Configurations
+
+These configurations apply only to test files and should be added **after** your main configuration.
+
+#### `@schafevormfenster/eslint-config/playwright`
+**Purpose**: Configuration for Playwright E2E tests  
+**Includes**: Playwright plugin + custom E2E testing rules  
+**Key rules**:
+- Enforce `*.spec.ts` file naming for E2E tests
+- Environment variable access restrictions (APITEST_* prefix)
+- No environment variable preservation in tests
+- Require describe() wrappers for test organization
+- Enforce meaningful test descriptions
+- Suggest test categorization (Happy Path → Error → Edge Cases)
+
+**Use when**: Writing end-to-end tests with Playwright
+
+**Applies to**: `**/e2e/**`, `**/*.spec.ts` files
+
+**Related documentation**: See `docs/instructions/testing-standards-guide.md` and `docs/instructions/rest-api-e2e-testing-guide.md` in `@schafevormfenster/eslint-plugin`
+
+#### `@schafevormfenster/eslint-config/vitest`
+**Purpose**: Configuration for Vitest unit and integration tests  
+**Includes**: Vitest plugin + custom testing rules  
+**Key rules**:
+- Enforce `*.test.ts` file naming
+- Prefer loose error matching (regex over exact strings)
+- Require environment setup in beforeEach
+- No environment variable preservation
+- Require describe() wrappers for test organization
+- Enforce meaningful test descriptions
+- Suggest test categorization (Happy Path → Error → Edge Cases)
+
+**Use when**: Writing unit or integration tests with Vitest
+
+**Applies to**: `**/*.test.ts` files
+
+**Related documentation**: See `docs/instructions/testing-standards-guide.md` and `docs/instructions/unit-test-env-vars-guide.md` in `@schafevormfenster/eslint-plugin`
+
+#### `@schafevormfenster/eslint-config/integration`
+**Purpose**: Configuration for Vitest integration tests  
+**Includes**: Custom integration testing rules  
+**Key rules**:
+- Enforce `*.test.ts` file naming
+- Prefer loose error matching (regex over exact strings)
+- No environment variable preservation
+- Require environment setup in beforeEach
+- Require describe() wrappers for test organization
+- Enforce meaningful test descriptions
+- Suggest test categorization (Happy Path → Error → Edge Cases)
+
+**Use when**: Writing integration tests with Vitest (tests that involve multiple modules or external services)
+
+**Applies to**: `**/*.test.ts` files
+
+**Related documentation**: See `docs/instructions/testing-standards-guide.md` in `@schafevormfenster/eslint-plugin`
+
+## Rules by Configuration
+
+### Base Configuration Rules
+
+The base configuration includes rules from these community plugins:
+
+| Plugin | Source | Rules Count |
+|--------|--------|-------------|
+| TypeScript ESLint | `typescript-eslint` | ~50 recommended rules |
+| Import | `eslint-plugin-import` | Import ordering, dependency validation |
+| SonarJS | `eslint-plugin-sonarjs` | Code quality and complexity |
+| Unicorn | `eslint-plugin-unicorn` | Best practices and modern patterns |
+| Zod | `eslint-plugin-zod` | Zod schema validation |
+
+### Custom Rules by Domain
+
+Below is a comprehensive mapping of custom rules (from `@schafevormfenster/eslint-plugin`) to their configurations:
+
+#### Logging Rules (`@schafevormfenster/eslint-config/logging`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `enforce-log-before-throw` | error | Must log before throwing an error |
+| `enforce-log-level-before-throw` | warn | Enforce appropriate log level before throwing |
+| `prefer-custom-logger` | warn | Use custom logger instead of console |
+| `enforce-get-logger-category` | error | getLogger must be called with a category string |
+| `enforce-structured-logging` | error | Log calls must include context object + message |
+| `no-raw-logging` | warn | Prevent logging raw objects without message |
+| `require-error-in-log-error` | warn | log.error must include an error object |
+| `no-sensitive-log-keys` | error | Prevent logging sensitive keys (password, token, etc.) |
+| `no-unsafe-log-property-access` | warn | Prevent unsafe property access in log context |
+| `no-redundant-normalize-error` | error | Don't call normalizeError() in log.error() |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/enforce-log-before-throw.md` (and similar files)
+
+#### Architecture Rules (`@schafevormfenster/eslint-config/architecture`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `enforce-file-naming` | warn | Enforce kebab-case with semantic suffixes |
+| `enforce-folder-structure` | warn | Enforce src/ folder conventions |
+| `one-function-per-file` | warn | Warn if file exports multiple named functions |
+| `no-reexport-files` | warn | Prevent files that only re-export from other modules |
+| `enforce-layer-dependencies` | error | Enforce architectural layer dependency rules |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/enforce-file-naming.md` (and similar files)
+
+#### REST Rules (`@schafevormfenster/eslint-config/rest`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `enforce-api-route-structure` | error | Require route.test.ts, *.contract.ts, *.schema.ts for API routes |
+| `enforce-schema-type-export` | error | Export TypeScript types for all Zod schemas |
+| `prefer-schema-extension` | warn | Reuse schemas with .extend() or .merge() |
+| `enforce-token-in-path` | error | API routes must include [token] in path or validate params.token |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/enforce-api-route-structure.md` (and similar files)
+
+#### Caching Rules (`@schafevormfenster/eslint-config/caching`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `no-use-cache-in-post` | error | Forbid "use cache" directive in POST handlers |
+| `enforce-semantic-cache-headers` | warn | Ensure Cache-Control header in GET handlers |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/no-use-cache-in-post.md` (and similar files)
+
+#### Stack Rules (`@schafevormfenster/eslint-config/stack`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `no-forbidden-imports` | warn | Forbid libraries with preferred alternatives |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/no-forbidden-imports.md`
+
+#### Testing Rules (E2E - `@schafevormfenster/eslint-config/playwright`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `enforce-apitest-env-vars` | error | Require APITEST_* prefix for env vars in E2E tests |
+| `enforce-test-file-naming` | error | Enforce *.spec.ts for Playwright tests |
+| `no-env-preservation-in-tests` | error | Forbid preserving/restoring process.env in tests |
+| `require-describe-wrapper` | warn | Require test cases to be wrapped in describe() blocks |
+| `require-meaningful-descriptions` | warn | Require meaningful descriptions (min 10 chars for describe, 15 for it/test) |
+| `suggest-test-categorization` | warn | Suggest organizing tests into categories (Happy Path → Error → Edge Cases) |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/enforce-apitest-env-vars.md` (and similar files)
+
+#### Testing Rules (Unit/Integration - `@schafevormfenster/eslint-config/vitest`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `prefer-loose-error-matching` | warn | Prefer regex over exact string matching for errors |
+| `enforce-test-file-naming` | error | Enforce *.test.ts for Vitest tests |
+| `no-env-preservation-in-tests` | error | Forbid preserving/restoring process.env in tests |
+| `require-env-setup-in-tests` | warn | Require beforeEach to initialize env vars |
+| `require-describe-wrapper` | warn | Require test cases to be wrapped in describe() blocks |
+| `require-meaningful-descriptions` | warn | Require meaningful descriptions (min 10 chars for describe, 15 for it/test) |
+| `suggest-test-categorization` | warn | Suggest organizing tests into categories (Happy Path → Error → Edge Cases) |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/prefer-loose-error-matching.md` (and similar files)
+
+#### Testing Rules (Integration - `@schafevormfenster/eslint-config/integration`)
+
+| Rule | Severity | Description |
+|------|----------|-------------|
+| `prefer-loose-error-matching` | warn | Prefer regex over exact string matching for errors |
+| `enforce-test-file-naming` | error | Enforce *.test.ts for integration tests |
+| `no-env-preservation-in-tests` | error | Forbid preserving/restoring process.env in tests |
+| `require-env-setup-in-tests` | warn | Require beforeEach to initialize env vars |
+| `require-describe-wrapper` | warn | Require test cases to be wrapped in describe() blocks |
+| `require-meaningful-descriptions` | warn | Require meaningful descriptions (min 10 chars for describe, 15 for it/test) |
+| `suggest-test-categorization` | warn | Suggest organizing tests into categories (Happy Path → Error → Edge Cases) |
+
+**Documentation**: See `node_modules/@schafevormfenster/eslint-plugin/docs/rules/prefer-loose-error-matching.md` (and similar files)
+
+## Usage Examples
+
+### Basic Next.js Application
+
+```javascript
+// eslint.config.mjs
+import { defineConfig } from "eslint/config";
+import svfNext from "@schafevormfenster/eslint-config/next";
+import svfLogging from "@schafevormfenster/eslint-config/logging";
+import svfPlaywright from "@schafevormfenster/eslint-config/playwright";
+
+export default defineConfig([
+  ...svfNext,
+  ...svfLogging,
+  ...svfPlaywright,
+]);
+```
+
+### REST API with Full Stack
+
+```javascript
+// eslint.config.mjs
+import { defineConfig } from "eslint/config";
+import svfNext from "@schafevormfenster/eslint-config/next";
+import svfLogging from "@schafevormfenster/eslint-config/logging";
+import svfArchitecture from "@schafevormfenster/eslint-config/architecture";
+import svfRest from "@schafevormfenster/eslint-config/rest";
+import svfCaching from "@schafevormfenster/eslint-config/caching";
+import svfStack from "@schafevormfenster/eslint-config/stack";
+import svfPlaywright from "@schafevormfenster/eslint-config/playwright";
+import svfVitest from "@schafevormfenster/eslint-config/vitest";
+
+export default defineConfig([
+  // Base stack
+  ...svfNext,
+  
+  // Domain rules
+  ...svfLogging,
+  ...svfArchitecture,
+  ...svfRest,
+  ...svfCaching,
+  ...svfStack,
+  
+  // Testing rules
+  ...svfPlaywright,
+  ...svfVitest,
+]);
+```
+
+### Pure TypeScript Library
+
+```javascript
+// eslint.config.mjs
+import { defineConfig } from "eslint/config";
+import svfLibrary from "@schafevormfenster/eslint-config/library";
+import svfLogging from "@schafevormfenster/eslint-config/logging";
+import svfVitest from "@schafevormfenster/eslint-config/vitest";
+
+export default defineConfig([
+  ...svfLibrary,
+  ...svfLogging,
+  ...svfVitest,
+]);
+```
+
+## Guidance for AI Coding Agents
+
+### When to Reference Documentation
+
+1. **Before implementing logging**: Read `docs/instructions/logging-guide.md` in `@schafevormfenster/eslint-plugin`
+2. **Before creating REST APIs**: Read `docs/instructions/rest-service-design-guide.md` in `@schafevormfenster/eslint-plugin`
+3. **Before implementing caching**: Read `docs/instructions/caching-guide.md` in `@schafevormfenster/eslint-plugin`
+4. **When ESLint errors occur**: Check the specific rule documentation in `docs/rules/` to understand the requirement
+
+### Finding Documentation Programmatically
+
+```bash
+# List all available instruction guides
+ls node_modules/@schafevormfenster/eslint-plugin/docs/instructions/
+
+# List all rule documentation
+ls node_modules/@schafevormfenster/eslint-plugin/docs/rules/
+
+# Search for specific topics
+grep -r "structured logging" node_modules/@schafevormfenster/eslint-plugin/docs/
+```
+
+### Best Practices
+
+1. **Check AGENTS.md first**: Projects using these configs should have an `AGENTS.md` file in their root that references these documentation files
+2. **Read instruction guides proactively**: Don't wait for ESLint errors - read the relevant instruction guide before writing code
+3. **Use offline docs when needed**: In isolated environments, always use the node_modules paths to access documentation
+4. **Reference rule docs for fixes**: When you encounter an ESLint error, read the specific rule documentation to understand the correct pattern
+
+## Version Compatibility
+
+- `@schafevormfenster/eslint-config` requires ESLint 9+ (Flat Config)
+- All rules assume TypeScript 5+
+- Next.js configurations require Next.js 14+
+- Testing configurations work with Vitest 1+ and Playwright 1.40+
+
+## See Also
+
+- Main package README: [`packages/eslint-config/README.md`](../README.md)
+- Plugin documentation: https://www.npmjs.com/package/@schafevormfenster/eslint-plugin
+- Coding guidelines: `node_modules/@schafevormfenster/eslint-plugin/docs/instructions/`
+- Rule catalog: `node_modules/@schafevormfenster/eslint-plugin/docs/rules/`

package/integration.js

@@ -1,6 +1,7 @@
 import svfPlugin from "@schafevormfenster/eslint-plugin";
 
 export default [
+  svfPlugin.configs.base,
   {
     files: ["**/*.test.ts", "**/*.spec.ts"],
     ...svfPlugin.configs["testing-integration"]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@schafevormfenster/eslint-config",
-  "version": "0.0.8",
+  "version": "0.0.10",
   "publishConfig": {
     "access": "public"
   },
@@ -37,10 +37,13 @@
     "eslint-plugin-zod": "^1.4.0",
     "globals": "^16.5.0",
     "typescript-eslint": "^8.51.0",
-    "@schafevormfenster/eslint-plugin": "0.0.8"
+    "@schafevormfenster/eslint-plugin": "0.0.11"
   },
   "engines": {
     "node": ">=22"
   },
-  "scripts": {}
+  "scripts": {
+    "check": "echo 'eslint-config: no build required'",
+    "release": "../../scripts/smart-publish.sh"
+  }
 }

package/vitest.js

@@ -1,6 +1,8 @@
 import vitest from "eslint-plugin-vitest";
+import svfPlugin from "@schafevormfenster/eslint-plugin";
 
 export default [
+  svfPlugin.configs.base,
   {
     files: ["**/*.test.ts", "**/*.spec.ts"],
     plugins: {
@@ -13,5 +15,9 @@ export default [
       // Disable deep nesting rule for test files - describe/it nesting is organizational, not functional
       "sonarjs/no-nested-functions": "off"
     }
+  },
+  {
+    files: ["**/*.test.ts", "**/*.spec.ts"],
+    ...svfPlugin.configs["testing-unit"]
   }
 ];