[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75B1PCSDK9ED7YN51TYZHSC":3,"skill-same:01M75B1PCSDK9ED7YN51TYZHSC":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75B1PCSDK9ED7YN51TYZHSC","missing-protections",null,"A checklist of protections that should be present in a contract but are absent entirely — the gaps a clause-by-clause review misses because there is no clause to flag. Use when reviewing an NDA, services agreement or MSA, DPA, or employment agreement and asked what is missing, what gaps exist, or whether the document adequately protects a party.","sure-scale\u002Fdoc-haus","sure-scale","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F282511471?v=4","01M75B01D5K1FE0HVC061PM46S","01M75B01E8V6PACDS15PW1JQK0",82,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fdochaus\u002Fskill\u002Fmissing-protections\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: missing-protections\ndescription: A checklist of protections that should be present in a contract but are absent entirely — the gaps a clause-by-clause review misses because there is no clause to flag. Use when reviewing an NDA, services agreement or MSA, DPA, or employment agreement and asked what is missing, what gaps exist, or whether the document adequately protects a party.\n---\n\nReviewing what a contract says is not the same as reviewing what it omits. A\none-sided clause is visible on the page; a missing limitation of liability is\ninvisible until it matters. After any clause-level review, walk the checklist\nfor the contract's type and report every expected protection that is absent.\n\nThese checklists are commercial-market reference points, not legal standards —\nwhat is \"expected\" varies by jurisdiction, deal size, and bargaining position.\nEstablish the governing law and which party the firm represents first, and\nqualify any finding that depends on either.\n\nMethod: build the checklist for the contract's type as an explicit list with\nthe `todowrite` tool — one item per expected protection — so the absence sweep\nis exhaustive and no expected protection is skipped (recall is what this sweep\nexists to protect). For each item, search the whole document — protections hide\nin schedules, definitions, and annexes, not just the obvious section — then mark\nthe item `completed` with its verdict (present \u002F partial \u002F missing). Report an\nitem as missing only when no provision anywhere covers it; if a provision\npartially covers it, that is a weak-clause finding for the clause review, not\na gap. Cite the absence as `[\u003CDocument> — no provision found]` and cite\npartial coverage as `[\u003CDocument> § \u003Csection>]`.\n\n\u003Cnda>\n- **Return or destruction of confidential information** — without it, the\n  recipient may keep disclosed materials indefinitely after the relationship\n  ends. Ask for: an obligation to return or destroy on request or termination,\n  with certification on request.\n- **Term and survival of confidentiality** — with no stated duration, the\n  parties dispute how long protection lasts; trade secrets typically need\n  protection for as long as they remain secret. Ask for: a defined\n  confidentiality period, with trade secrets protected for as long as they\n  qualify.\n- **Standard exclusions** — without the customary carve-outs (already known,\n  independently developed, publicly available, rightfully received from a\n  third party), the recipient breaches by using information it already had.\n  Ask for: the standard exclusions from the definition of confidential\n  information.\n- **Compelled-disclosure procedure** — without it, a subpoena forces the\n  recipient to choose between breaching the NDA and defying legal process.\n  Ask for: permission to disclose when legally required, with prompt notice\n  to the discloser where lawful and cooperation on protective measures.\n- **No-license \u002F no-obligation clause** — without it, the counterparty may\n  argue the disclosure implied IP rights or a duty to transact. Ask for: a\n  statement that no license is granted and neither party is obliged to\n  proceed with any transaction.\n- **Equitable relief acknowledgment** — damages are hard to prove for\n  information leaks; without it, stopping an imminent disclosure is slower.\n  Ask for: acknowledgment that breach may cause irreparable harm and that the\n  discloser may seek injunctive relief (availability is jurisdiction- and\n  court-dependent).\n\u003C\u002Fnda>\n\n\u003Cservices-msa>\n- **Limitation of liability** — an MSA with no liability cap exposes each\n  party to uncapped damages for any breach; a cap is standard commercial\n  practice in most markets. Ask for: a mutual cap (commonly tied to fees\n  paid or payable over a defined period) with negotiated carve-outs.\n- **Consequential-damages exclusion** — without it, lost profits and other\n  indirect losses are in play for ordinary breaches. Ask for: a mutual\n  waiver of indirect and consequential damages, subject to the same\n  carve-outs as the cap.\n- **Indemnification** — with no indemnity, third-party claims caused by one\n  party (IP infringement by deliverables, bodily injury, breach of law) land\n  on whichever party gets sued. Ask for: indemnities matched to each party's\n  risks, at minimum provider IP-infringement indemnity for the deliverables.\n- **Intellectual property ownership** — silence on work product leaves\n  ownership to default law, which differs by jurisdiction and often surprises\n  the paying party. Ask for: an express allocation — assignment or license of\n  deliverables, each party retaining its pre-existing IP.\n- **Termination rights** — a contract with no termination clause may lock the\n  parties in for the full term regardless of nonperformance. Ask for:\n  termination for material breach with notice and cure, and the negotiated\n  position on termination for convenience.\n- **Effect of termination** — without wind-down terms, the parties dispute\n  fees, data return, and transition at the worst possible moment. Ask for:\n  payment for work performed, return of materials and data, and survival of\n  the clauses meant to outlast the contract.\n- **Warranties and service standards** — with no performance warranty, the\n  customer's remedy for bad work is a general breach claim with no defined\n  standard. Ask for: a workmanlike-performance or conformance-to-spec\n  warranty with a defined remedy.\n- **Insurance** — without required coverage, an indemnity is only as good as\n  the counterparty's balance sheet. Ask for: insurance requirements\n  proportionate to the engagement's risk.\n- **Confidentiality** — an MSA with no confidentiality clause leaves pricing,\n  data, and know-how exchanged under it unprotected. Ask for: a mutual\n  confidentiality clause or incorporation of an existing NDA.\n- **Dispute resolution and governing law** — silence forces a conflict-of-laws\n  fight before the merits. Ask for: express governing law and forum (or\n  arbitration), chosen deliberately rather than defaulted.\n\u003C\u002Fservices-msa>\n\n\u003Cdpa>\n- **Breach-notification deadline** — \"without undue delay\" alone gives the\n  controller nothing to enforce, while the controller may face fixed\n  regulatory deadlines (under GDPR\u002FUK GDPR regimes, the controller generally\n  must notify its authority within a short fixed window). Ask for: processor\n  notification within a defined short period after becoming aware of a\n  personal-data breach, with cooperation and required details.\n- **Processing instructions limitation** — without it, the document fails the\n  basic controller-processor allocation. Ask for: processing only on the\n  controller's documented instructions, with a notice obligation if an\n  instruction appears unlawful.\n- **Subprocessor controls** — without consent or notice rights, the controller\n  cannot manage where its data goes. Ask for: prior authorization (general or\n  specific) for subprocessors, an obligation to flow down equivalent terms,\n  and processor liability for subprocessor acts.\n- **Security measures** — a DPA with no security schedule has no enforceable\n  baseline. Ask for: defined technical and organizational measures\n  appropriate to the risk, referenced in an annex.\n- **International-transfer mechanism** — under GDPR\u002FUK GDPR-style regimes,\n  transfers to third countries need a lawful mechanism; silence leaves the\n  controller non-compliant. Ask for: an approved transfer mechanism (such as\n  standard contractual clauses or an equivalent) where transfers occur.\n- **Audit and information rights** — without them, the controller cannot\n  demonstrate compliance to its regulator. Ask for: information and audit\n  rights, commonly satisfied first by certifications or third-party reports.\n- **Data-subject-request assistance** — the controller answers requests on\n  statutory clocks but the processor holds the data. Ask for: an obligation\n  to assist with data-subject requests and to forward requests received\n  directly.\n- **Return or deletion on termination** — without it, personal data persists\n  after the engagement with no lawful basis. Ask for: deletion or return of\n  personal data at the controller's choice on termination, with certification.\n- **Confidentiality of processing personnel** — without it, the processor's\n  staff are outside the protection chain. Ask for: a commitment that persons\n  processing the data are bound by confidentiality obligations.\n\u003C\u002Fdpa>\n\n\u003Cemployment>\n- **Confidentiality and trade-secret protection** — without it, the employer\n  relies solely on background law, which varies by jurisdiction and is harder\n  to enforce than an express obligation. Ask for: a confidentiality clause\n  surviving termination.\n- **IP and invention assignment** — without express assignment, ownership of\n  employee-created work depends on default rules that differ by jurisdiction\n  and work type. Ask for: assignment of work-related inventions and works,\n  subject to any statutory employee-invention protections in the governing\n  jurisdiction.\n- **Termination notice and severance terms** — silence leaves both parties to\n  statutory or at-will defaults that may not match expectations. Ask for:\n  express notice periods or severance terms (statutory minimums in many\n  jurisdictions override anything less).\n- **Post-termination restrictive covenants** — if the role justifies them and\n  none exist, the employer has no protection against immediate competition or\n  solicitation. Ask for: non-solicitation (and non-compete only where the\n  governing jurisdiction enforces them — enforceability varies sharply and\n  several jurisdictions restrict or void them), drafted to local\n  reasonableness standards.\n- **Compensation completeness** — an offer silent on bonus terms, equity\n  vesting, or benefits invites disputes over what was promised. Ask for:\n  express terms for every compensation element referenced or promised,\n  including treatment on termination.\n- **Dispute-resolution terms** — silence defaults to local courts and rules;\n  arbitration clauses and jury waivers are enforceable in some jurisdictions\n  and restricted in others. Ask for: a deliberate choice, validated against\n  the governing jurisdiction's employment-law limits.\n\u003C\u002Femployment>\n\n\u003Coutput>\nReport gaps separately from clause-level findings, one row per missing\nprotection:\n\n| Protection | Status | Why it matters here | Suggested request |\n|---|---|---|---|\n\nStatus is **missing** (no provision anywhere) or **partial** (cite the\nsection and hand it to the clause review). \"Why it matters here\" must be\nspecific to this contract and party, not the generic rationale above. The\nsuggested request is the one-line ask to send the counterparty. Order rows by\nconsequence to the represented party, and mark any item whose importance or\nenforceability depends on the governing law as jurisdiction-dependent.\n\u003C\u002Foutput>\n","Reviewing what a contract says is not the same as reviewing what it omits. A\none-sided clause is visible on the page; a missing limitation of liability is\ninvisible until it matters. After any clause-level review, walk the checklist\nfor the contract's type and report every expected protection that is absent.\n\nThese checklists are commercial-market reference points, not legal standards —\nwhat is \"expected\" varies by jurisdiction, deal size, and bargaining position.\nEstablish the governing law and which party the firm represents first, and\nqualify any finding that depends on either.\n\nMethod: build the checklist for the contract's type as an explicit list with\nthe `todowrite` tool — one item per expected protection — so the absence sweep\nis exhaustive and no expected protection is skipped (recall is what this sweep\nexists to protect). For each item, search the whole document — protections hide\nin schedules, definitions, and annexes, not just the obvious section — then mark\nthe item `completed` with its verdict (present \u002F partial \u002F missing). Report an\nitem as missing only when no provision anywhere covers it; if a provision\npartially covers it, that is a weak-clause finding for the clause review, not\na gap. Cite the absence as `[\u003CDocument> — no provision found]` and cite\npartial coverage as `[\u003CDocument> § \u003Csection>]`.\n\n\u003Cnda>\n- **Return or destruction of confidential information** — without it, the\n  recipient may keep disclosed materials indefinitely after the relationship\n  ends. Ask for: an obligation to return or destroy on request or termination,\n  with certification on request.\n- **Term and survival of confidentiality** — with no stated duration, the\n  parties dispute how long protection lasts; trade secrets typically need\n  protection for as long as they remain secret. Ask for: a defined\n  confidentiality period, with trade secrets protected for as long as they\n  qualify.\n- **Standard exclusions** — without the customary carve-outs (already known,\n  independently developed, publicly available, rightfully received from a\n  third party), the recipient breaches by using information it already had.\n  Ask for: the standard exclusions from the definition of confidential\n  information.\n- **Compelled-disclosure procedure** — without it, a subpoena forces the\n  recipient to choose between breaching the NDA and defying legal process.\n  Ask for: permission to disclose when legally required, with prompt notice\n  to the discloser where lawful and cooperation on protective measures.\n- **No-license \u002F no-obligation clause** — without it, the counterparty may\n  argue the disclosure implied IP rights or a duty to transact. Ask for: a\n  statement that no license is granted and neither party is obliged to\n  proceed with any transaction.\n- **Equitable relief acknowledgment** — damages are hard to prove for\n  information leaks; without it, stopping an imminent disclosure is slower.\n  Ask for: acknowledgment that breach may cause irreparable harm and that the\n  discloser may seek injunctive relief (availability is jurisdiction- and\n  court-dependent).\n\u003C\u002Fnda>\n\n\u003Cservices-msa>\n- **Limitation of liability** — an MSA with no liability cap exposes each\n  party to uncapped damages for any breach; a cap is standard commercial\n  practice in most markets. Ask for: a mutual cap (commonly tied to fees\n  paid or payable over a defined period) with negotiated carve-outs.\n- **Consequential-damages exclusion** — without it, lost profits and other\n  indirect losses are in play for ordinary breaches. Ask for: a mutual\n  waiver of indirect and consequential damages, subject to the same\n  carve-outs as the cap.\n- **Indemnification** — with no indemnity, third-party claims caused by one\n  party (IP infringement by deliverables, bodily injury, breach of law) land\n  on whichever party gets sued. Ask for: indemnities matched to each party's\n  risks, at minimum provider IP-infringement indemnity for the deliverables.\n- **Intellectual property ownership** — silence on work product leaves\n  ownership to default law, which differs by jurisdiction and often surprises\n  the paying party. Ask for: an express allocation — assignment or license of\n  deliverables, each party retaining its pre-existing IP.\n- **Termination rights** — a contract with no termination clause may lock the\n  parties in for the full term regardless of nonperformance. Ask for:\n  termination for material breach with notice and cure, and the negotiated\n  position on termination for convenience.\n- **Effect of termination** — without wind-down terms, the parties dispute\n  fees, data return, and transition at the worst possible moment. Ask for:\n  payment for work performed, return of materials and data, and survival of\n  the clauses meant to outlast the contract.\n- **Warranties and service standards** — with no performance warranty, the\n  customer's remedy for bad work is a general breach claim with no defined\n  standard. Ask for: a workmanlike-performance or conformance-to-spec\n  warranty with a defined remedy.\n- **Insurance** — without required coverage, an indemnity is only as good as\n  the counterparty's balance sheet. Ask for: insurance requirements\n  proportionate to the engagement's risk.\n- **Confidentiality** — an MSA with no confidentiality clause leaves pricing,\n  data, and know-how exchanged under it unprotected. Ask for: a mutual\n  confidentiality clause or incorporation of an existing NDA.\n- **Dispute resolution and governing law** — silence forces a conflict-of-laws\n  fight before the merits. Ask for: express governing law and forum (or\n  arbitration), chosen deliberately rather than defaulted.\n\u003C\u002Fservices-msa>\n\n\u003Cdpa>\n- **Breach-notification deadline** — \"without undue delay\" alone gives the\n  controller nothing to enforce, while the controller may face fixed\n  regulatory deadlines (under GDPR\u002FUK GDPR regimes, the controller generally\n  must notify its authority within a short fixed window). Ask for: processor\n  notification within a defined short period after becoming aware of a\n  personal-data breach, with cooperation and required details.\n- **Processing instructions limitation** — without it, the document fails the\n  basic controller-processor allocation. Ask for: processing only on the\n  controller's documented instructions, with a notice obligation if an\n  instruction appears unlawful.\n- **Subprocessor controls** — without consent or notice rights, the controller\n  cannot manage where its data goes. Ask for: prior authorization (general or\n  specific) for subprocessors, an obligation to flow down equivalent terms,\n  and processor liability for subprocessor acts.\n- **Security measures** — a DPA with no security schedule has no enforceable\n  baseline. Ask for: defined technical and organizational measures\n  appropriate to the risk, referenced in an annex.\n- **International-transfer mechanism** — under GDPR\u002FUK GDPR-style regimes,\n  transfers to third countries need a lawful mechanism; silence leaves the\n  controller non-compliant. Ask for: an approved transfer mechanism (such as\n  standard contractual clauses or an equivalent) where transfers occur.\n- **Audit and information rights** — without them, the controller cannot\n  demonstrate compliance to its regulator. Ask for: information and audit\n  rights, commonly satisfied first by certifications or third-party reports.\n- **Data-subject-request assistance** — the controller answers requests on\n  statutory clocks but the processor holds the data. Ask for: an obligation\n  to assist with data-subject requests and to forward requests received\n  directly.\n- **Return or deletion on termination** — without it, personal data persists\n  after the engagement with no lawful basis. Ask for: deletion or return of\n  personal data at the controller's choice on termination, with certification.\n- **Confidentiality of processing personnel** — without it, the processor's\n  staff are outside the protection chain. Ask for: a commitment that persons\n  processing the data are bound by confidentiality obligations.\n\u003C\u002Fdpa>\n\n\u003Cemployment>\n- **Confidentiality and trade-secret protection** — without it, the employer\n  relies solely on background law, which varies by jurisdiction and is harder\n  to enforce than an express obligation. Ask for: a confidentiality clause\n  surviving termination.\n- **IP and invention assignment** — without express assignment, ownership of\n  employee-created work depends on default rules that differ by jurisdiction\n  and work type. Ask for: assignment of work-related inventions and works,\n  subject to any statutory employee-invention protections in the governing\n  jurisdiction.\n- **Termination notice and severance terms** — silence leaves both parties to\n  statutory or at-will defaults that may not match expectations. Ask for:\n  express notice periods or severance terms (statutory minimums in many\n  jurisdictions override anything less).\n- **Post-termination restrictive covenants** — if the role justifies them and\n  none exist, the employer has no protection against immediate competition or\n  solicitation. Ask for: non-solicitation (and non-compete only where the\n  governing jurisdiction enforces them — enforceability varies sharply and\n  several jurisdictions restrict or void them), drafted to local\n  reasonableness standards.\n- **Compensation completeness** — an offer silent on bonus terms, equity\n  vesting, or benefits invites disputes over what was promised. Ask for:\n  express terms for every compensation element referenced or promised,\n  including treatment on termination.\n- **Dispute-resolution terms** — silence defaults to local courts and rules;\n  arbitration clauses and jury waivers are enforceable in some jurisdictions\n  and restricted in others. Ask for: a deliberate choice, validated against\n  the governing jurisdiction's employment-law limits.\n\u003C\u002Femployment>\n\n\u003Coutput>\nReport gaps separately from clause-level findings, one row per missing\nprotection:\n\n| Protection | Status | Why it matters here | Suggested request |\n|---|---|---|---|\n\nStatus is **missing** (no provision anywhere) or **partial** (cite the\nsection and hand it to the clause review). \"Why it matters here\" must be\nspecific to this contract and party, not the generic rationale above. The\nsuggested request is the one-line ask to send the counterparty. Order rows by\nconsequence to the represented party, and mark any item whose importance or\nenforceability depends on the governing law as jurisdiction-dependent.\n\u003C\u002Foutput>\n",{"name":5,"description":7},"dochaus","4fa71c1afaa510e46a51760c035a6be7350a4bfe","dochaus\u002Fskill\u002Fmissing-protections",23,"https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus","https:\u002F\u002Fdoc.haus","https:\u002F\u002Fgithub.com\u002Fsure-scale","2026-11-14 21:10:36",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sure-scale\u002Fdoc-haus --skill missing-protections",{"tool":37,"command":38},"bunx","bunx skills add sure-scale\u002Fdoc-haus --skill missing-protections",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sure-scale\u002Fdoc-haus --skill missing-protections","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fdochaus\u002Fskill\u002Fmissing-protections\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75B44S57BSW28BPNSY32KM3","figma-use","**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create\u002Fedit\u002Fdelete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75B41F6YZ7GGZR11247RWP4","figma-use-slides","This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-slides\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75B3XJZ4RQEVMRB8KJEZCXW","figma-use-motion","Motion \u002F animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-motion\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75B3TSPBY2M1V5RJGDYMP60","figma-use-figjam","This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-figjam\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75B3NXNVRF8RRK5771619D6","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 \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.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-swiftui\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75B3K427PFQTYE8TKXW6NST","figma-shaders","**MANDATORY prerequisite** — load this skill before calling `create_shader` or `update_shader`. Use when the user asks to create, author, change, fix, or iterate on a shader effect, shader fill, custom effect, custom fill, or procedural shader in Figma.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-shaders\u002FSKILL.md",[],[]]