Design Asset Libraries

High Quality UI and UX Assets Every Designer Should Bookmark Good assets don’t replace thinking. They speed up execution after decisions are made. These platforms are used by working designers who care about quality, consistency, and shipping faster without visual debt. Save this. You’ll come back to it. UI8 Premium UI kits, design systems, and templates built for real products. Best when you want production-ready components, not Dribbble fluff. Wannathis High-quality 3D illustrations and mockups with strong visual consistency. Useful for hero sections, marketing pages, and product storytelling. Lstore Graphics Mockups, scene creators, and UI tools designed to save time. Great for presentations, case studies, and fast client visuals. WhiteUI.Store Clean, minimal UI kits focused on structure and usability. Helpful when building dashboards, SaaS products, and internal tools. Flyerwrk Bold graphic assets inspired by anti-design and brutalism. Good for experimental layouts, landing pages, and brand-led visuals. UX Kits UX-focused kits for planning, workshops, and communication. Useful before Figma screens begin, especially in team environments. Why these matter They reduce repetitive work They improve visual consistency They speed up delivery They help you focus on UX decisions They support real-world workflows Assets should support thinking, not replace it. If you want Part 2 with free UI assets, icon systems, and illustration libraries designers actually use, comment PART 2. #uidesign #uxdesign #designresources #productdesign #figmadesign #uxworkflow

🍱 How To Organize Your Design System At Scale (https://lnkd.in/e9343uqv), a fantastic case study on how to set up a design system with 900 shared components and 25 designers — with product-specific domain components and shared ownership between the design system guild and product designers. Written by Jérôme Benoit ↓ Key takeaways: ✅ 1 design system, 8 design libraries, 1 library serves 1 goal. ✅ Each library has owners, editors (edit/publish), users (view-only). ✅ All designers have access to all resources from all files. ✅ Product team has domains, each domain has feature teams. ✅ Foundations + Core components are owned by design system team. ✅ Domain components are product-specific, owned by product designers. ✅ Each feature team has its own frame (not a page!) on a Domain page. ✅ Domain components are structured [Instance name] 💠 [Core name]. ✅ The work by product teams can move up to the Core level, too. In many products, different feature teams often have very different needs, and that’s why secondary design systems emerge. With this set-up, all teams are still working within 1 single design system, pulling and pushing components between levels and having search across all design work in all domains at once — without an organizational overhead! 👏🏼👏🏽👏🏾 Useful resources: How To Organize 1250+ Design Screens in Figma (+ File examples), by Lorenzo Palacios Venin https://lnkd.in/e7X4fKcj Booking.com: Multi-Platform Design System (+ Figma), by Nicole Saidy https://lnkd.in/edueYQPG Frog: Building A Global Design System, by Anthony Nguyen https://lnkd.in/etkiTxfB Doctolib Figma Files Organization Tips, by Jérôme Benoit https://lnkd.in/eK7bhQeS Multi-Brand Design System, by Pavel Kiselev https://lnkd.in/eShgnPnW Design System Structure for Teams, Projects and Files, by Luis Ouriach https://lnkd.in/eFZUjUCU How to Organize Your Figma Files For Design System, by Jules Mahé https://lnkd.in/eeHG2VzU Organizing Design System For Scalability, by Allie Paschal https://lnkd.in/eeAtakGs Design That Scales (Book), by Dan Mall https://lnkd.in/eeFrqFfP And kudos to the wonderful design team at Doctolib and all the wonderful designers above for sharing their insights for everyone to learn from!👏🏼👏🏽👏🏾 #ux #design #designsystems

“Where am I?” As our design system matures, things move around. We’re trying to invest in ways that allow feature designers and engineers to locate where they are within a design system, and where to find what they need. → Multiple design libraries can be hard to track and become confusing when designers and engineers aren’t aware of what does and doesn’t exist in each library. → Every component and pattern has a varying degree of specificity from generic to a specific business context or content pattern and deciding what goes where is confusing. → Theming in Figma is great, but... the current nature of variables can make managing multiple modes across multiple brands challenging. Here’s how we’ve been trying to get our head around reducing complexity for our team and consumers 🏗 Figma file architecture - Having a clear plan for structuring your design system libraries is critical for folks to find stuff. Our early attempts at a highly modular system with numerous smaller libraries were too unwieldy. We’ve landed into a Tokens, Components, Patterns, and Features structure that streamlines the process for everyone. It was super cool to stumble on these Figma docs that deep dive into various strategies for organizing your files https://lnkd.in/dGyN-SQw 🚦 Wayfinding elements - Once designers and engineers are in the files themselves, it's still easy to get lost. We’ve implemented consistent color-coded “file covers” distinguishing design system files from feature files, “getting started” pages outlining file dependencies, and consistent page naming conventions indicating iterations from elements that are ready for development. Thanks to Vitaly Friedman for the reference to Saurav Rastogi's post on Figma file organization which is packed with insights. https://lnkd.in/giBs_Jgn 🎨 Multi-brand variables - Our team has worked hard to figure out the most intuitive way to allow for white-labeling our design system for custom theming. We currently leverage modes at multiple layers of the design system based on their specificity from global to semantic to component to pattern. Romina Kavcic has endless resources for teams who are looking to build out their token strategy. https://lnkd.in/deiMGCe9 💎 Wayfinding within design systems is hard but a couple of things that help folks understand where they are and what they can do → Partner with engineers on an architecture that maps somewhat to their mental model making things more intuitive → Setup wayfinding documentation within your Figma files that orient users to where they are within the system → Map your tokens and variables across your system so that it is clear how to layer modes to achieve custom themes #designsystems #figma #uidesign #tokens #components #patterns

"Where do you find good icons?", "What's your LP/ad inspo?", "How do you pick brand fonts?" I get DMs like this DAILY. After years of sharing one-off links, I've actually started sending everyone to Toools.design. It's a super-curated collection of hundreds (thousands?) of design resources. Everything from UI kits to typography, inspiration, stock photos, icons, etc. Here’s why I like it →  • Clean interface that doesn't overwhelm • Quality-filtered resources (no junk) • Organized by exactly what you need • Regularly updated with fresh tools Been using this at Obvi for months. It's replaced like 50 bookmarks in my browser. For non-designers: It removes the guesswork. You'll find professional-grade resources without getting lost in the weeds. For designers: It's like having a master list of vetted tools. Plus they surface new ones I haven't seen before. Not affiliated - just sharing because it's become my go-to recommendation for anyone who asks about design resources 🙌