Results for “bulk-loading”

Redesign Salesforce Flows to handle bulk data loads without hitting transaction limits, using collection-first patterns and safe transaction scope.

Implements Bulk API 2.0 REST calls for ingest and query jobs, covering CSV format requirements, locator pagination, and v1 vs v2 selection.

Provides guidance on enabling and optimizing GKE Cluster Autoscaler, including Node Auto Provisioning, troubleshooting scale-up/down issues, and best practices for capacity management.

Load sharded datasets (npy, Parquet, HDF5, raw binary) into distributed cuPyNumeric arrays using manual partitioning and Legate task launches.

Sets up Microsoft Testing Platform hot reload to iterate fixes on failing tests without rebuilding, covering package installation, environment configuration, and the iterative workflow.

Diagnose and optimize slow-loading, high-memory, or low-FPS USD scenes using a structured workflow with profiling, validation, and mutation phases.

Diagnoses and resolves slow Qdrant indexing and data ingestion by optimizing batching, sharding, HNSW parameters, and payload indexing strategies.

Deploy an entire redesigned site to AEM Edge Delivery Services by inventorying migrated pages, deduplicating blocks, and driving per-page deployment with tracking and verification.

Runs batch processing and high-performance computing (HPC) workloads on Google Kubernetes Engine (GKE), including job queues, parallel processing, and MPI workloads.

Audit and update metadata across multiple AEM Edge Delivery Services pages by scanning the query index, identifying gaps, and generating a corrected bulk metadata spreadsheet.

Guides when to use Salesforce Bulk API 2.0 and provides commands for importing, updating, upserting, deleting, and exporting records, along with CSV format requirements, limits, and error handling.

Evaluates a containerized framework for deploying distributed big data workloads, measuring execution time and cloud cost scaling from four to eight nodes.

Prepare safe production launches — pre-launch checklist, monitoring, staged rollout, and rollback. Load when deploying to production, releasing a major change, opening beta access, or the user asks for a launch checklist, go-live plan, rollout strategy, or rollback plan. Not for local-only prototypes. Pairs with ci-cd-and-automation and app-security-hardening.

Design loading, skeleton, and progressive content reveal patterns that maintain user confidence and perceived performance.

Kubernetes

Analyzes and manages Cargo builds, workspaces, features, and build profiles, including cross-compilation and build script analysis.

Orchestrates a complete bulk RNA-seq differential-expression study from raw FASTQ reads through QC, alignment, quantification, differential expression, pathway enrichment, and publication figures.

Compress bloated project or global memory while preserving decisions, rationale, revisit triggers, provenance, and active user preferences. Load when memory exceeds budget, global memory is too large, session logs are repetitive, or before appending to an over-budget memory file.

Provides expertise in containerization technology, covering container creation, orchestration integration, security hardening, and operational best practices for production workloads.

Imported skill load from langchain

Use this skill for transporting logs. Covers § 393.116 specific rules, bunks, stakes, and tiedowns required.

Design and run a k6/Artillery load profile that measures throughput, latency percentiles, error rate, and the breaking point under concurrent traffic. Use when "load test this", "will it handle launch traffic", or "find the breaking point". Resilience-by-reading-code → audit-resilience. Never hit prod unsigned.

Three.js asset loading - GLTF, textures, images, models, async patterns. Use when loading 3D models, textures, HDR environments, or managing loading progress.

Render long lists (1k+ rows) efficiently in Salesforce LWC using lightning-datatable infinite loading or an IntersectionObserver sentinel, with keyset pagination and accessibility guidance.

Data pipeline specialist for ML experiments. Use when the user asks to talk to Gekko, requests the data engineer, or needs DataLoader optimization.

Bulk extract content from an entire website or site section by crawling pages that follow links, with configurable depth, path filters, and concurrency.

Analyse and shrink JavaScript bundle size for any web app. Use when asked to "reduce bundle size", "analyse bundle", "tree shaking", "lazy loading", "code splitting", "slow initial load", "large JS", "chunk size", "build performance", "LCP caused by JS", "why is the bundle so big", or "first load JS too large".

Generates award-level UI with GSAP motion, bento grids, and Python-driven randomization for layout variety.

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues.

Compute, object storage, block storage, a managed relational database, a message

Package an in-progress task on this cluster so a Claude agent on another cluster (MMM Young, CX3, HX1, Isambard) can pick it up, or resume a task handed off to this cluster. Use when the user says hand off / migrate / continue this on <cluster>, or asks you to pick up an existing handoff.

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Nx build system and monorepo tools. Advanced task orchestration, generators, and plugins. Use for complex enterprise monorepos with multiple technologies. USE WHEN: user mentions "Nx", "nx.json", "Nx monorepo", "Nx generators", asks about "Nx workspace", "affected commands", "module boundaries" DO NOT USE FOR: Turborepo (use turborepo skill), simple monorepos (Turborepo is simpler), single-package projects