[CONFIG] Create CLAUDE.md Configuration File

[raegAI]

@claude Please create a new CLAUDE.md file in the repository root that defines code style guidelines, review criteria, project-specific rules, and preferred patterns for this Hyperliquid Python SDK project.

File Structure Required:

# Claude Code Configuration for Hyperliquid Python SDK

## Project Overview
[Brief description of the Python SDK for Hyperliquid API trading]

## Code Style Guidelines
- Follow existing Python patterns in the codebase
- Use type hints for all new functions and methods
- Maintain backwards compatibility for all public APIs
- Follow PEP 8 style guidelines with project-specific exceptions

## Development Workflow
- Use Poetry for dependency management (Python 3.10+ required)
- Run `make install` for setup, `make test` for testing, `make lint` for linting
- All examples should remain functional after changes
- Configuration files go in examples/config.json

## Review Criteria
- Security considerations for trading API interactions
- Performance implications for trading operations
- Proper error handling and logging
- Comprehensive test coverage for new features

## Project-Specific Rules
- Never break existing API methods or signatures
- All trading operations must have proper error handling
- Rate limiting considerations for API calls
- Secure handling of API keys and credentials

## Preferred Patterns
- [Document existing patterns found in the codebase]
- Exception handling strategies
- Logging conventions
- API response processing patterns

## Testing Requirements
- Unit tests for all new functionality
- Integration tests where applicable
- Example validation after changes
- No test failures allowed in production merges

## Documentation Standards
- Clear docstrings for all public methods
- Update README.md for significant changes
- Maintain example code in examples/ directory
- Keep CHANGELOG.md updated for releases

Requirements:

• Analyze the existing codebase to understand current patterns
• Review examples/ directory to understand usage patterns
• Check existing test structure and conventions
• Document any specific trading/API related considerations
• Create comprehensive guidelines that Claude Code can follow

Integration:

• This file will guide all future Claude Code operations
• Should be referenced in workflow custom_instructions
• Must align with existing project structure and patterns

Please analyze the codebase thoroughly and create comprehensive guidelines that ensure consistent, secure, and high-quality code generation.

[claude]

Claude finished @raegAI's task —— View job • claude/issue-7-20250601_193431 • Create PR ➔

---

I've successfully created the CLAUDE.md configuration file for the Hyperliquid Python SDK project.

Tasks Completed:

• Analyze project structure and read key files (README.md, pyproject.toml, Makefile)
• Examine code patterns in hyperliquid/ directory
• Review examples directory to understand usage patterns
• Check test structure and conventions
• Create comprehensive CLAUDE.md file
• Commit and push CLAUDE.md to the branch

The CLAUDE.md file includes:

• Project Overview: Description of the SDK's purpose and functionality
• Code Style Guidelines: Python version requirements, type hints, formatting rules with Black
• Development Workflow: Poetry commands, testing with pytest, linting procedures
• Review Criteria: API compatibility, type safety, security considerations
• Project-Specific Rules: API structure patterns, signing requirements, configuration handling
• Preferred Patterns: TypedDict usage, error handling, WebSocket management
• Testing Requirements: pytest with VCR.py, coverage reporting, test conventions
• Documentation Standards: README maintenance, example structure, error messaging

The configuration is based on thorough analysis of the existing codebase patterns and aligns with the project's current conventions.