
Tech • AI • Robotics
This video provides a detailed guide on how to effectively use Cloud Design on cloud.ai, including important usage tips, limitations, and best practices to avoid common pitfalls, especially regarding token consumption and design system integration.
The video introduces the Cloud Design feature on cloud.ai, which allows users to create designs, interactive prototypes, presentations, and one-pagers by conversing with Claude, an AI model. Unlike other models on the platform, Cloud Design has distinct usage and token limits resetting weekly, not daily, which users must carefully monitor to avoid running out of usage.
Usage of Cloud Design is tied to the user’s subscription plan. For example, the Pro plan offers limited usage, the Max 5 plan provides more capacity, and the Forfait 20 plan offers the most tokens. Since limits reset only once a week, users need to plan their design sessions accordingly.
A key feature is the ability to upload a design system, which allows Claude to generate designs consistent with a company’s branding, such as logos, fonts, and color palettes. Users can add design assets, graphical guidelines, and even website code from GitHub or local files to enable Claude to better understand and adhere to style constraints. The richer the input design system, the more consistent and token-efficient the output will be.
Providing thorough context before starting a design project reduces token usage and improves output quality. The recommended prompt includes four elements: the objective (what you want to build), layout (the arrangement of design elements), content (text or media to fill the design), and target audience. This pre-planning ensures less back-and-forth interaction and more precise results.
When creating slides or design elements, users interact with both a chat and comments section. The chat is reserved for major structural changes, such as adding slides or changing color themes, and consumes more tokens. Meanwhile, comments allow for small, targeted corrections and are more token-efficient. Users must be aware of a current bug where comments can disappear, potentially requiring re-entry through the chat, which is more costly token-wise.
Finished designs can be exported in multiple formats, including ZIP, PDF, and PPTX. The presenter prefers ZIP but noted some issues saving PDFs. This flexibility supports a range of workflows from presentations to web use.
The speaker experimented with generating a full graphic charter for a newsletter project called "I got It," dedicated to weekly AI news. Five design variations were produced. While one was coherent and usable, others were less successful, highlighting the need for detailed prompts and context. The speaker suggests that current outputs can vary widely, requiring iterative prompting to optimize.
Users in the community are combining Cloud Design with other AI tools to generate videos, email marketing templates, and more, showing the potential for multi-AI workflows. Examples seen online showcase creative implementations that extend beyond just static designs.
Cloud Design remains in preview, and some features or bugs are still being refined by the developers, so user feedback is valuable.
The video encourages users to explore example projects and templates provided within Cloud Design to understand best practices and token usage, as direct usage without preparation can rapidly consume tokens. The speaker promises future videos to share deeper insights from ongoing experimentation.
Cloud Design is a promising AI-powered tool for generating complex designs through conversation with Claude, but it requires strategy to avoid resource waste and maximize quality. With proper preparation, design system inputs, and iterative interactions, users can produce professional-looking presentations, charters, and more.
This thorough walkthrough highlights both the capabilities and current limitations of Cloud Design, providing a valuable resource for users looking to leverage AI in their design workflows effectively.
Explain this