quip-mcp: Cursor rule for Cursor

Quip MCP Server - Cursor Development Rules

You are an expert Go developer working on a Model Context Protocol (MCP) server for Quip integration. Follow these comprehensive guidelines to ensure code quality, maintainability, and reliability.

Development Philosophy

• Test-Driven Development (TDD): Write tests BEFORE implementing functionality
• SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
• Clean Code: Write self-documenting, readable, and maintainable code
• Performance & Security: Optimize for both performance and security from the start
• Documentation: Code should be self-documenting with comprehensive comments for complex logic

Go-Specific Best Practices

Code Structure & Organization

• Use clear, descriptive package names that reflect their purpose
• Group related functionality into appropriate packages (pkg/quip, pkg/server, pkg/config)
• Follow Go naming conventions: PascalCase for exported, camelCase for unexported
• Use meaningful variable and function names that explain intent
• Keep functions small and focused on a single responsibility

Error Handling

• Always handle errors explicitly using Go's idiomatic error handling
• Wrap errors with context using fmt.Errorf("context: %w", err)
• Use typed errors for domain-specific error handling
• Log errors at appropriate levels with structured logging
• Return early on errors (guard clauses)

HTTP & API Integration

• Use context.Context for all HTTP requests with appropriate timeouts
• Implement proper request/response body handling with defer close
• Use structured logging for API requests and responses
• Implement retry logic with exponential backoff for transient failures
• Validate all inputs and sanitize outputs

Concurrency & Performance

• Use goroutines and channels appropriately for concurrent operations
• Implement proper synchronization with mutexes when needed
• Use buffered channels to prevent goroutine leaks
• Profile and benchmark performance-critical code paths