SkillsAdd

smithery/neversight

design-spec

Create UI/UX design specifications from requirements or Figma designs.

Installation

$ npx skills add smithery/neversight --skill design-spec
View on skills.sh ↗ Website ↗

Summary

  • Create UI/UX design specifications from requirements or Figma designs.
  • Covers component specs (Atom/Molecule/Organism), accessibility audits (WCAG 2.1 AA), design tokens, responsive behavior, and dev handoffs.
  • Triggers on "design spec", "ui spec", "component spec", "accessibility audit", "design handoff", "design tokens", "wireframe", "mockup".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/neversight · top by installs.

npx skills add smithery/neversight
zoom-meeting 0 ziwei-doushu 0 zimage-skill 0 zig 0 zhimeng-agent 0 zfc 0 zenbin 0 zeberg-salomon-rotator 0 zdev 0 youtube-transcript 0

Browse all from smithery/neversight

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Edit, Grep, Glob, WebSearch, ai-multimodal, mcp__figma__*

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,121 B
  • docs SUMMARY.md 365 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Design Specification

Create comprehensive UI/UX specifications for implementation.

When to Use

  • PBI needs design documentation
  • Figma design ready for handoff
  • Component specification required
  • Accessibility audit needed
  • Design system additions

⚠️ MUST READ References

IMPORTANT: You MUST read these reference files for complete protocol. Do NOT skip.

  • ⚠️ MUST READ references/design-system-reference.md — component specs, accessibility audit template, design tokens, responsive breakpoints, handoff checklist

Workflow

  1. Determine Source Type

- If URL starting with figma.com: treat as direct Figma source - If file path: read file and check for figma_link in frontmatter

  1. Load Source

- Read PBI/requirements file - Parse YAML frontmatter - Extract figma_link field if present

  1. Detect Figma Link

`` Sources (priority order): 1. Direct Figma URL argument 2. frontmatter.figma_link 3. Figma URLs in "Design Reference" section ` Pattern: https?://(?:www\.)?figma\.com/(design|file)/([a-zA-Z0-9]+)(?:/[^?]*)?(?:\?node-id=([0-9]+:[0-9]+))?`

  1. Extract Figma Specs (if link found)

- Call /figma-extract {url} internally - Handle failures gracefully (continue without Figma data)

  1. Define Components (use template from references/design-system-reference.md)

- Type classification: Atom / Molecule / Organism / Template - States: default, hover, active, disabled, error, loading - Design tokens mapping - Accessibility requirements (WCAG 2.1 AA)

  1. Specify Responsive Behavior (breakpoints in reference)
  1. Generate Spec

Structure: Overview, Component Inventory, States, Design Tokens, Accessibility, Responsive, Figma Extracted Specs

  1. Save Artifact

- Path: team-artifacts/design-specs/{YYMMDD}-designspec-{feature}.md

Fallback Behavior

When Figma extraction unavailable:

  1. Log warning: "Figma specs not extracted: {reason}"
  2. Continue with manual spec creation
  3. Leave Section 7 with placeholder text

Design Token Format

$primary: #1976D2;     // Colors
$heading: 24px/1.2 'Inter'; // Typography
$gap-sm: 8px;          // Spacing

Example

/design-spec https://www.figma.com/design/ABC123/UserProfile
/design-spec team-artifacts/pbis/260119-pbi-user-profile.md

Output

Creates: team-artifacts/design-specs/{YYMMDD}-designspec-{feature}.md

IMPORTANT Task Planning Notes

  • Always plan and break many small todo tasks
  • Always add a final review todo task to review the works done at the end to find any fix or enhancement needed