Recently I did a website using Elementor in Wordpress and tried using clause to help build it.

4 things I learnt

1. Move with purpose.
   When I first started transitioning from a concept to a finished product with Claude, I faced many many problems. It quickly became clear that a full website mockup was just too much to give the AI, so I changed my approach. Instead of asking it to code my entire site, I asked it to code a plugin for a specific use case where the result I wanted was beyond the capabilities of Eliminator. Doing so resulted in a product that was easy for me and my client to use.
   
   

2. Come prepared.
   It took me 30+ attempts with Claude to produce a product I was happy with. Throughout the refinement process I learnt what it was capable of and how to get the best results out of it. Firstly, I learnt that screenshots aren’t enough. You should also provide a written design guide, outlining padding, corner radius, colour swatches and any other details that should stay consistent across the design. Responsive design is also super important so include screenshots of your design at different breakpoints and add descriptions of how the breakpoints should behave.
   
   

3. Know your platform and know your functions.
   In addition to the design guide, include a description of what you specifically want your product to do. Obviously you should describe the user experience for the website clients, but you can also dictate how the plugin works within the Elementor UI, giving me control over the back end experience too. My functionality guide included a description of exactly what I wanted my plug in to do and how to behave. I described the required features and instructed it to work with Wordpess and Elementor. This allowed me to make my product with customisable variables that fit into Elementor UI and referenced their Wordpress databases (like its image library and font styles). The end result felt like it was natively part of Elementor, making it easy for me or my client to customise the component whenever we needed.
   
   

4. Clean your code.
   I found as I made iterations, residue code was causing problems. I learnt that it’s beneficial to instruct Claude to review its code, removing all old code that’s no longer necessary. I did this whenever something wasn’t behaving as it should be and when I got close to a finished product. This has three benefits; it reduces the chances of a bug occurring, it speeds up generation time when doing the final alterations and when it’s in your website, it’ll load faster (very important!).