CD 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.
Promises bidirectional translation between Figma and SwiftUI: design to code and back. Triggers on Swift, iOS, iPhone, iPad mentions and Figma URLs next to `.swift` files. Three files in the folder, but broken references outnumber working ones—half the resources are simply missing. Content quality scores 72/100, process execution 42/100. Never tested on models, never run in sandbox. Requires Figma API and SwiftUI context already set up separately; the skill itself is just a router with gaps.
Install if you already have a working Figma + Swift project and just need a trigger to switch between paths. If you expect full sync—you'll be disappointed: half the links go nowhere, nothing's been tested.
SwiftUI ↔ Figma translation.
As a process D 42/100 · Unfinished process — References files that are not bundled: ../figma-use/SKILL.md, ../figma-generate-design/SKILL.md, ../figma-generate-library/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../figma-use/SKILL.md - warning
missing-refreference to a missing file: ../figma-generate-design/SKILL.md - warning
missing-refreference to a missing file: ../figma-generate-library/SKILL.md
Process rating: all ten parameters 42/100
- 0Tools and files. 3 referenced file(s) missing: ../figma-use/SKILL.md, ../figma-generate-design/SKILL.md, ../figma-generate-library/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 6 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 829 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 611: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 6 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.