build-pipeline
Project Build Pipeline
Execute a comprehensive build pipeline with fail-fast behavior for the Tetris project.
Pipeline Steps (6 stages)
- Dead Code Detection (
bun run knip) - Identify unused code, exports, and dependencies - Code Formatting (
bun run format) - Apply consistent code style via Biome - Linting (
bun run lint) - Perform code quality checks and import optimization - Type Checking (
bun run typecheck) - Validate TypeScript type safety - Testing (
bun test) - Execute all test suites (160+ tests) - Production Build (
bun run build) - Create optimized production bundle
Execution
# Execute full pipeline with fail-fast behavior
bun run knip && \
bun run format && \
bun run lint && \
bun run typecheck && \
bun test && \
bun run build
The pipeline uses && operator to ensure immediate termination upon any step failure.
Pipeline Rationale
- knip (first): Detect unused code early to reduce processing time
- format (second): Ensure consistent code style before quality checks
- lint (third): Check code quality on properly formatted code
- typecheck (fourth): Verify type safety after code structure validation
- test (fifth): Confirm functionality with comprehensive test suite
- build (last): Generate production bundle only when all gates pass
When This Skill Activates
- "Build the project"
- "Run all checks"
- "Prepare for production"
- "Validate code quality"
- "Execute the full pipeline"
- "Check if everything is ready to deploy"
More from sakataka/tetris-game2
i18n-completeness
Comprehensive i18n consistency check with dynamic pattern detection and hardcoded string analysis. Use when working with translations, localization, i18n keys, or when the user mentions translation issues, missing keys, or language support. Auto-triggers on phrases like "check translations", "i18n consistency", "localization issues", or "translation keys".
8tdd-workflow
Test-driven development guidance for Tetris game logic. Use when writing tests, fixing test failures, improving test coverage, or implementing game mechanics. Auto-triggers on phrases like "write a test", "test this function", "improve coverage", "fix failing tests", or "add game logic". Emphasizes Result<T,E> pattern and property-based testing with fast-check.
7typescript-strict
Enforce TypeScript strict mode practices and type safety in Tetris codebase. Use when writing game logic, handling errors, improving type safety, or fixing type errors. Auto-triggers on phrases like "fix type errors", "improve type safety", "handle this error", or "make this type-safe". Focuses on Result<T,E> pattern, proper type guards, and avoiding type assertions.
7react-component-design
Design React components following Tetris architecture guidelines. Use when creating new components, refactoring components, optimizing performance, or improving component structure. Auto-triggers on phrases like "create a component", "refactor this component", "optimize rendering", or "improve component design". Emphasizes component consolidation, unified patterns, and efficient hook usage.
6architecture-compliance
Verify Tetris architecture compliance with coding rules and design patterns. Use when reviewing code, implementing features, refactoring, or validating architectural decisions. Auto-triggers on phrases like "review this code", "check architecture", "is this correct?", "refactor this", or "implement feature". Checks for prohibited patterns (classes, enums, any types, hardcoded strings) and required patterns (functional programming, Result type, proper imports).
6