First-time setup for uSpec. Prompts for MCP provider and environment (Cursor, Claude Code, Codex), syncs skills to the chosen platform, then configures your Figma template library. Use when the user mentions "firstrun", "first run", "setup", "setup library", "configure templates", or "link templates".
92
88%
Does it follow best practices?
Impact
100%
1.88xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Config file structure and template key mapping
Correct filename
100%
100%
Root location
100%
100%
mcpProvider field
100%
100%
environment field
100%
100%
fontFamily field
100%
100%
templateKeys field
100%
100%
screenReader key
100%
100%
colorAnnotation key
100%
100%
anatomyOverview key
100%
100%
apiOverview key
100%
100%
propertyOverview key
100%
100%
structureSpec key
100%
100%
motionSpec key
100%
100%
Environment-specific skill sync commands
Cursor skips sync
100%
100%
Claude Code sync flag
0%
100%
Codex sync flag
0%
100%
Correct script path
0%
100%
Script not invoked for Cursor
100%
100%
Sync failure guidance
20%
100%
Three environments covered
100%
100%
SETUP.md explains Cursor skip
0%
100%
No invented script names
100%
100%
Both output files present
100%
100%
Figma URL parsing and template search workflow
Standard URL parsing
100%
100%
Branch URL uses branchKey
0%
100%
Console MCP field: componentKey
0%
100%
Native MCP field: key
0%
100%
Output field: screenReader
0%
100%
Output field: colorAnnotation
0%
100%
Output field: anatomyOverview
0%
100%
Output field: apiOverview
0%
100%
Output field: propertyOverview
0%
100%
Output field: structureSpec
0%
100%
Output field: motionSpec
0%
100%
Branch URL test case
25%
100%
Both MCP formats tested
40%
100%
b1213ef
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.