scrcpy-cli-argument-to-code-mapper

Automate scrcpy CLI argument code generation by mapping CLI argument specifications to corresponding Dart class definitions. This Skill takes argument details—name, description, UI control type, and advanced flag—and produces categorized classes under @lib/application/model/scrcpy/arguments, aligned with your project's existing structure and @scrcpyArg annotations.

Yes. When a new scrcpy CLI argument is released, provide its documented specification from scrcpy docs or docs/scrcpy_options. The Skill generates the necessary backend Dart classes automatically, eliminating manual class creation and ensuring consistency with your established code structure.

For unknown arguments, this Skill drafts class definitions based on available information and confirms details with you before finalizing. It guides the process of gathering missing argument specifications from documentation or other sources to ensure accuracy.

Yes. Generated classes follow your project's established patterns, including proper use of @scrcpyArg annotations, UI control type categorization, and the Advanced flag. All output aligns with the structure documented in Supported scrcpy CLI Options.

Provide the argument name, human-readable description, UI control type (e.g., text input, toggle, dropdown), and whether it's marked as advanced. The Skill uses these details to generate complete, annotated Dart class definitions ready for integration.

Manual class creation is repetitive and error-prone. Automating the mapping from CLI specifications to code eliminates transcription mistakes, ensures consistent annotation usage, and maintains alignment with your project structure across multiple arguments.