build-optimization
Build system optimization covering compilation, caching, incremental builds, and developer tooling. Use when improving build times, configuring CI pipelines, or designing developer tools.
What this skill does
# Build Optimization Expert guidance for optimizing build systems, reducing compilation times, maximizing cache hit rates, and building developer tools that enhance productivity across the development lifecycle. ## When to Use This Skill - Diagnosing slow build times and identifying bottlenecks - Configuring caching strategies (local, remote, distributed) - Setting up incremental builds and parallel execution - Optimizing CI/CD pipeline performance and cost - Designing or improving bundle splitting and tree shaking - Building CLIs, plugins, code generators, or IDE extensions - Configuring monorepo tooling (Nx, Turborepo, Bazel) - Reducing developer feedback loop times (hot reload, watch mode) - Managing build artifacts and reproducibility ## Quick Reference | Task | Load reference | | --- | --- | | Compilation, caching, incremental builds, CI/CD optimization | `skills/build-optimization/references/build-systems.md` | | Plugin systems, code generation, linting, IDE integration, monorepo tooling | `skills/build-optimization/references/developer-tooling.md` | ## Core Targets - Build time under 30 seconds for development builds - Rebuild time under 5 seconds with watch mode - Cache hit rate above 90% in CI - Zero flaky builds in production pipelines - Reproducible builds across environments ## Workflow ### 1. Performance Analysis Profile the current build before making changes. - Measure cold build, incremental rebuild, and hot reload times - Profile CPU, memory, and I/O during builds - Map the dependency graph and identify bottlenecks - Evaluate cache hit rates and invalidation patterns - Review current tool configuration for missed optimizations ### 2. Optimization Apply targeted improvements based on profiling data. - Enable incremental compilation and caching - Configure parallel execution across available cores - Set up code splitting and tree shaking - Optimize module resolution and source transformation - Implement remote or distributed caching for CI ### 3. Tooling Build or configure developer tools for fast feedback loops. - Configure watch mode and hot module replacement - Set up clear error messages and progress indicators - Integrate build analytics and performance dashboards - Add pre-commit hooks for format, lint, and validation ### 4. Monitoring Track build health over time. - Set up automated build time tracking and alerting - Monitor cache hit rates and bundle size trends - Detect performance regressions in CI - Review and optimize periodically based on data ## Common Mistakes - Optimizing without profiling first - Disabling caching due to intermittent issues instead of fixing invalidation - Running full builds when incremental builds would suffice - Not parallelizing independent build tasks - Ignoring I/O as a bottleneck (disk speed, network latency) - Letting bundle sizes grow unchecked without analysis - Using a single build configuration for development and production
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.