Skill This
AI Skill Report Card

Configuring Deployment Standards

B+75·Apr 25, 2026·Source: Web
YAML
---
name: configuring-deployment-standards
description: Configures uniform deployment standards and hard configurations across TypeScript, JavaScript, Java, and HTML/CSS projects for Cloudflare Workers, D1, and other tech stacks. Use when setting up new projects or standardizing existing deployments.
---

# Configuring Deployment Standards
Quick Start15 / 15

Create .deploy/ directory with standard configs:

Bash
mkdir .deploy
cd .deploy

wrangler.toml (Cloudflare Workers):

TOML
name = "{{project-name}}"
main = "src/index.ts"
compatibility_date = "2024-01-15"
node_compat = true

[env.production]
name = "{{project-name}}-prod"

[env.staging] 
name = "{{project-name}}-staging"

[[d1_databases]]
binding = "DB"
database_name = "{{project-name}}-db"
database_id = "{{database-id}}"
Recommendation▾
Add concrete input/output examples showing actual project setup transformation - currently examples show final code but not the before/after process
Workflow13 / 15

1. Project Structure Setup

project/
├── .deploy/
│   ├── wrangler.toml
│   ├── docker-compose.yml
│   └── deploy.sh
├── .config/
│   ├── eslint.config.js
│   ├── prettier.config.js
│   └── tsconfig.json
└── scripts/
    ├── build.sh
    └── test.sh

2. Standard Configuration Files

ESLint Config (.config/eslint.config.js):

JavaScript
export default [
  {
    ignores: ["dist/", "node_modules/", ".wrangler/"]
  },
  {
    files: ["**/*.{js,ts,jsx,tsx}"],
    rules: {
      "no-console": "error",
      "prefer-const": "error",
      "no-var": "error"
    }
  }
];

Prettier Config (.config/prettier.config.js):

JavaScript
export default {
  semi: true,
  singleQuote: true,
  tabWidth: 2,
  trailingComma: 'es5',
  printWidth: 100
};

TypeScript Config (.config/tsconfig.json):

JSON
{
  "compilerOptions": {
    "target": "ES2022",
    "module": "ESNext",
    "moduleResolution": "bundler",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "outDir": "./dist",
    "rootDir": "./src"
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "dist", ".wrangler"]
}

3. Deployment Scripts

Build Script (scripts/build.sh):

Bash
#!/bin/bash
set -e

echo "🔨 Building project..."
npm run lint
npm run typecheck
npm run build

echo "✅ Build complete"

Deploy Script (.deploy/deploy.sh):

Bash
#!/bin/bash
set -e

ENV=${1:-staging}

echo "🚀 Deploying to $ENV..."

case $ENV in
  "production")
    wrangler deploy --env production
    ;;
  "staging")
    wrangler deploy --env staging
    ;;
  *)
    echo "❌ Invalid environment. Use 'staging' or 'production'"
    exit 1
    ;;
esac

echo "✅ Deployment to $ENV complete"

4. Package.json Standards

JSON
{
  "scripts": {
    "dev": "wrangler dev",
    "build": "tsc && esbuild src/index.ts --bundle --outfile=dist/worker.js --format=esm",
    "deploy:staging": "./.deploy/deploy.sh staging",
    "deploy:prod": "./.deploy/deploy.sh production",
    "lint": "eslint . --config .config/eslint.config.js",
    "lint:fix": "eslint . --config .config/eslint.config.js --fix",
    "format": "prettier --write . --config .config/prettier.config.js",
    "typecheck": "tsc --noEmit"
  }
}
Recommendation▾
Reduce redundancy between Quick Start and Workflow sections - they both show configuration files with similar content
Examples15 / 20

Example 1: New Cloudflare Worker Project Input: TypeScript API with D1 database Output:

TypeScript
// src/index.ts
export interface Env {
  DB: D1Database;
}

export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const { pathname } = new URL(request.url);
    
    if (pathname === '/health') {
      return new Response('OK', { status: 200 });
    }
    
    return new Response('Not Found', { status: 404 });
  },
};

Example 2: Java Spring Boot Standards Input: Microservice deployment Output:

YAML
# .deploy/docker-compose.yml
version: '3.8'
services:
  app:
    build: .
    ports:
      - "8080:8080"
    environment:
      - SPRING_PROFILES_ACTIVE=production
      - DATABASE_URL=${DATABASE_URL}
Recommendation▾
Include specific error scenarios and troubleshooting steps, such as common wrangler deployment failures or configuration conflicts
Best Practices
  • Environment Variables: Store in .env.example template, never commit actual .env
  • Database Migrations: Include in deployment pipeline before app deployment
  • Health Checks: Always include /health endpoint returning 200 OK
  • Error Handling: Use structured logging with consistent error formats
  • Versioning: Tag releases with semantic versioning
  • Rollback Strategy: Keep previous deployment artifacts for quick rollback
Common Pitfalls
  • Don't mix development and production configurations in same file
  • Don't deploy without running tests and linting first
  • Don't hardcode environment-specific values
  • Don't skip database migration validation
  • Don't deploy on Friday afternoons without monitoring plan
  • Avoid custom deployment scripts without error handling
  • Never commit secrets or API keys to repository

Progress Checklist:

  • Create .deploy/ and .config/ directories
  • Set up standard configuration files
  • Configure deployment scripts with error handling
  • Test deployment pipeline in staging
  • Document environment variables
  • Set up monitoring and alerting
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
15/15
Workflow
13/15
Examples
15/20
Completeness
17/20
Format
15/15
Conciseness
12/15
Save to My Skills