Act as a Principal Software Engineer and Technical Lead with 15+ years of experience establishing coding standards for high-performing engineering teams. Generate a comprehensive, production-ready code style guide based on the following parameters:

**CONTEXT:**
- Primary Language: [PROGRAMMING_LANGUAGE]
- Framework/Stack: [FRAMEWORK_OR_STACK]
- Team Context: [TEAM_CONTEXT]
- Compliance/Existing Standards: [EXISTING_STANDARDS]
- Special Focus Areas: [SPECIFIC_FOCUS]

**OUTPUT REQUIREMENTS:**
Create a professional style guide organized into these sections:

1. **Core Philosophy** - 3-5 guiding principles (e.g., readability over cleverness, explicit over implicit)
2. **Naming Conventions** - Specific rules for variables, functions, classes, constants, files with regex patterns where applicable
3. **Formatting Standards** - Line length, indentation, brace style, import organization, whitespace rules, maximum file length
4. **Architecture Patterns** - Preferred design patterns, module structure, dependency injection rules, API design standards, error handling approaches
5. **Code Quality Metrics** - Maximum cyclomatic complexity, function length limits, parameter count limits, nesting depth restrictions
6. **Testing Standards** - Test file naming, AAA pattern (Arrange-Act-Assert), mocking guidelines, coverage thresholds, test data management
7. **Documentation Rules** - Docstring formats, comment standards (when to comment vs. refactor), README requirements, changelog practices
8. **Security Guidelines** - Input validation patterns, authentication/authorization standards, secrets management, dependency scanning
9. **Performance Constraints** - Time/space complexity guidelines, async patterns, resource cleanup rules, memory management
10. **Tooling Configuration** - Linter rules (ESLint/Prettier/Ruff), pre-commit hooks, CI checks, IDE settings

**FORMAT SPECIFICATIONS:**
- Use Markdown with clear H2/H3 headers and table of contents
- For EVERY rule, provide: (a) The Rule statement, (b) ✅ GOOD example, (c) ❌ BAD example, (d) Rationale explaining "why"
- Include a "Quick Reference Cheat Sheet" table at the end for printing/posting
- Add an "Onboarding Checklist" for new team members
- Reference industry standards (Google Style Guide, PEP8, Airbnb, Rust API Guidelines) where relevant

**TONE:** Authoritative but pragmatic. Emphasize maintainability and team collaboration over personal preferences. Avoid bike-shedding rules; every standard must have a concrete justification.