@tenantegroup/ai-rules-mcp 1.1.0 → 1.2.0

package/CHANGELOG.md

@@ -7,6 +7,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [1.2.0] - 2026-07-02
+
+### Added
+- **TypeScript Clean Code Manual**: Created [03 - TypeScript Clean Code Standards.md](vault/00%20-%20Core%20Standards/03%20-%20TypeScript%20Clean%20Code%20Standards.md) in the vault's core standards.
+- **MCP Code Quality Updates**: Integrated Clean Code principles (variables, naming, functions, immutability, side-effect prevention) into [rules/nuxt/code-quality.md](rules/nuxt/code-quality.md).
+- Updated [vault/99 - Master Index.md](vault/99%20-%20Master%20Index.md) to register the new Clean Code manual.
+
+---
+
 ## [1.1.0] - 2026-07-02
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tenantegroup/ai-rules-mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Unified MCP server providing AI coding rules for Cloudflare Backend, Nuxt Frontend, Flutter Client, and dotNET MAUI stacks with smart context filtering",
   "main": "src/index.js",
   "type": "module",

package/rules/nuxt/code-quality.md

@@ -1,25 +1,23 @@
 # Code Quality Standards
 
-## TypeScript Requirements
-- Enable strict mode in `tsconfig.json`
-- Never use `any` type without justification
-- Define interfaces for all data structures
-- Use type inference where appropriate
+## TypeScript Requirements & Clean Naming
+- Enable strict mode in `tsconfig.json` (specifically check `--strictNullChecks`)
+- Never use `any` type without justification; use explicit typing or generics
+- Define interfaces or type aliases for all data structures
+- Use meaningful, pronounceable, and searchable variable/constant names (avoid magic numbers/strings)
+- Avoid mental mapping; use explicit names (e.g. `user` instead of `u`)
+- Avoid unneeded context in property definitions (e.g. `make` instead of `carMake` inside a `Car` type)
+- Use default parameters instead of short-circuiting (`||` or ternary checks)
 - Export types for reuse across services
 
-## Code Organization
-- Keep functions small and focused (single responsibility)
-- Extract complex logic into named helper functions
-- Group related functionality in services
-- Avoid deep nesting (max 3 levels recommended)
-- Use early returns to reduce nesting
-
-## Naming Conventions
-- Use camelCase for variables and functions
-- Use PascalCase for classes and types
-- Use UPPER_CASE for constants
-- Use descriptive names (avoid abbreviations)
-- Prefix boolean variables with `is`, `has`, or `should`
+## Code Organization & Functions
+- Keep functions small and focused (Single Responsibility Principle)
+- Functions should ideally take **2 or fewer arguments**; consolidate larger parameter lists into a config object and use destructuring
+- Functions should do exactly one thing and maintain a single level of abstraction
+- Never use flags (boolean parameters) in function signatures; split them into separate functions (e.g. `createTempFile` vs `createFile`)
+- Avoid side effects: do not mutate input objects or arrays; return cloned, modified copies (e.g., `[...cart, item]` instead of `cart.push(item)`)
+- Group related functionality in classes or services
+- Avoid deep nesting (max 3 levels recommended) and use early returns
 
 ## Comments and Documentation
 - Write self-documenting code when possible

package/src/index.js

@@ -275,7 +275,7 @@ class AIRulesServer {
     this.server = new Server(
       {
         name: "@tenantegroup/ai-rules-mcp",
-        version: "1.1.0",
+        version: "1.2.0",
       },
       {
         capabilities: {