Manages the build lifecycle for the Cosmos Explorer project.

Install

mkdir -p .claude/skills/build-azure && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10051" && unzip -o skill.zip -d .claude/skills/build-azure && rm skill.zip

Installs to .claude/skills/build-azure

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Build the Cosmos Explorer project. Use this skill when asked to build, compile, or check the build status of the project.
121 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Run production builds
  • Check linting status
  • Compile TypeScript
  • Verify dependencies
  • Format code

How it works

It executes specific npm scripts for production, CI, or type-checking after verifying dependency freshness.

Inputs & outputs

You give it
Build task
You get back
Compiled project

When to use build

  • Running a full production build
  • Checking linting status
  • Compiling TypeScript
  • Verifying dependencies

About this skill

Build Skill

Use the following commands to build the Cosmos Explorer project. Choose the appropriate command based on the task.

Full Production Build

Run a complete production build (format check → lint → compile → strict compile → webpack prod → copy):

npm run build

CI Build (Faster)

Run a CI build that uses webpack dev mode for faster bundling:

npm run build:ci

TypeScript Compile Only

Run a TypeScript type-check without emitting output:

npm run compile

Strict TypeScript Compile

Run a strict null-checks compile on the subset of files in tsconfig.strict.json:

npm run compile:strict

Lint Only

Run ESLint across all .ts and .tsx files:

npm run lint

Format Check

Run Prettier to verify formatting without modifying files:

npm run format:check

Pre-Build: Check Dependencies

Before running any build command, check whether npm install needs to be run. Do this by comparing package.json and package-lock.json against the installed node_modules:

  1. Check if the node_modules directory exists. If it does not, run npm install.
  2. If node_modules exists, check whether package.json or package-lock.json have been modified more recently than node_modules. If so, run npm install.
# Check if node_modules is missing or outdated
if [ ! -d node_modules ] || [ package.json -nt node_modules ] || [ package-lock.json -nt node_modules ]; then
  npm install
fi

On Windows PowerShell:

if (-not (Test-Path node_modules) -or
    (Get-Item package.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime -or
    (Get-Item package-lock.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime) {
    npm install
}

Always run this check before proceeding with any build command.

Guidelines

  • When asked to simply "build", run npm run build for a full production build.
  • When asked for a quick or fast build, use npm run build:ci.
  • When asked to just check types, use npm run compile.
  • If the build fails, read the error output carefully. Common issues include:
    • TypeScript errors: Fix type errors shown in the npm run compile output.
    • Strict null-check errors: Fix strict errors shown in npm run compile:strict output.
    • Lint errors: Fix lint issues shown in npm run lint output.
    • Format errors: Run npm run format to auto-fix formatting, then retry the build.
  • New files must be added to tsconfig.strict.json so they compile under strict mode.

When not to use it

  • Running build without dependency check

Prerequisites

npm

Limitations

  • New files must be added to tsconfig.strict.json

How it compares

It enforces a pre-build dependency check to ensure the environment is up to date.

Compared to similar skills

build side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
build (this skill)04moReviewBeginner
turborepo-caching55moReviewIntermediate
turborepo612moReviewIntermediate
chrome-devtools417moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

turborepo-caching

wshobson

Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.

535

turborepo

vercel

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

61191

chrome-devtools

mrgoonie

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

41157

bullmq-specialist

davila7

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.

2595

nx-workspace-patterns

wshobson

Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.

589

pnpm-upgrade

openai

Keep pnpm current: run pnpm self-update/corepack prepare, align packageManager in package.json, and bump pnpm/action-setup + pinned pnpm versions in .github/workflows to the latest release. Use this when refreshing the pnpm toolchain manually or in automation.

211

Search skills

Search the agent skills registry