worker-scaffold

Generate worker project scaffolds with Temporal, Docker, and Coolify deployment configuration.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill worker-scaffold
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker-scaffold
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/worker-scaffold
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill worker-scaffold

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a systematic scaffold for new workers across Temporal, Docker, and Coolify deployments, ensuring a reproducible starting point for production-grade services.

Core Features & Use Cases

  • Scaffold a complete worker project structure with conventional directories and boilerplate files.
  • Configure Temporal task queues, Dockerization, and deployment via Coolify for quick production start.
  • Provide lifecycle management, monitoring, and multi-tenant considerations to simplify ops.

Quick Start

Invoke the worker-scaffold skill to generate a complete skeleton for a new worker domain and function.

Frequently Asked Questions about worker-scaffold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a Temporal worker project for Docker and Coolify deployment?

To scaffold a Temporal worker, this skill generates a complete project structure with conventional directories, Dockerization boilerplate, and Coolify deployment pipelines for immediate production startup.

What is included in a production-ready worker scaffold for Temporal?

A production-ready worker scaffold includes Temporal task queue configurations, Docker boilerplate, lifecycle management, monitoring hooks, multi-tenant guardrails, and clean separation of concerns.

Can I configure multi-tenant workflows and monitoring hooks when scaffolding a new worker?

Yes, you can configure multi-tenant workflows and monitoring hooks. The scaffold enforces deterministic rules and provides operational guardrails to simplify lifecycle management for new worker domains.

What's the best way to standardize new worker project structures across different domains?

The best way to standardize new worker structures is applying deterministic scaffolding rules that generate consistent directories, boilerplate files, and deployment pipelines for every new worker domain or function.

Does this worker scaffold require existing Coolify or Temporal environments to function?

The scaffold generates boilerplate to configure Temporal task queues and Coolify deployments. It creates the project structure and deployment configurations needed to connect to these environments.

When should I not use an automated worker scaffold for my infrastructure?

You should not use this automated worker scaffold if your project requires a non-Docker deployment strategy, does not use Temporal workflows, or needs a custom project structure outside conventional directory layouts.