Merge pull request #6044 from redis/release/3.6.0

merge release/3.6.0 to latest

Author: dantovska

.agents/skills

@@ -0,0 +1 @@
+../.ai/skills

.ai/README.md

@@ -7,36 +7,35 @@ This directory contains the **single source of truth** for AI-assisted developme
 This repository uses a centralized approach to AI development rules:
 
 - **`AGENTS.md`** (at repository root) - Entry point for AI agents with essential commands, testing instructions, and quick reference
-- **`.ai/rules/`** - Detailed development standards organized by topic
-- **`.ai/skills/`** - Agent skills (local and from npm packages)
+- **`.ai/skills/`** - Detailed development standards as skills, plus skills from npm packages
 - **`.ai/commands/`** - AI workflow commands and templates
 
-These rules are used by multiple AI coding assistants:
+These standards are consumed by:
 
-- **Cursor** (via symlinks: `.cursor/rules/` and `.cursor/commands/`)
-- **Augment** (via symlink: `.augment/`)
-- **Windsurf** (via symlink: `.windsurfrules`)
-- **GitHub Copilot** (via file: `.github/copilot-instructions.md`)
+- **Claude Code** (via `CLAUDE.md -> AGENTS.md` plus `.claude/commands/` and `.claude/skills/` symlinks)
+- **Codex** (via `AGENTS.md` and the `.agents/skills` symlink)
+- **GitHub Copilot** (via file: `.github/copilot-instructions.md`, optional)
 
 ## Structure
 
 ```
 AGENTS.md                              # 🎯 AI agent entry point
+CLAUDE.md -> AGENTS.md                 # Claude Code entry point
 .ai/                                   # Single source of truth
 ├── README.md                          # This file (human-readable overview)
-├── rules/                             # Development standards (modular)
-│   ├── code-quality.md                # Linting, TypeScript standards
-│   ├── frontend.md                    # React, Redux, UI patterns
-│   ├── backend.md                     # NestJS, API patterns
-│   ├── testing.md                     # Testing standards
-│   ├── branches.md                    # Branch naming conventions
-│   ├── commits.md                     # Commit message guidelines
-│   └── pull-requests.md               # Pull request process
-├── skills/                            # Agent skills
-│   ├── branches/                      # Branch naming skill
-│   ├── commits/                       # Commit message skill
-│   ├── pull-requests/                 # Pull request skill
-|   └── feature-flags/SKILL.md         # Feature flag lifecycle
+├── skills/                            # Development standards and agent skills
+│   ├── code-quality/SKILL.md          # Linting, TypeScript standards, naming, imports
+│   ├── frontend/SKILL.md              # React, Redux, styled-components, UI patterns
+│   ├── backend/SKILL.md               # NestJS, API patterns, DI, error handling
+│   ├── testing/SKILL.md               # Jest/Testing Library standards, faker, helpers
+│   ├── e2e-testing/SKILL.md           # Playwright standards, page objects, fixtures
+│   ├── git-safety/SKILL.md            # Protected-branch guardrails
+│   ├── branches/SKILL.md              # Branch naming
+│   ├── commits/SKILL.md               # Commit messages (Conventional Commits)
+│   ├── pull-requests/SKILL.md         # Pull request process
+│   ├── feature-flags/SKILL.md         # Feature flag lifecycle
+│   ├── tsconfigs/SKILL.md             # TypeScript configuration
+│   ├── type-check-baselines/SKILL.md  # TS error baseline workflow
 │   └── redis-ui-components/ -> node_modules/@redis-ui/components/skills/redis-ui-components
 │       ├── SKILL.md                   # Component catalog and usage patterns
 │       └── references/                # Per-component API docs (Button, Select, etc.)
@@ -45,16 +44,17 @@ AGENTS.md                              # 🎯 AI agent entry point
     ├── commit-message.md              # Commit message generation
     └── pull-request-review.md         # PR review workflow
 
-# Symlinks (all AI tools read from .ai/)
-.cursor/
-  ├── rules/ -> ../.ai/rules/          # Cursor AI (rules)
-  ├── commands/ -> ../.ai/commands/    # Cursor AI (commands)
-  └── skills/ -> ../.ai/skills/        # Cursor AI (skills)
-.augment/ -> .ai/                      # Augment AI
-.windsurfrules -> .ai/                 # Windsurf AI
-.github/copilot-instructions.md        # GitHub Copilot
+# Symlinks
+.claude/
+  ├── commands/ -> ../.ai/commands/    # Claude Code (commands)
+  └── skills/ -> ../.ai/skills/        # Claude Code (skills)
+.agents/
+  └── skills -> ../.ai/skills          # Codex (skills)
+.github/copilot-instructions.md        # GitHub Copilot reference (if used)
 ```
 
