mohitagw15856/figma-component-audit
plugins/pm-figma/skills/figma-component-audit/SKILL.md
Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impact, naming recommendations, and a fix plan.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills figma-component-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 11:56 AM4.4s1 file scanned
SKILL.md
- name:
- figma-component-audit
- description:
- Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impact, naming recommendations, and a fix plan.
Figma Component Audit Skill
Produces a structured audit of a Figma component library — identifying inconsistencies, naming problems, coverage gaps, and prioritised recommendations.
Required Inputs
- Component list or description (paste component names or describe what exists)
- Product type (mobile app / web app / desktop / multi-platform)
- Design system maturity (new / growing / mature / legacy)
- Primary concern (optional)
Output Structure
1. Audit Summary
| Dimension | Status | Score | |---|---|---| | Naming consistency | Red/Amber/Green | /10 | | Component coverage | | /10 | | Variant completeness | | /10 | | Documentation | | /10 | | Overall health | | /10 |
Verdict: What is the state of this library and the single most important thing to fix?
2. Naming Issues
For each problem: Issue: [Problem type]
- What is happening: [Specific examples]
- Why it matters: [Impact on designers and developers]
- Fix: [Exact naming convention to adopt]
- Examples: Before / After
Naming convention to enforce:
- Components: PascalCase (NavigationBar)
- Variants: Lowercase with slashes (size/large, state/hover)
- Pages: All caps (COMPONENTS, FOUNDATIONS)
3. Coverage Gaps
| Missing Component | Priority | Why Needed | |---|---|---| | [Component] | High/Medium/Low | [Use case] |
4. Variant Completeness Check
| Component | Default | Hover | Active | Disabled | Error | Missing | |---|---|---|---|---|---|---| | [Button] | Yes | Yes | No | Yes | No | Active, Error |
5. Prioritised Fix Plan
| # | Fix | Effort | Impact | Do First? | |---|---|---|---|---| | 1 | [Fix] | Low/Med/High | High | Yes |
Quality Checks
- [ ] Naming recommendations have before/after examples
- [ ] Coverage gaps are relevant to the product type
- [ ] Fix plan is ordered by impact-to-effort ratio
- [ ] Variant completeness covers all interactive states
Example Trigger Phrases
- "Audit my Figma component library"
- "Review our design system for consistency issues"
- "What components are we missing in our Figma library?"
- "Our component naming is a mess — help me fix it"
- "Do a health check on our Figma components"
Related Skills
mohitagw15856/viral-content-framework
development
VerifiedTrustedCommunity
Build a framework for creating shareable, high-reach social media content. Use when asked to plan viral content, develop a shareable content strategy, create a hook writing system, or build a repeatable process for content that gets shared. Produces a platform-specific viral content framework with hook formulas, content structures, shareability triggers, and a content testing system.
905SKILL.mdUpdated May 28, 2026
mohitagw15856/thumbnail-creator
development
VerifiedTrustedCommunity
Generate article or newsletter thumbnail candidates using the Gemini API from inside Claude Code. Claude reads article copy, proposes composition concepts, writes image generation prompts incorporating brand specs, calls Gemini to generate the images, evaluates the results via computer vision, and returns ranked candidates with rationale. Use when asked to create thumbnails, generate cover images, or produce visual candidates for an article or newsletter.
905SKILL.mdUpdated May 28, 2026
mohitagw15856/sycophancy-challenger
testing
VerifiedTrustedCommunity
Flips Claude's default from "find reasons you're right" to "find reasons you're wrong." A genuine thinking partner, not a mirror with grammar. Use before high-stakes decisions, plans, assumptions, or pitches you haven't stress-tested.
905SKILL.mdUpdated May 28, 2026
mohitagw15856/substack-notes-scraper
development
VerifiedTrustedCommunity
Scrapes a Substack Notes page and exports engagement data (likes, comments, restacks) to a formatted .xlsx file with conditional formatting and summary stats.
905SKILL.mdUpdated May 28, 2026