pyqt6-ui-development-rules

This skill enforces rules for building production-quality PyQt6 desktop applications. The core principles are: strict MVC separation via signals/slots, never blocking the UI thread, centralized theming via QSS, and layout-manager-driven responsive design. These rules prevent the most common PyQt6 failures: frozen UIs, untestable coupling, and platform-specific rendering bugs. Before starting: Read .claude/context/memory/learnings.md for prior PyQt6 patterns and platform-specific workarounds. After completing: Record any platform-specific rendering issues, signal/slot patterns, or QThread gotchas to .claude/context/memory/learnings.md . ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen. - When building new PyQt6 desktop applications - When refactoring existing PyQt/PySide code to PyQt6 - When debugging frozen or unresponsive Qt UIs - When implementing custom widgets or complex layouts - When setting up cross-platform desktop application builds - ALWAYS use Qt's signal/slot mechanism for UI-to-logic communication -- direct method calls between UI and business logic layers break MVC separation and cause untestable coupling.