+**Codex note**: Codex reads `AGENTS.md` for project instructions and discovers repo skills from `.agents/skills`. Do not create `.codex/rules/`: Codex `.rules` files are command execution policies, not Markdown development guidelines.
+
 ## For AI Agents
 
 **Start here**: Read `AGENTS.md` at the repository root for:
@@ -65,20 +65,23 @@ AGENTS.md                              # 🎯 AI agent entry point
 - Git workflow guidelines
 - Boundaries and best practices
 
-**Then refer to**: `.ai/rules/` for detailed guidelines on specific topics.
+**Then refer to**: `.ai/skills/` for detailed guidelines on specific topics.
 
 ## For Human Developers
 
-This directory contains comprehensive development standards that are automatically used by AI coding assistants. The rules are organized into modular files for easy maintenance:
-
-- **Code Quality Standards**: `.ai/rules/code-quality.md` - TypeScript standards, import organization, best practices
-- **Frontend Patterns**: `.ai/rules/frontend.md` - React, Redux, styled-components, UI component usage
-- **Backend Patterns**: `.ai/rules/backend.md` - NestJS, dependency injection, API patterns
-- **Testing Standards**: `.ai/rules/testing.md` - Testing patterns, faker usage, test helpers
-- **Branch Naming**: `.ai/rules/branches.md` - Branch naming conventions
-- **Commit Messages**: `.ai/rules/commits.md` - Commit message guidelines (Conventional Commits)
-- **Pull Request Process**: `.ai/rules/pull-requests.md` - PR creation and review guidelines
+This directory contains comprehensive development standards used by AI coding assistants. Each topic lives in its own skill folder:
+
+- **Code Quality**: `.ai/skills/code-quality/SKILL.md` - TypeScript standards, import organization, best practices
+- **Frontend**: `.ai/skills/frontend/SKILL.md` - React, Redux, styled-components, UI component usage
+- **Backend**: `.ai/skills/backend/SKILL.md` - NestJS, dependency injection, API patterns
+- **Testing**: `.ai/skills/testing/SKILL.md` - Jest/Testing Library patterns, faker, helpers
+- **E2E Testing**: `.ai/skills/e2e-testing/SKILL.md` - Playwright standards, page objects
+- **Git Safety**: `.ai/skills/git-safety/SKILL.md` - Protected-branch guardrails
+- **Branches**: `.ai/skills/branches/SKILL.md` - Branch naming conventions
+- **Commits**: `.ai/skills/commits/SKILL.md` - Commit message guidelines (Conventional Commits)
+- **Pull Requests**: `.ai/skills/pull-requests/SKILL.md` - PR creation and review guidelines
 - **Feature Flags**: `.ai/skills/feature-flags/SKILL.md` - Adding, promoting, and removing feature flags
+- **TS Error Baselines**: `.ai/skills/type-check-baselines/SKILL.md` - TypeScript error baseline workflow
 - **Redis UI Components**: `.ai/skills/redis-ui-components/` - Component API references, props, and usage examples (sourced from `@redis-ui/components` npm package via symlink)
 
 ## MCP (Model Context Protocol) Setup
@@ -137,11 +140,11 @@ The `mcp.json` file configures these services:
 
 ## Updating These Rules
 
