UI Production Builder

VerifiedSafe

Builds optimized production bundles for the trading platform UI with minification, code splitting, and chunk hashing. Supports staging builds, bundle analysis with visualizer, source maps, and a preview server. Helps ensure fast load times and stay within size budgets before deployment.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#ui-build#production-bundling#bundle-analysis#optimization

Recommended for

Automated summary

Builds an optimized production bundle for the trading platform UI, with integrated type checking and linting.

Strengths

  • Automates TypeScript validation and linting before the build.
  • Provides bundle analysis to identify large dependencies.
  • Enforces size budgets to ensure optimal performance.
  • Offers options for staging environments and preview.

Limitations

  • Specific to an existing build setup (npm, Vite/Rollup).
  • Does not handle build errors beyond pre-build checks.
  • Does not support other bundlers like Webpack without adaptation.
When to use it

When you need to generate a production-ready bundle for deployment with optimizations and size analysis.

When not to use it

For rapid development builds or if your project uses a non-standard build configuration.

Security analysis

Safe
Quality score90/100

This skill runs standard local build commands (npm run build, etc.) with no destructive or exfiltration actions. It does not involve network requests to external services or manipulation of sensitive data beyond what a typical build process entails.

No concerns found

How this analysis is made

Examples

Standard production build
/ui-build
Build with bundle analysis
/ui-build --analyze
Staging environment build
/ui-build --staging

name: ui-build description: Build production UI bundle with optimizations argument-hint: "[--staging|--analyze|--sourcemap]"

UI Production Builder

Build optimized production bundle for the trading platform UI.

Usage

  • /ui-build - Build for production
  • /ui-build --staging - Build for staging environment
  • /ui-build --analyze - Build with bundle analysis
  • /ui-build --sourcemap - Include source maps
  • /ui-build --preview - Build and start preview server

Build Outputs

services/ui/dist/
├── index.html
├── assets/
│   ├── index-[hash].js      # Main bundle
│   ├── index-[hash].css     # Styles
│   ├── vendor-[hash].js     # Vendor chunk
│   └── [chunk]-[hash].js    # Code-split chunks
└── favicon.ico

Instructions

When this skill is invoked:

  1. Parse arguments:

    • No args: npm run build (production)
    • --staging: npm run build:staging
    • --analyze: Add rollup-plugin-visualizer
    • --sourcemap: Enable source maps
    • --preview: Build then run preview
  2. Pre-build checks:

    • Run TypeScript check: npm run typecheck
    • Run linter: npm run lint
    • Check for environment variables
  3. Build:

    cd services/ui
    npm run build
    
  4. Display build results:

    UI Build Complete
    ═══════════════════════════════════════════════════════════
    
    Environment: production
    Build time:  12.4s
    
    Output: dist/
    ─────────────────────────────────────────────────────────
    index.html                    1.2 KB
    assets/index-a1b2c3.js      245.8 KB  (gzip: 78.2 KB)
    assets/index-d4e5f6.css      32.4 KB  (gzip: 6.8 KB)
    assets/vendor-g7h8i9.js     412.3 KB  (gzip: 132.1 KB)
    assets/charts-j0k1l2.js      89.5 KB  (gzip: 28.4 KB)
    ─────────────────────────────────────────────────────────
    Total:                      781.2 KB  (gzip: 245.5 KB)
    
    ✓ No unused exports detected
    ✓ All chunks within size budget
    
  5. For --analyze:

    • Generate bundle visualization
    • Open stats.html in browser
    • Show largest dependencies
    • Identify optimization opportunities
  6. For --preview:

    npm run preview
    
    • Serve built files locally
    • Test production build before deploy
  7. Build warnings to surface:

    • Large bundle sizes (>500KB)
    • Missing environment variables
    • Deprecated dependencies
    • TypeScript errors (build will fail)
  8. Size budgets:

    • Main bundle: <300KB (gzip <100KB)
    • Vendor bundle: <500KB (gzip <150KB)
    • Individual chunks: <100KB

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/ui-production-builder-mmbizkii/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/ui-production-builder-mmbizkii' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ui-production-builder-mmbizkii/download' --output '.skill-downloads/ui-production-builder-mmbizkii/SKILL.md.part' && mv '.skill-downloads/ui-production-builder-mmbizkii/SKILL.md.part' '.skill-downloads/ui-production-builder-mmbizkii/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/ui-production-builder-mmbizkii/SKILL.md' && test -s '.skill-downloads/ui-production-builder-mmbizkii/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ui-build' && cp -R '.skill-downloads/ui-production-builder-mmbizkii' '.claude/skills/ui-build'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/ui-production-builder-mmbizkii'

openskills read 'ui-production-builder-mmbizkii'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/ui-production-builder-mmbizkii/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills