InfaAi

This is actually big! ‼️ Why waste time writing tickets? The fastest way to iterate is to make changes directly in your product right from your browser. With the new Evolve feature in the Infa AI Chrome Extension, you can capture elements, give instructions, and send them straight to your code editor. No friction. No handoff. And it’s completely free! Coming soon: you’ll even be able to leave comments that trigger @cursor_ai Background Agents to make changes automatically no local setup required 🤩 I’ve got a bunch of free Pro coupons (1 month) for early testers. Want one? Drop a comment, and I’ll share access! #Design #Cursor #DesignSystems #DevTools

This is actually big! ‼️ @ShopifyEng Polaris #DesignSystem Inspect & Reflect! I’m excited to team up with @danmall , Maya Hampton, Lucas Mosele, and @pattyrozmus to explore how Shopify is evolving its design system and integrating it into their products. Register here: infa.ai/events/shopify… This is the perfect opportunity to dive deeper and analyze how their components, tokens, and patterns are shaping up. We’ll take a hands-on approach, reviewing their documentation, tagging components, and discussing practical insights on scaling a design system. What You’ll Get From This Session: → A closer look at how Shopify applies its design system across its products. → Insights into design system adoption, consistency, and future-proofing. → A collaborative discussion with experts sharing real-world strategies. Our goal? Learn, explore, and collaborate, not critique. If you’re into modern frontend ecosystems, design tokens, and how design systems scale in fast-moving companies like Shopify, this is for you! Join us for an interactive co-creation session, it’s going to be insightful and fun! #DesignSystems #Component

Does Your SMB Need a #DesignSystem? Look at @vercel's Geist Approach During our Inspect & Reflect, Jon Delman shared an interesting observation about Geist's documentation approach. Key Takeaways: → Geist focuses primarily on components rather than patterns or detailed usage guidelines → They provide code examples but minimal prescriptive guidance on when to use specific variants → Even with buttons that have semantic variants (error, warning), the examples show practical usage (upload) rather than explaining the semantic meaning → This suggests a deliberate choice to let developers consume the code directly rather than reading extensive guidelines My Thoughts: This could be a perfect example of how small-to-medium businesses (SMBs) can approach design systems without overwhelming documentation. Interestingly, Vercel doesn't use Storybook—they keep everything in one place using Nextra (their own documentation framework built on Next.js) to render markdown files. Why This Works: 1️⃣ Self-Explanatory Code > Documentation → Clean implementations with minimal but well-named props → Focus on solving real use cases rather than documenting every possibility → Faster learning curve for developers who prefer reading code over docs 2️⃣ Unified Documentation Architecture → Single technology stack (Nextra/Next.js) instead of separate tools → Markdown-driven workflow that's easy to maintain → Version control that treats documentation and code as a unified system 3️⃣ Right-Sized for SMBs → Scales with your team instead of requiring dedicated documentation resources → Prioritizes speed and implementation over comprehensiveness → Fits teams where designers and developers collaborate closely What's your take? Could this minimalist approach work for your team? 📢 Join us for the upcoming Inspect & Reflect: Monday.com's Vibe Design System! Check my profile for details. #DesignOps

In our recent Inspect and Reflect session, we explored the Gestalt #DesignSystem and discussed the Accordion component. Steve Dodier-Lazaro highlighted the importance of using the new HTML <details> element instead of custom solutions 🧵