[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DP5TFKRPCZM08R036HD3R":3,"skill-same:01M79DP5TFKRPCZM08R036HD3R":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79DP5TFKRPCZM08R036HD3R","figma-swiftui",null,"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 \u002F screens \u002F 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 \u002F an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Ffigma-swiftui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: figma-swiftui\ndescription: \"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 \u002F screens \u002F 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 \u002F an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.\"\ndisable-model-invocation: false\n---\n\n# Figma ↔ SwiftUI\n\nTranslation between Figma designs and SwiftUI code, both directions. This file is a router — actual guidance lives in the references below.\n\n## Pick the direction\n\n| Direction | Trigger | Reference |\n|---|---|---|\n| **Design → code** | User wants SwiftUI in their iOS project from a Figma file\u002Fframe | [references\u002Fdesign-to-code.md](references\u002Fdesign-to-code.md) |\n| **Code → design** | User wants to push SwiftUI views \u002F screens \u002F tokens into a Figma file | [references\u002Fcode-to-design.md](references\u002Fcode-to-design.md) |\n\nIf the request is ambiguous — a Figma URL and `.swift` files both present, no verb makes it clear — ask the user which direction before loading a reference.\n\n## Shared context (applies to both directions)\n\nThese points hold regardless of direction; the direction-specific references assume them.\n\n1. **`get_design_context` is the read tool for Figma.** Pass `clientLanguages: \"swift\"` and `clientFrameworks: \"swiftui\"` so the response is framed as Swift. URL → tool args: `figma.com\u002Fdesign\u002F:fileKey\u002F:fileName?node-id=:nodeId` → use `fileKey`, replace `-` with `:` in `nodeId`. For `figma.com\u002Fdesign\u002F:fileKey\u002Fbranch\u002F:branchKey\u002F:fileName`, use `branchKey` as `fileKey`.\n2. **The React+Tailwind in `get_design_context` output is a structural reference, not a literal source.** It approximates the visual. Never transliterate `position: absolute` \u002F pixel frames \u002F `mix-blend-mode` stacks into SwiftUI or into Figma — the screenshot is the source of truth in both directions.\n3. **iOS HIG semantic colors are tokens, not hex.** `var(--backgrounds\u002Fprimary, …)`, `var(--labels\u002Fsecondary, …)`, `var(--separators\u002Fnon-opaque, …)` etc. map to `Color(.systemBackground)`, `Color.secondary`, `Color(.separator)` in SwiftUI, and to variables in a semantic collection in Figma. Keep the mapping; drop the literal RGBA.\n4. **SF Symbols round-trip by name in both directions — never by codepoint.** Design → code: `get_design_context` substitutes Figma's SF Symbol glyph runs back into `\u003CSFSymbol>{Image(systemName: \"...\")}\u003C\u002FSFSymbol>` wrappers in the response. Use those names verbatim. Code → design: call `figma.util.getSfSymbolCharacter(name)` inside `use_figma` to convert a symbol name to the matching character — never look up codepoints by hand.\n5. **Recognize the underlying iOS pattern, not the literal node \u002F view name.** The same patterns recur in both directions: large title + back chevron + trailing action = `NavigationStack` chrome; bottom row of icon+label pairs = `TabView`; repeating same-height rows with leading\u002Ftrailing chrome = `List`. Match those system patterns rather than rebuilding them from primitives.\n6. **For code → design, `use_figma` is the API.** Always load [`figma-use`](..\u002Ffigma-use\u002FSKILL.md) before any `use_figma` call. If the task involves building a full screen, also load [`figma-generate-design`](..\u002Ffigma-generate-design\u002FSKILL.md); if it involves building components or a design system, also load [`figma-generate-library`](..\u002Ffigma-generate-library\u002FSKILL.md).\n\n## References\n\n| Doc | When to load |\n|---|---|\n| [references\u002Fdesign-to-code.md](references\u002Fdesign-to-code.md) | Translating a Figma design \u002F frame into SwiftUI |\n| [references\u002Fcode-to-design.md](references\u002Fcode-to-design.md) | Pushing SwiftUI views \u002F screens \u002F tokens into Figma |\n","# Figma ↔ SwiftUI\n\nTranslation between Figma designs and SwiftUI code, both directions. This file is a router — actual guidance lives in the references below.\n\n## Pick the direction\n\n| Direction | Trigger | Reference |\n|---|---|---|\n| **Design → code** | User wants SwiftUI in their iOS project from a Figma file\u002Fframe | [references\u002Fdesign-to-code.md](references\u002Fdesign-to-code.md) |\n| **Code → design** | User wants to push SwiftUI views \u002F screens \u002F tokens into a Figma file | [references\u002Fcode-to-design.md](references\u002Fcode-to-design.md) |\n\nIf the request is ambiguous — a Figma URL and `.swift` files both present, no verb makes it clear — ask the user which direction before loading a reference.\n\n## Shared context (applies to both directions)\n\nThese points hold regardless of direction; the direction-specific references assume them.\n\n1. **`get_design_context` is the read tool for Figma.** Pass `clientLanguages: \"swift\"` and `clientFrameworks: \"swiftui\"` so the response is framed as Swift. URL → tool args: `figma.com\u002Fdesign\u002F:fileKey\u002F:fileName?node-id=:nodeId` → use `fileKey`, replace `-` with `:` in `nodeId`. For `figma.com\u002Fdesign\u002F:fileKey\u002Fbranch\u002F:branchKey\u002F:fileName`, use `branchKey` as `fileKey`.\n2. **The React+Tailwind in `get_design_context` output is a structural reference, not a literal source.** It approximates the visual. Never transliterate `position: absolute` \u002F pixel frames \u002F `mix-blend-mode` stacks into SwiftUI or into Figma — the screenshot is the source of truth in both directions.\n3. **iOS HIG semantic colors are tokens, not hex.** `var(--backgrounds\u002Fprimary, …)`, `var(--labels\u002Fsecondary, …)`, `var(--separators\u002Fnon-opaque, …)` etc. map to `Color(.systemBackground)`, `Color.secondary`, `Color(.separator)` in SwiftUI, and to variables in a semantic collection in Figma. Keep the mapping; drop the literal RGBA.\n4. **SF Symbols round-trip by name in both directions — never by codepoint.** Design → code: `get_design_context` substitutes Figma's SF Symbol glyph runs back into `\u003CSFSymbol>{Image(systemName: \"...\")}\u003C\u002FSFSymbol>` wrappers in the response. Use those names verbatim. Code → design: call `figma.util.getSfSymbolCharacter(name)` inside `use_figma` to convert a symbol name to the matching character — never look up codepoints by hand.\n5. **Recognize the underlying iOS pattern, not the literal node \u002F view name.** The same patterns recur in both directions: large title + back chevron + trailing action = `NavigationStack` chrome; bottom row of icon+label pairs = `TabView`; repeating same-height rows with leading\u002Ftrailing chrome = `List`. Match those system patterns rather than rebuilding them from primitives.\n6. **For code → design, `use_figma` is the API.** Always load [`figma-use`](..\u002Ffigma-use\u002FSKILL.md) before any `use_figma` call. If the task involves building a full screen, also load [`figma-generate-design`](..\u002Ffigma-generate-design\u002FSKILL.md); if it involves building components or a design system, also load [`figma-generate-library`](..\u002Ffigma-generate-library\u002FSKILL.md).\n\n## References\n\n| Doc | When to load |\n|---|---|\n| [references\u002Fdesign-to-code.md](references\u002Fdesign-to-code.md) | Translating a Figma design \u002F frame into SwiftUI |\n| [references\u002Fcode-to-design.md](references\u002Fcode-to-design.md) | Pushing SwiftUI views \u002F screens \u002F tokens into Figma |\n",{"name":5,"description":7,"disable-model-invocation":20},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Ffigma-swiftui","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill figma-swiftui",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill figma-swiftui",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill figma-swiftui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Ffigma-swiftui\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcode-to-design.md","REFERENCE","参考文档",18991,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Ffigma-swiftui\u002Freferences\u002Fcode-to-design.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdesign-to-code.md",37329,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Ffigma-swiftui\u002Freferences\u002Fdesign-to-code.md",[56,63,70,77,86,93],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]