Loading...
Loading...
Found 4 Skills
Salesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs), sets up DataPack CI/CD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use deploying-metadata), authoring OmniStudio artifacts (use building-omnistudio-*), or writing Apex/LWC business logic (use generating-apex/generating-lwc-components).
Galaxy database migration with Alembic - create schema changes (add table/column), upgrade/downgrade database versions, check migration status, troubleshoot errors. Use for: SQLAlchemy model changes, database schema modifications, Alembic revisions, migration version conflicts, lib/galaxy/model changes.
Deep reference for when the migration chain misbehaves — upgrade compatibility errors you cannot explain, migration files you cannot write, a project converted from legacy persistence, or a request to remove the chain. Load only when the rules in migrating-motoko-actors do not explain what you are seeing.
Use this skill when migrating a Taiga UI project to a new major version. Before starting, confirm with the user which major versions are involved (e.g. v4 → v5). Substitute the source version as CURRENT_MAJOR and the target version as NEXT_MAJOR throughout this workflow. Also invoke when running migration schematics, handling migration TODOs left after `ng update` or `nx migrate`, asked to fix TODOs, clean up migration notes, resolve deprecation warnings, or work with @taiga-ui/legacy package. Follow the complete migration workflow: gather context, prepare environment, run schematics, review changes, handle TODOs, and troubleshoot common issues. Resolve every actionable TODO only when the surrounding code proves the fix is safe; otherwise inspect more context or ask the user before changing behavior, templates, styles, or scripts.