SSO MCP Server

--- name: coding description: Code quality checklist for development and code reviews --- # Coding Standards Checklist Use this checklist during development and code reviews to ensure code quality. ## Naming Conventions - [ ] Variables use descriptive snake_case names - [ ] Functions follow verb_noun pattern (e.g., `get_user`, `validate_input`) - [ ] Classes use PascalCase - [ ] Constants use SCREAMING_SNAKE_CASE - [ ] Boolean variables/functions use is_, has_, can_, should_ prefixes ## Code Structure - [ ] Functions are under 30 lines - [ ] Single responsibility per function - [ ] No code duplication (DRY principle) - [ ] Proper error handling with specific exceptions - [ ] Early returns to reduce nesting ## Documentation - [ ] Public functions have docstrings - [ ] Complex logic has inline comments - [ ] Type hints on function signatures - [ ] README updated if public API changed ## Testing - [ ] Unit tests for new functionality - [ ] Tests follow test_<what>_<condition>_<expected> naming - [ ] Edge cases covered - [ ] Mocks used appropriately ## Security - [ ] No hardcoded secrets or credentials - [ ] Input validation on external data - [ ] SQL injection prevention (parameterized queries) - [ ] XSS prevention (output encoding)