agentleFS
mahirautela2020-designmahirautela2020-design/claude-skills-ux/collab-leadership-mentoring/SKILL.md

collab-leadership-mentoring

Skill1 starsChanged 8 months agoMITView on GitHub

Supports senior designers in leadership, mentoring, and influence. Use when the user needs help mentoring others, shaping standards, influencing product direction, driving cross-team initiatives, setting quality bars, and representing design in strategic forums, beyond individual delivery.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when operating in senior/lead tracks, leveling up your influence, or supporting the growth of other designers.

    line 21
  2. Distinctive:

    Use this to focus your energy on the areas where your leadership can most improve outcomes, not just artifacts.

    line 42
  3. Distinctive:

    Treat mentoring as a structured, ongoing practice, not ad‑hoc advice.[web:408][web:413][web:416][web:419]

    line 48
  4. Distinctive:

    Use critiques and reviews to:

    line 77
  5. Distinctive:

    Document standards in a visible place (e.g., craft excellence guidelines, pattern library) and reinforce them in hiring, onboarding, and …

    line 81
  6. Very specific:

    Use data and stories to connect design proposals to business outcomes and strategic bets, leveraging product-ux-strategy-alignment, …

    line 101
  7. Distinctive:

    When joining roadmap reviews, planning, or leadership meetings:

    line 109
  8. Distinctive:

    Use your position to create more leaders, not just more followers.[web:407][web:412][web:416]

    line 185
  9. Distinctive:

    Add a simple structure (cadence, shared doc, recurring topics).

    line 239
  10. Distinctive:

    Ask mentees regularly what’s helping and what they’d like more/less of.[web:413][web:416][web:419]

    line 240
  11. Distinctive:

    Ask for feedback, receive it gracefully, and act on it.

    line 245
  12. Very specific:

    Use team rituals (crits, retros) to normalize constructive feedback and learning, working with collab-design-ops-process.

    line 247
  13. Distinctive:

    Use this skill with:

    line 253

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Leadership, Mentoring & Influence

Purpose

This skill helps senior and lead designers expand their impact beyond individual projects into team, product, and organizational leadership.[web:407][web:409][web:410][web:411][web:412] It focuses on mentoring, shaping standards and quality bars, influencing product direction and cross‑team initiatives, and giving/receiving feedback while representing design credibly in strategic forums and aligning with product, engineering, and metrics practices from related skills.[web:407][web:409][web:412][web:418][web:417]

Use this skill when operating in senior/lead tracks, leveling up your influence, or supporting the growth of other designers.


Instructions

Step 1: Clarify your leadership scope and responsibilities

Define what leadership means in your current role.[web:409][web:411][web:412]

Ask:

  • "What decisions do I influence today (team, product area, org)?"
  • "Where am I expected to lead: craft, people, process, or strategy?"
  • "What impact am I accountable for beyond my own delivery?"

Summarize:

  • Primary leadership scopes (e.g., own a domain, mentor designers, drive a cross‑team initiative, steward a design system).
  • Key partners (PMs, Eng leads, other design leads) you must influence and support.[web:409][web:412]

Use this to focus your energy on the areas where your leadership can most improve outcomes, not just artifacts.


Step 2: Practice intentional mentoring

Treat mentoring as a structured, ongoing practice, not ad‑hoc advice.[web:408][web:413][web:416][web:419]

For each mentee:

  • Align on goals:
    • Skills they want to grow.
    • Types of support they need (feedback, shadowing, sponsorship).
  • Set a simple structure:
    • Regular cadence (e.g., bi‑weekly).
    • Shared doc or board for topics, actions, and progress.
  • Mix:
    • Craft feedback (e.g., on current work).
    • Process and stakeholder coaching.
    • Career and growth conversations.

Encourage mentees to own the agenda and come with questions; your role is to guide, challenge, and unblock, not to solve everything for them.[web:416][web:413][web:408]


Step 3: Shape standards and quality bars

Help define and uphold quality standards for design work.[web:412][web:418][web:421]

Practices:

  • Co‑create and refine:
    • Design principles.
    • Definition of done for UX (states covered, accessibility, error flows, etc.).
    • Examples of “good” for key artefacts (flows, specs, research reports, interaction patterns).[web:421]
  • Use critiques and reviews to:
    • Tie feedback to standards and principles, not personal taste.
    • Highlight positive examples as well as gaps.

Document standards in a visible place (e.g., craft excellence guidelines, pattern library) and reinforce them in hiring, onboarding, and performance conversations.[web:412][web:421][web:418]


Step 4: Influence product direction and cross‑team initiatives

Move from designing features to helping shape what the team works on.[web:409][web:410][web:411]

Practices:

  • Partner with PMs to:
    • Frame and prioritize problems and opportunities.
    • Bring user insights into roadmap and strategy discussions.
  • Identify cross‑team initiatives:
    • Common UX problems (e.g., onboarding, navigation, trust) that span squads.
    • Horizontal work like design systems, accessibility, experimentation, or research practices.[web:409][web:412]
  • Lead or co‑lead these initiatives:
    • Define vision and success criteria.
    • Align multiple teams around shared frameworks, patterns, or journeys.

Use data and stories to connect design proposals to business outcomes and strategic bets, leveraging product-ux-strategy-alignment, product-discovery-opportunity, and ux-product-design-metrics.[web:409][web:410][web:411]


