CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-swiftui

SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is figma-swiftui in openai/plugins

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an effective lean router: actionable shared context, clear direction routing with an ambiguity checkpoint, and well-organized one-level-deep references. It avoids explaining concepts Claude already knows and keeps every token purposeful.

DimensionReasoningScore

Conciseness

A lean router that assumes Claude's competence — it delegates detail to references and every line earns its place, with no padding explaining concepts Claude already knows.

3 / 3

Actionability

Provides fully executable guidance: exact tool args ('clientLanguages: "swift"', 'clientFrameworks: "swiftui"'), a concrete URL→tool-arg parsing rule, token mappings (Color(.systemBackground), Color.secondary), and named APIs (figma.util.getSfSymbolCharacter(name)).

3 / 3

Workflow Clarity

Sequences the work clearly — pick direction via a table, handle ambiguity with an explicit checkpoint ('ask the user which direction before loading a reference'), then shared context that both reference docs assume.

3 / 3

Progressive Disclosure

Clear overview with two well-signaled, one-level-deep real references (references/design-to-code.md, references/code-to-design.md), each surfaced twice in direction tables — content is appropriately split, navigation is easy.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete bidirectional actions, surfaces natural trigger terms, and gives explicit 'use when' guidance with distinguishing contextual signals. It is concise for the breadth it covers.

DimensionReasoningScore

Specificity

Lists multiple concrete bidirectional actions — 'translating a Figma design into SwiftUI (design → code)' and 'pushing SwiftUI views / screens / tokens back into a Figma file (code → design)' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (bidirectional Figma↔SwiftUI translation, routing to direction-specific docs) and when ('Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad') with concrete trigger phrases.

3 / 3

Trigger Term Quality

Covers natural terms users would say ('Swift, SwiftUI, iOS, iPhone, or iPad') plus contextual triggers ('Figma URL appears alongside .swift files / an .xcodeproj') and natural phrases like 'implement this Figma design in SwiftUI'.

3 / 3

Distinctiveness Conflict Risk

Clear niche at the Figma↔SwiftUI intersection with distinct bidirectional triggers and file-type co-occurrence signals, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
Devin-AXIS/iPolloWork
Reviewed

Table of Contents

Is this your skill?

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.