The context of innovation
At TREIZE, we are not the last to jump on the innovation bandwagon. When we saw the potential of Claude, we made it our mission to explore its possibilities without losing sight of what makes our team’s DNA: maintaining our expert status and our critical thinking in all circumstances.
With the foundations laid, experimentation began in all our departments. In my case, in design.
I long held reservations about AI in a creative profession. Creation involves human emotions and the desire to transmit them to an audience. My first question was therefore: how can I use AI without it distorting my work, or making me lose the meaning of what I do on a daily basis? The answer ended up being one sentence. I keep the creative part entirely, and I rely on Claude to better approach the technical part.
Facilitating a transition from one department to another
This technical part, for us, is the transition between the mockups and the development team.
After a discussion with the developers, we realized that there was a way to standardize the colors, typographies, or corner radii that I had chosen myself during the art direction phase. As I have long worked on interfaces designed primarily for mobile screens, I wanted to go further: also entrust all the context I had planned for responsive design, so that nothing would be lost along the way. I therefore connected Claude’s MCP to my Figma account and launched the first analyses of my mockups.
The iterative approach as a keystone
It took several iterations before Claude understood my logic. As is often the case with AI, there was initially some free interpretation on several elements: text sizes that were illegible on mobile, color combinations that did not meet contrast standards, among others. Through adjustments, and by learning to better formulate my requests, I ended up with a document that includes the breakpoints and all the established graphic standards, with ready-to-use code bases to accelerate the implementation of the style. It contains conversions to em, functional CSS variables for Tailwind, as well as the desired behaviors according to screen resolutions.
Nothing that Claude produces should be taken for granted. The output must always be reviewed, and that is exactly where the process makes sense. It is because we review that we remain experts in our own work. In the process, it forces us to sharpen the functional analysis of what we wish to produce next.
Conclusion
This entire procedure is now a Claude skill that we use internally and continuously improve, as we develop our skills with AI tools and our way of handling interfaces on different screen resolutions. Concretely, we have reduced daily back-and-forth and we communicate better between departments. In a team of our size, that changes a lot of things.
