Awesome advice here. As a dev and also design person who works with non-dev art folks all day, I'd say the more you can get down to specific exact asset files a

Awesome advice here. As a dev and also design person who works with non-dev art folks all day, I'd say the more you can get down to specific exact asset files and names, the easier things will be for your devs. On the design side people work with multiple protypes and sketches in different states. But none of that ever makes it to the cold bare metal of programming. Design folks are often surprised that no visual tools are involved in actual website or software creation. Software requires exact numbers (margins, image sizes, color codes) and exact assets in specific places (on screen and on disk) to work. This means it will be as much effort for your dev to implement a "wrong" or temporary design as it will be to implement your final. Whenever you can carve out individual components or design aspects that don't change and canonize them in writing, this will help your devs. Think of their job as translating ideas and pictures into code which produces something like your pictures and you'll be easy to work with. And, have fun and keep adding the joy of your art skills to the (sometimes dreary) programming side.