design-engineering
This skill helps users establish and scale design engineering functions by drawing on frameworks from leaders who built these roles at Snap, Captions, and Vercel. Use it when hiring design engineers, reducing design-to-engineering handoff friction, determining organizational placement, or deciding whether to develop existing team members into the role versus recruiting specialists.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/design-engineering && cp -r /tmp/design-engineering/skills/design-engineering ~/.claude/skills/design-engineeringSKILL.md
# Design Engineering Help the user understand design engineering using frameworks from 2 product leaders who have built design engineering functions at companies like Snap, Captions, and Vercel. ## How to Help When the user asks for help with design engineering: 1. **Define the role** - Clarify what design engineering means in their context (prototyping, production code, or both) 2. **Identify the need** - Determine if the gap is between design and engineering handoffs, prototype fidelity, or shipping speed 3. **Assess feasibility** - Help them evaluate whether to hire specialists or develop existing team members 4. **Design the function** - Guide them on where design engineering should sit organizationally ## Core Principles ### Merge UX design and engineering Gaurav Misra: "A big part of what I did there was create this function called design engineering." The design engineering function at Snap and Captions merges UX design and engineering to prototype and ship faster. ### Combine design sensibility with shipping ability Guillermo Rauch: "A lot of the people that we were noticing were being very successful at Vercel were people that had both the design and engineering skills." The most valued design engineers combine high-end design sensibility with the ability to ship production-ready code. ## Questions to Help Users - "What's the current handoff friction between design and engineering?" - "Do you need prototypes for validation or production-ready code?" - "Where would design engineering sit in your org - design, engineering, or product?" - "Do you have existing team members who could grow into this role?" - "What tools and frameworks would design engineers use?" ## Common Mistakes to Flag - **Unclear scope** - Not defining whether design engineers prototype or ship production code - **Wrong org placement** - Isolating design engineers from both design and engineering teams - **Hiring for unicorns** - Looking for people who are world-class at both rather than strong at the intersection - **Ignoring AI tools** - Missing how AI-assisted development is making this role more accessible ## Deep Dive For all 2 insights from 2 guests, see `references/guest-insights.md` ## Related Skills - Technical Roadmaps - Managing Tech Debt - Platform & Infrastructure - Engineering Culture
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.