What problem does it solve? Building classroom software for Windows involves unique constraints—touch and pen input, projector and dual-screen setups, offline operation, and crash recovery—that generic WPF guidance does not address. This Skill provides product priorities, engineering checks, and verification practices tailored to teacher-facing desktop applications. ## Core Features & Use Cases - Classroom-First Engineering Checks: Enforces separation of domain logic from WPF views, Dispatcher-safe threading, DPI-aware overlays, and stylus/touch input handling without duplicate ink or commands. - Desktop UI Observation & Operation: Guides non-invasive inspection using UI Automation, FlaUI, or pywinauto, with stable automation identifiers preferred over coordinate clicks. - Recovery & Persistence Contracts: Defines write, interruption, corruption, and version-migration behavior for settings, session state, and classroom artifacts. - Use Case: When implementing a teacher's presentation tool with ink annotation on a dual-screen classroom PC, use this Skill to structure the architecture, verify touch targets at real scaling, and test recovery after a power interruption. ## Quick Start Use the custom-windows-wpf-teacher-app skill to design and implement my WPF classroom application with touch, projector, and local recovery requirements.
