New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Design Handoff Brief

by mohitagw15856 in mohitagw15856/pm-claude-skills

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma.

MITAuto-check passedProduct & Project Management

Install Design Handoff Brief

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill design-handoff-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills design-handoff-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/design-handoff-brief .claude/skills/design-handoff-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-handoff-brief
GitHub stars
1.4k
Token cost
~1.3k tokens
SKILL.md length
663 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma.

  • Works in 7 steps: Read the feature brief or PRD provided → Extract user goal (reframe from feature… → Identify constraints — technical… → …
  • Asked to write a design brief
  • SKILL.md covers Required Inputs, What Designers Actually Need…, Process and Programmatic Helper, plus 4 more sections
  • Calls npx

What it does

Design Handoff Brief is an agent skill from mohitagw15856/pm-claude-skills. Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. It works with Figma. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a design brief
  • Create a design handoff
  • Brief a designer on a new feature
  • Translate a PRD into design requirements

Example prompts

  • “/design-handoff-brief”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read the feature brief or PRD provided
  2. Extract user goal (reframe from feature language to user outcome language)
  3. Identify constraints — technical limitations, brand guidelines, accessibility requirements
  4. List edge cases the design must handle
  5. Define success criteria the design should be evaluated against
  6. Write a "not in scope" section to prevent scope creep in design
  7. Validate — Confirm every edge case listed is specific enough to design for, and every out-of-scope item is concrete enough to say "no" to

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design Handoff Brief loads about 1.3k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 663 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 663 words, ~1,297 tokens.

Download SKILL.mdSave it as .claude/skills/design-handoff-brief/SKILL.md (or your agent's skills folder).
name
design-handoff-brief
description
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.

Design Handoff Brief Skill

Produce a design brief that sets designers up for success — grounding them in user context and constraints before they open Figma, not after they've gone in the wrong direction.

Required Inputs

Ask the user for these if not provided:

  • Feature brief or PRD (even rough notes work)
  • Designer's name or team (for personalisation)
  • Technical constraints (any engineering limitations already known)
  • Timeline (when does design need to be done?)

What Designers Actually Need (and PMs Often Skip)

  • The user's goal, not the feature name
  • The emotional state of the user at this moment in the journey
  • What success looks like — how will we know the design worked?
  • Constraints: technical, legal, brand, accessibility
  • Edge cases that must be handled
  • What we're explicitly NOT solving for

Process

  1. Read the feature brief or PRD provided
  2. Extract user goal (reframe from feature language to user outcome language)
  3. Identify constraints — technical limitations, brand guidelines, accessibility requirements
  4. List edge cases the design must handle
  5. Define success criteria the design should be evaluated against
  6. Write a "not in scope" section to prevent scope creep in design
  7. Validate — Confirm every edge case listed is specific enough to design for, and every out-of-scope item is concrete enough to say "no" to

Programmatic Helper

Contrast ratios cannot be eyeballed. The AA line sits at 4.5:1, and #777777 on white is 4.478 (fails) while #767676 is 4.54 (passes) — no amount of looking at a screenshot separates those. Compute them:

bash
npx --yes notugly fix "#8ab4f8" "#ffffff"     # ratio, APCA, and the nearest passing colour
npx --yes notugly onepager <url> --out review.html   # every pairing, printable
npx --yes notugly vision                      # which colours merge for colour-blind viewers

notugly fix returns the ratio, the APCA lightness contrast, and the closest colour to the one already chosen that passes — same hue, same chroma. Paste those numbers into the tables below rather than estimating them.

Deterministic, zero dependencies, and no model call — so it costs nothing to run and gives the same answer every time.

Handoff is exactly where contrast gets lost: a designer picks a colour in a tool with no contrast checker, and an engineer implements it faithfully. Put the measured ratio next to every colour in the handoff table so the number travels with the value.

Output Structure

Show full SKILL.md (314 more words)Show less
Design Brief: [Feature Name]

User Goal: (in the user's words, not ours) "When I [situation], I want to [motivation] so that I can [outcome]."

Context & Emotional State: [Where is the user in their journey? What are they feeling? What just happened?]

Design Success Criteria:

  • [Criterion 1 — measurable where possible]
  • [Criterion 2]
  • [Criterion 3]

Constraints:

  • Technical: [limitations engineering has flagged]
  • Brand: [relevant brand guidelines]
  • Accessibility: [WCAG level required, any specific requirements]
  • Legal/Compliance: [if applicable]

Edge Cases to Design For:

  • [Edge case 1]
  • [Edge case 2]
  • [Edge case 3]

Explicitly Out of Scope:

  • [What we are NOT solving in this design iteration]

Reference Material:

  • User research: [link]
  • Existing patterns: [Figma component library link]
  • Competitor examples: [links if relevant]

Quality Checks

  • User goal is written in user language (not feature/product language)
  • At least one edge case covers an error or failure state
  • Success criteria are measurable or observable (not "looks good")
  • Out-of-scope section names at least one thing that might seem in scope but isn't
  • Technical constraints are specific enough for an engineer to confirm

Anti-Patterns

  • Do not write the user goal in feature language ("design the checkout flow") — it must be written from the user's perspective with a motivation and outcome
  • Do not skip the "Explicitly Out of Scope" section — without it, designers will inadvertently solve problems not intended for this iteration
  • Do not list edge cases that are so generic they apply to any feature (e.g. "handle errors") — each edge case must be specific to this feature's failure modes
  • Do not hand off the brief without confirming engineering constraints are accurate — a constraint that is wrong is worse than no constraint
  • Do not omit the emotional context of the user — designs without emotional grounding produce technically correct but experientially flat results

Example Trigger Phrases

  • "Write a design brief."
  • "Create a design handoff."
  • "Brief a designer on a new feature."
  • "Translate a PRD into design requirements."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/design-handoff-brief of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Design Handoff Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design Handoff Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design Handoff Brief this skillmohitagw15856/pm-claude-skills1.4k—~1.3kAutomated safety check: PassMIT
Prd To UXragnar-pwninskjold/tech-snacks137—~1.3kAutomated safety check: PassMIT
Experience Lwc Design Generateforcedotcom/sf-skills1.1k—~4kAutomated safety check: PassApache-2.0
Write Product SpecTerry-Mao/AICodingFlow167—~818Automated safety check: PassMIT
Spec App Consistency Auditleo-kuang-ai/spec-first107—~4.6kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Prd To UX

    ragnar-pwninskjold/tech-snacks

    A skill your agent uses when translating a PRD, feature spec, or raw product idea into screen-level prompts for web UX generators (Google Stitch, Figma AI, Pencil.dev, Claude Design, v0, or similar).

    137 GitHub stars~1.3k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Experience Lwc Design Generate

    forcedotcom/sf-skills

    A skill your agent uses when you need to create a brand new Lightning Web Component from a Figma design, a Product Requirements Document, or another design artifact — orchestrating the five-phase…

    1.1k GitHub stars~4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Write Product Spec

    Terry-Mao/AICodingFlow

    Write a behavior-focused product spec for a significant or ambiguous feature in this repository.

    167 GitHub stars~818 tokensUpdated 7 days ago
    Product & Project ManagementAuto-check passed

  • Spec App Consistency Audit

    leo-kuang-ai/spec-first

    Audit mobile App PRD/Figma/local-source consistency across page routes, KMP/Clean Architecture, components, analytics, i18n, engineering quality, and industry lenses before runtime validation; use…

    107 GitHub stars~4.6k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Design Handoff Brief

What does Design Handoff Brief do?

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Design Handoff Brief is an agent skill from mohitagw15856/pm-claude-skills. Transform feature briefs into structured design briefs that give designers the context they need before opening Figma.

When should I use Design Handoff Brief?

Design Handoff Brief fits situations like: asked to write a design brief; create a design handoff; brief a designer on a new feature; translate a PRD into design requirements.

How do I install Design Handoff Brief in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill design-handoff-brief -a claude-code`. Or copy the skill folder (skills/design-handoff-brief in mohitagw15856/pm-claude-skills) into .claude/skills/design-handoff-brief in your project. Claude Code loads it when a task matches its description.

How do I install Design Handoff Brief in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill design-handoff-brief -a codex`. Or copy the skill folder (skills/design-handoff-brief in mohitagw15856/pm-claude-skills) into .agents/skills/design-handoff-brief in your project. Codex loads it when a task matches its description.

Can I use Design Handoff Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill design-handoff-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-handoff-brief, .gemini/skills/design-handoff-brief, .github/skills/design-handoff-brief and .opencode/skills/design-handoff-brief in your project.

What does Design Handoff Brief need to run?

Going by SKILL.md and its folder, Design Handoff Brief needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Design Handoff Brief access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Design Handoff Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design Handoff Brief use?

Design Handoff Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design Handoff Brief use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design Handoff Brief?

Skills that share tags, products or a category with Design Handoff Brief: Prd To UX (ragnar-pwninskjold/tech-snacks, 137 stars), Experience Lwc Design Generate (forcedotcom/sf-skills, 1.1k stars), Write Product Spec (Terry-Mao/AICodingFlow, 167 stars) and Spec App Consistency Audit (leo-kuang-ai/spec-first, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design Handoff Brief?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.