Add more instructions to claude (#3992)

Add instructions to claude due to repetitive errors: Avoid programmatic
skips, imports always at the top of the module, and keep conftest.py for
fixtures

Signed-off-by: Asia Khromov <azhivovk@redhat.com>

Author: azhivovk

CLAUDE.md

@@ -39,6 +39,8 @@ Before writing ANY new code:
 - **NEVER use single-letter variable names** - ALWAYS use descriptive, meaningful names
 - **No dead code** - every function, variable, fixture MUST be used or removed. Code marked with `# skip-unused-code` is excluded from dead code analysis (enforced via custom ruff plugin).
 - **Prefer direct attribute access** - use `foo.attr` directly. Save to variables only when: reusing the same attribute multiple times improves readability, or extracting clarifies intent.
+- **Imports always at the top of the module** - do not import inside functions
+- **`conftest.py` is for fixtures only** - helper functions, utility functions, and classes must NOT be defined in conftest.py or test_*.py; place them in dedicated utility modules instead
 
 ### Acceptable Defensive Checks (Exceptions Only)
 
@@ -65,6 +67,7 @@ The "no defensive programming" rule has these five exceptions:
 - **Tests MUST be independent** - use `pytest-dependency` ONLY when test B requires side effects from test A (e.g., cluster-wide configuration).
   For resource dependencies, use shared fixtures instead. **When using `@pytest.mark.dependency`, a comment explaining WHY the dependency exists is REQUIRED.**
 - **ALWAYS use `@pytest.mark.usefixtures`** - REQUIRED when fixture return value is not used by test
+- **Do not offer to use `pytest.skip()` or `@pytest.mark.skip` or `@pytest.mark.skipif`** - pytest skip and skipif options are forbidden
 
 **`__test__ = False` Usage Rules:**