-To update AI rules:
+To update AI standards:
 
-1. **Edit files in `.ai/` only** (never edit symlinked files directly)
-2. **Update `AGENTS.md`** if you change commands, testing instructions, or boundaries
-3. Changes automatically propagate to all AI tools via symlinks
+1. **Edit `SKILL.md` files under `.ai/skills/`** (never edit symlinked files directly)
+2. **Update `AGENTS.md`** if you change commands, testing instructions, or the always-on rules block
+3. Changes propagate to Claude Code automatically via the `.claude/` symlinks
 4. Commit changes to version control
 
 **Remember**: These rules exist to maintain code quality and consistency. Follow them, but also use good judgment.

.ai/commands/e2e-fix.md

@@ -7,7 +7,7 @@ argument-hint: <test-pattern>
 
 Run E2E tests matching a pattern, analyze failures, and fix them.
 
-**Follow all standards in `.ai/rules/e2e-testing.md`**
+**Follow all standards in `.ai/skills/e2e-testing/SKILL.md`**
 
 ## Input
 

.ai/commands/e2e-generate.md

@@ -7,7 +7,7 @@ argument-hint: <ticket-id or ticket-url>
 
 Use Playwright MCP to explore a page, discover testable functionality, and generate E2E tests based on a Jira ticket.
 
-**Follow all standards in `.ai/rules/e2e-testing.md`**
+**Follow all standards in `.ai/skills/e2e-testing/SKILL.md`**
 
 **Reference:** @tests/e2e-playwright/TEST_PLAN.md
 
@@ -73,11 +73,11 @@ Run only the new tests using list reporter (no HTML report):
 
 ```bash
 cd tests/e2e-playwright
-npx playwright test tests/main/{feature}/{action}/ --project=chromium --reporter=list
+npx playwright test tests/parallel/{feature}/{action}/ --project=chromium-parallel --reporter=list
 npm run lint && npx tsc --noEmit
 ```
 
-**Note:** Use `--reporter=list` to avoid Playwright generating and hosting an HTML report. Use `--project=chromium` to run only browser tests (faster feedback).
+**Note:** Use `--reporter=list` to avoid Playwright generating and hosting an HTML report. Use `--project=chromium-parallel` to run only browser tests (faster feedback).
 
 ### Step 7: Update Test Plan
 

.ai/commands/pr-plan.md

@@ -307,8 +307,8 @@ After saving the plan document:
 - **ALWAYS save the plan document** - use `write` tool to save to `docs/pr-plan-{ticket-id}-{brief-description}.md`
 - **Use main branch as baseline** - all analysis should be against current main
 - **Be specific and actionable** - every task should be clear and verifiable
-- **Consider PR stacking** - plan for small, reviewable PRs (see `.ai/rules/pull-requests.md`). plan breaking the implementation in a stack of PRs.
-- **Follow all project standards** - reference rules in `.ai/rules/`
+- **Consider PR stacking** - plan for small, reviewable PRs (see `.ai/skills/pull-requests/SKILL.md`). plan breaking the implementation in a stack of PRs.
+- **Follow all project standards** - reference skills in `.ai/skills/`
 - **Document assumptions** - if anything is unclear, document the assumption made
 - **Identify blockers early** - surface dependencies and knowledge gaps upfront
 

.ai/rules/backend.md .ai/skills/backend/SKILL.md.ai/rules/backend.md renamed to .ai/skills/backend/SKILL.md

@@ -1,9 +1,15 @@
 ---