Step 5: Represent design in strategic forums

Show up as a credible, prepared voice for users and design in leadership settings.[web:409][web:410][web:412]

When joining roadmap reviews, planning, or leadership meetings:

  • Come prepared with:
    • Clear articulation of user problems and opportunities.
    • Evidence from research and experiments.
    • Simple visuals (journeys, OSTs, before/after examples) when helpful.
  • Speak in terms of:
    • Outcomes and trade‑offs.
    • Risk and opportunity, not just UX polish.

Aim to be seen as a trusted advisor, not merely a service provider: someone who helps the group make better decisions and manages change effectively.[web:409][web:410][web:411]


Step 6: Give feedback that grows people and work

As a leader, your feedback should improve both outcomes and confidence.[web:412][web:418]

Guidelines:

  • Be specific and behavioural:
    • Point to concrete examples in the work.
    • Describe impact (“This may confuse users because…”).
  • Balance:
    • Appreciation (what’s working well).
    • Suggestions (where to explore further).
  • Focus on:
    • Alignment with problem, users, and strategy.
    • Risks and trade‑offs rather than purely aesthetic preferences.

Adjust tone for experience level: more directive for juniors, more coaching and questioning for seniors. Use team standards as the reference point, not personal style.[web:412][web:418][web:421]


Step 7: Receive feedback and model growth

Model healthy feedback behaviour by how you receive it.[web:411][web:417]

Practices:

  • Proactively ask for feedback from:
    • Peers.
    • PM and engineering partners.
    • Your own reports.
  • Listen fully before responding; clarify, don’t defend.
  • Reflect and act:
    • Decide what you will change.
    • Share back how you applied feedback, when appropriate.

This builds trust and shows that feedback is a normal part of growth at every level, countering “leadership mediocrity” and keeping standards high.[web:415][web:418][web:417]


Step 8: Build and nurture design culture

Leaders shape the culture of the design team.[web:407][web:412][web:418]

Examples:

  • Encourage:
    • Sharing work early and often.
    • Curiosity about users and other disciplines.
    • Psychological safety in critiques and retros.
  • Support:
    • Reasonable workloads and healthy boundaries.
    • Recognition of contributions, not just outcomes.
  • Embed design thinking beyond the team:
    • Invite cross‑functional partners into research and workshops.
    • Share stories and frameworks that help others think in user‑centred ways.

Culture is reinforced by repeated behaviours; be intentional about the habits you model and reward, and use collab-design-ops-process to encode them into rituals and processes.


Step 9: Grow the next generation of leaders

Use your position to create more leaders, not just more followers.[web:407][web:412][web:416]

Practices:

  • Delegate ownership:
    • Have others lead parts of projects, workshops, or initiatives.
    • Support them publicly, coach them privately.
  • Expose emerging leaders to:
    • Strategy and stakeholder meetings.
    • Cross‑team collaboration opportunities.
  • Help them:
    • Articulate their own point of view.
    • Build networks beyond the design team.

Track their growth over time with tools like skills/competency matrices and mentoring programs, and adjust responsibilities so they can stretch safely.[web:393][web:404][web:416][web:419]


Examples

Example 1: Senior designer shaping a cross-team initiative

  • Situation:
    • Multiple teams created inconsistent onboarding experiences.
  • Leadership:
    • Senior designer led a cross‑team effort to define shared principles and patterns.
    • Partnered with PMs and Eng leads to align on metrics and roadmap impact.
  • Outcomes:
    • Coherent onboarding across products, clearer activation metrics, and a stronger perception of design as a strategic partner.[web:409][web:410][web:412]

Example 2: Mentoring and raising quality bars

  • Situation:
    • Varied quality across design work; juniors unsure what “good” looks like.
  • Leadership:
    • Lead designer created a quality checklist and example gallery.
    • Set up regular mentoring and crits focused on applying these standards.
  • Outcomes:
    • More consistent UX across products and faster growth for juniors, with clearer expectations and feedback loops.[web:412][web:418][web:421][web:416]

Troubleshooting

You feel stuck in execution, not influence

  • Spend more time upstream:
    • Join discovery and strategy discussions.
    • Bring user insights and opportunity framing to PMs and leaders.[web:409][web:411]
  • Take ownership of at least one cross‑team or strategic initiative, even if small.

Mentoring feels ad‑hoc or ineffective

  • Align expectations and goals with mentees explicitly.
  • Add a simple structure (cadence, shared doc, recurring topics).
  • Ask mentees regularly what’s helping and what they’d like more/less of.[web:413][web:416][web:419]

Feedback culture is weak or tense

  • Model the behaviour you want:
    • Ask for feedback, receive it gracefully, and act on it.
    • Give feedback that is specific, kind, and focused on growth.[web:412][web:418]
  • Use team rituals (crits, retros) to normalize constructive feedback and learning, working with collab-design-ops-process.

Notes for use with other skills

  • Use this skill with:
    • collab-design-ops-process to shape rituals, templates, and skill matrices that support leadership and mentoring.
    • collab-stakeholder-communication and collab-ux-engineering to amplify your influence across functions and represent design effectively.
    • Product-thinking, discovery, and metrics skills (product-discovery-opportunity, product-ux-strategy-alignment, ux-product-design-metrics, product-experimentation-data) to bring strong, evidence-based perspectives into strategic forums.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.