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).
Write a structured design brief for a Figma design task from a product requirement or feature request.
Install Figma Design Brief
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-design-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/figma-design-brief .claude/skills/figma-design-brief && rm -rf skills-srcUse ~/.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/
Install the "figma-design-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-brief into .claude/skills/figma-design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-design-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-design-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/figma-design-brief .agents/skills/figma-design-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "figma-design-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-brief into .agents/skills/figma-design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-design-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-design-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/figma-design-brief .cursor/skills/figma-design-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "figma-design-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-brief into .cursor/skills/figma-design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-design-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/figma-design-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-design-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/figma-design-brief .gemini/skills/figma-design-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "figma-design-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-brief into .gemini/skills/figma-design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-design-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills figma-design-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/figma-design-brief .github/skills/figma-design-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "figma-design-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-brief into .github/skills/figma-design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-design-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills figma-design-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/figma-design-brief .opencode/skills/figma-design-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "figma-design-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/figma-design-brief into .opencode/skills/figma-design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "figma-design-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
figma-design-brief- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 483 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a structured design brief for a Figma design task from a product requirement or feature request.
- Works in 7 steps: Brief Header → What We Are Designing and Why → User Flows to Design → …
- Asked to write a design brief
- SKILL.md covers Required Inputs, Programmatic Helper, Output Structure and Quality Checks, plus 2 more sections
- Calls npx
What it does
Figma Design Brief is an agent skill from mohitagw15856/pm-claude-skills. Write a structured design brief for a Figma design task from a product requirement or feature request. Use when asked to write a design brief, create a design spec for Figma, turn a PRD into design requirements, or brief a designer on what to build in Figma. Produces a brief with goals, scope, user flows, components needed, constraints, and success criteria.
Its SKILL.md is about 1k 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 and UX design. 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 spec for Figma
- Turn a PRD into design requirements
- Brief a designer on what to build in Figma
Example prompts
- “/figma-design-brief”
Requirements
- Node.js
Workflow steps
7 steps, taken from the step headings in SKILL.md.
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
Figma Design Brief loads about 1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 483 words of instructions outside code blocks.
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). 483 words, ~1,046 tokens.
Download SKILL.mdSave it as
.claude/skills/figma-design-brief/SKILL.md (or your agent's skills folder).- name
- figma-design-brief
- description
- Write a structured design brief for a Figma design task from a product requirement or feature request. Use when asked to write a design brief, create a design spec for Figma, turn a PRD into design requirements, or brief a designer on what to build in Figma. Produces a brief with goals, scope, user flows, components needed, constraints, and success criteria.
Figma Design Brief Skill
Converts a product requirement or feature request into a structured design brief — everything a designer needs to open Figma and start building confidently.
Not quite this? Use
figma-design-qawhen the design already exists and you are checking it against the spec.
Required Inputs
- Feature or requirement (paste PRD snippet, ticket, or describe the feature)
- User goal (what is the user trying to accomplish?)
- Platform (iOS / Android / Web / Responsive / All)
- Existing components available (optional)
- Timeline (when does design need to be ready?)
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:
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 viewersnotugly 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.
If the brief specifies colours, state the measured ratio for each intended text/background pairing. A brief that specifies an unreachable pairing wastes a design cycle before anybody notices.
Output Structure
1. Brief Header
Feature, PM, Designer, Platform, Design due, Dev handoff dates.
2. What We Are Designing and Why
- The goal: [One sentence — user problem being solved]
- Context: [2-3 sentences. Why now? What triggers this?]
- Success looks like: [Specific observable outcome]
3. User Flows to Design
Flow N: [Flow name]
- Entry point: [Where user starts]
- Steps: [Numbered key steps]
- Exit point: [Where flow ends]
- Edge cases: [empty state, error state, loading state]
4. Screens Required
| Screen | New / Update | Notes |
|---|---|---|
| [Screen] | New | [Key requirement] |
Show full SKILL.md (194 more words)Show less
5. Components Needed
| Component | In library? | Action |
|---|---|---|
| [Component] | Yes/No/Needs variant | Use/Create/Extend |
6. Constraints and Requirements
- Must haves: [Non-negotiable constraints]
- Must avoid: [Design patterns to not use]
- Accessibility: [WCAG level, touch target sizes]
7. Open Questions
- [Question — with owner]
Quality Checks
- Goal is outcome-focused (not "design the feature")
- All flows include edge cases
- Components table identifies create vs reuse
- Constraints include accessibility requirements
- Open questions have owners
Anti-Patterns
- Do not write a design brief that describes the solution — the brief must describe the problem and constraints, not the design answer
- Do not skip the success criteria — designers need to know what "done" looks like before starting
- Do not omit existing components to reuse — briefs that ignore the design system lead to inconsistent implementations
- Do not leave open questions unresolved — escalate them before design work starts, not during it
- Do not confuse requirements with design instructions — the brief defines what, not how
Example Trigger Phrases
- "Write a design brief for [feature]"
- "Turn this PRD into a Figma design brief"
- "Brief the designer on what to build for [requirement]"
- "Create a design spec for [feature] for Figma"
- "What does the designer need to know to design [feature]?"
© 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/figma-design-brief of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Figma Design 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Figma Design Brief this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Prd To UXragnar-pwninskjold/tech-snacks | 137 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Vscuse Scenario AuthoringOfficeDev/microsoft-365-agents-toolkit | 780 | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Reviewgolbin/agent-skills | 214 | — | ~706 | Automated safety check: Pass | None | |
| Write Product Specbholmesdev/hubble.md | 1.5k | — | ~966 | Automated safety check: Pass | MIT | |
| Prd UX DesignOfficeDev/microsoft-365-agents-toolkit | 780 | — | ~8.1k | Automated safety check: Pass | Custom licence |
Similar skills
Vscuse Scenario Authoring
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: reading a docs scenario, PRD, mockup, or user flow and using vscuse-ui/noVNC as the primary authoring surface to record, generate, replace, or update vscuse test plans…
Review
golbin/agent-skills
Review software designs and implementations for user experience, simplicity, and maintainability; apply fixes when requested.
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
Prd UX Design
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when adding or changing product requirements, scenarios, user flows, surface behavior, or design artifacts before specs or implementation.
Opportunity Assessment
andreaskelm/pm-brain
Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar 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…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
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.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
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.
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.
Related
Works with
Categories
Questions about Figma Design Brief
What does Figma Design Brief do?
Write a structured design brief for a Figma design task from a product requirement or feature request. Figma Design Brief is an agent skill from mohitagw15856/pm-claude-skills. Write a structured design brief for a Figma design task from a product requirement or feature request.
When should I use Figma Design Brief?
Figma Design Brief fits situations like: asked to write a design brief; create a design spec for Figma; turn a PRD into design requirements; brief a designer on what to build in Figma.
How do I install Figma Design Brief in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a claude-code`. Or copy the skill folder (skills/figma-design-brief in mohitagw15856/pm-claude-skills) into .claude/skills/figma-design-brief in your project. Claude Code loads it when a task matches its description.
How do I install Figma Design Brief in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill figma-design-brief -a codex`. Or copy the skill folder (skills/figma-design-brief in mohitagw15856/pm-claude-skills) into .agents/skills/figma-design-brief in your project. Codex loads it when a task matches its description.
Can I use Figma Design 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 figma-design-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/figma-design-brief, .gemini/skills/figma-design-brief, .github/skills/figma-design-brief and .opencode/skills/figma-design-brief in your project.
What does Figma Design Brief need to run?
Going by SKILL.md and its folder, Figma Design Brief needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Figma Design 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 Figma Design 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 Figma Design Brief use?
Figma Design 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 Figma Design Brief use?
About 1k tokens (SKILL.md is roughly 4.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 Figma Design Brief?
Skills that share tags, products or a category with Figma Design Brief: Prd To UX (ragnar-pwninskjold/tech-snacks, 137 stars), Vscuse Scenario Authoring (OfficeDev/microsoft-365-agents-toolkit, 780 stars), Review (golbin/agent-skills, 214 stars) and Write Product Spec (bholmesdev/hubble.md, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Figma Design 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.