[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WYVX0TJTVPB1FC3G0EBDP3":3,"skill-same:01M6WYVX0TJTVPB1FC3G0EBDP3":78},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6WYVX0TJTVPB1FC3G0EBDP3","salesforce-developer",null,"Writes and debugs Apex code, builds Lightning Web Components, optimizes SOQL queries, implements triggers, batch jobs, platform events, and integrations on the Salesforce platform. Use when developing Salesforce applications, customizing CRM workflows, managing governor limits, bulk processing, or setting up Salesforce DX and CI\u002FCD pipelines.","PIXARTSeu\u002FSynapse","PIXARTSeu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274446381?v=4","01M6RB4XPN9YBZCRY4FVN9PJCT","Pixarts ","01M6RB4XTF8G9KHQEMC21FGDKD",12,"MIT","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fsalesforce-developer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"developer","salesforce developer","salesforce","when","workflows","limits","salesforce dx","CI\u002FCD","bulk","processing","apex","crm","expert","engineer","up","api","ci","batch","code","components","2026-11-10 10:12:30",false,"---\nname: salesforce-developer\ndescription: Writes and debugs Apex code, builds Lightning Web Components, optimizes SOQL queries, implements triggers, batch jobs, platform events, and integrations on the Salesforce platform. Use when developing Salesforce applications, customizing CRM workflows, managing governor limits, bulk processing, or setting up Salesforce DX and CI\u002FCD pipelines.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: platform\n  triggers: Salesforce, Apex, Lightning Web Components, LWC, SOQL, SOSL, Visualforce, Salesforce DX, governor limits, triggers, platform events, CRM integration, Sales Cloud, Service Cloud\n  role: expert\n  scope: implementation\n  output-format: code\n  related-skills: api-designer, java-architect, cloud-architect, devops-engineer\n---\n\n# Salesforce Developer\n\n## Core Workflow\n\n1. **Analyze requirements** - Understand business needs, data model, governor limits, scalability\n2. **Design solution** - Choose declarative vs programmatic, plan bulkification, design integrations\n3. **Implement** - Write Apex classes, LWC components, SOQL queries with best practices\n4. **Validate governor limits** - Verify SOQL\u002FDML counts, heap size, and CPU time stay within platform limits before proceeding\n5. **Test thoroughly** - Write test classes with 90%+ coverage, test bulk scenarios (200-record batches)\n6. **Deploy** - Use Salesforce DX, scratch orgs, CI\u002FCD for metadata deployment\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Apex Development | `references\u002Fapex-development.md` | Classes, triggers, async patterns, batch processing |\n| Lightning Web Components | `references\u002Flightning-web-components.md` | LWC framework, component design, events, wire service |\n| SOQL\u002FSOSL | `references\u002Fsoql-sosl.md` | Query optimization, relationships, governor limits |\n| Integration Patterns | `references\u002Fintegration-patterns.md` | REST\u002FSOAP APIs, platform events, external services |\n| Deployment & DevOps | `references\u002Fdeployment-devops.md` | Salesforce DX, CI\u002FCD, scratch orgs, metadata API |\n\n## Constraints\n\n### MUST DO\n- Bulkify Apex code — collect IDs\u002Frecords before loops, query\u002FDML outside loops\n- Write test classes with minimum 90% code coverage, including bulk scenarios\n- Use selective SOQL queries with indexed fields; leverage relationship queries\n- Use appropriate async processing (batch, queueable, future) for long-running work\n- Implement proper error handling and logging; use `Database.update(scope, false)` for partial success\n- Use Salesforce DX for source-driven development and metadata deployment\n\n### MUST NOT DO\n- Execute SOQL\u002FDML inside loops (governor limit violation — see bulkified trigger pattern below)\n- Hard-code IDs or credentials in code\n- Create recursive triggers without safeguards\n- Skip field-level security and sharing rules checks\n- Use deprecated Salesforce APIs or components\n\n## Code Patterns\n\n### Bulkified Trigger (Correct Pattern)\n\n```apex\n\u002F\u002F CORRECT: collect IDs, query once outside the loop\ntrigger AccountTrigger on Account (before insert, before update) {\n    AccountTriggerHandler.handleBeforeInsert(Trigger.new);\n}\n\npublic class AccountTriggerHandler {\n    public static void handleBeforeInsert(List\u003CAccount> newAccounts) {\n        Set\u003CId> parentIds = new Set\u003CId>();\n        for (Account acc : newAccounts) {\n            if (acc.ParentId != null) parentIds.add(acc.ParentId);\n        }\n        Map\u003CId, Account> parentMap = new Map\u003CId, Account>(\n            [SELECT Id, Name FROM Account WHERE Id IN :parentIds]\n        );\n        for (Account acc : newAccounts) {\n            if (acc.ParentId != null && parentMap.containsKey(acc.ParentId)) {\n                acc.Description = 'Child of: ' + parentMap.get(acc.ParentId).Name;\n            }\n        }\n    }\n}\n```\n\n```apex\n\u002F\u002F INCORRECT: SOQL inside loop — governor limit violation\ntrigger AccountTrigger on Account (before insert) {\n    for (Account acc : Trigger.new) {\n        Account parent = [SELECT Id, Name FROM Account WHERE Id = :acc.ParentId]; \u002F\u002F BAD\n        acc.Description = 'Child of: ' + parent.Name;\n    }\n}\n```\n\n### Batch Apex\n\n```apex\npublic class ContactBatchUpdate implements Database.Batchable\u003CSObject> {\n    public Database.QueryLocator start(Database.BatchableContext bc) {\n        return Database.getQueryLocator([SELECT Id, Email FROM Contact WHERE Email = null]);\n    }\n    public void execute(Database.BatchableContext bc, List\u003CContact> scope) {\n        for (Contact c : scope) {\n            c.Email = 'unknown@example.com';\n        }\n        Database.update(scope, false); \u002F\u002F partial success allowed\n    }\n    public void finish(Database.BatchableContext bc) {\n        \u002F\u002F Send notification or chain next batch\n    }\n}\n\u002F\u002F Execute: Database.executeBatch(new ContactBatchUpdate(), 200);\n```\n\n### Test Class\n\n```apex\n@IsTest\nprivate class AccountTriggerHandlerTest {\n    @TestSetup\n    static void makeData() {\n        Account parent = new Account(Name = 'Parent Co');\n        insert parent;\n        Account child = new Account(Name = 'Child Co', ParentId = parent.Id);\n        insert child;\n    }\n\n    @IsTest\n    static void testBulkInsert() {\n        Account parent = [SELECT Id FROM Account WHERE Name = 'Parent Co' LIMIT 1];\n        List\u003CAccount> children = new List\u003CAccount>();\n        for (Integer i = 0; i \u003C 200; i++) {\n            children.add(new Account(Name = 'Child ' + i, ParentId = parent.Id));\n        }\n        Test.startTest();\n        insert children;\n        Test.stopTest();\n\n        List\u003CAccount> updated = [SELECT Description FROM Account WHERE ParentId = :parent.Id];\n        System.assert(!updated.isEmpty(), 'Children should have descriptions set');\n        System.assert(updated[0].Description.startsWith('Child of:'), 'Description format mismatch');\n    }\n}\n```\n\n### SOQL Best Practices\n\n```apex\n\u002F\u002F Selective query — use indexed fields in WHERE clause\nList\u003COpportunity> opps = [\n    SELECT Id, Name, Amount, StageName\n    FROM Opportunity\n    WHERE AccountId IN :accountIds      \u002F\u002F indexed field\n      AND CloseDate >= :Date.today()    \u002F\u002F indexed field\n    ORDER BY CloseDate ASC\n    LIMIT 200\n];\n\n\u002F\u002F Relationship query to avoid extra round-trips\nList\u003CAccount> accounts = [\n    SELECT Id, Name,\n           (SELECT Id, LastName, Email FROM Contacts WHERE Email != null)\n    FROM Account\n    WHERE Id IN :accountIds\n];\n```\n\n### Lightning Web Component (Counter Example)\n\n```html\n\u003C!-- counterComponent.html -->\n\u003Ctemplate>\n    \u003Clightning-card title=\"Counter\">\n        \u003Cdiv class=\"slds-p-around_medium\">\n            \u003Cp>Count: {count}\u003C\u002Fp>\n            \u003Clightning-button label=\"Increment\" onclick={handleIncrement}>\u003C\u002Flightning-button>\n        \u003C\u002Fdiv>\n    \u003C\u002Flightning-card>\n\u003C\u002Ftemplate>\n```\n\n```javascript\n\u002F\u002F counterComponent.js\nimport { LightningElement, track } from 'lwc';\nexport default class CounterComponent extends LightningElement {\n    @track count = 0;\n    handleIncrement() {\n        this.count += 1;\n    }\n}\n```\n\n```xml\n\u003C!-- counterComponent.js-meta.xml -->\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\u003CLightningComponentBundle xmlns=\"http:\u002F\u002Fsoap.sforce.com\u002F2006\u002F04\u002Fmetadata\">\n    \u003CapiVersion>59.0\u003C\u002FapiVersion>\n    \u003CisExposed>true\u003C\u002FisExposed>\n    \u003Ctargets>\n        \u003Ctarget>lightning__AppPage\u003C\u002Ftarget>\n        \u003Ctarget>lightning__RecordPage\u003C\u002Ftarget>\n    \u003C\u002Ftargets>\n\u003C\u002FLightningComponentBundle>\n```\n","# Salesforce Developer\n\n## Core Workflow\n\n1. **Analyze requirements** - Understand business needs, data model, governor limits, scalability\n2. **Design solution** - Choose declarative vs programmatic, plan bulkification, design integrations\n3. **Implement** - Write Apex classes, LWC components, SOQL queries with best practices\n4. **Validate governor limits** - Verify SOQL\u002FDML counts, heap size, and CPU time stay within platform limits before proceeding\n5. **Test thoroughly** - Write test classes with 90%+ coverage, test bulk scenarios (200-record batches)\n6. **Deploy** - Use Salesforce DX, scratch orgs, CI\u002FCD for metadata deployment\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Apex Development | `references\u002Fapex-development.md` | Classes, triggers, async patterns, batch processing |\n| Lightning Web Components | `references\u002Flightning-web-components.md` | LWC framework, component design, events, wire service |\n| SOQL\u002FSOSL | `references\u002Fsoql-sosl.md` | Query optimization, relationships, governor limits |\n| Integration Patterns | `references\u002Fintegration-patterns.md` | REST\u002FSOAP APIs, platform events, external services |\n| Deployment & DevOps | `references\u002Fdeployment-devops.md` | Salesforce DX, CI\u002FCD, scratch orgs, metadata API |\n\n## Constraints\n\n### MUST DO\n- Bulkify Apex code — collect IDs\u002Frecords before loops, query\u002FDML outside loops\n- Write test classes with minimum 90% code coverage, including bulk scenarios\n- Use selective SOQL queries with indexed fields; leverage relationship queries\n- Use appropriate async processing (batch, queueable, future) for long-running work\n- Implement proper error handling and logging; use `Database.update(scope, false)` for partial success\n- Use Salesforce DX for source-driven development and metadata deployment\n\n### MUST NOT DO\n- Execute SOQL\u002FDML inside loops (governor limit violation — see bulkified trigger pattern below)\n- Hard-code IDs or credentials in code\n- Create recursive triggers without safeguards\n- Skip field-level security and sharing rules checks\n- Use deprecated Salesforce APIs or components\n\n## Code Patterns\n\n### Bulkified Trigger (Correct Pattern)\n\n```apex\n\u002F\u002F CORRECT: collect IDs, query once outside the loop\ntrigger AccountTrigger on Account (before insert, before update) {\n    AccountTriggerHandler.handleBeforeInsert(Trigger.new);\n}\n\npublic class AccountTriggerHandler {\n    public static void handleBeforeInsert(List\u003CAccount> newAccounts) {\n        Set\u003CId> parentIds = new Set\u003CId>();\n        for (Account acc : newAccounts) {\n            if (acc.ParentId != null) parentIds.add(acc.ParentId);\n        }\n        Map\u003CId, Account> parentMap = new Map\u003CId, Account>(\n            [SELECT Id, Name FROM Account WHERE Id IN :parentIds]\n        );\n        for (Account acc : newAccounts) {\n            if (acc.ParentId != null && parentMap.containsKey(acc.ParentId)) {\n                acc.Description = 'Child of: ' + parentMap.get(acc.ParentId).Name;\n            }\n        }\n    }\n}\n```\n\n```apex\n\u002F\u002F INCORRECT: SOQL inside loop — governor limit violation\ntrigger AccountTrigger on Account (before insert) {\n    for (Account acc : Trigger.new) {\n        Account parent = [SELECT Id, Name FROM Account WHERE Id = :acc.ParentId]; \u002F\u002F BAD\n        acc.Description = 'Child of: ' + parent.Name;\n    }\n}\n```\n\n### Batch Apex\n\n```apex\npublic class ContactBatchUpdate implements Database.Batchable\u003CSObject> {\n    public Database.QueryLocator start(Database.BatchableContext bc) {\n        return Database.getQueryLocator([SELECT Id, Email FROM Contact WHERE Email = null]);\n    }\n    public void execute(Database.BatchableContext bc, List\u003CContact> scope) {\n        for (Contact c : scope) {\n            c.Email = 'unknown@example.com';\n        }\n        Database.update(scope, false); \u002F\u002F partial success allowed\n    }\n    public void finish(Database.BatchableContext bc) {\n        \u002F\u002F Send notification or chain next batch\n    }\n}\n\u002F\u002F Execute: Database.executeBatch(new ContactBatchUpdate(), 200);\n```\n\n### Test Class\n\n```apex\n@IsTest\nprivate class AccountTriggerHandlerTest {\n    @TestSetup\n    static void makeData() {\n        Account parent = new Account(Name = 'Parent Co');\n        insert parent;\n        Account child = new Account(Name = 'Child Co', ParentId = parent.Id);\n        insert child;\n    }\n\n    @IsTest\n    static void testBulkInsert() {\n        Account parent = [SELECT Id FROM Account WHERE Name = 'Parent Co' LIMIT 1];\n        List\u003CAccount> children = new List\u003CAccount>();\n        for (Integer i = 0; i \u003C 200; i++) {\n            children.add(new Account(Name = 'Child ' + i, ParentId = parent.Id));\n        }\n        Test.startTest();\n        insert children;\n        Test.stopTest();\n\n        List\u003CAccount> updated = [SELECT Description FROM Account WHERE ParentId = :parent.Id];\n        System.assert(!updated.isEmpty(), 'Children should have descriptions set');\n        System.assert(updated[0].Description.startsWith('Child of:'), 'Description format mismatch');\n    }\n}\n```\n\n### SOQL Best Practices\n\n```apex\n\u002F\u002F Selective query — use indexed fields in WHERE clause\nList\u003COpportunity> opps = [\n    SELECT Id, Name, Amount, StageName\n    FROM Opportunity\n    WHERE AccountId IN :accountIds      \u002F\u002F indexed field\n      AND CloseDate >= :Date.today()    \u002F\u002F indexed field\n    ORDER BY CloseDate ASC\n    LIMIT 200\n];\n\n\u002F\u002F Relationship query to avoid extra round-trips\nList\u003CAccount> accounts = [\n    SELECT Id, Name,\n           (SELECT Id, LastName, Email FROM Contacts WHERE Email != null)\n    FROM Account\n    WHERE Id IN :accountIds\n];\n```\n\n### Lightning Web Component (Counter Example)\n\n```html\n\u003C!-- counterComponent.html -->\n\u003Ctemplate>\n    \u003Clightning-card title=\"Counter\">\n        \u003Cdiv class=\"slds-p-around_medium\">\n            \u003Cp>Count: {count}\u003C\u002Fp>\n            \u003Clightning-button label=\"Increment\" onclick={handleIncrement}>\u003C\u002Flightning-button>\n        \u003C\u002Fdiv>\n    \u003C\u002Flightning-card>\n\u003C\u002Ftemplate>\n```\n\n```javascript\n\u002F\u002F counterComponent.js\nimport { LightningElement, track } from 'lwc';\nexport default class CounterComponent extends LightningElement {\n    @track count = 0;\n    handleIncrement() {\n        this.count += 1;\n    }\n}\n```\n\n```xml\n\u003C!-- counterComponent.js-meta.xml -->\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\u003CLightningComponentBundle xmlns=\"http:\u002F\u002Fsoap.sforce.com\u002F2006\u002F04\u002Fmetadata\">\n    \u003CapiVersion>59.0\u003C\u002FapiVersion>\n    \u003CisExposed>true\u003C\u002FisExposed>\n    \u003Ctargets>\n        \u003Ctarget>lightning__AppPage\u003C\u002Ftarget>\n        \u003Ctarget>lightning__RecordPage\u003C\u002Ftarget>\n    \u003C\u002Ftargets>\n\u003C\u002FLightningComponentBundle>\n```\n",{"name":5,"license":15,"metadata":49,"description":7},{"role":36,"scope":50,"author":51,"domain":52,"version":53,"triggers":54,"output-format":42,"related-skills":55},"implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","platform","1.1.0","Salesforce, Apex, Lightning Web Components, LWC, SOQL, SOSL, Visualforce, Salesforce DX, governor limits, triggers, platform events, CRM integration, Sales Cloud, Service Cloud","api-designer, java-architect, cloud-architect, devops-engineer","main","c19c0bc0a04d25a849ce749fe88250e688f06437","packages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fsalesforce-developer",1,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse","https:\u002F\u002Fgithub.com\u002FPIXARTSeu","https:\u002F\u002Fpixarts.eu\u002F","2026-09-24 06:30:45",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add PIXARTSeu\u002FSynapse --skill salesforce-developer",{"tool":70,"command":71},"bunx","bunx skills add PIXARTSeu\u002FSynapse --skill salesforce-developer",{"tool":73,"command":74},"pnpm","pnpm dlx skills add PIXARTSeu\u002FSynapse --skill salesforce-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fsalesforce-developer\u002FSKILL.md",true,[],[79,109,116,141,164,191],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":91,"publishedAt":44},"01M6X0ECZKGP44NP2JW588B9RG","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,94,95,96,97,98,43,99,100,101,42,102,103,104,105,106,107,108,27],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","react components","guidelines","tasks","Optimization","data","refactoring","patterns","next","triggers","data fetching",{"skillNo":110,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":115,"publishedAt":44},"01M6X05WCVH879XKZEAQ15PHQX","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Fskill\u002Fvercel-react-best-practices\u002FSKILL.md",[113,114],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,94,95,96,97,98,43,99,100,101,42,102,103,104,105,106,107,108,27],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":44},"01M6WZ286AR2SYE9GZYVW0CNYG","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwordpress-pro\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,97,130,98,42,131,39,132,133,134,135,36,136,137,138,139,140,27],"wordpress","wordpress pro","pro","security","tuning","laravel","reviewer","hooks","filters","query","woocommerce","caching","themes","sanitization",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":149,"publishedAt":44},"01M6WZ1ZVG6PJ4PVN9RTK0BX7Z","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwebsocket-engineer\u002FSKILL.md",[147,148],{"categoryNo":123,"categoryName":124,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[150,37,151,152,42,153,154,39,133,155,36,156,157,158,159,160,161,162,163,27],"websocket","websocket engineer","architecture","messaging","monitoring","fastapi","time","scaling","io","communication systems","presence","updates","socket","invoke",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":44},"01M6WZ1G86ZR73H0WNM6CGNRGF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert\u002FSKILL.md",[170,171,172],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":123,"categoryName":124,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,36,175,176,97,177,43,178,179,180,181,182,183,184,185,186,187,188,189,190],"vue","vue expert","frontend","typescript","config","applications","Composition","projects","pinia","use","router","workers","mobile","reusable","worker","apps","hybrid",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":199,"publishedAt":44},"01M6WZ1AP3GFCBAMD712X8KRP7","vue-expert-js","Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js\u002FSKILL.md",[197,198],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,200,36,201,175,176,177,43,42,39,180,181,202,203,38,204,205,206,207,27],"js","vue expert js","coverage","only","modules","options","jsdoc","quick"]