/build
Build, compile, and package projects with intelligent error handling and optimization
> /plugin marketplace add Galaxy-Dawn/claude-scholar > /plugin install claude-scholar@claude-scholar
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/build
Context preview
What this command does when you run it.
Build, compile, and package projects with intelligent error handling and optimization
Command definition
build.mdname: build
description: "Build, compile, and package projects with intelligent error handling and optimization"
category: utility
complexity: enhanced
mcp-servers: [playwright]
personas: [devops-engineer]
/sc:build - Project Building and Packaging
Triggers
- Project compilation and packaging requests for different environments
- Build optimization and artifact generation needs
- Error debugging during build processes
- Deployment preparation and artifact packaging requirements
Usage
/sc:build [target] [--type dev|prod|test] [--clean] [--optimize] [--verbose]
Behavioral Flow
1. **Analyze**: Project structure, build configurations, and dependency manifests 2. **Validate**: Build environment, dependencies, and required toolchain components 3. **Execute**: Build process with real-time monitoring and error detection 4. **Optimize**: Build artifacts, apply optimizations, and minimize bundle sizes 5. **Package**: Generate deployment artifacts and comprehensive build reports
Key behaviors:
- Configuration-driven build orchestration with dependency validation
- Intelligent error analysis with actionable resolution guidance
- Environment-specific optimization (dev/prod/test configurations)
- Comprehensive build reporting with timing metrics and artifact analysis
MCP Integration
- **Playwright MCP**: Auto-activated for build validation and UI testing during builds
- **DevOps Engineer Persona**: Activated for build optimization and deployment preparation
- **Enhanced Capabilities**: Build pipeline integration, performance monitoring, artifact validation
Tool Coordination
- **Bash**: Build system execution and process management
- **Read**: Configuration analysis and manifest inspection
- **Grep**: Error parsing and build log analysis
- **Glob**: Artifact discovery and validation
- **Write**: Build reports and deployment documentation
Key Patterns
- **Environment Builds**: dev/prod/test → appropriate configuration and optimization
- **Error Analysis**: Build failures → diagnostic analysis and resolution guidance
- **Optimization**: Artifact analysis → size reduction and performance improvements
- **Validation**: Build verification → quality gates and deployment readiness
Examples
Standard Project Build
/sc:build
# Builds entire project using default configuration
# Generates artifacts and comprehensive build report
Production Optimization Build
/sc:build --type prod --clean --optimize
# Clean production build with advanced optimizations
# Minification, tree-shaking, and deployment preparation
Targeted Component Build
/sc:build frontend --verbose
# Builds specific project component with detailed output
# Real-time progress monitoring and diagnostic information
Development Build with Validation
/sc:build --type dev --validate
# Development build with Playwright validation
# UI testing and build verification integration
Boundaries
**Will:**
- Execute project build systems using existing configurations
- Provide comprehensive error analysis and optimization recommendations
- Generate deployment-ready artifacts with detailed reporting
**Will Not:**
- Modify build system configuration or create new build scripts
- Install missing build dependencies or development tools
- Execute deployment operations beyond artifact preparation
Read more
name: build description: "Build, compile, and package projects with intelligent error handling and optimization" category: utility complexity: enhanced mcp-servers: [playwright] personas: [devops-engineer]
/sc:build - Project Building and Packaging
Triggers
- Project compilation and packaging requests for different environments
- Build optimization and artifact generation needs
- Error debugging during build processes
- Deployment preparation and artifact packaging requirements
Usage
/sc:build [target] [--type dev|prod|test] [--clean] [--optimize] [--verbose]
Behavioral Flow
1. **Analyze**: Project structure, build configurations, and dependency manifests 2. **Validate**: Build environment, dependencies, and required toolchain components 3. **Execute**: Build process with real-time monitoring and error detection 4. **Optimize**: Build artifacts, apply optimizations, and minimize bundle sizes 5. **Package**: Generate deployment artifacts and comprehensive build reports
Key behaviors:
- Configuration-driven build orchestration with dependency validation
- Intelligent error analysis with actionable resolution guidance
- Environment-specific optimization (dev/prod/test configurations)
- Comprehensive build reporting with timing metrics and artifact analysis
MCP Integration
- **Playwright MCP**: Auto-activated for build validation and UI testing during builds
- **DevOps Engineer Persona**: Activated for build optimization and deployment preparation
- **Enhanced Capabilities**: Build pipeline integration, performance monitoring, artifact validation
Tool Coordination
- **Bash**: Build system execution and process management
- **Read**: Configuration analysis and manifest inspection
- **Grep**: Error parsing and build log analysis
- **Glob**: Artifact discovery and validation
- **Write**: Build reports and deployment documentation
Key Patterns
- **Environment Builds**: dev/prod/test → appropriate configuration and optimization
- **Error Analysis**: Build failures → diagnostic analysis and resolution guidance
- **Optimization**: Artifact analysis → size reduction and performance improvements
- **Validation**: Build verification → quality gates and deployment readiness
Examples
Standard Project Build
/sc:build # Builds entire project using default configuration # Generates artifacts and comprehensive build report
Production Optimization Build
/sc:build --type prod --clean --optimize # Clean production build with advanced optimizations # Minification, tree-shaking, and deployment preparation
Targeted Component Build
/sc:build frontend --verbose # Builds specific project component with detailed output # Real-time progress monitoring and diagnostic information
Development Build with Validation
/sc:build --type dev --validate # Development build with Playwright validation # UI testing and build verification integration
Boundaries
**Will:**
- Execute project build systems using existing configurations
- Provide comprehensive error analysis and optimization recommendations
- Generate deployment-ready artifacts with detailed reporting
**Will Not:**
- Modify build system configuration or create new build scripts
- Install missing build dependencies or development tools
- Execute deployment operations beyond artifact preparation
Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.
Repo: Galaxy-Dawn/claude-scholar
Other commands on claude-scholar.
- /analyze-results
Optional experiment line slug for report naming
Open command - /build-fix
Incrementally fix Python type and lint errors:
Open command - /checkpoint
Create or verify a checkpoint in your workflow.
Open command - /code-review
Comprehensive security and quality review of uncommitted changes:
Open command - /commit
Commit changes following Conventional Commits format (local only, no push).
Open command - /create_project
使用本地模板 ~/Code/template 而非 GitHub(覆盖 template_repo)
Open command

