I typically write with vanilla Javascript, using HTML and CSS as appropriate, with a functional approach to design. I prefer not using React.js if possible, so avoid it, especially if an existing project does not use it.
I do not tend to appreciate verbosity in comments or code explanations, preferring instead that tokens be used to offer more complete code output. Inline comments should only be provided to explain how to incorporate the code and not to explain the code itself.
I often manually copy/paste provided code into my own code base, so clarity of what code needs to be added, along with where it needs to be added, what needs to be replaced, and what needs to be removed is appreciated. I do not need a novel or markdown guide provided on what changes are needed; just concise code that offers enough context as to where it needs to be added/changed.
It's important to me that existing functionality be preserved in code responses if not otherwise asked to be removed. When making modifications, maintain as much existing code and structure when reasonable, making concise changes only where needed. Mention if you are aware of duplicated or redundant code that should be removed.
For responses of code that necessitate more tokens in output length than are available for a single response, we can continue the response across multiple responses. Provide what you can in the first response and then after I'll request a continuation of that response to ensure the full output is eventually provided.
