[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7323WPB9MBTTYQMK2GE4R7H":3,"skill-same:01M7323WPB9MBTTYQMK2GE4R7H":114},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M7323WPB9MBTTYQMK2GE4R7H","espocrm-development",null,"Comprehensive guide for developing on EspoCRM - metadata-driven CRM with service layer architecture","julio211916\u002FTlantiCAD-Studio-V0.1-alpha","julio211916","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128201165?v=4","01M730ENY015MHFY82VKR6AGGR","José Carlos amador garcia","01M730ENYT83EWH6EXRHF9FTXV",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: espocrm-development\ndescription: Comprehensive guide for developing on EspoCRM - metadata-driven CRM with service layer architecture\nversion: 1.0.0\ncategory: development\nauthor: Claude MPM Team\nlicense: MIT\nprogressive_disclosure:\n  entry_point:\n    summary: \"Metadata-driven CRM development using service layer, ORM EntityManager, and hook-based business logic\"\n    when_to_use: \"When developing custom modules, entities, hooks, or integrations for EspoCRM\"\n    quick_start: \"1. Understand metadata-driven architecture 2. Use EntityManager for data access 3. Implement business logic in Services 4. Register hooks for lifecycle events 5. Rebuild cache after changes\"\n  references:\n    - architecture.md\n    - development-workflow.md\n    - hooks-and-services.md\n    - frontend-customization.md\n    - common-tasks.md\n    - testing-debugging.md\n    - select-builder.md\n    - api-actions.md\n    - custom-field-types.md\n    - extension-packages.md\ncontext_limit: 800\ntags:\n  - espocrm\n  - php\n  - crm\n  - metadata-driven\n  - orm\nrequires_tools: []\n---\n\n# EspoCRM Development\n\n## Overview\n\nEspoCRM is a metadata-driven CRM platform where configuration lives in JSON files, business logic belongs in Services, and data access happens through ORM EntityManager. This skill enforces architectural patterns to prevent common mistakes like passing Container dependencies, bypassing the service layer, or implementing business logic in hooks.\n\n## When to Use This Skill\n\nActivate when developing custom EspoCRM modules, entities, relationships, hooks, services, API endpoints, or integrations. **Use especially when:** working with ORM (EntityManager required), implementing business logic (belongs in Services), creating hooks (use interfaces), modifying metadata (requires cache rebuild), building custom field types, creating complex queries with SelectBuilder, implementing custom API actions, or packaging extensions.\n\n## The Iron Law\n\n**BUSINESS LOGIC IN SERVICES, NOT HOOKS | DATA ACCESS VIA ENTITYMANAGER, NEVER DIRECT PDO | NEVER PASS CONTAINER AS DEPENDENCY**\n\nAccessing Container directly or writing business logic in hooks violates architecture.\n\n## Core Architecture Principles\n\n1. **Metadata-Driven**: Entity definitions, layouts, field configs live in JSON\n2. **Service Layer**: All business logic implemented in Service classes\n3. **ORM EntityManager**: Central access point for all database operations\n4. **Dependency Injection**: Constructor injection, never pass Container\n5. **Hook System**: Lifecycle events for validation and side effects (not business logic)\n6. **Repository Pattern**: Entities accessed through repositories\n\n## Quick Start\n\n1. **Setup Development Environment** - Use ext-template, work in `src\u002F` directory (EspoCRM 7.4+), understand metadata structure: `custom\u002FEspo\u002FModules\u002F{ModuleName}\u002FResources\u002Fmetadata\u002F`\n\n2. **Access Data with EntityManager**\n   ```php\n   use Espo\\ORM\\EntityManager;\n\n   public function __construct(private EntityManager $entityManager) {}\n\n   \u002F\u002F Find entity\n   $account = $this->entityManager->getEntityById('Account', $id);\n\n   \u002F\u002F Query with conditions\n   $collection = $this->entityManager\n       ->getRDBRepository('Contact')\n       ->where(['accountId' => $accountId])\n       ->find();\n   ```\n\n3. **Implement Business Logic in Services**\n   ```php\n   namespace Espo\\Modules\\MyModule\\Services;\n\n   use Espo\\Services\\Record;\n\n   class MyEntity extends Record {\n       public function customAction(string $id, object $data): object {\n           \u002F\u002F Business logic here\n           $entity = $this->entityManager->getEntityById($this->entityType, $id);\n           \u002F\u002F ... process ...\n           $this->entityManager->saveEntity($entity);\n           return $entity;\n       }\n   }\n   ```\n\n4. **Register Hooks for Lifecycle Events**\n   ```php\n   namespace Espo\\Modules\\MyModule\\Hooks\\Account;\n\n   use Espo\\ORM\\Entity;\n   use Espo\\Core\\Hook\\Hook\\BeforeSave;\n\n   class MyHook implements BeforeSave {\n       public function beforeSave(Entity $entity, array $options): void {\n           \u002F\u002F Validation or side effects only\n           if ($entity->isAttributeChanged('status')) {\n               \u002F\u002F React to changes\n           }\n       }\n   }\n   ```\n\n5. **Rebuild Cache After Changes**\n   ```bash\n   bin\u002Fcommand rebuild\n   ```\n\n## Hook Types (Interfaces)\n\nEspoCRM provides 7 hook types - ALWAYS use interfaces: `BeforeSave` (validation before save), `AfterSave` (side effects after save), `BeforeRemove` (validation before delete), `AfterRemove` (cleanup after delete), `AfterRelate` (relationship creation), `AfterUnrelate` (relationship removal), `AfterMassRelate` (bulk relationship operations).\n\n## Navigation\n\n### Core Concepts\n- **[Architecture](references\u002Farchitecture.md)**: Metadata system, ORM, DI container, repository pattern, and core architectural patterns\n- **[Development Workflow](references\u002Fdevelopment-workflow.md)**: Module creation, custom entities, fields, APIs, and extension development process\n- **[Hooks and Services](references\u002Fhooks-and-services.md)**: Service layer implementation, hook types, dependency injection, and business logic patterns\n\n### Advanced Topics\n- **[SelectBuilder](references\u002Fselect-builder.md)**: Advanced querying with SelectBuilder - complex queries, joins, aggregations, and query optimization\n- **[API Actions](references\u002Fapi-actions.md)**: Creating custom API endpoints - action handlers, request\u002Fresponse patterns, and authentication\n- **[Custom Field Types](references\u002Fcustom-field-types.md)**: Building custom field types - backend, frontend, metadata, and integration\n\n### UI and Integration\n- **[Frontend Customization](references\u002Ffrontend-customization.md)**: View system, client-side development, and UI customization\n- **[Common Tasks](references\u002Fcommon-tasks.md)**: Scheduled jobs, emails, PDFs, ACL, workflows, and integration patterns\n- **[Extension Packages](references\u002Fextension-packages.md)**: Packaging and distributing extensions - manifest files, installation, and versioning\n\n### Quality Assurance\n- **[Testing and Debugging](references\u002Ftesting-debugging.md)**: Unit tests, debugging techniques, performance optimization, and common pitfalls\n\n## Key Patterns\n\n**Correct Pattern:**\n```php\n✅ Service with injected dependencies\n✅ EntityManager for data access\n✅ Hooks using interfaces\n✅ Type declarations on all methods\n✅ Exceptions for error handling\n```\n\n**Incorrect Patterns:**\n```php\n❌ Passing Container as dependency\n❌ Direct PDO database access\n❌ Business logic in hooks\n❌ Hook base classes instead of interfaces\n❌ Missing type declarations\n```\n\n## Common Mistakes to Avoid\n\n- **Never pass Container** - Inject specific dependencies instead\n- **Don't bypass EntityManager** - Use ORM, not raw queries\n- **Business logic doesn't belong in hooks** - Use Services\n- **Always rebuild cache** - After metadata changes (`bin\u002Fcommand rebuild`)\n- **Use interfaces for hooks** - Not base classes\n- **Type everything** - PHP 7.4+ requires type declarations\n- **Throw exceptions** - Don't return booleans for errors\n\n## Integration with Other Skills\n\n- **systematic-debugging**: Debug EspoCRM issues using logs and step debugging\n- **verification-before-completion**: Always test with cache rebuild before claiming complete\n- **test-driven-development**: Write unit tests for Services and hooks\n\n## The Bottom Line\n\n**EspoCRM is metadata-driven with a service layer architecture.**\n\nUnderstand the metadata system. Use EntityManager for data. Implement business logic in Services. Use hooks for lifecycle events only. Rebuild cache after changes.\n\nThis is the EspoCRM way.\n","# EspoCRM Development\n\n## Overview\n\nEspoCRM is a metadata-driven CRM platform where configuration lives in JSON files, business logic belongs in Services, and data access happens through ORM EntityManager. This skill enforces architectural patterns to prevent common mistakes like passing Container dependencies, bypassing the service layer, or implementing business logic in hooks.\n\n## When to Use This Skill\n\nActivate when developing custom EspoCRM modules, entities, relationships, hooks, services, API endpoints, or integrations. **Use especially when:** working with ORM (EntityManager required), implementing business logic (belongs in Services), creating hooks (use interfaces), modifying metadata (requires cache rebuild), building custom field types, creating complex queries with SelectBuilder, implementing custom API actions, or packaging extensions.\n\n## The Iron Law\n\n**BUSINESS LOGIC IN SERVICES, NOT HOOKS | DATA ACCESS VIA ENTITYMANAGER, NEVER DIRECT PDO | NEVER PASS CONTAINER AS DEPENDENCY**\n\nAccessing Container directly or writing business logic in hooks violates architecture.\n\n## Core Architecture Principles\n\n1. **Metadata-Driven**: Entity definitions, layouts, field configs live in JSON\n2. **Service Layer**: All business logic implemented in Service classes\n3. **ORM EntityManager**: Central access point for all database operations\n4. **Dependency Injection**: Constructor injection, never pass Container\n5. **Hook System**: Lifecycle events for validation and side effects (not business logic)\n6. **Repository Pattern**: Entities accessed through repositories\n\n## Quick Start\n\n1. **Setup Development Environment** - Use ext-template, work in `src\u002F` directory (EspoCRM 7.4+), understand metadata structure: `custom\u002FEspo\u002FModules\u002F{ModuleName}\u002FResources\u002Fmetadata\u002F`\n\n2. **Access Data with EntityManager**\n   ```php\n   use Espo\\ORM\\EntityManager;\n\n   public function __construct(private EntityManager $entityManager) {}\n\n   \u002F\u002F Find entity\n   $account = $this->entityManager->getEntityById('Account', $id);\n\n   \u002F\u002F Query with conditions\n   $collection = $this->entityManager\n       ->getRDBRepository('Contact')\n       ->where(['accountId' => $accountId])\n       ->find();\n   ```\n\n3. **Implement Business Logic in Services**\n   ```php\n   namespace Espo\\Modules\\MyModule\\Services;\n\n   use Espo\\Services\\Record;\n\n   class MyEntity extends Record {\n       public function customAction(string $id, object $data): object {\n           \u002F\u002F Business logic here\n           $entity = $this->entityManager->getEntityById($this->entityType, $id);\n           \u002F\u002F ... process ...\n           $this->entityManager->saveEntity($entity);\n           return $entity;\n       }\n   }\n   ```\n\n4. **Register Hooks for Lifecycle Events**\n   ```php\n   namespace Espo\\Modules\\MyModule\\Hooks\\Account;\n\n   use Espo\\ORM\\Entity;\n   use Espo\\Core\\Hook\\Hook\\BeforeSave;\n\n   class MyHook implements BeforeSave {\n       public function beforeSave(Entity $entity, array $options): void {\n           \u002F\u002F Validation or side effects only\n           if ($entity->isAttributeChanged('status')) {\n               \u002F\u002F React to changes\n           }\n       }\n   }\n   ```\n\n5. **Rebuild Cache After Changes**\n   ```bash\n   bin\u002Fcommand rebuild\n   ```\n\n## Hook Types (Interfaces)\n\nEspoCRM provides 7 hook types - ALWAYS use interfaces: `BeforeSave` (validation before save), `AfterSave` (side effects after save), `BeforeRemove` (validation before delete), `AfterRemove` (cleanup after delete), `AfterRelate` (relationship creation), `AfterUnrelate` (relationship removal), `AfterMassRelate` (bulk relationship operations).\n\n## Navigation\n\n### Core Concepts\n- **[Architecture](references\u002Farchitecture.md)**: Metadata system, ORM, DI container, repository pattern, and core architectural patterns\n- **[Development Workflow](references\u002Fdevelopment-workflow.md)**: Module creation, custom entities, fields, APIs, and extension development process\n- **[Hooks and Services](references\u002Fhooks-and-services.md)**: Service layer implementation, hook types, dependency injection, and business logic patterns\n\n### Advanced Topics\n- **[SelectBuilder](references\u002Fselect-builder.md)**: Advanced querying with SelectBuilder - complex queries, joins, aggregations, and query optimization\n- **[API Actions](references\u002Fapi-actions.md)**: Creating custom API endpoints - action handlers, request\u002Fresponse patterns, and authentication\n- **[Custom Field Types](references\u002Fcustom-field-types.md)**: Building custom field types - backend, frontend, metadata, and integration\n\n### UI and Integration\n- **[Frontend Customization](references\u002Ffrontend-customization.md)**: View system, client-side development, and UI customization\n- **[Common Tasks](references\u002Fcommon-tasks.md)**: Scheduled jobs, emails, PDFs, ACL, workflows, and integration patterns\n- **[Extension Packages](references\u002Fextension-packages.md)**: Packaging and distributing extensions - manifest files, installation, and versioning\n\n### Quality Assurance\n- **[Testing and Debugging](references\u002Ftesting-debugging.md)**: Unit tests, debugging techniques, performance optimization, and common pitfalls\n\n## Key Patterns\n\n**Correct Pattern:**\n```php\n✅ Service with injected dependencies\n✅ EntityManager for data access\n✅ Hooks using interfaces\n✅ Type declarations on all methods\n✅ Exceptions for error handling\n```\n\n**Incorrect Patterns:**\n```php\n❌ Passing Container as dependency\n❌ Direct PDO database access\n❌ Business logic in hooks\n❌ Hook base classes instead of interfaces\n❌ Missing type declarations\n```\n\n## Common Mistakes to Avoid\n\n- **Never pass Container** - Inject specific dependencies instead\n- **Don't bypass EntityManager** - Use ORM, not raw queries\n- **Business logic doesn't belong in hooks** - Use Services\n- **Always rebuild cache** - After metadata changes (`bin\u002Fcommand rebuild`)\n- **Use interfaces for hooks** - Not base classes\n- **Type everything** - PHP 7.4+ requires type declarations\n- **Throw exceptions** - Don't return booleans for errors\n\n## Integration with Other Skills\n\n- **systematic-debugging**: Debug EspoCRM issues using logs and step debugging\n- **verification-before-completion**: Always test with cache rebuild before claiming complete\n- **test-driven-development**: Write unit tests for Services and hooks\n\n## The Bottom Line\n\n**EspoCRM is metadata-driven with a service layer architecture.**\n\nUnderstand the metadata system. Use EntityManager for data. Implement business logic in Services. Use hooks for lifecycle events only. Rebuild cache after changes.\n\nThis is the EspoCRM way.\n",{"name":5,"tags":24,"author":30,"license":15,"version":31,"category":32,"description":7,"context_limit":33,"requires_tools":34,"progressive_disclosure":35},[25,26,27,28,29],"espocrm","php","crm","metadata-driven","orm","Claude MPM Team","1.0.0","development",800,[],{"references":36,"entry_point":47},[37,38,39,40,41,42,43,44,45,46],"architecture.md","development-workflow.md","hooks-and-services.md","frontend-customization.md","common-tasks.md","testing-debugging.md","select-builder.md","api-actions.md","custom-field-types.md","extension-packages.md",{"summary":48,"quick_start":49,"when_to_use":50},"Metadata-driven CRM development using service layer, ORM EntityManager, and hook-based business logic","1. Understand metadata-driven architecture 2. Use EntityManager for data access 3. Implement business logic in Services 4. Register hooks for lifecycle events 5. Rebuild cache after changes","When developing custom modules, entities, hooks, or integrations for EspoCRM","main","590aa4fe05d1ec71a02ee9cc76c9a20508b5bcea","skills\u002Fju\u002Fskills\u002Fespocrm-development","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha","https:\u002F\u002Fgithub.com\u002Fjulio211916","Estudiante de ing sistemas y psicologia","2026-05-22 04:43:54",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add julio211916\u002FTlantiCAD-Studio-V0.1-alpha --skill espocrm-development",{"tool":64,"command":65},"bunx","bunx skills add julio211916\u002FTlantiCAD-Studio-V0.1-alpha --skill espocrm-development",{"tool":67,"command":68},"pnpm","pnpm dlx skills add julio211916\u002FTlantiCAD-Studio-V0.1-alpha --skill espocrm-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,110],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fapi-actions.md","REFERENCE","参考文档",15942,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fapi-actions.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Farchitecture.md",14190,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Farchitecture.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fcommon-tasks.md",20428,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fcommon-tasks.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcustom-field-types.md",17987,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fcustom-field-types.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdevelopment-workflow.md",16071,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fdevelopment-workflow.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fextension-packages.md",28256,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fextension-packages.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Ffrontend-customization.md",17519,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Ffrontend-customization.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fhooks-and-services.md",20820,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fhooks-and-services.md",{"path":107,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fselect-builder.md",13842,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Fselect-builder.md",{"path":111,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Ftesting-debugging.md",18250,"https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fespocrm-development\u002Freferences\u002Ftesting-debugging.md",[115,122,129,136,143,150],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M735PMP7K29TEC1BC5A3VJ3Z","simpy","Process-based discrete-event simulation framework in Python. Use this skill when building simulations of systems with processes, queues, resources, and time-based events such as manufacturing systems, service operations, network traffic, logistics, or any system where entities interact with shared resources over time.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fsimpy\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M735NX56AZHYMV3BQ8GYZ7J0","shopify-expert","Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fshopify-expert\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M735N9WTN69TVA2T5VS9W1CA","shap","Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing models, or implementing explainable AI. Works with tree-based models (XGBoost, LightGBM, Random Forest), deep learning (TensorFlow, PyTorch), linear models, and any black-box model.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fshap\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M735N3VQ8R56TXFF16BMF19H","shadcn-ui","Deep expertise on shadcn\u002Fui component library including installation, customization, theming, and accessibility patterns. Use when building UI with shadcn\u002Fui components, integrating Radix UI primitives, configuring Tailwind CSS v4 themes, or implementing dark mode. Covers Next.js App Router, Pages Router, and Vite setups.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fshadcn-ui\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M735KH64KS6Z58H6BJWX89BV","seoul-subway-arrival","Look up Seoul real-time subway arrival information with the official Seoul Open Data API. Use when the user asks when a train arrives, which trains are approaching a station, or how crowded Seoul subway timing looks right now.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fseoul-subway-arrival\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":19},"01M735K7KAFBZNACQ66PMDQMQD","seo-optimization","Comprehensive 7-phase SEO optimization workflow covering technical SEO auditing, keyword research strategy, on-page optimization, content SEO and E-E-A-T, structured data implementation, link building, and AI search optimization. Use when auditing search engine visibility, diagnosing ranking issues, implementing schema markup, conducting keyword research, optimizing content for E-E-A-T signals, or adapting for AI-driven search (AI Overviews, SGE).","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fseo-optimization\u002FSKILL.md",[],[]]