quasi-coder_skill

Overview

This skill turns shorthand, quasi-code, and natural language descriptions into production-quality JavaScript implementations. It interprets imperfect or incomplete input, applies expert judgment, and produces robust, maintainable code that matches intent. Use it when collaborators provide pseudo-code, shorthand markers, or non-technical descriptions that need translation into working code.

How this skill works

The skill scans shorthand sections (markers like start-shorthand / end-shorthand and lines prefixed with ()=>), extracts intent, and assesses the collaborator's expertise level to decide how much correction is required. It replaces shorthand lines with idiomatic JavaScript, adds validation and error handling as needed, and removes all ()=> shorthand markers. When intent is unclear it asks clarifying questions and presents trade-offs for alternative implementations.

When to use it

• Collaborator provides shorthand, pseudo-code, or lines starting with ()=>
• Translating natural-language requirements into working JavaScript functions
• Fixing or completing incomplete snippets with possible typos or wrong terminology
• Converting mixed-language pseudo-code into the appropriate target language
• Implementing core mechanisms from high-level descriptions for production use

Best practices

• Read the entire shorthand block before editing to capture full intent
• Assess the collaborator’s expertise level and adjust the amount of correction and explanation
• Prefer clear, testable, and minimal implementations—avoid over-engineering
• Add appropriate error handling, input validation, and descriptive names
• Respect existing project style and reuse persistent project resources where available
• Remove all shorthand markers and ()=> lines in the final code

Example use cases

• Transforming registration shorthand into a validateUserInput(email, password) function with email regex and password rules
• Converting a rough migration mapping note into a one-time migration script using provided JSON mapping
• Interpreting mixed-language pseudo-code to implement a users filter in the project’s preferred language and idioms
• Taking non-technical feature requests and producing a working API endpoint with input checks and clear responses
• Repairing collaborator-submitted snippets that use wrong method names or incorrect library assumptions