agentleFS
NVIDIAKnown publisherNVIDIA/elements/.agents/skills/guidance-build-system/SKILL.md

guidance-build

Skill115 starsChanged 57 days agoApache-2.0View on GitHub

Wireit orchestration, build optimization, caching strategies, and build troubleshooting for the Elements monorepo. Use this skill whenever the user asks about Wireit configuration, build tasks, build dependencies, cache invalidation, build performance, adding new build tasks to package.json, cross-package dependency patterns, sideEffects declarations, CI pipeline configuration, or diagnosing slow or failing builds. Also trigger when the user mentions wireit, vite build issues, pnpm run ci, or build output problems.

  • Deletes or force-pushes
  • Installs packages

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add the script to package.json with a wireit config

    line 81
  2. Very specific:

    Add dependencies on upstream packages that must build first

    line 83
  3. Very specific:

    If the task should run in CI, add it to the dependency chain of the root ci script

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Guidance Build System

You MUST review the build system documentation before modifying build configurations or troubleshooting build issues.

When to Use This Skill

  • Optimizing build performance and parallelization
  • Understanding Wireit task dependencies
  • Troubleshooting build failures or cache issues
  • Adding new build tasks to projects
  • Configuring build orchestration across packages
  • Understanding CI/CD build pipeline

Quick Reference

Common Commands

# Full CI locally (lint, build, test):same as CI pipeline
pnpm run ci

# Clean everything (node_modules, dist, .wireit caches)
pnpm run ci:reset

# Build a single project
cd projects/core && pnpm run build

# Force that project's Wireit scripts to rerun
mise exec -- git clean -dfX -- .wireit
mise exec -- pnpm run build

# Dev mode with watch
cd projects/core && pnpm run dev

Wireit Basics

Wireit configs live in each project's package.json under the wireit key. Each task declares:

  • command:the shell command to run
  • dependencies:other wireit tasks that must complete first (can be cross-package)
  • files:input file globs for cache invalidation
  • output:output file globs that get cached

Wireit skips tasks whose inputs have not changed since the last run. WIREIT_CACHE=none turns off output caching but does not bypass this incremental freshness check. To force a rerun, run mise exec -- git clean -dfX -- .wireit from the target project directory before invoking the project script.

Dependency Patterns

Cross-package dependencies use the <package>:<script> format:

{
  "wireit": {
    "build": {
      "dependencies": ["../themes:build", "../styles:build"],
      "command": "vite build",
      "files": ["src/**/*", "tsconfig.json"],
      "output": ["dist/**"]
    }
  }
}

Troubleshooting Build Failures

SymptomFix
Stale cache causing wrong outputClean .wireit/ in the affected project, then rebuild
"Cannot find module" after package changesRun pnpm i --frozen-lockfile to re-link workspaces
TypeScript errors after dependency updateRebuild dependencies first: cd projects/themes && pnpm run build
CI passes locally but fails in pipelineCheck Node version (node -v should match .nvmrc) and pnpm version
Full resetpnpm run ci:reset && pnpm i --frozen-lockfile && pnpm run ci

Adding a New Wireit Task

  1. Add the script to package.json with a wireit config
  2. Declare files (inputs) and output (outputs) for caching
  3. Add dependencies on upstream packages that must build first
  4. If the task should run in CI, add it to the dependency chain of the root ci script

Key Tools

  • pnpm:package manager with workspaces
  • Wireit:build orchestration with caching (like Bazel for Node)
  • Vite:TypeScript compilation and bundling
  • Semantic Release:automated versioning from conventional commits

References

  • Build System Documentation
  • Root Wireit Configuration
  • Project package.json files for individual build patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.