Cedric’s Design Process: Five Essential Lessons for High-Velocity AI Product Teams
Cedric’s design process highlights how AI shifts focus from coding to clear communication and integrating design with engineering. Success comes from speed, clarity, and blending skills.

Five Takeaways from Cedric’s Design Process to Inspire Product Teams
1. Taste Is a Moat. Design Thinking Is the New Superpower.
With AI generating functional code instantly, the advantage no longer lies in who can build but in who knows what to build. Software is abundant, and barriers to creation are low, making design thinking more crucial than ever. Traditional technical moats are fading.
Those who excel will be the ones who identify the right problems and craft elegant solutions with strong product sense, UI/UX quality, and execution speed. Generative design tools let designers explore more concepts faster, automating multiple options based on user-defined parameters. This goes beyond aesthetics—it’s about deeply grasping user needs and crafting experiences that feel inevitable.
Companies that combine AI’s implementation power with refined taste and design judgment will lead the pack.
2. Natural Language Is a New Design Interface.
Cedric’s workflow highlights a major shift: moving from traditional design tools to using natural language as the main design interface. The key skill now is not coding but clearly articulating ideas and changes to AI.
This means developing a "design vocabulary"—the ability to fluently describe UI elements, CSS properties, and technical concepts without writing code. For example, Cedric uses precise terms like “4 pixel corner radius” or “opacity of 0.2” to communicate with AI tools. Complex interactions that once took days can be prototyped in minutes via conversational prompts.
Clarity is vital. Break down requests into simple, actionable steps:
- OK prompt: “Add different labels to the boxes in white text.”
- Great prompt: “For each bounding box drawn on the image, add a unique label in the top-left corner of the box that displays its index number (e.g., Box 1, Box 2) in bold, white text.”
Consistency in language matters. Use the same terms for UI elements or features throughout prompts—if you call something “segment mode” once, keep using that name.
Shared terminology helps avoid confusion in complex prototypes. Cedric introduces terms early and reuses them, ensuring both the team and AI “speak the same language.”
Designers thriving in this landscape quickly adopt new tools and expand their technical vocabulary without becoming engineers. The future belongs to those comfortable moving between tools like Figma, V0, and Cursor.
3. AI Is Driving the Rise of the "Design Engineer" Role.
The line between design and engineering is blurring. Cedric’s workflow moves from Figma to prototyping in V0, then directly adjusting code with Cursor. This is more than efficiency—it changes how products are built.
- Closed-loop ownership: Design engineers work across the stack, making sure design intent translates seamlessly to production. Cedric describes it as a "closed loop system" offering unprecedented control.
- Static mockups are obsolete: The old handoff model—designers tossing static images over the wall—is fading. Now, teams share high-fidelity designs alongside functional prototypes with real interactions.
- Rapid iteration: Design reviews and fixes shrink from days to hours. Cedric tweaks styling directly in code, accelerating cycles.
Teams blending design and engineering skills, where members contribute both prototypes and code, will move faster and build better products.
4. Four AI-Native Design Principles Are Emerging.
AI-powered products require new design principles:
- Minimize cognitive load: AI interactions should feel like natural conversations that pick up context without burdening the user with setup. Tools like Recall AI and Granola handle conversational data smoothly without forcing users to structure thoughts.
- Embrace non-determinism and handle interruptions: AI outputs can vary. Interfaces must manage this variability gracefully, offering controls to stop or redirect AI processes. Mechanisms to checkpoint and revert actions (as seen in tools like Cursor and V0) improve user experience.
- Use AI that shows its work: Transparency builds trust. Showing reasoning steps or source citations (like Perplexity or Deepseek) helps users understand AI decisions.
- Design for supervision, not operation: Users will manage AI agents rather than operate them directly. This calls for new UX patterns—dashboards for agent management, notifications for task completion, progress indicators, and interactive prompts.
These principles are evolving, but early adoption will lead to more intuitive and trustworthy AI experiences.
5. In the AI Era, Velocity Is Everything.
The pace of change is intense. Tools and best practices shift so quickly that today's go-to may be outdated tomorrow. This demands organizational agility in experimentation and adoption.
Successful companies will:
- Allow teams to try new tools freely
- Prioritize shipping and learning over perfection
- Build modular, API-driven architectures to integrate new capabilities fast
- Value learning speed as much as existing expertise
For larger organizations, starting with prototyping is key. Even without production code changes, AI tools can create prototypes that demonstrate what’s possible and build buy-in.
When designers prototype faster, engineers implement quicker, and teams iterate rapidly, product development cycles shrink significantly.
Cedric’s AI Design Stack
- Figma: The visual design source of truth. Exports specific frames for AI prototyping. Limitations include lack of dynamic interactions and state management.
- V0, Lovable, Bolt.new: Import frames from Figma and add dynamic interactions through natural language prompts. Example: bounding box drawing with coordinate tracking.
- Cursor, Windsurf: Make direct styling and logic adjustments in the codebase. Submit pull requests for engineering review.
- Shad.cn, Tailwind, UntitledUI, HeroUI: Pre-built component libraries AI references by name. Using consistent component language reduces AI errors and ensures standard patterns.
For more practical insights on AI-powered product design, check out Complete AI Training’s latest courses.