twitter-example Cursor Rules

# Golang Project Rules

## Code Style
- Use Go standard formatting (goimports)
- Follow Go naming conventions (CamelCase for exported, camelCase for unexported)
- Keep functions and methods concise and focused
- Avoid unnecessary comments - let the code speak for itself
- Use meaningful variable and function names

## Project Structure
- Follow 3-layer architecture pattern strictly
- Keep handlers, services, and repositories in separate packages
- Use interfaces for dependency injection and testability

## Error Handling
- Always handle errors explicitly
- Use structured error responses for HTTP APIs
- Log errors with appropriate context using logrus

## Dependencies
- Prefer standard library when possible
- Use well-maintained third-party packages
- Keep dependencies minimal and focused