-description: NestJS backend development patterns, module structure, services, controllers, DTOs, and error handling
-globs: redisinsight/api/**/*.ts
-alwaysApply: false
+name: backend
+description: >-
+  NestJS backend development patterns for the RedisInsight API:
+  module structure, services, controllers, DTOs, dependency injection,
+  and error handling. Use when editing any file under
+  redisinsight/api/**, writing or modifying NestJS modules,
+  controllers, services, DTOs, providers, or when the user mentions
+  the backend, API, or NestJS.
 ---
 
+
 # Backend Development (NestJS/API)
 
 ## Module Structure
@@ -72,7 +78,7 @@ export const FEATURE_ERROR_MESSAGES = {
 
 1. Node.js built-in modules
 2. External dependencies (`@nestjs/*`, etc.)
-3. Internal modules (using `apiSrc/*` alias)
+3. Internal modules (using `src/*` alias — the backend's self-reference into `redisinsight/api/src/*`)
 4. Local relative imports
 
 ## Service Layer
@@ -192,7 +198,7 @@ this.logger.error('Error message', error.stack, { context })
 
 ### Redis Service Pattern
 
-- Use RedisClient from `apiSrc/modules/redis`
+- Use RedisClient from `src/modules/redis`
 - Handle errors gracefully
 - Log Redis operations
 - Use try-catch for error handling

.ai/skills/branches/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: branches
 description: >-
-  Create and name git branches following project conventions and GitHub Actions
-  enforcement rules. Use when creating branches, checking out new branches, or
-  the user mentions branch naming.
+  Create and name git branches following project conventions. Use when
+  creating branches, checking out new branches, or the user mentions
+  branch naming.
 ---
 
 # Branch Naming Conventions
 
-Use lowercase kebab-case with type prefix and issue/ticket identifier. **Branch names must match GitHub Actions workflow rules** (see `.github/workflows/enforce-branch-name-rules.yml`).
+Use lowercase kebab-case with type prefix and issue/ticket identifier.
 
 ```bash
 # Pattern: <type>/<issue-ref>/<short-title>
@@ -31,7 +31,7 @@ release/v2.0.0
 ric/RI-666/custom-prefix
 ```
 
-## Allowed Branch Types (GitHub Actions Enforced)
+## Branch Types
 
 - `feature/` - New features and refactoring (affects multiple areas)
 - `bugfix/` - Bug fixes (affects multiple areas)

.ai/rules/code-quality.md .ai/skills/code-quality/SKILL.md.ai/rules/code-quality.md renamed to .ai/skills/code-quality/SKILL.md

@@ -1,7 +1,16 @@
 ---
-alwaysApply: true
+name: code-quality
+description: >-
+  Code-quality standards for RedisInsight: TypeScript strictness,
+  naming conventions (camelCase, PascalCase, UPPER_SNAKE_CASE),
+  linting rules, no `any` without reason, no `!important` in styles,
+  and constant extraction. Use when writing or refactoring any
+  TypeScript/JavaScript code in this repo, when ESLint or Prettier
+  issues come up, or when the user mentions code style, lint, naming
+  conventions, or general code quality.
 ---
 
+
 # Code Quality Standards
 
 ## Critical Rules
@@ -27,15 +36,17 @@ alwaysApply: true
 
 1. External libraries (`react`, `lodash`, etc.)
 2. Built-in Node modules (`path`, `fs` - backend only)
-3. Internal modules with aliases (`uiSrc/*`, `apiSrc/*`)
+3. Internal modules with aliases (`uiSrc/*`, `apiClient`)
 4. Sibling/parent relative imports
 5. Style imports (ALWAYS LAST)
 
 ### Module Aliases
 
-- `uiSrc/*` → `redisinsight/ui/src/*`
-- `apiSrc/*` → `redisinsight/api/src/*`
-- `desktopSrc/*` → `redisinsight/desktop/src/*`
+- `uiSrc/*` → `redisinsight/ui/src/*` (UI workspace)
+- `apiClient` → `redisinsight/api-client` (auto-generated OpenAPI types — the UI's only entry point into BE-defined shapes)
+- `desktopSrc/*` → `redisinsight/desktop/src/*` (desktop workspace)
+
+The UI workspace must not import from the backend codebase directly. Use `apiClient` for types and the existing service layer (`uiSrc/services`) for HTTP calls.
 
 ✅ **Use aliases**: `import { Button } from 'uiSrc/components/Button'`  
 ❌ **Avoid relative**: `import { Button } from '../../../ui/src/components/Button'`