Jonathan D'Mello

Claude’s new “Skills” could change how design teams use AI. Every designer knows the grind. You open AI. You paste the same wall of text. Brand tone. Design rules. File names. Review process. You do it every time. That’s the context tax. Claude just killed it with Skills. Think of them as mini brains. Each one remembers a part of your world. Your brand voice. Your UX principles. Your accessibility checks. Your Figma rules. You teach it once. It remembers forever. And the best part? Skills stack. One for tone. One for motion. One for layout. Claude pulls them together when needed. No more messy prompts. No more “oh, I forgot to mention” moments. Just consistent, on-brand output every time. This could change how design teams use AI. From creative briefs to brand QA. It’s not RAG. It’s not fine-tuning. It’s on-demand design memory.

23

2 Comments

Design for the Now, Build for the Future As design leads, it's our responsibility to think beyond the current product state. Even if your product isn't responsive today, your design system should be ready for it. When we build dynamic systems from the start, flexible layouts, scalable components, clear spacing, and typography rules, we save ourselves from major rework later. A few principles I share with my team: Design with responsiveness in mind, even if it's not needed yet. Use tokens, constraints, and naming conventions that scale. Keep documentation clear so others (or future you) can build with confidence. Future-ready systems make design faster, more consistent, and easier to grow. It's not just about solving today’s problems. It's about setting the foundation for what's next. #DesignSystems #UXLeadership #ResponsiveDesign #TeamGrowth #ScalableDesign

5

INDUSTRIAL DESIGNERS: hardware and software design aren’t the same game ——— Designing in pixels teaches iteration. Designing in atoms teaches judgment. When you work in hardware, failure has weight. One wrong call can cost millions in tooling, inventory, logistics, or safety. There’s no rollback, no patch. If something breaks at scale, you're already too late. That changes how you think. You make decisions earlier, with less data and more at risk. You learn to model failure before it happens. To tell when something works in CAD but not in the hand. To spot when research says yes but reality says no. It builds instincts that don’t show up in sprint reviews. You notice when tolerances kill experience. When materials tell the wrong story. When unseen tradeoffs shape what actually ships. It’s difficult to see all of this for those who’ve only worked in digital. And many hardware teams today are run using that same playbook. So make that expertise visible, before hardware problems are being solved with software thinking. ——— Craftedby.agency

46

10 Comments

From VoC to Validation: Closing the Loop in Product Development In product development, it's easy to treat each phase as a checkbox. But when done right, they form a powerful loop: 👉 Voice of the Customer defines 👉 Product Requirements, which guide 👉 Design FMEA, which informs 👉 Verification Planning, culminating in 👉 Product Validation. When these steps align, we go beyond building products — we build confidence. ✅ VoC ensures we solve real customer needs ✅ Requirements turn needs into measurable objectives ✅ DFMEA anticipates and mitigates design risks ✅ Verification checks that we built it right ✅ Validation confirms we built the right thing Skip a step, and you risk: misaligned specs, undetected failures, and unmet user expectations. Let’s stop thinking in silos. Let’s close the loop — from customer insights to customer satisfaction. #ProductDevelopment #VoiceOfCustomer #DFMEA #Verification #Validation #SystemsThinking #QualityByDesign #EngineeringExcellence

5