Resolves: MTV-5111 | consolidate Claude.md to AGENTS.md (#2394)

avivtur · cursoragent · web-flow · commit 44bd9e308c4b · 2026-05-06T04:08:04.000Z
* Resolves: MTV-5111 | consolidate Claude.md to AGENTS.md

Signed-off-by: Aviv Turgeman &lt;aturgema@redhat.com&gt;

* Add DCO signoff requirement to commit message format

Resolves: None
Signed-off-by: Aviv Turgeman &lt;aturgema@redhat.com&gt;
Co-authored-by: Cursor &lt;cursoragent@cursor.com&gt;

---------

Signed-off-by: Aviv Turgeman &lt;aturgema@redhat.com&gt;
Co-authored-by: Cursor &lt;cursoragent@cursor.com&gt;
diff --git a/.cursor/rules/agents/developer.mdc b/.cursor/rules/agents/developer.mdc
@@ -22,7 +22,7 @@ Your approach:
 
 ## Focus Areas
 
-**Important:** For file conventions, naming, and styling details, defer to the project's **CLAUDE.md**. Do not duplicate those rules. For formatting and linting, run `npm run lint` and `npm run lint:fix`.
+**Important:** For file conventions, naming, and styling details, defer to the project's **AGENTS.md**. Do not duplicate those rules. For formatting and linting, run `npm run lint` and `npm run lint:fix`.
 
 ### 1. Code Correctness
 
@@ -179,7 +179,7 @@ Your approach:
 - Names that don't describe purpose
 - Abbreviations that aren't universally known
 - Functions doing more than one thing
-- Prefer shorter, focused functions (project hard limit is 150 lines per function per CLAUDE.md)
+- Prefer shorter, focused functions (project hard limit is 150 lines per function per AGENTS.md)
 - Nesting deeper than 3 levels (prefer early returns)
 - Magic numbers without named constants
 
diff --git a/.cursor/rules/agents/ux-reviewer.mdc b/.cursor/rules/agents/ux-reviewer.mdc
@@ -121,7 +121,7 @@ Your approach:
 - Using appropriate PatternFly components
 - Not recreating existing components
 - Consistent with OpenShift Console patterns
-- **Reference:** [PatternFly docs](https://www.patternfly.org/components) and project Coding Standards (CLAUDE.md)
+- **Reference:** [PatternFly docs](https://www.patternfly.org/components) and project Coding Standards (AGENTS.md)
 
 **Visual Consistency**
 - Using PatternFly spacing variables
diff --git a/.cursor/rules/i18n.mdc b/.cursor/rules/i18n.mdc
@@ -6,7 +6,7 @@ alwaysApply: false
 
 # i18n Guidelines (Supplement)
 
-For basic i18n usage (`useForkliftTranslation`, `ForkliftTrans`, `t` function), see **CLAUDE.md**. This rule adds detailed patterns.
+For basic i18n usage (`useForkliftTranslation`, `ForkliftTrans`, `t` function), see **AGENTS.md**. This rule adds detailed patterns.
 
 ---
 
@@ -21,7 +21,7 @@ For basic i18n usage (`useForkliftTranslation`, `ForkliftTrans`, `t` function),
 
 ## 2. Translation Utilities
 
-For the three utilities (`useForkliftTranslation`, `ForkliftTrans`, `t`) and when to use each, see **CLAUDE.md**.
+For the three utilities (`useForkliftTranslation`, `ForkliftTrans`, `t`) and when to use each, see **AGENTS.md**.
 
 ---
 
diff --git a/.cursor/rules/project-context.mdc b/.cursor/rules/project-context.mdc
@@ -5,7 +5,7 @@ alwaysApply: true
 
 # Forklift Console Plugin - Domain Context
 
-For coding standards, conventions, and development commands, see **CLAUDE.md** at the project root.
+For coding standards, conventions, and development commands, see **AGENTS.md** at the project root.
 
 This rule provides Forklift-specific domain knowledge not covered there.
 
@@ -116,11 +116,11 @@ src/
 
 ## Rule Maintenance
 
-When implementing a new feature that introduces concepts, patterns, CRDs, provider types, statuses, or conventions **not already covered** by the existing rules (this file, `CLAUDE.md`, or any file under `.cursor/rules/`), you **must** update the relevant rule file as part of the same change. Examples:
+When implementing a new feature that introduces concepts, patterns, CRDs, provider types, statuses, or conventions **not already covered** by the existing rules (this file, `AGENTS.md`, or any file under `.cursor/rules/`), you **must** update the relevant rule file as part of the same change. Examples:
 
 - New CRD or resource type -- add it to this file under **Core CRDs**.
 - New provider type or status -- add it to this file and to `agents/forklift-expert.mdc`.
-- New shared hook, utility, or component pattern -- add it to `CLAUDE.md` or the matching file-specific rule.
+- New shared hook, utility, or component pattern -- add it to `AGENTS.md` or the matching file-specific rule.
 - New testing pattern or tooling -- update `testing.mdc`.
 - New i18n utility or namespace change -- update `i18n.mdc`.
 - New workflow or development process -- add or update the relevant file under `workflows/`.
diff --git a/.cursor/rules/react-components.mdc b/.cursor/rules/react-components.mdc
@@ -6,7 +6,7 @@ alwaysApply: false
 
 # React Component Patterns (Supplement)
 
-For core React conventions (functional components, FC type, imports, hooks rules), see **CLAUDE.md**. This rule adds PatternFly and Console SDK patterns.
+For core React conventions (functional components, FC type, imports, hooks rules), see **AGENTS.md**. This rule adds PatternFly and Console SDK patterns.
 
 ---
 
diff --git a/.cursor/rules/styles.mdc b/.cursor/rules/styles.mdc
@@ -6,7 +6,7 @@ alwaysApply: false
 
 # SCSS Styling Guidelines (Supplement)
 
-For core styling conventions (SCSS preference, BEM methodology, no `!important`), see **CLAUDE.md**. This rule adds PatternFly theme variable references (version-agnostic) and layout patterns.
+For core styling conventions (SCSS preference, BEM methodology, no `!important`), see **AGENTS.md**. This rule adds PatternFly theme variable references (version-agnostic) and layout patterns.
 
 ---
 
diff --git a/.cursor/rules/testing.mdc b/.cursor/rules/testing.mdc
@@ -6,7 +6,7 @@ alwaysApply: false
 
 # Testing Guidelines (Supplement)
 
-For basic testing approach (Jest for unit, Playwright for E2E), see **CLAUDE.md**. This rule adds detailed patterns.
+For basic testing approach (Jest for unit, Playwright for E2E), see **AGENTS.md**. This rule adds detailed patterns.
 
 ---
 
diff --git a/.cursor/rules/typescript.mdc b/.cursor/rules/typescript.mdc
@@ -6,7 +6,7 @@ alwaysApply: false
 
 # TypeScript Guidelines (Supplement)
 
-For core TypeScript conventions (type vs interface, no `any`, explicit return types, naming), see **CLAUDE.md**. This rule adds advanced patterns.
+For core TypeScript conventions (type vs interface, no `any`, explicit return types, naming), see **AGENTS.md**. This rule adds advanced patterns.
 
 ---
 
diff --git a/.cursor/rules/workflows/debugging.mdc b/.cursor/rules/workflows/debugging.mdc
@@ -122,7 +122,7 @@ npm run lint
 
 ### Implement Fix
 1. Make the minimal change needed
-2. Follow project coding conventions (see CLAUDE.md)
+2. Follow project coding conventions (see AGENTS.md)
 3. Add error handling if the root cause was missing error handling
 4. Consider edge cases
 
diff --git a/.cursor/rules/workflows/feature-development.mdc b/.cursor/rules/workflows/feature-development.mdc
@@ -24,7 +24,7 @@ This is the complete workflow from picking up a Jira ticket to submitting a PR.
 
 3. IMPLEMENT
    "Create the component", "Add the feature"
-   Write code following project standards (CLAUDE.md)
+   Write code following project standards (AGENTS.md)
 
 4. TEST
    "Test my changes", "Add unit tests"
@@ -224,7 +224,7 @@ Following `pr-preparation.mdc`:
 - **Playwright / E2E**: Use separate clusters or avoid heavy automated traffic so shared environments are not blocked.
 
 ### Rules Applied
-- **CLAUDE.md**: Project coding standards
+- **AGENTS.md**: Project coding standards
 - **team-review.mdc**: Multi-perspective review
 - **ticket-workflow.mdc**: Agent tracking for tickets
 - **pr-preparation.mdc**: PR checklist
diff --git a/.cursor/rules/workflows/new-component.mdc b/.cursor/rules/workflows/new-component.mdc
@@ -7,7 +7,7 @@ alwaysApply: false
 
 Invoke with: *"create a component"*, *"new component"*, *"build a component for"*
 
-Follow this comprehensive workflow when creating new components. For coding conventions, see **CLAUDE.md**.
+Follow this comprehensive workflow when creating new components. For coding conventions, see **AGENTS.md**.
 
 ---
 
diff --git a/.cursor/rules/workflows/ticket-workflow.mdc b/.cursor/rules/workflows/ticket-workflow.mdc
@@ -60,7 +60,7 @@ Present findings to the user:
 ## 5. Phase 4: Implementation (after user selects approach)
 
 1. Implement the selected fix/feature
-2. Follow project coding conventions (CLAUDE.md)
+2. Follow project coding conventions (AGENTS.md)
 3. Add appropriate error handling
 4. Consider edge cases
 
diff --git a/AGENTS.md b/AGENTS.md
@@ -1,4 +1,4 @@
-# Claude.md - AI Assistant Guidelines for Forklift Console Plugin
+# AI Assistant Guidelines for Forklift Console Plugin
 
 ## Project Overview
 
@@ -530,6 +530,8 @@ npm run test:e2e           # Run E2E tests
 
 ## Commit Message Format
 
+**All commits must be signed off** (`git commit -s`) for DCO compliance. The DCO check **will fail** without `Signed-off-by`. **Always use `-s` (or `--signoff`) on every `git commit` command.**
+
 **All commits must include a `Resolves:` line** in the commit description:
 
 ### Format Options
@@ -557,6 +559,7 @@ Updated login validation to handle edge cases.
 Added proper error messages for invalid inputs.
 
 Resolves: MTV-456
+Signed-off-by: Your Name <your-email@redhat.com>
 ```
 
 ### Validate Locally
diff --git a/AI_README.md b/AI_README.md
@@ -2,7 +2,7 @@
 
 This project includes Cursor AI rules that provide consistent coding assistance across the team. When you open this project in Cursor, these rules are automatically loaded.
 
-**CLAUDE.md** is the source of truth for conventions; `.cursor/rules/` supplements it.
+**AGENTS.md** is the source of truth for conventions; `.cursor/rules/` supplements it.
 
 ---
 
@@ -32,7 +32,7 @@ Rules are in `.cursor/rules/` and apply automatically:
 
 | Knowledge Area | What It Knows |
 | -------------- | ------------- |
-| **Project Conventions** | TypeScript, React, SCSS standards (from CLAUDE.md) |
+| **Project Conventions** | TypeScript, React, SCSS standards (from AGENTS.md) |
 | **Domain Context** | Forklift CRDs, provider types, migration flow |
 | **Team Perspectives** | Developer, UX, QE, Security, Forklift Expert |
 | **Workflows** | How to create components, debug, prepare PRs |
@@ -162,4 +162,4 @@ Create `.cursor/rules/personal-<name>.mdc` -- it's gitignored. Add your preferen
 
 ## Contributing to Rules
 
-Edit files in `.cursor/rules/`, keep them focused, avoid duplicating CLAUDE.md, and submit a PR.
+Edit files in `.cursor/rules/`, keep them focused, avoid duplicating AGENTS.md, and submit a PR.
